WCCILpmon as service Error 1067 occured

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search

Post Reply
7 posts • Page 1 of 1
johanningmann
Posts: 55
Joined: Thu Nov 24, 2016 5:06 pm

WCCILpmon as service Error 1067 occured

Post by johanningmann » Fri Sep 13, 2019 9:58 am

Hello,
we struggling to run WinCC-OA 3.16 P.7 as a service on our Server.
Please find att. the Windows message which occurs after trying to start manually the Service. The Service will not start automatic and if we start manually the att. message pops up. We tried as well to run the service as NetworkService and LocalService, no difference.
Only if we run the service as a local system account the project starts up.

Please find att. the Windows error message and the system information's.

Best regards,
Frank Johanningmann
Attachments
WinCCOA_Network_Service.PNG

User avatar
leoknipp
Posts: 2091
Joined: Tue Aug 24, 2010 5:28 pm

Re: WCCILpmon as service Error 1067 occured

Post by leoknipp » Mon Sep 16, 2019 6:42 am

Can you please check if the service works when using a real user account and not one of the "Service" accounts.

Best Regards
Leopold Knipp
Senior Support Specialist

johanningmann
Posts: 55
Joined: Thu Nov 24, 2016 5:06 pm

Re: WCCILpmon as service Error 1067 occured

Post by johanningmann » Mon Sep 16, 2019 9:06 am

Good Day Mr. Leopold,
we tried to setup a normal user account but unfortunately the system will not progress as expected. Please find att. a picture of the message and the Server System we are using.

Kind regards
Frank Johanningmann
Attachments
try to setup normal user.JPG

johanningmann
Posts: 55
Joined: Thu Nov 24, 2016 5:06 pm

Re: WCCILpmon as service Error 1067 occured

Post by johanningmann » Mon Sep 16, 2019 9:11 am

Central System
Attachments
Central System.JPG

User avatar
schneebergera
Posts: 89
Joined: Sun Apr 03, 2016 3:52 pm

Re: WCCILpmon as service Error 1067 occured

Post by schneebergera » Tue Sep 17, 2019 6:26 am

Hello,

it seems that there is an error during registration of the service
--switch to bin directory of <<WinCCOA-InstallDir>> --> E:\Siemens\Automation\WinCC_OA\3.16\bin
--enter command: WCCILpmon -install -set E:\Siemens\Automation\Central\config\config 1 -name newservice
<<newservice>> ... is a name defined by your own.
<<E:\Siemens\Automation\Central\config\>> ... is the path of your project config

you can easily check the service in registry.
--HKEY_LOCAL_MACHINE/SOFTWARE/ETM/PVSSII/AutoStart

Afterwards it is necessary to assign a "real Account" (the login user who have permission to WinCCOA) ans set the starttyp to "Automatically".


with best regards,
Andreas

johanningmann
Posts: 55
Joined: Thu Nov 24, 2016 5:06 pm

Re: WCCILpmon as service Error 1067 occured

Post by johanningmann » Wed Sep 25, 2019 8:03 am

Dear Mr. Knipp,
we managed now to run the pmon as Service with an normal corporate domain User. We entered the user in the Windows user group of the server and put the user to the administrator group. We removed the old service by using the console and install the pmon as service with the corporate user. We restart the system and the pmon started automatically.

But still the question left: Why is the Network Service account not working. We run now about ten Nanoboxes (Win10 or WIn7)) as distributed system and the account for the service pmon is NetworkService and on the central Server (2012) it is not working.

Do you have maybe any further idea where we have to look for a solution? We would like to setup the central machine in the same manner like the Nanoboxes and according to the WinCC OA help.

Best regards,
Frank Johanningmann

User avatar
leoknipp
Posts: 2091
Joined: Tue Aug 24, 2010 5:28 pm

Re: WCCILpmon as service Error 1067 occured

Post by leoknipp » Wed Sep 25, 2019 1:13 pm

The error code 1067 is an information given by the operating system. This is not an error code generated by WinCC OA.
Possibly your system administration can give you more information for this error code.
Maybe there a differences in Windows between a Server 2012 and Windows 7/10 which leads to the different behaviour.

Best Regards
Leopold Knipp
Senior Support Specialist

Post Reply
7 posts • Page 1 of 1