Troubleshoot RPC, WMI, Access Denied or Network Path Not Found errors in Control Compliance Suite(CCS)
Last Updated April 22, 2019
Cannot collect data from some target Windows machines with Control Compliance Suite (CCS).
"RPC Server is unavailable"
"WMI failure: Connecting to \\SERVERNAME\root\default"
"Access is denied"
"The Network Path was not found"
Verify that the Windows targets are connected to the Network, and able to communicate through RPC and TCP/IP ports with the CCS Manager Machines. Ports 135,137,139,445 need to be opened between the CCS Manager and the Target Machines. Use the telnet application on the CCS Manager to connect on Ports 135,139 & 445 on the Target Machines. If Telnet Fails–Check for Firewalls between the CCS Manager and the target....they might be blocking these ports. Also check any Local Firewall on the target machine if there is no physical Firewall between the CCS Manager and the Targets. Open these ports on the Local Firewall (Inbound/Outbound Rules).
Make sure that the following services are running on the Target Machines/Assets-
Remote Procedure Call (RPC)
Windows Management Instrumentation
Remote Desktop Services
Windows Remote Management (WS-Management)
"wbemtest" can be run on the CCS Manager Machine/Query Engine Machines from a command window
Type wbemtest on the command prompt of the CCS Manager---Once open Click the Connect button
In the Namespace Type- \\IP Address of the Target Machine\root\default
Input the credentials being used by CCS for data collection on this target machine and then click Connect
If wbemtest can connect, then you should be returned to the first page and will be connected. Otherwise an error will occur. As wbemtest is a Microsoft application, this demonstrates that the issue is most likely the configuration on the target machine and not CCS based.
SETTING WMI PERMISSIONS
To set WMI permissions, on the target machine do the following
Click Start > Run > type wmimgmt.msc, and then click OK.
On the resulting screen, right-click WMI Control click Properties >> Security tab >> expand Root, and then click Default (or the failing node). Click Security >> Advanced.
On the advanced settings screen, click the service account or the group containing the service account and ensure it has the Enable Account and Remote Enable permissions. If not, grant the permissions.
NOTE: wmimgmt.msc may not run on certain machines due to Internet security settings. You may not have access to change the internet security settings on the target machine in order to use this tool…….there may be a GPO enforced setting. Instead you can use the Computer Management utility to grant WMI permissions. Please search for instructions on how to grant WMI permissions using Computer Management utility.
LESS LIKELY SETTINGS TO LOOK AT
NOTE: Again internet security policies can cause the group policy editor not to be available]
On the remote computer, open gpedit.msc, open Computer Configuration, open Administrative Templates, open Network, open Network Connections, open Windows Firewall, and then open either Domain Profile or Standard Profile, depending on which profile you want to configure. Enable the following exception: "Allow Remote Administration Exception" and "Allow File and Printer Sharing Exception".
RETEST with wbemtest.
The following suggestions are at the risk of the user. They are often recommended by Microsoft articles, however, consultation with Microsoft is always recommended.
Depending on your version of Windows, these are the following ways to repair/rebuild/reset WMI on your machine.
Windows Vista/Windows Server 2008, 2008 R2, 2012, and 2012R2
Open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type the following command winmgmt /salvagerepository
The above command performs a consistency check on the WMI repository, and if an inconsistency is detected, rebuilds the repository. The content of the inconsistent repository is merged into the rebuilt repository if it can be read.
Windows XP Service Pack 2
Click Start > Run and type the following command rundll32 wbemupgd, UpgradeRepository
This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%\system32\wbem\logs\setup.log) file.
Windows Server 2003 Service Pack 1
Use the following command to detect and repair a corrupted WMI Repository rundll32 wbemupgd, RepairWMISetup
Re-register WMI on the machine using these commands