MS SQL Connection

[gper]

I have created an SQL Database and everything seems ok.
But when i press on the DBadmin i get the following report:

========================================

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>
=========================

Does anybody had the same problem or any solution ?

 

[jaytee]

Which OS version and edition are you using?

 

[gper]

OS

Windows 2003 Server,
with
SQL Server & Service Pack 3

 

[shwonder]

If somebody get the same error message, please, read it carefully. First part of it tells that some error was occured on server but it won't be shown due to the currect security model restrictions. Second part of it tells how to change this model or to login on server and try to get error message locally.
Please, read carefully. It is standard ASP.NET error message.

In case above It was the problem with permissions on folders. psaserv and psacln should have read and execute access to the folder.