Internet Information Services stops responding on a Microsoft Dynamics CRM 3.0 server

On a Microsoft Dynamics CRM 3.0 server or on a Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers server, Microsoft Internet Information Services (IIS) is unexpectedly reset. Next, IIS stops responding. When IIS stops responding, you receive an error message that resembles the following error messages.Additionally, the following event messages are logged in the system event log.

A process serving application pool 'CRMAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '7420'. The data field contains the error number.

A worker process with process id of '5864' serving application pool 'CRMAppPool' has requested a recycle because the worker process reached its allowed processing time limit.

A process serving application pool 'CRMAppPool' terminated unexpectedly. The process id was '1240'. The process exit code was '0x80'.

Application popup: Service Control Manager: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

EventID = 26 Source = Application Popup Description = "Application popup: Service Control Manager: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

After IIS stops responding, you have to restart one or both of the following services if these services cannot restart automatically:

• IIS Admin Service
• World Wide Web Service

The problem occurs because two threads are active but not synchronized. One thread is for initialization. This thread starts and stops the listener. The other thread implements a loop that queries the database. When these two threads are active but not synchronized, Microsoft Dynamics CRM may return an address in a module that has been unloaded.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Microsoft Dynamics CRM 3.0

This problem is fixed in Update Rollup 2 for Microsoft Dynamics CRM 3.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers

This problem is fixed in Update Rollup 1 for Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft Dynamics CRM 3.0, Japanese or Chinese version

This problem is fixed in the Chinese Simplified version of Microsoft Dynamics CRM 3.0 and in the Japanese version of Microsoft Dynamics CRM 3.0 Update Rollup 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base: By default, this fix is disabled. To enable this fix, create a new registry key. To do this, follow these steps:

1. Exit Microsoft Dynamics CRM 3.0.
2. On the server that is running Microsoft Dynamics CRM, click Start, click Run, type regedit, and then click OK.
3. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM
4. On the Edit menu, point to New, and then click DWORD Value.
5. Type SuspendThreadOnStopListener, and then press ENTER.
6. Right-click SuspendThreadOnStopListener, and then click Modify.
7. In the Value box, type 1, and then click OK.
8. On the File menu, click Exit to exit Registry Editor.
9. Click Start, click Run, and then type iisreset.

Notes

• This procedure will momentarily stop all running Web sites and then start the Web sites.
• After you enable this hotfix, notification threads are suspended instead of shutdown events being set.

This problem is not fixed in Update Rollup 1 for the Japanese version or the Chinese version of Microsoft Dynamics CRM 3.0. If you are using Update Rollup 1 for the Japanese version or the Chinese version of Microsoft Dynamics CRM 3.0, you must install this hotfix.

Japanese version and Chinese version of Microsoft Dynamics CRM 3.0

Hotfix information

If you are using the Japanese version or the Chinese version of Microsoft Dynamics CRM, a supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next update rollup that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Microsoft Dynamics CRM client for OutlookMicrosoft Dynamics CRM client for Outlook Compatibility UpdateMicrosoft Dynamics CRM 3.0 server

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Microsoft Dynamics CRM 3.0 Update Rollup 2, in Update Rollup 1 for Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers, in Update Rollup 2 for the Chinese Simplified version of Microsoft Dynamics CRM 3.0, and in the Japanese version of Microsoft Dynamics CRM 3.0.

You can use the Log Parser tool to determine the errors that occurred on the Microsoft Dynamics CRM 3.0 server. To obtain the Log Parser tool, visit the following Microsoft Web site: After you install the Log Parser tool, use this tool to query errors. To do this, follow these steps:

1. Click Start, point to All Programs, point to Log Parser 2.2, and then click Log Parser 2.2.
2. At the Log Parser 2.2 command prompt, type the following command:
   Logparser "select TimeGenerated,SourceName,EventCategoryName, Message into System.csv from System where EventID IN (7034;1074;26) order by TimeGenerated desc"
3. Press ENTER.
4. Open the System.csv file by using one of the following programs:
   • Microsoft Office Excel
   • Microsoft Office Word
   • Notepad
   Note By default, the System.csv file is in the following directory:
   C:\Program Files\Log Parser 2.2

The records in the System.csv file show the errors that occurred on the Microsoft Dynamics CRM 3.0 server.

For information about performance tuning for CRM 3.0, see the following white paper: For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base: