After you install Microsoft Systems Management Server (SMS) 2003 Advanced Client on a computer that is running Microsoft Internet Information Services (IIS), ASP.NET Web-based programs that use Windows Management Instrumentation (WMI) may not be able to connect. Additionally, you may receive the following error message:
Error loading type library/DLL
This problem typically occurs after you the install SMS 2003 Advanced Client. During the installation of SMS Advanced Client, the Setup program registers the Policyagent.dll file. This action may change the current WMI COM registrations. In this case, the type library reference is updated to point to the Policyagent.dll-type library instead of the Wbemdisp.dll-type library.
When this problem occurs, the account that is used by the ASP.NET Web-based program may not have access to the Policyagent.dll file.
Note This problem does not occur if you are using VBScript or the System.Management namespace to access WMI.
To resolve this problem, follow these steps:
Re-register the Wbemdisp.dll file. To do this, follow these steps:
Use an administrative account to log on to the SMS Advanced Client computer. Click Start, click Run, type cmd, and then click OK.
At the command prompt, type regsvr32 wbemdisp.dll.
In the Regsvr32 dialog box, click OK.
Note If you re-install SMS Advanced Client or apply a service pack hotfix, you may have to re-register the Wbemdisp.dll file.
If the error still occurs, make sure that the ASP.NET or IIS account that is used to run the Web-based program has the correct permissions to use the Policyagent.dll file. To do this, follow these steps:
Use Windows Explorer to locate and open the WINNT\system32\CCM folder. Note On an SMS management point computer, the Policyagent.dll file may reside in the SMS_CCM folder.
Right-click the Policyagent.dll file, and then click Properties.
In the Policyagent.dll Properties dialog box, click the Security tab.
Make sure that the ASP.NET or IIS account that is used to run the Web-based program has read access permissions for the Policyagent.dll file, and then click OK.
You may also be able to work around this problem by changing the account under which your ASP.NET program runs. ASP.NET Web-based programs are typically run by the Aspnet_wp.exe or W3wp.exe process.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
Note This problem typically occurs on Windows XP-based computers that are running IIS. Windows Server 2003-based computers that are running IIS are not affected by this problem because the ASP.NET program runs under the system account. The system account has access to the Policyagent.dll file.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.