I have been struggling with an issue here. In my hardware alarms, I have an alarm the states that the "Database Not Connected". Then when I go to the Alarm Summary page, I see thousands of alarms to say "Login attempt failed from <ip address> - unknown user" (the ip addresses on the message are my servers). When I look at my tracelog file, I see...
2020-03-22 10:47:27.747 -07:00 15492 0 Error AlarmClientAdaptor LegacyAdaptor::OnDataError ViewType=Display hCtrl=3 Error=DataRequestTimeout Message=Data not available Cluster=Stanton_U2
2020-03-22 10:47:27.747 -07:00 15492 0 Error AlarmClientAdaptor LegacyAdaptor::OnDataError ViewType=Display hCtrl=3 Error=DataRequestTimeout Message=Data not available Cluster=Stanton_U1
2020-03-22 10:47:27.747 -07:00 15492 0 Error AlarmClientAdaptor LegacyAdaptor::OnDataError ViewType=Display hCtrl=3 Error=DataRequestTimeout Message=Data not available Cluster=Stanton_U0
...when I look at my tracelog for the alarm server, I see...
2020-03-22 10:49:49.989 -07:00 15328 0 Error AlarmServerComms Exception An error occurred using the .NetApi Client in LogOn: {0} ClearScada.Client.AccessDeniedException: The username or password was incorrect.
at ClearScada.Client.Advanced.ScxComClient.ProcessServerException(Int32 requestCode)
at ClearScada.Client.Advanced.ScxComClientTcp.SendRequest(Int32 requestCode)
at ClearScada.Client.Advanced.ScxComLinkServer.LogOn(String userName, SecureString password, ILogonInformation& logonInformation)
at ClearScada.Client.Advanced.ScxComLinkServer.LogOn(String userName, SecureString password)
at ClearScada.Client.Simple.Connection.LogOn(String userName, String password)
at SchneiderElectric.Alarm.Server.Connection.Manager.ClearScadaClientApiConnection.LogOn(String userName, String password)
We have configured roles to use our corporate domain logins plus a few additional Citect users for the API connection used for the Wonderware Historian connector and kernal access.
We get these errors no matter what client we run, even the one on the servers. We also have shutdown the connector and all remote clients, same errors. I am beginning to think this is a bug of sorts, as these errors have added up to about 7GB of alarm event storage data in the last 12 days.
We have also tried to running the alarm servers in 64bit mode, same result.
We are running 2 physical servers, each with 3 clusters assigned to them. We have manually defined the port numbers for the second and third server processes so that they can coexist.
Being that we are run our clients and servers inside our own network, we have the windows firewalls turned off, but just for good measure, we have allowed all traffic on all ports and network types on both the servers and all clients.
What user name are the logs pointing to? We have setup the appropriate domain user groups to the Citect.**** groups. These errors still occur even if nobody in logged into the Citect client, it seems to be a server thing...but I'm not even sure that's accurate.
