Hello, thanks for detailed description.
First of all, we really need to determine whether you want to connect to OPC Alarms and Events (A&E) server, or to OPC Data Access (DA) server. In your post, these things are quite mixed:
you say that you want to connect to OPC AE
but you also say that "connection to a local OPC DA server worked fine"
you are instantiating our object that is for OPC Data Access (for OPC Alarms and Events, it would be "OPCLabs.EasyAEClient.5.1")
you say that you want "get the status of an item" which (by using the term "item") indicates OPC-DA (there are no "items" in OPC-A&E)
you are using syntax ("opcae://...") and server's ProgID (.... OPCEventServer ....) that seem to indicate (although not guarantee) that what you want is an A&E server.
Regardless of the above, here are one thing that definitely needs correction: the syntax you have used ("opcae://PGVM-W7V7/OPCES.OPCEventServer/{[CLSID]}") appears to come from the Softing or similar client, and is vendor-specific. Assuming that "PGVM-W7V7" is name of the computer, and "OPCES.OPCEventServer" is the ProgID of the server, a command to read OPC-DA item value would be, with our component:
$EasyDAClient->ReadItemValue("PGVM-W7V7", "OPCES.OPCEventServer", "257.Field.29");
Note that some servers support both OPC-DA and OPC-A&E, and in such case, they typically have two different ProgID's for that, although in theory it could also be the same.
If you want to deal with OPC Alarms and Events, you will have to use different object and methods altogether; there is no such thing as "reading" an alarm (the closest thing to it might be getting a condition status). If you need OPC A&E, please explain in plain words what you want to achieve, or how you have done it in some other client, and I will try to help.
Also, if you get any kind of exception that you do not expect and do not know why you are getting it, please obtain the exception message, and post it as well.
Best regards,
Zbynek Zahradnik
