FAQs – Windows Services

When do I need to use the OPC Data Fix?
Only when the OPC Server(s) you are connecting to do not run as a Windows Service and cannot be accessed from the SYSTEM account due to DCOM security.
What account are the OAS Services run under?
By default the SYSTEM account, but you can change the Service LogOn using the Service Control Manager.

Remoting Security

The OAS Service communicates with other OAS Services and .NET components through .NET WCF so networking has never been easier.  The default TCP port number that Open Automation Software uses is 58724. If you have a firewall simply add this port number in the exceptions list. The TCP port is adjustable using the Configure OAS application under Configure-Options as the WCF Port Number. You can also set the WCFPortNumber property in all .NET controls.

To add a port to the exceptions list select Control Panel-Windows Firewall, then the Exceptions Tab. Use the Add Port button to add the TCP Port 58724. Use the Change scope button to specify the range of security for the port number.

For remote connections you can either use a Network Node name, IP Address, or registered Internet domain name of the remote nodes.

Service Control

To Start and Stop the 3 OAS Services you can use either the Service Control Manager built into the Windows Operating System or the OAS Service Control application.

Using the OAS Service Control application

To run the OAS Service Control application select Start-All ProgramsOpen Automation Software-OAS Service.

Service Control 1

Select the desired feature of the Service Control application:

  • Refresh Status:  Refreshes the Service Status and License Status.
  • Start Service: Starts the Service.
  • Stop Service: Stops the Service.
  • Start Runtime: Starts Runtime of Open Automation Software if the Service is running.
    Use the OAS Configuration to have the Service start automatically in Runtime.
  • Stop Runtime: Stops Runtime of Open Automation Software if the Service is running.
  • Configure OAS: Launches the Open Automation Software Configuration application.
  • Hide: Hides the application and leaves it running with the system tray icon available.
  • Exit: Exits the application.

Using the Windows built-in  Service Control Manager

Alternatively you can use the Service Control Manager built into the operating system. To start the Service Control Manager you must first have Administrative rights to the system.

For Windows 2000, XP, Server 2003, and Server 2008: Select Start-Control Panel-Administrative Tools-Services to view all Services installed on the system.

For Vista: Select Start-Control Panel-System Maintenance-Administrative Tools-Services to view all Services installed on the system.

For Windows 7, 8, and 10: Select Start-Control Panel-System and Security-Administrative Tools-Services to view all Services installed on the system.

Select OAS, OAS Data, and OAS Database and select Start or Stop.  Using Properties of the Service you can also set the Startup Type as Manual, Disabled, or Automatic.  Automatic is the default after installation so the Service will start with the Operating System.

Service Control 2

Service Logon

The OPC Client connection to third party OPC Servers runs in a Windows Service called OAS Data Service. By default this Windows Service runs under the System account. Connecting to other OPC Servers on the same PC that also run under the System account is easy.

Some OPC Servers cannot run as a Windows Service, so you may need to either use the OPC Data Fix or set the OAS Data Service to run under the desktop user account so that the operating system allows the connection.

If you are receiving bad data quality from the OPC Server it is most likely due to a security logon restriction in the operating system. To correct this it is recommended to use the OPC Data Fix or set the OAS Data Service Log On to a valid user account.

View the following section on the Service Control Manager.

If the OPC Server is running as a Service you can often leave the Service Log On to the Local System account, but check the box for “allow service to interact with desktop” if DCOM security is restricting the connection.

Refer to the OPC Communications – Troubleshooting section in this help file or the following video to resolve all OPC connection issues.

Service Control Manager

To start the Service Control Manager you must first have Administrative rights to the system.

For Windows 2000, XP, Server 2003, and Server 2008:

Select Start-Control Panel-Administrative Tools-Services to view all Services installed on the system.

Service Control Manager 1

For Vista:

Select Start-Control Panel-System Maintenance-Administrative Tools-Services to view all Services installed on the system.

Service Control Manager 2

For Windows 7, 8, and 10:

Select Start-Control Panel-System and Security-Administrative Tools-Services to view all Services installed on the system.

Service Control Manager 3   Service Control Manager 4

Starting the Service:

Select OAS Data and right click to select Properties:

Service Control Manager 5

Select the Log On Tab to view the current Logon Account. 

Select This account radio button and use the Browse button to Select User:

Service Control Manager 6

Use the Advanced button in the lower left:

Service Control Manager 7

Then the Find Now button to select the desired Logon User Account:

Service Control Manager 8

Select OK twice to return to the Log On Tab dialog.

Enter the Password for the User Account and select OK:

Service Control Manager 9

If the Service is already started it must be Stopped and Started for the changes to take effect.