Custom driver as a service

[adaneau]

Hi,

I have created a custom driver and a custom manager and they run fine as a managers added into console. However as soon as I start the project as a service, then the managers refuse to start without any error, simply immediately stopping.

At first I thought it was permission issue so I made my service account administrator, but that doesn't solve the issue.

I also tried with the default generated driver and the issue is identical. It seems that custom components cannot be started when WinCC OA runs as service. Is this known?

Version 3.18.007 (I know there is issue with NGA but nowhere was stated something about API...)

Thanks in advance

BR
Alex

[leoknipp]

I have seen that also a service request was created with the same question. You will get an answer from the support team.
In future please also one communication channel for your questions.

Best Regards
Leopold Knipp
Senior Support Specialist

[amichon]

maybe it is due to environment variables which are not defined for the user who starts the service?

[adaneau]

Hi,

FYI this is a bug in 3.18.007. Will be solved in next patch.

BR
Alex

[dgi]

Sounds like you have two wincc oa versions installed. I assume because of your "PATH" variable your binaries use the WinCC OA libraries of the wrong installation.

Same problem like here: https://www.winccoa.com/forum/viewtopic ... 84#p969384