7.5 SP3 New Server - Runtime Error on Web Page

[Former Member]

Hi experts

I have added a new web server to an existing BPC installation.

The environment is load-balanced, 7.5 SP3, built on windows server 2003 SP2, with SQL 2008 SP1

I used the prerequisites:

Xceed v6.5

Antixscript v3

However, when I try to open the /osoft page directly on the new server, I see the error shown at the bottom of this page.

I checked the DLLs against those on the 2 working servers, and they are the same.

I have copied the antixscript dll from system32 to websvr\bin, as I have seen similar problems before and this has resolved it.

Unfortunately, it hasn't worked this time.

I have also checked that I can log my PC (windows 7, IE8) into either of the existing web servers, and they work fine

I have also opened the web site directly on the new server and that works fine (although it offers nothing but Web and Admin, as Excel is not installed)

I really need to get this server up for user testing first thing in the morning (UK time)

Does anyone have any suggestions?

Thanks

ERROR DETAILS:

-

---

Server Error in '/OSoft' Application.

-

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>

<system.web>

<customErrors mode="Off"/>

</system.web>

</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>

<system.web>

<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>

</system.web>

</configuration>

[Former Member]

Please guys.

I'm getting desperate now.

I need to get this server online, but I can't get past this.

Any suggestions please?

Thanks

[Former Member]

Quick update:

I'm removing BPC and reinstalling, as the issue definitely lies within BPC and/or its associated Web Site.

I know this as I am able to successfully connect from a client PC to to Reporting Services website.

If anyone has any suggestions, now would be a great time to make them known.

Thanks again