SecurityManager is not starting

[tommy3000]

Hello together

I have a little problem with my SecurityManager on my station.

The client does not start.

Logfile:

17:14:28.4040|Microsoft.Hosting.Lifetime|INFO|Application is shutting down...
2022-02-09 17:14:59.3503|Bosch.Nexeed.Automation.SecurityManager.Program|DEBUG|init Program.Main
2022-02-09 17:15:00.1845|Bosch.Nexeed.Automation.SecurityManager.Worker|INFO|=----=----=----=----=----=----=----=----=----=----=----== Bosch.Nexeed.Automation.SecurityManager (1.0.0.0)=----=----=----=----=----=----=----=----=----=----=----=
2022-02-09 17:15:00.2427|Bosch.Nexeed.Automation.SecurityManager.Worker|ERROR|Cannot find the requested object.
2022-02-09 17:15:00.4580|Microsoft.Hosting.Lifetime|INFO|Now listening on: http://localhost:61227
2022-02-09 17:15:00.4580|Microsoft.Hosting.Lifetime|INFO|Application started. Hosting environment: Production; Content root path: C:\OpconApp\SecurityManager\

Can you give me a hint, what I've done wrong?

I already tried several times deploying the standard, but still same behavior.

Thanks in advance

[Andreas_Sievers]

The cause of the error message will probably be a certificate located in the certificate folder.
Please remove the certificates from the certificate folder (C:\NexeedLocal\Certificates) (move them to another folder) and try to start the app.
Once the error has disappeared, please try to manually add one certificate after the other and test which one causes the problem again.

In the past, MachineHub had a problem with an incorrectly stored certificate, which has been fixed in the newer version of MachineHub.

[tommy3000]

Moving was not possible, because OpcUa folder was always in use.

I moved all the others, after restart the error was gone, but the client ist still not starting.

I deployed the standard completely again and restarted the machine, still same behavior. When I start the client manually, anything looks fine now.

How can I check the startup batches, that anything is deployed correctly?

Thanks

[Andreas_Sievers]

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.

[tommy3000]

The certifacte folder of TcUaServer wasn't possible to move.