nmaxwell-ks
asked on
iphone sync to SBS 2003 randomly fails till after reboot
I have an SBS 2003 server that has 5 or so Iphone users on it. Every so often, maybe a few days, maybe a couple of weeks. The iphone users loose their ability to sync. Server reboot fixes it. Resetting the Exchange services doesn't fix it.
I am getting the following errors:
Exchange mailbox Server response timeout: Server: [WCSRVXX.DomainName.local] User: [stefaniec@domainname.org] . Exchange ActiveSync Server failed to communicate with the Exchange mailbox server in a timely manner. Verify that the Exchange mailbox Server is working correctly and is not overloaded.
-------
Suggestions?
I am getting the following errors:
Exchange mailbox Server response timeout: Server: [WCSRVXX.DomainName.local]
-------
Suggestions?
Monitoring.
ASKER
cgaliher - I just did the iisreset /noforce
Attempting stop...
Restart attempt failed.
The service did not respond to the start or control request in a timely fashion.
(2147943453, 8007041d)
Attempting stop...
Restart attempt failed.
The service did not respond to the start or control request in a timely fashion.
(2147943453, 8007041d)
ASKER
Since that failed I did an iisreset /restart - that worked.
Checking with users to see if sync is working.
Checking with users to see if sync is working.
ASKER
As far as add-on apps, I've running Worry Free Business Security from Trend. I am going to upgrade to ver 7 to see if that changes anything.
ASKER
iisreset /restart resolved the sync issues. Next steps?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will be updating the AV from WFBS 6.x to 7. I will report back tomorrow or the following day.
ASKER
I just saw this was still open. Upgrading Worry Free Business Security from Trend resolved the issue.
If it does then you have *something* stomping on IIS. Usual culprits are AV scanners that lock log files, so IIS quits responding, and thus ActiveSync can't work correctly. Butg other things *can* stomp on IIS as well. I've seen several programs that insist on installing themselves into IIS's "default website" which is also where all of those Exchange hooks live with SBS 2003, so they end up in contention. One of the early spiceworks versions did this before they moved to Apache, for example. But there are many others. Gotta be careful installing 3rd-party apps on your SBS servers...
-Cliff