Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 941990 - Last Review: May 28, 2008 - Revision: 2.1
A digitally signed .NET Framework 2.0 Windows application may start very slowly, or a Windows service may time out during startup
On This Page
SYMPTOMS
When you try to start a digitally signed Microsoft .NET Framework 2.0 Windows application or Windows service, the application starts very slowly. Digitally signed Windows services may time out during startup, and you receive the following error message from the Service Control Manager:
Error 1053: The service did not respond to the start or control request in a timely fashion.
CAUSE
This problem occurs because the application must download the Certificate Revocation List (CRL) for authentication. However, a lack of network connectivity causes the download to fail by timing out. For example, a firewall may potentially block the download. When Windows first starts, the network connection is not yet initialized.
RESOLUTION
To resolve this problem, use one of the following methods.
Method 1
Cache the certificates locally.
Note The certificate will expire within 15 days.
Method 2
Minimize the default network time-out setting.
For more information about how to change the default time-out, click the following article number to view the article in the Microsoft Knowledge Base:
841632Â
(http://kbalertz.com/Feedback.aspx?kbNumber=841632/
)
You receive the "403.13 client certificate revoked" error message after you install the MS04-11 security update
Method 3
For a Windows service, you can increase the default time-out setting to allow for the service to start. To do this, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- On the Edit menu, point to New, and then click DWORD Value.
- Type ServicesPipeTimeout, and then press ENTER.
- Right-click ServicesPipeTimeout, and then click Modify.
- In the Value data box, type the desired time-out value in milliseconds (ms), and then click OK. For example, if the new service time-out should be 60 seconds, type 60000 in the Value data box.
- On the File menu, click Exit.
- Restart the computer.
Note You must restart the computer for the Service Control Manager to apply this change.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft .NET Framework 2.0
| kbdevsicnvrtkb kbpubtypekc kberrmsg kbtshoot kbprb KB941990 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please