Purpose
Many of the common Shavlik Protect scan errors can be corrected by changes to configuration or environment. This article lists the most common scan error messages and provides some guidance on correcting the issue.
Cause
Scan errors can occur:
- If one or more of the Shavlik Protect Scanning Prerequisites have not been met
- If one or more configuration issues are present in Shavlik Protect
- Due to one or more environmental issues
Resolution
This table lists the error codes:
| Error Code | Description |
| Error Code 105: MS_UNABLE_TO_GET_SYSTEM_DATA | This issue occurs due to an access denied message at the root of the problem, or due to other enironmental or network related issues. See the following KB: http://community.shavlik.com/docs/DOC-2233 |
| Error Code 200: System not found. Scan not performed. | This indicates that the specified computer was not located and could not be scanned. |
| Error Code 201: System not found. <system error message> | A network problem is preventing the specified machine from being scanned. Check to see that your computer (the scanning machine) is properly connected to the network and that you can remotely logon to the specified machine. |
| Error Code 202: System not found. Scan not performed. | A network or system error occurred while the scan was in process. Check to see that your scanning machine is properly connected to the network and that the machine being scanned is still connected to the network. Also ensure that the remote machine is running the Server service. |
| Error Code 230: Scan not performed. <system error message> | A general network error has occurred. See the system documentation for more information. |
| Error Code 235: System not found, or NetBIOS ports may be firewalled. Scan not performed. | Most likely, there is no machine with the specified IP address. If a machine does exist at this address, a personal firewall or port filtering device may be dropping packets destined for TCP ports 139 and 445. See the following KB: http://community.shavlik.com/docs/DOC-2220 |
| Error Code 261: System found but it is not listening on NetBIOS ports. Scan not performed. | A machine exists at this IP address but it is either not listening on, or is blocking access to, TCP ports 139 and 445. |
| Error Code 301: SystemRoot share access required to scan. | Unable to connect to the remote machine’s system share. This may occur if the administrator has unshared the systemroot (typically C$ or similar) or has disabled the AutoShareServer(Wks) via the registry. Set Value from 0 to 1 in these registries: HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\ parameters\AutoShareServer HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\ parameters\AutoShareWks For more information on restoring Admin Shares, see the Microsoft Knowledge Base article 318755. |
| Error Code 429: DLL is not properly registered. | |
| Error Code 430: Incorrect version of MDAC. | |
| Error Code 451: Admin rights are required to scan. Scan not performed. | The current or specified user account performing the scan does not have administrative rights to the machine being scanned. Check to see that the specified account is a member of the local administrators group on the machine being scanned (or is a member of a group with local administrative rights). |
| Error Code 452: NetChk is unable to scan this machine. Please check to see that you have administrative rights to this machine and are able to login to this machine from your workstation. Scan not performed. | Check to see that the Server service is enabled on the remote machine and that you can remotely logon to this machine. Ensure that the Workstation service is running on the machine performing the scan. See the following KB: http://community.shavlik.com/docs/DOC-2218 |
| Error Code 501: Remote registry access denied. Scan not performed. | Check to see that the Remote Registry service is enabled on the machine being scanned. See the following KB: http://community.shavlik.com/docs/DOC-2219 |
| Error Code 502: Scan not performed. Error reading Registry <system error message> | A general registry error has occurred. See the system documentation for more information. |
| Error Code 503: Scan not performed. Error reading Registry. | A general registry error has occurred. No additional information is available. |
| Error Code 553: Unable to read registry. Please ensure that the remote registry service is running. Scan not performed. | Check to see that the Remote Registry service is enabled on the machine being scanned. |
| Error Code 621: OS of target is an unsupported version of Windows | The specified may be a non-Microsoft platform running SMB services or otherwise emulating a Microsoft product. Review the document: http://community.shavlik.com/docs/DOC-23052 |
| Error Code 622: Machine OS is not Recognized. Please run with tracing on and send to technical support. Scan not performed. | Unable to determine the operating system of the specified machine. This may occur when scanning beta or unreleased versions of Microsoft operating systems. |
| Error Code 623: Machine Service pack is not Recognized. Please run with tracing on and send to technical support. Scan not performed. | Unable to determine the Service Pack of the specified machine. This may occur when scanning beta or unreleased versions of Microsoft Service Packs. |
| Error Code 701: File http://download.microsoft.com/download/ ... secure.cab was NOT downloaded. | The signed, compressed CAB file containing the security patch information could not be obtained from the specified location. This may occur if the scanning machine is not connected to a network, or is otherwise unable to access the specified file or location. If the CAB file is not obtained, an attempt is made to access the uncompressed XML file via https. |
| Error Code 702: File https://www.microsoft.com/technet/secur ... secure.xml was NOT downloaded. Attempting to find local copy of mssecure.cab. | The uncompressed XML file containing the security patch information could not be obtained from the specified location via https. This may occur if the scanning machine is not connected to a network, or is otherwise unable to access the specified file or location. If the XML file is not obtained from the network, an attempt is made to locate an existing version of this file on the local machine. |
| Error Code 799: Itanium class servers are not supported by Protect. | |
| Error Code 802: Could not read boot.ini file in harddrive at '%s' | Unable to read the image's boot.ini file after successfully mounting the hard disk (non-Vista systems). |
| Error Code 803: Could not find windows install directory in boot.ini file in harddrive at '%s' | The virtual image hard drive was successfully mounted and the boot.ini file was read but the scan engine was unable to locate the %systemroot% folder at the specified location (non-Vista systems). |
| Error Code 804: Could not find system32 directory for virtual system at '%s' | The virtual image hard drive was successfully mounted and the boot.ini file was read but the scan engine was unable to locate the %systemroot%\system32 folder at the specified location (non-Vista systems). |
| Error Code 805: Timeout when mounting hard drive at '%s' to drive '%c' | An attempt to mount the virtual image was not successful. The mounting process timed out after 60 seconds. Try scanning this image individually to see if the mount succeeds. |
| Error Code 806: Error mounting hard drive at '%s' to drive '%c' | An attempt to mount the virtual image was not successful. This can happen if the image being mounted is encrypted, is on a compressed drive, is a template or a linked clone, or any of the vmdk files are read-only. If this is a VMware Workstation or VMware Server image, this error occurs if the image is currently powered on or suspended. |
| Error Code 807: Error mounting hard drive at '%s' to drive '%c' with exit code %d | An attempt to mount the virtual image was not successful. The mounting process returned an unknown error code. Contact support for assistance. |
| Error Code 808: Could not get return code from mounting tool when mounting hard drive at '%s' to drive '%c' due to %s | The virtual image mounting process completed but the mount process was unable to determine if the mounting was successful. |
| Error Code 809: Unknown virtual image type '%s' extracted from '%s'. | The scan engine was unable to determine the virtual image type. This may occur if scanning a currently unsupported virtual image platform. |
| Error Code 810: Could not find system32 directory for virtual image: '%s' | The virtual image hard drive was successfully mounted but the scan engine was unable to locate the image's %systemroot%\system32 folder. |
| Error Code 811: Could not get information about drive mounted at '%s' for system:'%s' | The scan engine was unable to determine the systemroot drive letter for the mounted image. |
| Error Code 812: Could not open mounted registry key 'HKLM\\Software\\MountedDevices' for system: '%s' | The virtual image hard drive and registry was successfully mounted but the scan engine was unable to read the mounted registry. |
| Error Code 813: Could not enumerate the values under the key HKLM\\Software\\MountedDevices for system: '%s' | The virtual image hard drive and registry was successfully mounted but the scan engine was unable to enumerate values from the mounted registry. |
| Error Code 814: No path to vmware-mount.exe provided! | The scan engine was unable to locate the VMware mounting tool. Please make sure that the VMware Virtual Disk Development Kit has been properly installed. |
| Error Code 815: Could not find mounting tool at '%s' | The scan engine was unable to locate the VMware mounting tool. Please make sure that the VMware Virtual Disk Development Kit has been properly installed. |
| Error Code 816: Could not read system file at '%s' | The vmx configuration file does not exist for the specified VMware Workstation or VMware Server image. |
| Error Code 817: Error parsing system file at '%s' | The scan engine was unable to read the vmx file for the specified VMware Workstation or VMware Server image. Check the vmx file and ensure that it can be read in a text viewer. |
| Error Code 818: '%s'. Unable to mount the virtual image. The virtual image is currently powered on. | The scan engine was unable to mount the virtual image because the virtual image was powered on. The scan engine is only capable of scanning images that are offline (powered off). |
| Error Code 819: '%s'. Unknown PowerStatus '%d' | The scan engine was unable to determine the current state of the image (powered on, suspended, powered off). |
| Error Code 820: %s'. Scanning suspended or paused images is not currently supported. | The scan engine was unable to mount the virtual image because the virtual image was suspended (paused). The scan engine is only capable of scanning images that are offline (powered off). |
| Error Code 821: Could not open Objects key in BCD for image at '%s' | The scan engine was unable to access the boot configuration data (BCD) for this image. This error message could indicate that there is a problem with the specified image. Try powering on this image to ensure that it is still valid. This error message applies to Vista images only. |
| Error Code 822: Could not enumerate keys in 'BCD\\Objects' for image at '%s' | The scan engine was unable to enumerate information from the boot configuration data (BCD) for this image. This error message could indicate that there is a problem with the specified image. Try powering on this image to ensure that it is still valid. This error message applies to Vista images only. |
| Error Code 823: Could find default boot section in the BCD for image at '%s' | The scan engine was unable to enumerate boot information from the boot configuration data (BCD) for this image. This error message applies to Vista images only. |
| Error Code 824: Could not open key at 'BCD\\Objects\\%s\\Elements\\22000002' for image at '%s' | The scan engine was unable to open the boot information data from the boot configuration data (BCD) for this image. This error message applies to Vista images only. |
| Error Code 825: Could find the Windows root in default boot section of the BCD for image at '%s' | The scan engine was unable to locate the value which stores the location of the windows directory in the boot configuration data (BCD) for this image. This error message applies to Vista images only. |
| Error Code 826: Registry mount sentry is NULL! | The scan engine was enable to mount the virtual image's registry. The console may be running low on memory. |
| Error Code 827: Hard-drive mount sentry list is NULL or empty! | The scan engine was unable to read the vmx file and/or this file had no hard drives configured for the image. |
| Error Code 828: Could not mount registry for image '%s'. This could be caused by running a non supported configuration. Windows 2000 can't mount x64 registries. | The scan engine was unable to mount the registry for the virtual image. This may occur if using a Windows 2000 console and trying to mount x64 images (unsupported). |
Error Code 829:
Error: 829 - Accessing disk ID | This error can occur due to a number of different reasons. This is an error that occurs prior to mounting the image - it is not related to mounting the image (like the errors above)
General errors:
VIX_E_FAIL = 1, |
Product Versions
Shavlik NetChk Protect 7.x
Shavlik Protect 9.x