PRB: Domain controller reboot causes Zetalink alerts to stop and users cannot browse Inbox via the website
This Zetalink technical note applies to:
When users try to access the Zetalink WAP site they are able to get to the login page and successfully logon but when an attempt is made to recall any Exchange data they receive a timeout error message, similar to 'Unable to connect to server'. Also all Zetalink alerts and summary rules will stop working.
The Zetalink log will still have entries written to it but no actual errors are logged, if the level of logging is changed to 'trace' the message 'logging on to Mailbox xxx on Server yyy type message' will be reported when Zetalink tries to access data on the Exchange server. Also any alert rule setup attempt on the Zetalink user configuration site will timeout.
These symptoms have been known to occur between 45 minutes and 1 hour after the Windows 2000 domain controller has been rebooted in a single domain controller domain with Exchange server installed on a separate system.
Note: This erroneous behaviour will not occur immediately after the domain controller is rebooted but after an unspecified period of time.
There are two possible workarounds.
- Reboot the Exchange 2000 server to reinstate WAP browsing and SMS alerts. Follow this procedure each time the domain controller is restarted.
- Add another domain controller to the domain.
This has been identified by Equisys as a problem with the software versions given above.
Last updated: 19 February 2002 (GC/SV)