Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
A digitally signed .NET Framework 2.0 Windows application may start very slowly, or a Windows service may time out during startup
Article ID: 941990 - View products that this article applies to.
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.
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.
To resolve this problem, use one of the following methods.
Method 1Cache the certificates locally.
Note The certificate will expire within 15 days.
Method 2Minimize 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:
(http://support.microsoft.com/kb/841632/ )You receive the "403.13 client certificate revoked" error message after you install the MS04-11 security update
Method 3For a Windows service, you can increase the default time-out setting to allow for the service to start. To do this, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.