Hi there,

I installed a testing/developing environment (1) and therefor used a backup of the SQL database of the working environment (2). I deployed everything, created new connections and so on. Nearly everything works fine except one thing:

When creating a web report, the Web Client on machine 1 tries to connect to machine 2. But on machine 2 the web reports client was installed once but uninstalled later so there's an error showing up: "This website cannot be displayed." (I don't know the exact translation since it's in german) So the question is:

Where do I specify the server to be used when creating a web report? Without rebuilding/reinstalling the whole application?

Thanks in advance.

You do that within Deployments.

You can set the Path within the Dependencies area for the Portal.

Quote: Originally posted by Raul A. Chavez You do that within Deployments. You can set the Path within the Dependencies area for the Portal.

In the Application Architect on the Deployment Explorer I double clicked on slxwebrpt and set the following values:

[B]IIS Target Settings[/B]
Server: name of test machine
Base Directory: Same as defined in IIS
Port: 3334 (like suggested)
App Pool: SLX Web Reporting

A little further on advanced options:
checked 'Inherit from Target'
and added the following web dependency: Test - http://servername.domain:3334/slxwebrpt

After that I deployed the web report portal but nothing changed.

Besides that: Is it necessary to install the extended features in order to get the reports?

You add that dependency to the SLX Client Portal, not the Reporting Portal.

After you make the change, you have to redeploy the SLX Client Portal.

Okay sorry, my bad.

When I checked the Web Dependencies on the SLXClient Deployment there was one entry pointing to the working machine. I changed it to the correct server, deployed it once again, restarted the IIS and cleared the cache of the browser and now it's pointing to the correct server, but I get an internal server error instead.

I'll try to figure out what else went wrong. And If I don't find something I'll open another thread at another time. For today I'm done. I've been long enough at work, yet

Thanks a lot, especially for the fast and accurate help!