Communication error with a win-platform of an Operator Station? File Repository?

1 EWS, 2 AppServr, 1 Historian, and 2 OWS (OWS1, and OWS2), System was working proply, but after ( I don'y have details, but as I heared that someone did back up and restored ..) the OWS2 now can not connect with the galaxy, and when I want to deply its platform from EWS, it said ERROR: faile to get file repossitory. ? I have check all connection (phisycal, ping, firewall, EWS\c$, all is good .. but it keeps saying the same error! any help please!

Parents
  • Hi Samir, 

    Is the error message: " failed to get file repository path"?

    On OWS2, Could you try to update the Network Account (Run Change Network Account) and restart the server?

  • Hi Richard, thanks a lot for your reply, yes it is "failed to get file repository path"! 

    OK, will do that, can use the adm account on OWS2 or should creat a new one?

  • The important thing is that it should be the same account on all nodes in your system.
    Preferably a domain account, this will ensure that same credentials are used on all nodes, among other things.

    If it is a local account then it should already been created and you just need to re-apply the credentials, especially since you say that the system was working. 

    If you are uncertain you could check the account used on other nodes. But if you do, please make sure to click cancel or the X in top right to close the program, if you click OK it will restart that node and that might not be optimal.

    Also there are some known issues, if you use a domain account, and you create a local account with the same username, so please try to avoid this.

    But in your case, it should be enough to just ensure that you have the correct user (same as on other nodes), re-enter the password, click OK to reboot the server, after this, try to deploy again.

Reply
  • The important thing is that it should be the same account on all nodes in your system.
    Preferably a domain account, this will ensure that same credentials are used on all nodes, among other things.

    If it is a local account then it should already been created and you just need to re-apply the credentials, especially since you say that the system was working. 

    If you are uncertain you could check the account used on other nodes. But if you do, please make sure to click cancel or the X in top right to close the program, if you click OK it will restart that node and that might not be optimal.

    Also there are some known issues, if you use a domain account, and you create a local account with the same username, so please try to avoid this.

    But in your case, it should be enough to just ensure that you have the correct user (same as on other nodes), re-enter the password, click OK to reboot the server, after this, try to deploy again.

Children