Autosync reports an error while checking for updates against a Local Autosync Server running Windows (NETIQKB48211)

fact
NetIQ Vulnerability Manager 5.0

fact
NetIQ Vulnerability Manager 5.5

fact
Microsoft Windows Server 2003

fact
Microsoft Internet Information Services 6.0

symptom

Autosync reports an error while checking for updates against a Local Autosync Server running Windows 2003.

symptom
Error: 'The AutoSync process encountered an error while attempting to check for new updates: Core Services: A file is missing from its expected location.'

symptom
Autosync cannot find a file when trying to get the latest changes.

cause
The extensions of the files that Autosync uses are not mapped in the MimeMap property in Microsoft Internet Information Services (IIS). IIS 6.0 includes a new security feature called Known Extensions.  If you request a resource whose file name extension is not mapped to a known extension in the MimeMap property, IIS denies the requests and returns a 404 error (file not found). 

fix

To add a global MIME type for the .nap and .nfo extensions in IIS:

1. Click to Start > Control Panel > Administrative Tools.
2. Open the Internet Information Services (IIS) Manager Console.
3. Right-click the computer where you want to add the MIME types and click Properties.
4. Click MIME Types.
5. Click New.
6. In Extension, type .nap.
7. In MIME Type, type a description for this extension, such as VM Autosync .nap file, and click OK.
8. Click New on the MIME Types window.
9. In Extension, type .nfo.
10. In MIME Type, type a description for this extension, such as VM Autosync .nfo file, and click OK.
11. Click OK on the (Local Computer) Properties window.
12. Right-click the server name again and click All Tasks > Restart IIS.
13. Click OK on the Stop/Start/Restart window.
14. Wait until the Stop/Start/Restart window closes then close the Internet Information Services (IIS) Manager console.

Formerly known as NETIQKB48211