SMS Virtual Directory Server service may fail to start automatically on reboot on some Windows servers

Article:TECH84754  |  Created: 2006-01-16  |  Updated: 2011-06-16  |  Article URL http://www.symantec.com/docs/TECH84754
Article Type
Technical Solution

Environment

Issue



You have installed Symantec Mail Security 5.0 SMTP on a Windows server. After a reboot you notice the SMS Virtual Directory Server service and its dependent services fail to start automatically. A check of the System Event log shows multiple errors.

The error message seen in the System Event Viewer log is:
"Timeout (30000 milliseconds) waiting for the SMS Virtual Directory Server service to connect.+

Other errors follow:
The SMS Virtual Directory Server service failed to start due to the following error:
"The service did not respond to the start or control request in a timely fashion."

The SMS Exchange 5.5 Notification Agent service depends on the SMS Virtual Directory Server service which failed to start because of the following error:
"The service did not respond to the start or control request in a timely fashion."

The SMS IPlanet Notification Agent service depends on the SMS Virtual Directory Server service which failed to start because of the following error:
"The service did not respond to the start or control request in a timely fashion."

The SMS Active Directory Notification Agent service depends on the SMS Virtual Directory Server service which failed to start because of the following error:
"The service did not respond to the start or control request in a timely fashion."

The SMS Sync Server service depends on the SMS Virtual Directory Server service which failed to start because of the following error:
"The service did not respond to the start or control request in a timely fashion."



 


Solution



Use the "Services" control panel after the reboot completes, to manually start the SMS Sync Server service.

To prevent the issue with subsequent reboots, add a "ServicesPipeTimeout" entry to the Windows registry to control the SCM default timeout. This registry entry is missing from the registry by default.

To edit the Registry

 


WARNING: In the next steps you will edit the Windows registry. Back up the registry before you make any changes to it, because incorrect changes to the registry can result in permanent data loss or corrupted files. Modify only the registry keys that are specified.
For instructions, see How to back up the Windows registry.



 

  1. Open the Registry editor.
  2. Go to the key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  3. On the Menu bar, click Edit > New > DWORD.
  4. In the right pane, select New Value #1
    (the name of a new registry entry) is selected (highlighted) for editing.
  5. Type the following to change the name and then press ENTER.
    ServicesPipeTimeout
  6. Right click ServicesPipeTimeout > Modify.
    The Edit DWORD Value dialog box appears.
  7. In the Value data text box, type the timeout in milliseconds, and then click OK.
    Make sure the value entered is interpreted correctly as hexadecimal/decimal, depending on the type chosen. For example, to enter a value of 60 seconds, enter 60000 for a decimal value.


The next time the Windows host reboots, the SMS Virtual Directory Server should start. If the problem reoccurs, try increase the timeout value by another 30 seconds.



Technical Information
Two possible sources for this problem:

  • A Windows host that boots slowly due to insufficient hardware or a substantial list of startup tasks.
  • An existing LDAP sync source that consumes a large number of updates from an LDAP directory server


If this service start failure happens, LDAP Synchronization sources cannot be added, edited, or deleted in the Brightmail Control Center on the LDAP settings page. Existing LDAP Synchronization sources will fail to start scheduled synchronizations and replication.


 




Legacy ID



2006081610084963


Article URL http://www.symantec.com/docs/TECH84754


Terms of use for this information are found in Legal Notices