Microsoft KB Archive/941990

= Digitally signed components causing slow startup of applications when there is no network connectivity =

Article ID: 941990

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft .NET Framework 2.0

-



Source: Microsoft Support



RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.



Action
You attempt to start a digitally signed .NET Windows application or Windows service.



Result
The application starts very slowly. Digitally signed Windows services may time out during startup, with the Service Control Manager returning error &quot;Error 1053: The service did not respond to the start or control request in a timely fashion. &quot;



Cause
This occurs because the application needs to download the Certificate Revocation List (CRL) for authentication purposes, and a lack of network connectivity causes the download to fail by timing out. A firewall can potentially block the download and when Windows first starts up, the network connection is not initialized yet.



Resolution
1. One way is to cache the certificates locally, but it will expire within 15 days.

2. Another method is to minimize the default network timeout setting. To change the default timeout please follow the &quot;More Information&quot; section in the following Microsoft Knowledgebase article:

841632 You receive the &quot;403.13 client certificate revoked&quot; error message after you install the MS04-11 security update

http://support.microsoft.com/default.aspx?scid=kb;EN-US;841632



3. For a Windows service, you can increase the default timeout setting to allow the service to start by following these steps:

a. In Registry Editor, locate, and then right-click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

b. Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.

c. Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.

d. Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify. The Edit DWORD Value dialog box appears.

e. In the Value data text box, enter the desired timeout value in milliseconds and click OK. For example, if the new service timeout should be 60 seconds (60000 milliseconds), then enter 60000.

f. Restart the computer. You must restart the computer for Service Control Manager to apply this change.



MoreInformation


DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

Keywords: kbnomt kbrapidpub KB941990

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.