ferega.blogg.se

The name of the application is recommended From the tag browser, add an OPC Server Setup tag.VTScada was set to run as a service under that account.Įnsure that the credentials for the service account are correctly entered. The following steps were determined while using an account that was a member of the local machine's "Administrative Users" group. Continuing in the DCOM settings for Trihedral VTS OPC Server,Įnable local and remote access for the account.Remove "Remote Launch" for the INTERACTIVE user. Select Launch and Activation Permissions, Open the DCOM settings for Trihedral VTS OPC Server,.Steps may vary depending on whether you are using Windows Defender or a third-party firewall. Otherwise, create an exception for VTS.exe for all ports on the required profile(s). VTScada creates a rule for the Domain and Private profiles. A Firewall rule for VTScada should be enabled for the required connection profile.Protocol TCP -Direction Inbound -Program C:\Windows\SysWOW64\OpcEnum.exe New-NetFirewallRule -DisplayName "OPC Server Enumerator 1.10" -Action Allow Set the profile as required using an elevated PowerShell prompt. If not, execute the following commands in a Windows PowerShell prompt that has elevated permissions: The OPCEnum service must be set to start automatically, and must be running.If so, uninstall any older version of the OPC Core Components and repeat the VTScada installation. These are installed automatically by VTScada if your license includes the OPC option. A VTScada license key that includes the OPC Server option.Ĭontact your VTScada account representative.Before proceeding, ensure that you can run Windows PowerShell with elevated permissions and that you have access to a Windows account that is a member of the local machine's Administrative Group. Preparation is required before you configure VTScada to work as an OPC Server. Other OPC Servers and clients may differ. Tests used VTScada as a server and a client. They may not be applicable to other operating systems. Windows Server 2016 was used to determine these steps. The most common symptom is that the client will attempt to launch a second instance of VTScada rather than connect to the first. This may be the case if the client is being run as a service, or VTScada is being run under another account (again, as a service). You are likely to experience problems if the VTScada server and the OPC client are not running as the same Windows account. Configure VTScada as an OPC Classic Server