Why Can't LabVIEW DSC Connect to My OPC Server When Server Explorer and DataSocket Can? Primary Software: LabVIEW Modules>>DSC ModulePrimary Software Version: 8.2.1 Primary Software Fixed Version: N/A Secondary Software: LabVIEW Development Systems>>Base Package
Problem:
Reading or writing to the OPC Server using DataSocket works correctly and I can connect to the server using Server Explorer, so I know that the OPC server is functioning properly. How can I set up the OPC server to work with the LabVIEW Datalogging and Supervisory Control (DSC) Module? Solution: The I/O Server makes calls to the OPC server through DCOM, even if not using a remote OPC server. The DCOM user checking can block all user names that are not registered with the server. When using DSC as an OPC client, the NI Shared Variable Engine (SVE) is the application that makes the connection to the OPC server. The SVE is a system service and, by default, logs and runs as the local system user. The communication can be rejected if the user name of the service is system. As long as the I/O Server is still deployed, it will continue to try to connect with the OPC server and fail, and shared variables will return the Server Failure error or no data at all. To avoid this issue, you will need to change either of the following settings. Change the Identity Property of the OPC Server
Change the Log On Account for the SVE Service
Note: This behavior is known to occur with Campbell Scientific OPC Servers and Takebishi's DeviceXPlorer OPC Server. Related Links: KnowledgeBase 3T8E89L7: "Server Failure" Shared Variable Status When Using DSC 8.0 as a Remote OPC Client Attachments:
Report Date: 06/14/2007 Last Updated: 11/17/2007 Document ID: 4AD9T3KO |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
