Hi,
First, sorry for the long post, I have a few really weird issues, I'm trying to resolve since yesterday, without any luck :(
It would be great if someone could point me into the right direction since I don't even know where to start looking.
I hope that those issues are related and that they can be used to narrow it down:
Connecting from the internet works fine. ActiveSync autodiscovery and Outlook anywhere autodiscovery work and remote analyzer can't find any problems.
OWA internally as well as externally works fine too, the only problems are with Outlook when used from inside the network.
Setup:
The Exchange server 2013 is installed on a separate win2012 server.
The DC (also a win2012 server) is on the same network and currently none but one workstation is joined the domain (for testing purposes, migrating the other clients from a nt4 domain is planned).
The DC is also used as a DNS server for all clients. It's a split domain and quite identical to the public dns, except for the internal hosts and the records for the exchange pointing to their respective internal ips.
All clients run Windows XP SP3.
The problems occur when logging on with a local user account aswell as when logging on with a nt4 domain user account, it doesn't matter at all. It also doesn't matter whether Outlook 2007 or 2010 is used.
Configuring 1 Outlook profile (cached mode is always off)/user account works.
Autodicovery works. When starting Outlook for the first time a login/password prompt appears after which the profile is immediately available. Trying the autodiscovery test from Outlook also completes without any problems.
Accessing public folders works too, but trying to open the personal online archive results in an error: translation: folder couldn't be opened, error logging into Exchange.
Accessing the same personal archive via owa from inside the local or remote networks works without problems!
But the real issues start when configuring a second Outlook profile for the same user account on the same machine shortly afterwards.
While autodicovery runs it suddenly prompts for login/password after which outlook freezes for a few minutes, but it completes.
When starting Outlook with this second profile, the login prompt appears again after which Outlook freezes trying to connect to Exchange. It stays like that like forever. While this is going on an event 1309, code 3005 is logged (client closed connection..)
Application domain: /LM/W3SVC/1/ROOT/Rpc-7-130068161998831561
Trust level: Full
Application Virtual Path: /Rpc
Application Path: E:\Exchange Server\V15\FrontEnd\HttpProxy\rpc\
Machine name: EMAIL
Process information:
Process ID: 2508
Process name: w3wp.exe
Account name: NT-AUTORITÄT\SYSTEM
Exception information:
Exception type: HttpException
Exception message: Der Client hat die Verbindung getrennt. bei Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result) bei System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) Request information:
Request URL: https://<fqdn>:443/rpc/rpcproxy.dll?fba28549-98eb-4fde-8b6a-6aac708a70ca@ikjf.at:6001
Request path: /rpc/rpcproxy.dll
User host address: 192.168.0.167
User: <DOMAIN>\Administrator
Is authenticated: True
Authentication Type: NTLM
Thread account name: NT-AUTORITÄT\SYSTEM
Thread information:
Thread ID: 16
Thread account name: NT-AUTORITÄT\SYSTEM
Is impersonating: False
Stack trace: bei Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result) bei System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)
Afterwards the error about the standard mail container can't be opened et.c. appears.
The same event (although not everytime it seems) is also logged when trying to access the personal archive, but for user: <DOMAIN>\SM_a68acd26159349938
Finally, when trying to setup an Outlook profile on the ADC joined test machine, it states: the action couldn't be completed. The Exchange server couldn't be reached, Outlook must be in onlinemode or connected....
Trying the autodicovery test in Outlook on that machine doesn't tell about any problems either (found through scp) and the urls match the fqdn for the Exchange server.
Although the autodiscovery urls for a local client that isn't joined the ADC domain differ (same dns server): <exchange host name>.<domain>/Autodiscover/Autodiscover.xml <-- adc joined machine vs. autodiscover.<domain>/Autodiscover/Autodiscover.xml
Apart from the event mentioned above, the following warnings are logged:
A lot of 6002 "Ping of mdb ... timed out after '00:00:00' minutes. Last successful ping was at ... UTC."
And very rarely:
Failed to read killbit list file because of exception System.IO.IOException: Der Prozess kann nicht auf die Datei "E:\Exchange Server\V15\ClientAccess\owa\15.0.516.30\owa2\ext\killbit\killbit.xml" zugreifen, da sie von einem anderen Prozess verwendet wird. bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) bei System.IO.File.Open(String path, FileMode mode, FileAccess access, FileShare share) bei Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime)
And especially during boot: many "Performance counter updating errors"
I really hope that the issues described above are related
Thank you very much for any hint you can give me and for reading all that crap ;)
Max