Consider the following scenario. You have a process that has more than one thread. Additionally, the process uses the Internet Information Services (IIS) Active Directory Service Interfaces (ADSI) provider to access IIS 6.0. Two threads access IIS 6.0 at the same time. In this scenario, you may be unable to manage IIS 6.0 by using Server Manager.

When this problem occurs, you must restart IIS 6.0, or you must restart the process that uses the IIS ADSI provider.

This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. When this problem occurs for the SharePoint Timer service, you may experience the following symptoms:

•	In SharePoint Server 2007, tasks that are scheduled do not run.
•	On the SharePoint Web front-end server, you see repeated errors in the Application log in Event Viewer. These errors usually include one of the following three events: • Event ID 6398 • Event ID 6482 • Event ID 7076 For example, you may see an error message that resembles the following: Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: (964) Event ID: 6398 Date: 11/7/2007 Time: 5:45:38 PM User: N/A Computer: 44MOSSAGRUK Description: The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 02b5e3f2-21e3-4552-bf1d-6e152749458a) threw an exception. More information is included below. Attempted to read or write protected memory. This is often an indication that other memory is corrupt. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
•	When you try to manage IIS 6.0 by using Server Manager, you receive a blank page, or you receive the following error message: the path specified cannot be used at this time

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

Windows Server 2003 x64 Service Pack 1

File name	File version	File size	Date	Time	Platform	Service pack (SP) requirement
Adsiis.dll	6.0.3790.3062	391,168	19-Dec-2007	13:36	x86	SP1
Wadsiis.dll	6.0.3790.3062	291,840	19-Dec-2007	13:36	x64	SP1

Windows Server 2003 x64 Service Pack 2

File name	File version	File size	Date	Time	Platform	SP requirement
Adsiis.dll	6.0.3790.4208	391,168	19-Dec-2007	13:41	x86	SP2
Wadsiis.dll	6.0.3790.4208	291,840	19-Dec-2007	13:41	x64	SP2

Windows Server 2003 x86 Service Pack 1

File name	File version	File size	Date	Time	Platform
Adsiis.dll	6.0.3790.3062	291,840	19-Dec-2007	15:07	x86

Windows Server 2003 x86 Service Pack 2

File name	File version	File size	Date	Time	Platform
Adsiis.dll	6.0.3790.4208	291,840	19-Dec-2007	15:19	x86

Windows Server 2003 IA-64 Service Pack 1

File name	File version	File size	Date	Time	Platform	SP requirement
Adsiis.dll	6.0.3790.3062	584,704	19-Dec-2007	13:38	x86	SP1
Wadsiis.dll	6.0.3790.3062	291,840	19-Dec-2007	13:38	IA-64	SP1

Windows Server 2003 IA-64 Service Pack 2

File name	File version	File size	Date	Time	Platform	SP requirement
Adsiis.dll	6.0.3790.4208	584,704	19-Dec-2007	13:42	x86	SP2
Wadsiis.dll	6.0.3790.4208	291,840	19-Dec-2007	13:42	IA-64	SP2

Note There are files named "Wadsiis.dll" for Windows Server 2003 x64 and for Windows Server 2003 IA-64. However, after you apply the hotfix, these files are renamed "Adsiis.dll" and are placed in the following location:

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top