About Andreas_Sievers

This workaround should apply to an older version of the client, but not to the service running in the background, right? ... View more

Basically, the program does not need any specific parameters to start and all crashes are usually logged. If the program does not start at all, there may be a more fundamental problem. Since it is a .Net Core application, it could be that certain things are not present in the Windows installation that should be present. So I recommend to reinstall the image first and check if it works then. ... View more

Hello, could you please check if there is a _log folder (C:/OpconApp/SecurityManager/_log/ ) in the application directory of the service with current log files? If the service has an error, the error is written out here. Maybe you can find out where exactly the problem is. ... View more

The error is definitely not coming directly from DataSetAccess.... Currently I can't say exactly where the error comes from. Please check the running services and also the running tasks in the task manager if there is anything duplicated. And there are two logs in the DataSetAccess folder. The log folder of the service main instance and then a log in the config folder of the respective instance (normally only one, but several are also allowed). Please check both logfiles if there are also error entries at the same time stamps.  ... View more

Can you check again for exact verification which certificate has made the problem here? If you could send it to the support shortly, we would check once whether one can avoid these errors in the future. Concerning the startup behavior of the client, there is probably a problem that the autostart cannot be written to the registry. In this case you can find a remedy by copying a shortcut to the client into the autostart folder of Windows. There is already a workaround for this problem, which will be fixed with the next release. ... View more