4 Replies Latest reply on Jun 23, 2011 4:08 PM by spilon

    PI_OPCClient generates Write returns Generic failure..


      Testing the PI OPCClient functionality.
      I can browse the PI instance, created a groups and see the tags.  
      Selected one to see the values.


      The I attempted  to write some data into the historian.


      I get the error


      Unable to write value: Write returns Generic failure.


      Any idea what this means?
      where can I look to get more details about this error (on the client or server side)


      PIHOME\dat\pipc.log shows this error. I tried both (DA and HDA) interfaces.






      20-May-11 09:08:07


      PI_OSIHDA.exe>PI-API> pinetread> recv blocking failure or host machine123:5450 closed the socket






      20-May-11 09:12:26


      PI_OSIOPC.exe>PI-API> pinetread> recv blocking failure or host v-pi01:5450 closed the socket





        • Re: PI_OPCClient generates Write returns Generic failure..

          Hi David,


          You've already found the pipc.log file, which is one source of information for troubleshooting.


          Another one would be the PI OPC DA/HDA Server debug log file, to be setup according to these instructions from the PI OPC DA/HDA Server documentation:


          Debug Logs
          If debugging is turned on, debug messages are written to the specified debug log according to the value of the debug flags.
          Debugging is controlled via the registry. The server creates a set of registry keys upon installation, which can be viewed via the regedit program supplied with Windows (at the start button, select Run... and type regedit into the box, then select OK) or through the use of the PI OPC DA/HDA Server configuration tool (OPCServerConfigTool) which modifies the registry keys directly. The registry keys that control debugging are stored under HKEY_LOCAL_MACHINE/SOFTWARE/PISystem/PI_OSIOPC/Data and HKEY_LOCAL_MACHINE/SOFTWARE/PISystem/PI_OSIHDA/Data and are called LogFile, DebugArea, and DebugLevel as displayed below.


          Regardless of insights other vCampus members might have to share with you on this topic, I kindly invite you to contact our regular Technical Support to get assistance on this issue, as this is not really related to programming issues, but configuration. Here in vCampus we try to stay focused on programming and systems integration (from an architectural and design perspective) involving PI.


          For troubleshooting on configuration issues, you are better served by our regular Technical Support, as they have got the tools to access your system remotely, if required, and can also escalate the issue to the product developers, if need be.


          Please do not hesitate to keep posting your questions related to programming and systems integration (from an architectural and design perspective) involving PI here in the vCampus forums.