I have a working site on a local development workstation (XP SP2) pointing to a MS-SQL Server via IP and Port address to our DEV SQL server. The site works fine in this configuration.
I now want to move the site to the DEV Web Server to continue development (Multiple developers will do different tasks at different time). When I copy the website folder to the DEV Web Server, it complains that FrontPage.lnk is missing. So I have installed FrontPage Extensions on the Web Server (2003 Enterprise SP2) thinking that would fix the problem.
I continue to get the horrid customErrors message, no matter what I set the key to. That would indicate to me that there is some other issue that bubbles down to this error message...
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>
|
Here is the section from the Connection String down to and including the customErrors section...I don't see anything wrong with it...
Web.Config File:
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<!--<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />-->
<!-- Connection String for SQL Server 2000/2005 -->
<add name="SiteSqlServer" connectionString="Data Source=10.1.1.115,1433;Initial Catalog=AMCON_DNN;User ID=[not provided];Password=[not provided];" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules >
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/-->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
<add key="SiteSqlServer" value="Data Source=10.1.1.115,1433;Initial Catalog=AMCON_DNN;User ID=[not provided];Password=[not provided]" />
<!-- balance omitted for space – No editing done here -->
</appSettings>
<system.codedom>
<compilers>
<compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" extension=".VB" />
</compilers>
</system.codedom>
<!-- The system.webServer section is required for IIS7 compatability It is ignored by IIS6-->
<system.web>
<!-- Ensure validationkey is not set to AutoGenerate,IsolateApps so it correctly supports webfarms -->
<machineKey validationKey="A43D0607E8337B08CE0D5803991CA6F1382FAED0" decryptionKey="76100F1A091484511BDFDD5968AC2631DBC13C227DAC971C" decryption="3DES" validation="SHA1" />
<!-- HttpModules for Common Functionality -->
<httpModules>
<!--omitted for space – No editing done here -->
</httpModules>
<httpHandlers>
<!--omitted for space – No editing done here -->
</httpHandlers>
<!-- set code access security trust level - this is generally set in the machine.config
<trust level="Medium" originUrl=".*" />
-->
<!-- set debugmode to false for running application -->
<compilation debug="true" strict="false">
<!--omitted for space – No editing done here -->
</compilation>
<!-- permits errors to be displayed for remote clients -->
<!-- <strong>This appears to be correct.</strong> . . -->
<customErrors mode="Off" />
<!-- forms or Windows authentication -->
<authentication mode="forms">
<forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />
</authentication>
This web.config file was copied from the site that works. No matter what setting is used on the customErrors, the site will not display. I cannot go to the Install page either…Same issue…
Any Ideas?