Latest Version (3.2.1016) issue with installing CloudPanel Service

Reviving an older topic. 3.2.1016 Service will not install with AD account granted Log On as Service perms period. Not administrator or equivalent. Fails with unknown user or bad password. 3.2.1007 installs without issue.

Server & SQLExpress 2022. Log attached; remove the .jpg

The user installing it needs permission to the SQL server and the service account you are using needs log on as a service. Since it is failing with unknown user or bad password, when that happens, please open services.msc and manually edit the username & password on the “CloudPanel Service” it created. Once you do that and save, it probably will prompt that it granted it log on as a service rights and you can start it.

If you have a GPO setting log on as a service rights, it will strip that out and it won’t start next time. So if you are setting that with a GPO, make sure to add the service account you are using to the list.

Administrator is installing. Confirmed AD\CloudPanel account has been granted “Log on as service” via Local Security. I install 1007 w/out issue and same creds. Tried to update to 1016 and it fails… so editing creds in Services??? it is already there and functional. This is greenfield install. New domain, new exchange, etc. Old CP instance updated to 1016 w/out this issue. All same except Server 2019 and Dev SQL. This one is 2022 and SQL Express.

FYI in the log there is a dozen or more repeated “Changing password …” for the service account I assume. So perhaps there is when to edit services. I’ll try.

Editing the creds in Services worked.

Yes, tried that. Also tried:

-resetting password to that service account,

-trying to run Service under different account.

All attempts failed with same result: “Service does not start and fails with privilege error.”

That sounds like the user you are using doesn’t have log on as a service rights, but if it was using it before, it must have it. Can you export your Application event logs and C:\Program Files (x86)\Know More IT\CloudPanel Service\logs and send to support@knowmoreit.io?

It does work with same account and older version of service.

Will send logs shortly.

Hello,

Same issue here. In the application log in event viewer it returns:

Service cannot be started. System.IO.FileNotFoundException: Could not load file or assembly 'log4net, Version=2.0.17.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a' or one of its dependencies. The system cannot find the file specified.
File name: 'log4net, Version=2.0.17.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a'
at CPService.CPService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

and

Application: Scheduler.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
   at CPService.CPService.OnStart(System.String[])
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
   at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])
   at CPService.Program.Main()

and

Faulting application name: Scheduler.exe, version: 3.2.1016.0, time stamp: 0x66f62ba6
Faulting module name: KERNELBASE.dll, version: 10.0.20348.2849, time stamp: 0x428f05d7
Exception code: 0xe0434352
Fault offset: 0x00139332
Faulting process id: 0x22d0
Faulting application start time: 0x01db439bebf4220a
Faulting application path: C:\Program Files (x86)\Know More IT\CloudPanel Service\Scheduler.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: e5967ee1-87da-414e-bfe4-7d1d648c5129
Faulting package full name: 

These are different issues, but for yours, I would recommend a uninstall of the service and install it again. If you want to check the root cause, open the Scheduler.exe.config file in notepad and look for the <runtime> section. I believe this value is missing and would need to be added back:

Ooops I just see your answer now. Thanks a lot for it. I went the same path as suggested and it resolved the issue 🙂