Symptoms

When performing a scan, you receive the message:

Error 301

SystemRoot share access required to scan

Cause

Protect is 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.

Resolution

1) Test connecting remotely to the admin shares to see if any additional error is given.

Examples:

From Windows explorer:

\\machine\C$

\\machine\ADMIN$

Or from command-line:

net use \\machine\IPC$ (optional specify user/pw)

See: Net use

Test opening a file to test read access.

Test creating a .txt file or editing a file to test write access.

If you are unable to connect to the admin shares or successfully perform the above tests you most likely need to review the Scanning Prerequisites.

2) You may need to restore administrative shares with the following steps:

• Set Value from 0 to 1 in these registries:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\AutoShareServer
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\AutoShareWks
• More Information: HOW TO: Restore Administrative Shares That Have Been Deleted
  

Additional Information

If you receive the following error when testing access to admin shares:

“System Error 1130 not enough server storage”

We have previously seen this resolved by following steps in this third party documentation:

PChucks Network: Server Functionality Affected By IRPStackSize

Note: Following this documentation is at your own risk. Setting the IRPStackSize value larger than it needed can waste system resources and possibly cause other failures.

Affected Product(s)

Shavlik Protect, All Versions