Fix for Citrix Eventlog Errors 0, 1309

Yesterday – with one of Citrix Installations I support users reported that Web Interface performance has started degrading. Initially it took longer for initial loading of web page to get to Citrix Logon Page and longer logon times once users supply Login Name and Password and Click Logon at logon page. After a little while it changed to following message once user provides credentials and click logon.

The Web site is experiencing technical difficulties. We apologize for any inconvenience.

The internal error may only be temporary. Try reconnecting and, if the problem persists, contact your system administrator.

After reviewing eventlogs further on the server – I found following two errors back to back in Application Eventlog.

Source: Citrix Web Interface

Event ID: 0

Category: None


Site path: c:\inetpub\wwwroot\Citrix\XenApp.

A critical server error has occurred: System.Web.HttpException: Request timed out. [Log ID: 1e3ef1bb]

For more information, see Help and Support Center at

Source: ASP.NET 2.0.50727.0

Event ID: 1309

Category: Web Event


Event code: 3001

Event message: The request has been aborted.

Event time: 6/6/2009 7:10:41 AM

Event time (UTC): 6/6/2009 12:10:41 PM

Event ID: f3cd069ff8ae4acfbfce2275c7763250

Event sequence: 14

Event occurrence: 1

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/ROOT/Citrix/XenApp-1-128887636984531250

Trust level: Full

Application Virtual Path: /Citrix/XenApp

Application Path: c:\inetpub\wwwroot\Citrix\XenApp\


Process information:

Process ID: 9536

Process name: w3wp.exe


Exception information:

Exception type: HttpException

Exception message: Request timed out.

Request information:

Request URL:

Request path: /Citrix/XenApp/auth/login.aspx

User host address: XXX.XXX.XXX.XXX


Is authenticated: False

Authentication Type:


Thread information:

Thread ID: 5


Is impersonating: False

Stack trace:

Custom event details:

For more information, see Help and Support Center at MS etc. etc.

I reset IIS few times and performance will improve for first login and after that it will be back to previous state with same errros in the eventlog. I uninstalled and recreated website with same results but no luck. I repaired Citrix Web Interface installation without much luck. I also Granted NT AUTHORITY\Network Service write permissions on ASP.NET Temp Directories as explained in . No Luck.

Finally this is what I tried and seems like it did the trick

1. Removed Web Interface by going to Add/Remove Programs –> Remove Citrix Web Interface

2.Verified that Citrix Web Interface Directories are gone from wwwroot – if not manually delete those

3.Uninstalled ASP.Net Version referenced in Eventlog using following switch

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Aspnet_regiis -ua

4.Restarted IIS

5.Installed ASP.Net version I removed in previous steps by using following switch

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

6.Installed Citrix Web Interface

7.Created Web Interface

8.Configured Web Interface

9.Recreated Access Methods/Translations

And it did the trick… For web interface is working just fine now..

Also on a side note there was a harddrive failure on that server which rebuilt itself but I was not able to find any connection between webinterface issues and harddrive failure…



Filed under Uncategorized

3 responses to “Fix for Citrix Eventlog Errors 0, 1309

  1. Rems

    Hi. I have a similar problem.

    -PS server on internal LAN

    -WI on DMZ, necessary ports open

    While WI is on DMZ you can login, view and launch applications.

    When I move the server to the DMZ, you can login, but cannot view any application.

    I appreciate the help.

    Thank you.

  2. Rems

    Correction: When WI server is on the LAN – not DMZ – you can view and launch applications.

  3. Ben

    I had this same issue at the same time on 2 WI servers. Turns out the zone data collector had an issue. For reasons that I don’t understand, the other application servers figured this out and rolled over to the next zone data collector but the WI servers did not. I rebooted the zone data collector (which was frozen) and everything went back to normal. On the WI servers, the zone data collector was listed as the first XML broker. For some reason it didn’t failover to the next broker on the list.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s