ASP.Net does not work after IIS uninstall/reinstall

[Guest]

Due to real ds mistake on my part IIS was inadvertently uninstalled on my web server.

After reinstalling IIS, I have been able to get everything back up except ASP.net.

Any page served using ASP.net returns the generic Runtime Error page....

Server Error in '/Qmcfm' Application.
------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings.... etc

I can't get the details of the error to display no matter what I set <customErrors mode> to in my web.config file.

Another section of the web site uses ASP which seems to be running fine.

I use the aspnet_regiis tool with the -i switch to register the Framework and it did not fix the problem

I tried to reinstall the framework from my MSDN Library but the installer tells me that it cannot complete the install because the framework was installed with the Operating System.

I reinstalled the Operating System (2003) and it remains inop

Any help would be greatly appreciated. I have posted the <system.web> portion of my web.config file, but I don't think it's ever getting here

Thanks in advance

Joh

------------------------------------------------

<system.web><!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to insert debugging symbols (.pdb information)
into the compiled page. Because this creates a larger file that executes
more slowly, you should set this value to true only when debugging and to
false at all other times. For more information, refer to the documentation about
debugging ASP.NET files.
--><compilation defaultLanguage="vb" debug="true" /><!-- CUSTOM ERROR MESSAGES
Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.
Add <error> tags for each of the errors you want to handle.
--><customErrors mode="Off" /><!-- AUTHENTICATION
This section sets the authentication policies of the application. Possible modes are "Windows",
"Forms", "Passport" and "None"
--><authentication mode="Windows" /><!-- AUTHORIZATION
This section sets the authorization policies of the application. You can allow or deny access
to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous
(unauthenticated) users.
--><authorization><allow users="?" /><!-- Allow all users --><!-- <allow users="john"/>
roles="[comma separated list of roles]"/><deny users="?"/>
roles="[comma separated list of roles]"/> --></authorization><!-- APPLICATION-LEVEL TRACE LOGGING
Application-level tracing enables trace log output for every page within an application.
Set trace enabled="true" to enable application trace logging. If pageOutput="true", the
trace information will be displayed at the bottom of each page. Otherwise, you can view the
application trace log by browsing the "trace.axd" page from your web application
root.
--><trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" /><!-- SESSION STATE SETTINGS
By default ASP.NET uses cookies to identify which requests belong to a particular session.
If cookies are not available, a session can be tracked by adding a session identifier to the URL.
To disable cookies, set sessionState cookieless="true".
--><sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/><!-- GLOBALIZATION
This section sets the globalization settings of the application.
--><globalization requestEncoding="utf-8" responseEncoding="utf-8" /><trust level="Full" originUrl="" /></system.web>

 

[Scott Allen]

Find aspnet_regiis on your machine (typically
%systemdir%\microsoft.net\framework\v1.1.4322) and run

aspnet_regiis - i

This will install all the scriptmaps and client files for ASP.NET to
execute.

HTH,

--
Scott
http://www.OdeToCode.com

Due to real ds mistake on my part IIS was inadvertently uninstalled on my web server.

After reinstalling IIS, I have been able to get everything back up except ASP.net.

Any page served using ASP.net returns the generic Runtime Error page....

Server Error in '/Qmcfm' Application.
------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings.... etc.

I can't get the details of the error to display no matter what I set <customErrors mode> to in my web.config file.

Another section of the web site uses ASP which seems to be running fine.

I use the aspnet_regiis tool with the -i switch to register the Framework and it did not fix the problem.

I tried to reinstall the framework from my MSDN Library but the installer tells me that it cannot complete the install because the framework was installed with the Operating System.

I reinstalled the Operating System (2003) and it remains inop.

Any help would be greatly appreciated. I have posted the <system.web> portion of my web.config file, but I don't think it's ever getting here.

Thanks in advance,

John


-------------------------------------------------

<system.web><!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to insert debugging symbols (.pdb information)
into the compiled page. Because this creates a larger file that executes
more slowly, you should set this value to true only when debugging and to
false at all other times. For more information, refer to the documentation about
debugging ASP.NET files.
--><compilation defaultLanguage="vb" debug="true" /><!-- CUSTOM ERROR MESSAGES
Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.
Add <error> tags for each of the errors you want to handle.
--><customErrors mode="Off" /><!-- AUTHENTICATION
This section sets the authentication policies of the application. Possible modes are "Windows",
"Forms", "Passport" and "None"
--><authentication mode="Windows" /><!-- AUTHORIZATION
This section sets the authorization policies of the application. You can allow or deny access
to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous
(unauthenticated) users.
--><authorization><allow users="?" /><!-- Allow all users --><!-- <allow users="john"/>
roles="[comma separated list of roles]"/><deny users="?"/>
roles="[comma separated list of roles]"/> --></authorization><!-- APPLICATION-LEVEL TRACE LOGGING
Application-level tracing enables trace log output for every page within an application.
Set trace enabled="true" to enable application trace logging. If pageOutput="true", the
trace information will be displayed at the bottom of each page. Otherwise, you can view the
application trace log by browsing the "trace.axd" page from your web application
root.
--><trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" /><!-- SESSION STATE SETTINGS
By default ASP.NET uses cookies to identify which requests belong to a particular session.
If cookies are not available, a session can be tracked by adding a session identifier to the URL.
To disable cookies, set sessionState cookieless="true".
--><sessionState
mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424"
sqlConnectionString="data source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="20"
/><!-- GLOBALIZATION
This section sets the globalization settings of the application.
--><globalization requestEncoding="utf-8" responseEncoding="utf-8" /><trust level="Full" originUrl="" /></system.web>

 

[Guest]

Scott

Thanks for the suggestion. As noted in my original message I ran aspn_regiis with the -i switch and it did not fix the problem. Are there any other switches which might be useful in troubleshooting or fixing this problem

Joh


On Tue, 25 May 2004 10:11am, "Scott Allen" wrote

Find aspnet_regiis on your machine (typically
%systemdir%\microsoft.net\framework\v1.1.4322) and run

 

[Scott Allen]

Ooops, big apology for not paying attention, John.

I've seen this happen once when there were security problems with the
ASPNET account, but that was a Win2K server. Still it might be worth a
shot to enable security logging from administrative tools -> local
security policy -> local policies -> audit policies, and from there
enable failure logging for logon and object access events. this may
turn up some more clues in the Security event log.

Apologies again for the confusion. Let me know if you find anything in
the logs.

--s

 

[Guest]

Scott

That is what I was looking for but didn't think to ask. I looked at the logs but didn't know how to make them log anything when I tried to run the app. Thanks!

Unfortunately I am off to the mainland for a week and won't be able to check it oun until I get back on Monday

Thanks again

Joh


----- Scott Allen wrote: ----

Ooops, big apology for not paying attention, John.

I've seen this happen once when there were security problems with th
ASPNET account, but that was a Win2K server. Still it might be worth
shot to enable security logging from administrative tools -> loca
security policy -> local policies -> audit policies, and from ther
enable failure logging for logon and object access events. this ma
turn up some more clues in the Security event log

Apologies again for the confusion. Let me know if you find anything i
the logs.

--

On Tue, 25 May 2004 12:36:06 -0700, "johnbdh

Scott

-
Scot
http://www.OdeToCode.com