While trying to read tags from OPC server using PI OPC client. It showing error as advise returns error 80070532
What user did you use to run the PI OPC Client? Is it the same user that runs the OPC Interface? Ensure that this user account password is still valid and not expired.
Admin user id is used to run PI OPC client. PI OPC Client and Pi Interface are on same machine.
OPC server is on different machine.
Is the Admin user running the interface? If not, when opening OPC Client, click on the 'Shift key + Right click' on the mouse. Then click 'run as user' and run PI OPC client as the interface user. Do you still receive the error?
Sorry But i'm bit confused.
PI Interface and PI OPC client run as administrator.
When u mentioned, "Then click 'run as user' and run PI OPC client as the interface user" I dint understand what you meant by interface user
I did not realise that you were already running the OPC Client as the interface user. By the interface user I meant the user running the interface. If you open your interface in PI ICU and go to the 'service' tab you will see, 'Log on as:' Which user is present here?
Advise returns error 80070532 is an error usually associated with user permissions.
Have you checked whether the password for the user is still valid as sometimes user passwords are set to expire after a certain amount of time. Test the password by trying to log in as the user and entering the password. Is the log-in successful?
The Advise error is usually from the OPC server trying to access the interface machine and having insufficient permissions. Although most of the DCOM settings happen on the OPC server, DCOM may also be required on the interface machine. The Account that the OPC server runs as can be given access to the interface machine by configuring DCOM settings on the interface machine. The DCOM Security and Configuration Guide from OSIsoft is very useful to show the steps involved.
DCOM settings was performed was performed last year for this OPC server and data was getting archived.
This error was noticed recently
If you've already checked for usernames and passwords, I believe that the DCOM error will be present when you start the interface as a service also. Can you restart/start your interface and grab the interface logs. Follow this KB: KB00401 - How to read new UniInt 4.5.0.x and later Interface message logs (now in PI Message Log, not PIPC.log) if you've not gathered logs before. Please attach the logs in your comment.
Retrieving data ...