This issue occurs when you run the ServerProtect for Microsoft Windows/Novell Netware setup on the server to install only the NS component.
To resolve this issue, do any of the following:
- On the IS, go to the \Program Files\trend\Sprotect folder and back up the TMRPC.ini file.
- Open and edit the TMRPC.ini file.
- Look for the entry of the NS that you want to add. This may be the server name or IP address. If it does not exist, add the entry and give it the value "2".
Example:
server1=2 or xxx.xxx.xxx.xxx=2
- Save and close the TMRPC.ini file.
- Restart the Trend ServerProtect Agent service.
- On the Normal Server that could not be added to IS, go to the \Program Files\trend\Sprotect folder.
- Back up and edit the TMRPC.ini file.
- Look for the entry of the IS that you want to add. This may be the server name or IP address. If it does not exist, add the entry and give it the value "2".
Example:
server1=2 or xxx.xxx.xxx.xxx=2
- Save and close the TMRPC.ini file.
- Restart the Trend Server Protect service.
- Log on to the ServerProtect management console and retry adding the NS.
- Open the Registry Editor.
Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
- Go to HKLM/Software/Microsoft/Rpc/ClientProtocols.
If there is no entry for Client Protocols in the registry, then recreate the whole key.
- In the Registry Editor, create the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols subkey.
- Make sure that the following values are available:
Name Type Data
-------------------------------
ncacn_http REG_SZ rpcrt4.dll
ncacn_ip_tcp REG_SZ rpcrt4.dll
ncacn_nb_tcp REG_SZ rpcrt4.dll
ncacn_np REG_SZ rpcrt4.dll
ncadg_ip_udp REG_SZ rpcrt4.dll - Restart your computer.
- If you have another working Normal Server, then export the same registry key and then import it on the target server.
- Restart the server and try again.