This article was previously published under Q276557
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about editing the metabase. Before you edit the metabase, verify that you have a backup copy that you can restore if a problem occurs. For information about how to do this, see the "Configuration Backup/Restore" Help topic in Microsoft Management Console (MMC).
If you change the Msimsrv.dll script mapping or you remove Msimsrv.dll script mapping from the Instmsg vRoot, when you attempt to redefine the path as a valid path, you receiving the following error message:
Applications/Script Mappings You must enter a valid file path
When this behavior occurs, Instant Messaging users are not able to log on; they are prompted for user credentials for authentication.
In addition, an HTTP status 500 message is reported in the X:\Winnt\System32\Logfiles\W3SVC\appropriate date log file.
This behavior occurs if you create a path that has blank spaces. The Internet Information Service (IIS) does not accept a path that has spaces in it for script mappings.
Warning If you edit the metabase incorrectly, you can cause serious problems that may require you to reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk.
Note Always back up the metabase before you edit it.To resolve this issue, follow these steps:
Click Start, click Run, and then type cmd.
Change the directory to: CD Inetpub\AdminScripts
Run the following command:
adsutil.vbs set w3svc/1/root/instmsg/scriptmaps "*,c:\program files\exchsrvr\bin\msimsrv.dll,1"
This command sets the scriptmaps attribute to accept all file extensions (this is denoted by the "*"). The 1 gives the program the ability to run in a directory that does not have Execute permissions.
When you complete these steps, the Msimsrv.dll file is reintroduced back into the Instmsg vRoot Application Mappings section.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.
The Msimsrv.dll file provides information for the Instant Messaging service.