General

1. Check the operating system. Windows 2003 SP1 and Windows XP SP2 both have Data Execution Prevention (DEP) settings, which can be found by right clicking on My Computer, and going to Advanced -> Settings under Performance. 2003 SP1 has DEP set to "Turn on DEP for all programs..." by default. When DEP is set to this, this will cause our installers to fail, and you will have to turn DEP off and reinstall the software.

2. Check your default DCOM. All our servers use COM to communicate between the PSTCFG interface and the server executable. As such, you will have to open up COM to make sure our server can communicate. To do this, go to Start -> Run... -> dcomcnfg. Expand "Component Services," "Computers," "My Computer." Right click on "My Computer" and go to properties, and make sure the default settings for launch and activation permissions contain the 4 groups of "Everyone, Interactive, Network, and System."

3. Re-register the server executable. There might have been a glitch during the install, and the server didn’t register itself properly. Go into a command prompt, and navigate to the server installation directory. By default, this is C:\Program Files\Matrikon\OPC\«Server Name»

At this time, you will want to run a “dir” command so you can see exactly what the executable is named. Generally, this is OPC«Servername».exe. This explanation of this will include the Modbus OPC Server:

Type in the following commands, pressing <enter> for each new line.

OPCModbus.exe -unregserver (This causes the executable to un-register itself)
OPCModbus.exe -regserver (This will cause the executable to re-register itself)
OPCModbus.exe -service (This causes the executable to register itself as a windows service. This is an optional step)