Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Upgrade from 2.0.5 to 2.2 - Runtime Error

web-app

We're getting the following error while trying to upgrade our system.

Server Error in '/' 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>


We can't figure out why the error is not more specific and only refers to the root.  We've set up the Web.config file as per the installation instructions and have run the appropriate script on our SQL database.  We're doing a manual installation.

We're using SQL Server 2005, IIS 6.0 as our web server, and Windows 2003 as our operating system.

We've already tried setting the mode withing the <customErrors> tag to "No".

We must be missing some other configuration in the Web.config file.  The only other changes we've made to this file are the connection strings, authentication mode, and authentication cookie name.

mlamotteo
· 1
mlamotteo
Replies (5)
helpful
0
not helpful

I suspect the error is to do with the database connection strings in the web.config file.

To be sure set CustomErrors to Off in the web.config file.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful



We tried that exhaustively with no luck.  Also tried clearing the cache.  The DB connection to the existing DB is working fine. 

Any other thoughts or suggestions?

thanks


michaelf
· 1
michaelf
helpful
0
not helpful

Did you set customErrors to off in the web.config file?

Do you get the same error?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Yes.  Does it matter that I'm doing this upgrade from my desktop, not the webserver itself?


michaelf
· 1
michaelf
helpful
0
not helpful

Not sure I understand you. Are you saying that you are amending the web.config file on your desktop? You should do it on the server.


Saar Cohen
· 5000
Saar Cohen