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:\Windows\Web\RDWeb\Pages\
Machine name:
Process information:
Process ID: 2568
Process name: w3wp.exe
Account name: IIS APPPOOL\RDWebAccess
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 APPPOOL\RDWebAccess
Thread information:
Thread ID: 56
Thread account name: IIS APPPOOL\RDWebAccess
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:\Windows\Web\RDWeb\Pages\</Data>
<Data></Data>
<Data>
</Data>
<Data>2568</Data>
<Data>w3wp.exe</Data>
<Data>IIS APPPOOL\RDWebAccess</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 APPPOOL\RDWebAccess</Data>
<Data>56</Data>
<Data>IIS APPPOOL\RDWebAccess</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:\inetpub\wwwroot\
Machine name: XXXXXX
Process information:
Process ID: 12476
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
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 AUTHORITY\SYSTEM
Thread information:
Thread ID: 75
Thread account name: NT AUTHORITY\SYSTEM
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:\inetpub\wwwroot\XXXXX
12716
w3wp.exe
NT AUTHORITY\SYSTEM
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 AUTHORITY\SYSTEM
25
NT AUTHORITY\SYSTEM
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 Files\Microsoft\Exchange Server\V15\ClientAccess\owa\ Machine name: EX13-01 Process information: Process ID: 15216 Process name: w3wp.exe Account name: NT AUTHORITY\SYSTEM 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 AUTHORITY\SYSTEM ...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:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary 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
I am working on website, yesterday i faced a problem i.e server got down. i have checked the event log files then i came to know that it was due to «event id 1309 asp.net 4.0 unhandled exception» error. i just restore the back up of the website and restart the website it got worked.
Now my concern is why i got this error: is the criteria i had followed is actual way to recover from this error. i am asking this because might be we will not have latest code back up in future then what will we do? so i am asking to experts
- why this errors occurred, what is exact caused for this.?
- Best way to overcome this.
I have read theThis link and came to know this is due to
This problem occurs because the public headers properties of the Request.Headers property and of the Response.Headers property become non-serializable after you install the MS07-040 security update
But i have not used «Request.Headers».. please guide me.