Unable to connect to WMI

At times BPM Express for Hardware is unable to connect to WMI. There could be two reasons for this:

1.A firewall blocks the WMI protocol

2.The user does not have sufficient connection rights

Firewall is blocking the WMI protocol

In such a case, you are required to set the port for RPC/DCOM connections. WMI uses RPC/DCOM, so enabling the DCPM across the firewall should allow it to work. When WMI connects to a remote machine it uses port 135 for the initial negotiation, and then a random port is allocated for further connection. Stated below are two links that will help in setting a range of ports for the RPC/DCOM connection. Once you have set a range for RPC/DCOM communication, you can then configure the firewall to allow traffic through this range of ports.

●http://support.microsoft.com/default.aspx?scid=kb;en-us;154596

●http://msdn.microsoft.com/en-us/library/aa389286(VS.85).aspx

Insufficient connection rights

This means that the user credentials provided are insufficient to access WMI. This error occurs when the connected user is not recognized or is restricted in some fashion by the remote server (for example, the user might be locked out). The reasons may be the following:

●Accounts are in different domains

●Recent changes made to WMI security:

▪Blank passwords, formerly permitted, are not allowed since Windows Server 2003

▪The DCOM configuration access setting might have been changed

▪If the target computer is running Windows XP, the Force guest value under the registry key

▪HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa might be set to force the Guest account off (value is zero)

Request your network administrator to accord sufficient rights to the user credentials.