Solved

Exchange 2007 update caused .net problems

Posted on 2009-04-13
9
964 Views
Last Modified: 2013-11-07
Recently It was brought to my attention that my Outlook 2007 users could not schedule Out-of-Office information. I noticed that I am getting enormous amount of ASP.net 2.0 errors(Event ID: 1309). While we don't use OWA at this time, I noticed that it is no longer functioning as well. Other than those issues, Exchange seems to be running fine. I found an article stating that some updates can cause this. The article pointed to KB960384 as a fix. I ran updates to include the latest Rollup and KB960384-x64 and I still have no web functionality nor did it resolve the issue with my Outllook 2007 clients. Any Ideas on what I must do to resolve this issue?
Log Name:      Application

Source:        ASP.NET 2.0.50727.0

Date:          4/13/2009 12:27:04 PM

Event ID:      1309

Task Category: Web Event

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      EX1.xxxxxx.local

Description:

Event code: 3005 

Event message: An unhandled exception has occurred. 

Event time: 4/13/2009 12:27:04 PM 

Event time (UTC): 4/13/2009 7:27:04 PM 

Event ID: fb81200d8e3745b19e50152f8cb4cc2a 

Event sequence: 1 

Event occurrence: 1 

Event detail code: 0 

 

Application information: 

    Application domain: /LM/W3SVC/1/ROOT/Autodiscover-11064-128841244246453121 

    Trust level: Full 

    Application Virtual Path: /Autodiscover 

    Application Path: D:\Program Files\Microsoft\Exchange Server\ClientAccess\Autodiscover\ 

    Machine name: EX1 

 

Process information: 

    Process ID: 2912 

    Process name: w3wp.exe 

    Account name: NT AUTHORITY\SYSTEM 

 

Exception information: 

    Exception type: InvalidOperationException 

    Exception message: Failed to map the path '/'. 

 

Request information: 

    Request URL: https://EX1.xxxxxx.local:443/Autodiscover/Autodiscover.xml 

    Request path: /Autodiscover/Autodiscover.xml 

    User host address: 10.0.0.60 

    User:  

    Is authenticated: False 

    Authentication Type:  

    Thread account name: NT AUTHORITY\SYSTEM 

 

Thread information: 

    Thread ID: 11 

    Thread account name: NT AUTHORITY\SYSTEM 

    Is impersonating: False 

    Stack trace:    at System.Web.Configuration.ProcessHostMapPath.MapPathCaching(String siteID, VirtualPath path)

   at System.Web.Configuration.ProcessHostMapPath.System.Web.Configuration.IConfigMapPath2.MapPath(String siteID, VirtualPath path)

   at System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull)

   at System.Web.CachedPathData.GetConfigPathData(String configPath)

   at System.Web.CachedPathData.GetConfigPathData(String configPath)

   at System.Web.Configuration.RuntimeConfig.GetConfig(VirtualPath path)

   at System.Web.Configuration.RuntimeConfig.GetLKGRuntimeConfig(VirtualPath path)

 

 

Custom event details: 
 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ASP.NET 2.0.50727.0" />

    <EventID Qualifiers="32768">1309</EventID>

    <Level>3</Level>

    <Task>3</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2009-04-13T19:27:04.000Z" />

    <EventRecordID>452237</EventRecordID>

    <Channel>Application</Channel>

    <Computer>EX1.xxxxxx.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>3005</Data>

    <Data>An unhandled exception has occurred.</Data>

    <Data>4/13/2009 12:27:04 PM</Data>

    <Data>4/13/2009 7:27:04 PM</Data>

    <Data>fb81200d8e3745b19e50152f8cb4cc2a</Data>

    <Data>1</Data>

    <Data>1</Data>

    <Data>0</Data>

    <Data>/LM/W3SVC/1/ROOT/Autodiscover-11064-128841244246453121</Data>

    <Data>Full</Data>

    <Data>/Autodiscover</Data>

    <Data>D:\Program Files\Microsoft\Exchange Server\ClientAccess\Autodiscover\</Data>

    <Data>EX1</Data>

    <Data>

    </Data>

    <Data>2912</Data>

    <Data>w3wp.exe</Data>

    <Data>NT AUTHORITY\SYSTEM</Data>

    <Data>InvalidOperationException</Data>

    <Data>Failed to map the path '/'.</Data>

    <Data>https://EX1.xxxxxx.local:443/Autodiscover/Autodiscover.xml</Data>

    <Data>/Autodiscover/Autodiscover.xml</Data>

    <Data>10.0.0.60</Data>

    <Data>

    </Data>

    <Data>False</Data>

    <Data>

    </Data>

    <Data>NT AUTHORITY\SYSTEM</Data>

    <Data>11</Data>

    <Data>NT AUTHORITY\SYSTEM</Data>

    <Data>False</Data>

    <Data>   at System.Web.Configuration.ProcessHostMapPath.MapPathCaching(String siteID, VirtualPath path)

   at System.Web.Configuration.ProcessHostMapPath.System.Web.Configuration.IConfigMapPath2.MapPath(String siteID, VirtualPath path)

   at System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull)

   at System.Web.CachedPathData.GetConfigPathData(String configPath)

   at System.Web.CachedPathData.GetConfigPathData(String configPath)

   at System.Web.Configuration.RuntimeConfig.GetConfig(VirtualPath path)

   at System.Web.Configuration.RuntimeConfig.GetLKGRuntimeConfig(VirtualPath path)

</Data>

  </EventData>

</Event>

Open in new window

0
Comment
Question by:pkwillis
  • 5
  • 4
9 Comments
 
LVL 65

Assisted Solution

by:Mestha
Mestha earned 500 total points
ID: 24133841
Start by repair of asp.net:

"%windir%\Microsoft.NET\Framework\2.0.50727.0\aspnet_regiis.exe" -i

(The version number might be different, so check the location carefully).

Simon.
0
 

Author Comment

by:pkwillis
ID: 24150276
Thank you for the response Simon,

I ran the repair of asp.net on my Exchange Server 2007 using the following command:
"%windir%\Microsoft.NET\Framework\V2.0.50727\aspnet_regiis.exe" -i
I recieve the following message:
The error indicates that IIS is not installed on the machine. Please install IIS before using this tool.
Finished installing ASP.NET <2.0.50727>.

Not sure why the message. IIS is installed, maybe I need to install "Management Service?" Any help would be greatly appreciated


0
 
LVL 65

Assisted Solution

by:Mestha
Mestha earned 500 total points
ID: 24150756
Did you check the version number was correct? You need to confirm the correct path.

Checking again, the path is actually

"C:Windows\Microsoft.Net\Framework64\v2.0.50727\aspnet_regiis.exe" -i

Simon.
0
 

Author Comment

by:pkwillis
ID: 24152055
Yes, if you notice the path is slightly different from the one you posted.

Do you think I need to install additional Web Services?
0
Do email signature updates give you a headache?

Do you feel like you are constantly making changes to email signatures? Are the images not formatting how you want them to? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today.

 

Author Comment

by:pkwillis
ID: 24152085
I should mention that there are multiple directories for various versions of .net. The error I am getting specifically points to ASP.NET 2.0, so I ran the aspnet_regiis.exe from the v2.0.50727 directory. Do you think I should run this from one of the other directories?
0
 
LVL 65

Assisted Solution

by:Mestha
Mestha earned 500 total points
ID: 24156820
You need to run it for whichever version of asp.net 2.0 that you have installed. That is why I said to check the version number. Exchange 2007 is an asp.net 2.0 application, so running it for other versions may not apply.

Simon.
0
 

Author Comment

by:pkwillis
ID: 24168241
Exchange is running on asp.net 2.0. When I run the "asp.net_regiis.exe -i" it reports:
The error indicates that IIS is not installed on the machine. Please install IIS before using this tool.
Finished installing ASP.NET <2.0.50727>.

Any other ideas?
0
 
LVL 65

Accepted Solution

by:
Mestha earned 500 total points
ID: 24170675
Reinstall asp.net from the latest build from Microsoft maybe?

Simon.
0
 

Author Closing Comment

by:pkwillis
ID: 31569641
Ended up reinstalling CAS on Exchange Server.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Easy CSR creation in Exchange 2007,2010 and 2013
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now