search

st-one-io / node-red-contrib-opc-da

A Node-RED node to interact with OPC-DA servers.
Apache License 2.0
11 stars 8 forks source link

Error: 2147549457 #21

Open elyancorrea opened 3 years ago

elyancorrea commented 3 years ago

I've tested your node on W10 with success, now trying to run on another PC. After finish dcom setup i got this error when tried to test connection:

erroropc

First error (2147746132) appear when OPC server is off (to check if OpcEnum is working), after start OPC server I got error 2147549457. Any ideas?

I'm trying to connect with Raytek dtdp software.

steuck13 commented 3 years ago

Greetings,

Sadly this error code is too generic. I see from the interface that you are using the NPM version of this node. This issue could be related to the DCOM version used. I'm not sure if the updates were published to NPM yet but if you install the related packages (node-red-contrib-opc-da and node-dcom) from their GitHub repo it could help. It will add a new field in the configuration tab where you can choose the version used (DCOM 5.4 or 5.7) based on which OS is being used to host the server.

I guess it's worth a try.

elyancorrea commented 3 years ago

I'll try. I've formatted my PC today to ensure cleared all config. You recommend a way to debug this error? You recommend a way to debug this error? Thankou.

Att: I did your suggestions and don't notice any difference. Will keep trying.

elyancorrea commented 3 years ago

Hello,

What is the version of windows are you recommend? I'm trying to connect with OPC-DA server from software Datatemp DP Raytek.

cvashish297 commented 3 years ago

Hello,

I am using custom OPC DA server on localhost , after providing the required details when i am trying to get the get the opc items by clicking test & get items, it shows 0 items found. However other OPC clients are able to connect to the same OPC server and also showing the opc items. I am using on windows server 2019 node red version 1.2.9 node js version 14.16.0

steuck13 commented 3 years ago

Weird, it should be working with windows 10. I´ll test this again as soon as I have time.

Originally this node was made to run on way older versions likde NT4.0 and XP.

kubiz commented 3 years ago

I've tested your node on W10 with success, now trying to run on another PC. After finish dcom setup i got this error when tried to test connection:

erroropc

First error (2147746132) appear when OPC server is off (to check if OpcEnum is working), after start OPC server I got error 2147549457. Any ideas?

I'm trying to connect with Raytek dtdp software.

hi @elyancorrea, do you mind sharing a screen shot of what are your configs are on W10? i've tried to connect to it also but it tell me "Access denied. Username and/or password might be wrong." image

autoinst578 commented 2 years ago

I've tested your node on W10 with success, now trying to run on another PC. After finish dcom setup i got this error when tried to test connection:

erroropc

First error (2147746132) appear when OPC server is off (to check if OpcEnum is working), after start OPC server I got error 2147549457. Any ideas?

I'm trying to connect with Raytek dtdp software.

Hei, are you done with this issue? i have same issue....

balajitekkiam commented 2 years ago

I have observed the same error. I also noticed that the Windows event viewer has this event logged -

The server-side authentication level policy does not allow the user WIN-0DTR6ELH0JG\Administrator SID (S-1-5-21-2458098753-3105389666-3035658031-500) from address 127.0.0.1 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.

Changing the server's auth level to 'None' does not clear the error.

I think this is related to the DCOM hardening implemented by Windows although this does not seem to affect other OPC clients.

RobbeM1991 commented 1 year ago

Have you been able to solve this? I've set the authentication level of "my computer" and the OPC server itself, to "Packet Integrity", but that didn't solve the issue. The error in the windows event viewer dissapeared though...

One more strange thing: When the OPC DA Client is in the same network, it works. When the OPC DA Client is in another VLAN (and the VLANS are routed), it doesn't work (and firewalls are OK, because I can see the user from the client logging on).