Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Service application may hang when it calls bind() during system startup


Symptoms

If your self-developed autostart service application happens to call socket bind() API during system startup, the bind() API may not return. This issue just occurs in system startup phase and it does not occur if Shared Access servcie is not started in the system. 

↑ Back to the top


Cause

This is a design limitation of Window Server 2003. The Shared Access service does not register with the RPC Endpoint mapper during such an initial phase.

↑ Back to the top


Resolution

You can either disable Shared Access service or ensure sufficient delay in making the bind() call (e.g. write own code to make bind () call after timeout or sleep or ping) so as to allow time for Shared Access service registration with the RPC Endpoint mapper during start up.

↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2560294
Revision : 1
Created on : 1/7/2017
Published on : 6/15/2011
Exists online : False
Views : 615