Event 1309/Error code 3005 on Exchange 2016

Article
2020-01-07

Question

_{Tuesday, January 7, 2020 10:25 PM}

I'm getting a huge amount of ID 1309 errors (Source: ASP.NET 4.0.30319.0) on Exchange 2016.

Server is in co-existence with Exchange 2010, but not yet primary (DNS still points at exchange 2010) but going live soon. The errors are more than once a minute.

The server is at CU14. I'm planning to apply CU15 and see if that has a positive effect

All the errors that I've checked so far are like the following. Has anyone experienced a similar issue?

Event code:3005

Application domain: /LM/W3SVC/1/ROOT/owa-2-<number>

Application domain: /LM/W3SVC/1/ROOT/owa/Calendar-1-<number>

Application Path:

c:\program files\microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa

Exception type: HttpException

Exception message: Server cannot append header after headers have been sent

Thanks

All replies (4)

_{Wednesday, January 8, 2020 4:13 AM ✅Answered}

How is your server spec'd? I saw similar events on exchange 2019 when there was not enough resources assigned to the server.

Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

_{Wednesday, January 8, 2020 6:59 AM ✅Answered}

Hi dapdx,
Have you applied CU15? This may be the easiest way to solve the issue.
Lots of reasons could lead to Error 3005. Would you post more information shown after “Exception message: Server cannot append header after headers have been sent”?
For some suggestions, you can refer to this topic and delete the all folders under OWA subfolder, or replace the target folder from another Exchange2016 CU14 server if you have.

Regards,

Eric Yin

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, January 8, 2020 5:51 PM}

CU15 appears to have cleared the error on the Exchange 2016 server.

I'm still seeing the errors (referencing a different ASP.NET version) on an Exchange 2010 server.

To clarify my setup, I have Exchange 2010 and 2016 in co-existence. At this point, DNS still points to Exchange 2010 but I'm going to switchover next week.

I have a test machine with a host file pointing to the Exchange 2016 server. If I attempt to connect from that test machine to a mailbox on Exchange 2010 then Outlook connects ok but OWA results in a blank screen. Connections from the test box to an Exchange 2016 server mailbox work ok for both Outlook and OWA.

On the Exchange 2010 server the ID 1309/Event Code 3005 Warnings have the following in the next few lines after “Exception message: Server cannot append header after headers have been sent”

Request information

Request URL: https://<Internal fqdn of Exchange 2010 server (.local):443/owa

Request path: /owa/

User host addresss: <IP address of Exchange 2016 server>

User: <blank>

Is authenticated: False

Authentication Type: <blank>

Thread account name: NT AUTHORITY\SYSTEM

The authentication settings on the Exchange 2010 and Exchange 2016 owa servers are different. Get-OwaVirtualDirectory shows the following are enabled per server:

Exchange 2010:

Basic Authentication

Windows Authentication

Exchange 2016 (Default web site/front end):

Basic Authentication

Forms Authentication

I'm thinking that might be related

Thanks

_{Tuesday, January 14, 2020 6:36 AM}

Hi dapdx,

How the things going now, have you set it pointing to 2016?

Here I will provide a brief summary of this post so that other forum members could easily find useful information here:
[Exchange Server > Exchange Server 2016 -Event 1309/Error code 3005 on Exchange 2016 — Summary]

Issue Symptom:
In co-existence environment of Exchange 2016 and 2010, gets a huge amount of 1309 errors.

(Possible) Cause:
The authentification settings of Exchange 2010 and 2016 are different.

Solution:
Apply Exchange2016 CU15.

Reference Links:
https://support.microsoft.com/en-us/help/4522150/cumulative-update-15-for-exchange-server-2016