- Remove From My Forums
-
Question
-
We run Remote Desktop Services 2016 and have noticed some warnings in the event viewer of our Gateway Web Server.
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 3/31/2019 3:17:01 PM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/31/2019 3:17:01 PM
Event time (UTC): 3/31/2019 7:17:01 PM
Event ID: e81617fac6bc42abb32fa7b69388da07
Event sequence: 252
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/RDWeb/Pages-1-131981716874383622
Trust level: Full
Application Virtual Path: /RDWeb/Pages
Application Path: C:WindowsWebRDWebPages
Machine name:
Process information:
Process ID: 2568
Process name: w3wp.exe
Account name: IIS APPPOOLRDWebAccess
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Request information:
Request URL: :443/RDWeb/Pages/en-US/Default.aspx
Request path: /RDWeb/Pages/en-US/Default.aspx
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOLRDWebAccess
Thread information:
Thread ID: 56
Thread account name: IIS APPPOOLRDWebAccess
Is impersonating: False
Stack trace: at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext
objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Custom event details:Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»ASP.NET 4.0.30319.0″ />
<EventID Qualifiers=»32768″>1309</EventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2019-03-31T19:17:01.823012500Z» />
<EventRecordID>54382</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>3005</Data>
<Data>An unhandled exception has occurred.</Data>
<Data>3/31/2019 3:17:01 PM</Data>
<Data>3/31/2019 7:17:01 PM</Data>
<Data>e81617fac6bc42abb32fa7b69388da07</Data>
<Data>252</Data>
<Data>17</Data>
<Data>0</Data>
<Data>/LM/W3SVC/1/ROOT/RDWeb/Pages-1-131981716874383622</Data>
<Data>Full</Data>
<Data>/RDWeb/Pages</Data>
<Data>C:WindowsWebRDWebPages</Data>
<Data></Data>
<Data>
</Data>
<Data>2568</Data>
<Data>w3wp.exe</Data>
<Data>IIS APPPOOLRDWebAccess</Data>
<Data>NullReferenceException</Data>
<Data>Object reference not set to an instance of an object.
at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()</Data>
<Data>/RDWeb/Pages/en-US/Default.aspx</Data>
<Data>/RDWeb/Pages/en-US/Default.aspx</Data>
<Data></Data>
<Data>
</Data>
<Data>False</Data>
<Data>
</Data>
<Data>IIS APPPOOLRDWebAccess</Data>
<Data>56</Data>
<Data>IIS APPPOOLRDWebAccess</Data>
<Data>False</Data>
<Data> at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext
objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
</Data>
</EventData>
</Event>
Hi,
We run Remote Desktop Services 2012 R2 and have noticed some warnings in the event viewer of our Gateway Web Server.
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 11/09/2017 13:12:29 Event time (UTC): 11/09/2017 12:12:29 Event ID: a2d59adf5e0143b8bf23007e848b51b3 Event sequence: 1073 Event occurrence: 3 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT/RDWeb/Feed-2-131495975366454069 Trust level: Full Application Virtual Path: /RDWeb/Feed Application Path: C:WindowsWebRDWebFeed Machine name: HQRD-GWY-WEB01 Process information: Process ID: 948 Process name: w3wp.exe Account name: IIS APPPOOLRDWebAccess Exception information: Exception type: NullReferenceException Exception message: Object reference not set to an instance of an object. at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.PrepareRdpFile(String& rdp_contents, String fileExtension, String ts_name, String alias, String& rdp_file_url, String& rdp_file_name, DateTime requestTime) at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.ProcessPublishedApp(String alias, String name, String resourceFile, String fileExtension, Byte[] iconContents, UInt32 pceIconSize, Int32 resourceType, FileExtensionInfo[] fileAssociations, String[] folderNames, String securityDescriptor, ArrayList& apps, DateTime requestTime, UInt64 lastUpdateTime) at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.GetFreshApps(DateTime requestTime) at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.OnCacheItemRemoved(String key, Object value, CacheItemRemovedReason removedReason) at System.Web.Caching.CacheEntry.CallCacheItemRemovedCallback(CacheItemRemovedCallback callback, CacheItemRemovedReason reason) Request information: Request URL: Request path: User host address: User: Is authenticated: False Authentication Type: Thread account name: IIS APPPOOLRDWebAccess Thread information: Thread ID: 15 Thread account name: IIS APPPOOLRDWebAccess Is impersonating: False Stack trace: at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.PrepareRdpFile(String& rdp_contents, String fileExtension, String ts_name, String alias, String& rdp_file_url, String& rdp_file_name, DateTime requestTime) at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.ProcessPublishedApp(String alias, String name, String resourceFile, String fileExtension, Byte[] iconContents, UInt32 pceIconSize, Int32 resourceType, FileExtensionInfo[] fileAssociations, String[] folderNames, String securityDescriptor, ArrayList& apps, DateTime requestTime, UInt64 lastUpdateTime) at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.GetFreshApps(DateTime requestTime) at Microsoft.TerminalServices.Publishing.Portal.RWSCPUBAccessor.OnCacheItemRemoved(String key, Object value, CacheItemRemovedReason removedReason) at System.Web.Caching.CacheEntry.CallCacheItemRemovedCallback(CacheItemRemovedCallback callback, CacheItemRemovedReason reason) Custom event details:
Has anyone seen these errors before? They seem to have been cropping up every few hours. We’re investigating them now as over the past 2 days we’ve had users not be able to log in to our RDS Gateway Webpage with the error message of «The Username and
Password are not valid (or similar)». We’ve been able resolve the issue in both instances first by restoring the server from a back up and second by removing and then re-joining the server to our domain. We’re really conscious of stopping this happening
again. Does anyone have any advice on troubleshooting this issue? Are the error message and the symptoms related?
Note:
I have found some information regarding ASPxGridView.EnableRowsCache and setting it to false. This can be found
here.
Could this be related? Does anyone know where i can find this setting in order to test it as a fix?
Any assistance would be greatly appreciated.
-
Moved by
Monday, September 11, 2017 2:32 PM
I was helping a good friend of mine recently with his Exchange 2013 server. When he logged into Outlook Web App he would get the “Something went wrong” internal server error.
Unfortunately, this is an incredibly generic error that can be caused by a variety of different problems. We decided to hit the Event Logs. Almost instantly we ran across several occurrences of this error.
ASP.NET Event ID 1309 Event Code 3005 Event code: 3005 Event message: An unhandled exception has occurred. Event time: 6/1/2015 7:00:00 PM Event time (UTC): 6/1/2015 11:00:00 PM Event ID: 4d1bb9b639774fd689f5b1eeec309375 Event sequence: 2 Event occurrence: 1 Event detail code: 0
Sadly, ASP.NET Event ID 1309 is a very generic message. In fact, Event Code 3005 could be caused by any number of possibilities. Ruling the Event Code out we examined the rest of the error. We quickly found our answer in the Exception Message. I’ve highlighted the section below.
Tip: Exchange MVP Jeff Guillet identifies another cause of Code 3005 in this article.
Application information: Application domain: /LM/W3SVC/2/ROOT/owa Trust level: Full Application Virtual Path: /owa Application Path: E:Program FilesMicrosoftExchange ServerV15ClientAccessowa Machine name: EX13-01 Process information: Process ID: 15216 Process name: w3wp.exe Account name: NT AUTHORITYSYSTEM Exception information: Exception type: HttpException Exception message: The file or directory is corrupted and unreadable. ...edited for brevity... The file or directory is corrupted and unreadable. ...edited for brevity... Request information: Request URL: https://ex13-01.skaro.local:444/owa/ Request path: /owa/ User host address: fe80::31fa:8d7a:8000:d1d3 User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITYSYSTEM ...edited for brevity...
So, we had corruption. Not good!
However, the corruption was not located in the Application Path listed in the error above. But instead in the .NET caches located under the Windows folder. Thankfully the fix is quite simple.
Warning: You will need to schedule downtime for this server as the remediation requires you to stop the WWW Publishing Service
Fix the Corruption
Navigate to the following folder on your Exchange server.
C:WindowsMicrosoft.NETFramework64v4.0.30319Temporary ASP.NET Files
All files located in this folder are cached .NET files. For our particular issue, the corruption was one folder deeper — OWA.
Go to Start >> Administrative Tools >> Services. From the Services MMC, right-click the WWW Publishing Service and select Stop from the context menu.
Once stopped, delete all files located under the OWA subfolder. Don’t worry, the next time you log into OWA these files are regenerated.
Restart the WWW Publishing Service.
Once we did this we were able to log into Outlook Web App successfully.
Not finished yet
If you do run into this problem (and hopefully this fixes it) there is still one important question to ask; what caused your corruption in the first place?
For us, it was a storage problem. But any time you encounter any kind of corruption it’s always best to perform a root cause analysis. Check your logs. Use the tools from your hardware vendor. Be sure to find the cause before it becomes a much bigger problem — like data loss.
How about you? Have you experienced the dreaded ASP.NET 1309? What was your exception message and fix? Drop a comment below.
Gareth is an Microsoft MVP specializing in Exchange and Office 365. Gareth also contributes to the Office 365 for IT Pros book, which is updated monthly with new content. Find Gareth on LinkedIn, Twitter, or, Facebook.
Reader Interactions
Have you ever got stuck with the Asp.net error 1309
Unfortunately, Asp.net error 1309 is a very generic message that pops up when accessing the web interface.
It can happen when using an invalid string, or SQL connection timeout from an ASP.NET page.
At Bobcares, we often get requests to solve such ASP errors as part of our Server Management Services.
Today, let’s analyze the cause and see how our Support Team fix it for our customers.
Why use Asp.net?
Firstly, Let’s discuss the Asp.net.
ASP.NET is an open-source web framework, created by Microsoft. ASP stands for Active Server Pages. Which allows the programmers to execute its code using any .NET language(C#, VB, etc.).
It is used to create web pages and web technologies. And also designed to work with the HTTP protocol. ASP.NET is the main tool in the .NET framework for building web pages. Windows servers are most used for Asp development.
What is Asp.net error 1309?
This is a generic warning that an exception occurred in the ASP.NET. It can happen on anything from running 32-bit applications on a 64-bit machine. And an invalid string passed to a page, or to a SQL connection timeout from an ASP.NET page.
It occurs when the ASP.NET request executes for a period of time longer than the maximum timeout period. That means the execution time required by CRM connecting with remote SQL Server is exceeding the currently set ASP.NET request execution timeout value.
How we fix Asp.net error 1309?
So far, we discussed details about the Asp error 1309. Recently one of our customers contacted us with this error.
The error snippet is as below.
Let’s see how our Support Engineers fix this error for our customers. To solve this error, we modify the ASP.NET request execution timeout value.
For this, we do the following steps.
1. We first log into the system where Microsoft Dynamics CRM Server application is installed.
2. Then we start >> Internet Information Services (IIS) Manager.
3. We expand Web Sites option >> then right-click the Microsoft Dynamics CRM Web site >> and then click Properties.
4. From the Microsoft Dynamics CRM Web site >> properties page, >> click ASP.NET.
6. Then we click the Application tab>> and then in the Request execution timeout box >> increase the number of seconds.
7. At last, we click OK two times and close IIS Manager.
This fixes the Asp.net error 1309 error for our customers.
Need more assistance on Asp.net error? We’ll help you.]
Conclusion
In short, the main reason for this error is the execution time required by CRM connecting with remote SQL Server. Today’s write-up discussed how our Support Engineers fix this error for our customers.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
- Remove From My Forums
-
Question
-
We run Remote Desktop Services 2016 and have noticed some warnings in the event viewer of our Gateway Web Server.
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 3/31/2019 3:17:01 PM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/31/2019 3:17:01 PM
Event time (UTC): 3/31/2019 7:17:01 PM
Event ID: e81617fac6bc42abb32fa7b69388da07
Event sequence: 252
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/RDWeb/Pages-1-131981716874383622
Trust level: Full
Application Virtual Path: /RDWeb/Pages
Application Path: C:WindowsWebRDWebPages
Machine name:
Process information:
Process ID: 2568
Process name: w3wp.exe
Account name: IIS APPPOOLRDWebAccess
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Request information:
Request URL: :443/RDWeb/Pages/en-US/Default.aspx
Request path: /RDWeb/Pages/en-US/Default.aspx
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOLRDWebAccess
Thread information:
Thread ID: 56
Thread account name: IIS APPPOOLRDWebAccess
Is impersonating: False
Stack trace: at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext
objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Custom event details:Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»ASP.NET 4.0.30319.0″ />
<EventID Qualifiers=»32768″>1309</EventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2019-03-31T19:17:01.823012500Z» />
<EventRecordID>54382</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>3005</Data>
<Data>An unhandled exception has occurred.</Data>
<Data>3/31/2019 3:17:01 PM</Data>
<Data>3/31/2019 7:17:01 PM</Data>
<Data>e81617fac6bc42abb32fa7b69388da07</Data>
<Data>252</Data>
<Data>17</Data>
<Data>0</Data>
<Data>/LM/W3SVC/1/ROOT/RDWeb/Pages-1-131981716874383622</Data>
<Data>Full</Data>
<Data>/RDWeb/Pages</Data>
<Data>C:WindowsWebRDWebPages</Data>
<Data></Data>
<Data>
</Data>
<Data>2568</Data>
<Data>w3wp.exe</Data>
<Data>IIS APPPOOLRDWebAccess</Data>
<Data>NullReferenceException</Data>
<Data>Object reference not set to an instance of an object.
at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()</Data>
<Data>/RDWeb/Pages/en-US/Default.aspx</Data>
<Data>/RDWeb/Pages/en-US/Default.aspx</Data>
<Data></Data>
<Data>
</Data>
<Data>False</Data>
<Data>
</Data>
<Data>IIS APPPOOLRDWebAccess</Data>
<Data>56</Data>
<Data>IIS APPPOOLRDWebAccess</Data>
<Data>False</Data>
<Data> at Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext
objHttpContext)
at ASP.en_us_default_aspx.<GetAppsAsync>d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
</Data>
</EventData>
</Event>
User-1197427475 posted
Hi,
I’ve noticed this warning every 25 minutes on my server 2012R2. I do not have any problems with anything, at least I’ve not noticed any, but not sure what is causing it. Can someone help me? Thank you
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 17/03/2021 10:54:31 a.m.
Event time (UTC): 16/03/2021 9:54:31 p.m.
Event ID: 13e6455b069b418b8d3036db2df142f6
Event sequence: 2413
Event occurrence: 991
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT-3-132599694692667439
Trust level: Full
Application Virtual Path: /
Application Path: C:inetpubwwwroot
Machine name: XXXXXX
Process information:
Process ID: 12476
Process name: w3wp.exe
Account name: NT AUTHORITYSYSTEM
Exception information:
Exception type: ArgumentNullException
Exception message: Value cannot be null.
Parameter name: s
at System.Convert.FromBase64String(String s)
at ASP.aspnet_client_supp0rt_aspx.Page_Load()
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: https://autodiscover.xxxxxxxxx.co.xx:443/aspnet_client/supp0rt.aspx
Request path: /aspnet_client/supp0rt.aspx
User host address: xxx.xxx.xxx.xxx
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITYSYSTEM
Thread information:
Thread ID: 75
Thread account name: NT AUTHORITYSYSTEM
Is impersonating: False
Stack trace: at System.Convert.FromBase64String(String s)
at ASP.aspnet_client_supp0rt_aspx.Page_Load()
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
— System
— Provider
[ Name] ASP.NET 4.0.30319.0
— EventID 1309
[ Qualifiers] 32768
Level 3
Task 3
Keywords 0x80000000000000
— TimeCreated
[ SystemTime] 2021-03-17T00:54:14.000000000Z
EventRecordID 21771272
Channel Application
Computer XXXXXX.xxxxxx.local
Security
— EventData
3005
An unhandled exception has occurred.
17/03/2021 1:54:14 p.m.
17/03/2021 12:54:14 a.m.
090676a7fdb24ad38e0828ec2a75fb74
43
8
0
/LM/W3SVC/1/ROOT-3-132604143497063499
Full
/
C:inetpubwwwrootXXXXX
12716
w3wp.exe
NT AUTHORITYSYSTEM
ArgumentNullException
Value cannot be null. Parameter name: s at System.Convert.FromBase64String(String s) at ASP.aspnet_client_supp0rt_aspx.Page_Load() at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
https://autodiscover.xxxxxxx.co.xx:443/aspnet_client/supp0rt.aspx
/aspnet_client/supp0rt.aspx
159.89.222.138
False
NT AUTHORITYSYSTEM
25
NT AUTHORITYSYSTEM
False
at System.Convert.FromBase64String(String s) at ASP.aspnet_client_supp0rt_aspx.Page_Load() at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)
I was helping a good friend of mine recently with his Exchange 2013 server. When he logged into Outlook Web App he would get the “Something went wrong” internal server error.
Unfortunately, this is an incredibly generic error that can be caused by a variety of different problems. We decided to hit the Event Logs. Almost instantly we ran across several occurrences of this error.
ASP.NET Event ID 1309 Event Code 3005 Event code: 3005 Event message: An unhandled exception has occurred. Event time: 6/1/2015 7:00:00 PM Event time (UTC): 6/1/2015 11:00:00 PM Event ID: 4d1bb9b639774fd689f5b1eeec309375 Event sequence: 2 Event occurrence: 1 Event detail code: 0
Sadly, ASP.NET Event ID 1309 is a very generic message. In fact, Event Code 3005 could be caused by any number of possibilities. Ruling the Event Code out we examined the rest of the error. We quickly found our answer in the Exception Message. I’ve highlighted the section below.
Tip: Exchange MVP Jeff Guillet identifies another cause of Code 3005 in this article.
Application information: Application domain: /LM/W3SVC/2/ROOT/owa Trust level: Full Application Virtual Path: /owa Application Path: E:Program FilesMicrosoftExchange ServerV15ClientAccessowa Machine name: EX13-01 Process information: Process ID: 15216 Process name: w3wp.exe Account name: NT AUTHORITYSYSTEM Exception information: Exception type: HttpException Exception message: The file or directory is corrupted and unreadable. ...edited for brevity... The file or directory is corrupted and unreadable. ...edited for brevity... Request information: Request URL: https://ex13-01.skaro.local:444/owa/ Request path: /owa/ User host address: fe80::31fa:8d7a:8000:d1d3 User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITYSYSTEM ...edited for brevity...
So, we had corruption. Not good!
However, the corruption was not located in the Application Path listed in the error above. But instead in the .NET caches located under the Windows folder. Thankfully the fix is quite simple.
Warning: You will need to schedule downtime for this server as the remediation requires you to stop the WWW Publishing Service
Fix the Corruption
Navigate to the following folder on your Exchange server.
C:WindowsMicrosoft.NETFramework64v4.0.30319Temporary ASP.NET Files
All files located in this folder are cached .NET files. For our particular issue, the corruption was one folder deeper — OWA.
Go to Start >> Administrative Tools >> Services. From the Services MMC, right-click the WWW Publishing Service and select Stop from the context menu.
Once stopped, delete all files located under the OWA subfolder. Don’t worry, the next time you log into OWA these files are regenerated.
Restart the WWW Publishing Service.
Once we did this we were able to log into Outlook Web App successfully.
Not finished yet
If you do run into this problem (and hopefully this fixes it) there is still one important question to ask; what caused your corruption in the first place?
For us, it was a storage problem. But any time you encounter any kind of corruption it’s always best to perform a root cause analysis. Check your logs. Use the tools from your hardware vendor. Be sure to find the cause before it becomes a much bigger problem — like data loss.
How about you? Have you experienced the dreaded ASP.NET 1309? What was your exception message and fix? Drop a comment below.
Gareth is an Microsoft MVP specializing in Exchange and Office 365. Gareth also contributes to the Office 365 for IT Pros book, which is updated monthly with new content. Find Gareth on LinkedIn, Twitter, or, Facebook.
Reader Interactions
User-187114896 posted
I have been getting the warning id 1309 followed by error 4005. I have searched around and could not find a solution:
Please see below:
+ System
— Provider
[ Name] ASP.NET 4.0.30319.0
— EventID 1309
[ Qualifiers] 32768
Level 3
Task 3
Keywords 0x80000000000000
— TimeCreated
[ SystemTime] 2013-09-04T09:30:33.000000000Z
EventRecordID 3793
Channel Application
Computer serverid
Security
— EventData
3005
An unhandled exception has occurred.
9/4/2013 2:30:33 AM
9/4/2013 9:30:33 AM
ffa527e912a74f2b8a164b03a2a5e4f1
9390
4
0
/LM/W3SVC/5/ROOT-2-130227265363390640
Full
/
C:domainsmysite.comwwwroot
myservername
2728
w3wp.exe
IIS APPPOOLmysite.com
SqlException
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream,
BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader
ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at WebMatrix.Data.Database.<QueryInternal>d__0.MoveNext()
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source) at ASP._Page_shared_layout_cshtml.Execute() in c:domainsmysite.comwwwrootsharedlayout.cshtml:line 4 at System.Web.WebPages.WebPageBase.ExecutePageHierarchy() at System.Web.WebPages.WebPage.ExecutePageHierarchy()
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage) at System.Web.WebPages.WebPageBase.RenderSurrounding(String partialViewName, Action`1 body) at System.Web.WebPages.WebPageBase.PopContext()
at System.Web.WebPages.WebPageHttpHandler.ProcessRequestInternal(HttpContextBase httpContext) The wait operation timed out
http://www.mysite.com/job/182155
/job/182155
66.249.73.34
False
myservernameseriousteacher.com
16
myservernamemysite.com
False
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock,
Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior,
RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method,
TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at WebMatrix.Data.Database.<QueryInternal>d__0.MoveNext() at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source) at ASP._Page_shared_layout_cshtml.Execute()
in c:domainsmysite.comwwwrootsharedlayout.cshtml:line 4 at System.Web.WebPages.WebPageBase.ExecutePageHierarchy() at System.Web.WebPages.WebPage.ExecutePageHierarchy() at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext,
TextWriter writer, WebPageRenderingBase startPage) at System.Web.WebPages.WebPageBase.RenderSurrounding(String partialViewName, Action`1 body) at System.Web.WebPages.WebPageBase.PopContext() at System.Web.WebPages.WebPageHttpHandler.ProcessRequestInternal(HttpContextBase
httpContext)
User-187114896 posted
I have been getting the warning id 1309 followed by error 4005. I have searched around and could not find a solution:
Please see below:
+ System
— Provider
[ Name] ASP.NET 4.0.30319.0
— EventID 1309
[ Qualifiers] 32768
Level 3
Task 3
Keywords 0x80000000000000
— TimeCreated
[ SystemTime] 2013-09-04T09:30:33.000000000Z
EventRecordID 3793
Channel Application
Computer serverid
Security
— EventData
3005
An unhandled exception has occurred.
9/4/2013 2:30:33 AM
9/4/2013 9:30:33 AM
ffa527e912a74f2b8a164b03a2a5e4f1
9390
4
0
/LM/W3SVC/5/ROOT-2-130227265363390640
Full
/
C:domainsmysite.comwwwroot
myservername
2728
w3wp.exe
IIS APPPOOLmysite.com
SqlException
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream,
BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader
ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at WebMatrix.Data.Database.<QueryInternal>d__0.MoveNext()
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source) at ASP._Page_shared_layout_cshtml.Execute() in c:domainsmysite.comwwwrootsharedlayout.cshtml:line 4 at System.Web.WebPages.WebPageBase.ExecutePageHierarchy() at System.Web.WebPages.WebPage.ExecutePageHierarchy()
at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage) at System.Web.WebPages.WebPageBase.RenderSurrounding(String partialViewName, Action`1 body) at System.Web.WebPages.WebPageBase.PopContext()
at System.Web.WebPages.WebPageHttpHandler.ProcessRequestInternal(HttpContextBase httpContext) The wait operation timed out
http://www.mysite.com/job/182155
/job/182155
66.249.73.34
False
myservernameseriousteacher.com
16
myservernamemysite.com
False
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock,
Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior,
RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method,
TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at WebMatrix.Data.Database.<QueryInternal>d__0.MoveNext() at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source) at ASP._Page_shared_layout_cshtml.Execute()
in c:domainsmysite.comwwwrootsharedlayout.cshtml:line 4 at System.Web.WebPages.WebPageBase.ExecutePageHierarchy() at System.Web.WebPages.WebPage.ExecutePageHierarchy() at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext,
TextWriter writer, WebPageRenderingBase startPage) at System.Web.WebPages.WebPageBase.RenderSurrounding(String partialViewName, Action`1 body) at System.Web.WebPages.WebPageBase.PopContext() at System.Web.WebPages.WebPageHttpHandler.ProcessRequestInternal(HttpContextBase
httpContext)
Sometimes in Exchange 2016 or 2019, you have a server that hums with no errors and then you get those that give you a little more grief. You way have come across a warning for ASP.NET for the path C:Program FilesMicrosoftExchange ServerV15FrontEndHttpProxyrest that gives an error for “maxQueryString Length value”, below is the error:
The fix is not too difficult in this case to fix. You need to navigate to the path listed above which is:
- C:Program FilesMicrosoftExchange ServerV15FrontEndHttpProxyrest
First make a copy of the web.config file as we need to edit it. Open up Notepad elevated and navigate to the path above. Once open scroll down till you see <httpRuntime maxRequestLength…….
We need to add in the line highlighted above, the output will look like this:
I didn’t restart the transport service but left it and this event cleared.
Hope it helps.
title | description | author | ms.author | manager | audience | ms.topic | localization_priority | ms.custom | ms.reviewer | appliesto | search.appverid | ms.date | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Event ID 1309 and you can’t access OWA and ECP after you install Exchange Server 2016 or Exchange Server 2013 |
Resolves an issue that prevents you from accessing OWA and ECP and generates Event ID 1309 after you successfully install Exchange Server 2016 or Exchange Server 2013. |
simonxjx |
v-six |
dcscontentpm |
ITPro |
troubleshooting |
Normal |
|
jmartin, excontent, batre |
|
MET150 |
3/31/2022 |
Event ID 1309 and you can’t access OWA and ECP after you install Exchange Server 2016 or Exchange Server 2013
Original KB number: 3099532
Symptoms
You successfully installed Microsoft Exchange Server 2016 or Exchange Server 2013. The installation process may have failed or been interrupted at some stage and then resumed and finally completed successfully. However, when you try to access Exchange Control Panel (ECP) or Outlook Web App (OWA), you receive the following error message:
something went wrong
Sorry, we can’t get that information right now. Please try again later. If the problem continues, contact your helpdesk.
:::image type=»content» source=»media/event-1309-code-3005-cannot-access-owa-ecp/something-went-wrong-error.png» alt-text=»Screenshot of the error message — we can’t get that information right now.»:::
Additionally, the following event may be logged in the Application log:
Log Name: Application Source: ASP.NET 4.0.30319.0 Event ID: 1309 Task Category: Web Event Level: Warning Keywords: Classic User: N/A Computer: Exch2.contoso.com Description: Event code: 3005 Event message: An unhandled exception has occurred. Event ID: f23d9d455f3145068c57286262ac517f Event sequence: 1 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/2/ROOT/owa-5-130879214460462920 Trust level: Full Application Virtual Path: /owa Application Path: C:Program FilesMicrosoftExchange ServerV15ClientAccessowa Machine name: EXCH2 Process information: Process ID: 4348 Process name: w3wp.exe Account name: NT AUTHORITYSYSTEM Exception information: Exception type: TargetInvocationException Exception message: Exception has been thrown by the target of an invocation. at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean&canBeCached, RuntimeMethodHandleInternal&ctor, Boolean&bNeedSecurityCheck) * SharedWebConfig.config is missing from either of these locations: C:Program FilesMicrosoftExchange ServerV15FrontEndHttpProxy C:Program FilesMicrosoftExchange ServerV15ClientAccess
Cause
This issue occurs if SharedWebConfig.config is missing from either of the following locations:
- C:Program FilesMicrosoftExchange ServerV15FrontEndHttpProxy
- C:Program FilesMicrosoftExchange ServerV15ClientAccess
Resolution
To resolve this issue, follow these steps:
-
On the server that’s facing the problem, identify the location that the file is missing from.
-
Generate the missing file:
-
Run
cd %ExchangeInstallPath%bin
to change the current directory to the bin folder that’s under the Exchange installation path. -
Use the DependentAssemblyGenerator.exe tool to generate the file:
- If the file is missing from C:Program FilesMicrosoftExchange ServerV15ClientAccess, run the following command:
DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%bin" -exchangePath "%ExchangeInstallPath%ClientAccess" -configFile "%ExchangeInstallPath%ClientAccessSharedWebConfig.config"
- If the file is missing from C:Program FilesMicrosoftExchange ServerV15FrontEndHttpProxy, run the following command:
DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%bin" -exchangePath "%ExchangeInstallPath%FrontEndHttpProxy" -configFile "%ExchangeInstallPath%FrontEndHttpProxySharedWebConfig.config"
-
-
Run IISRESET, or restart the server.
More information
The SharedWebConfig.config file generates during the post-installation phase of Setup. If Setup resumes after an interruption, it doesn’t do the post-installation steps for the roles that were successfully installed before the interruption.