Antivirus uninstalled and server rebooted.
But first problem is already back : Scheduler OFF, and service won't restart.
And Guardian is not installed.
In the Event Viewer :
- Event ID 7009 : service restart waiting for more than 45000 milliseconds.
- Event ID 7000 : Syncovery_Service could not start.
Problems on Windows Server 2025
Re: Problems on Windows Server 2025
Questions:
- does the service have a user account assigned, or will it be running under the SYSTEM account?
- does the service have a user account assigned, or will it be running under the SYSTEM account?
Re: Problems on Windows Server 2025
Running under SYSTEM account (in order to allow backup of RedirectedProfiles).
Re: Problems on Windows Server 2025
- can you stop the service and uninstall it and try the Background Scheduler instead, does that work?
- do you still have Windows Explorer problems, or is it just the service now?
- do you still have Windows Explorer problems, or is it just the service now?
Re: Problems on Windows Server 2025
Service uninstalled, and background scheduler started.
I will check tomorronw morning if all backup tasks have been started.
Till now, there is no Explorer problem.
I will check tomorronw morning if all backup tasks have been started.
Till now, there is no Explorer problem.
Re: Problems on Windows Server 2025
OK, if the user account that you are logged in with has sufficient permissions, the jobs should work. Otherwise not.
We can surely debug the starting of the service with advanced logging and/or remote assistant. Please contact me via the support email address if problems remain.
Thanks!
We can surely debug the starting of the service with advanced logging and/or remote assistant. Please contact me via the support email address if problems remain.
Thanks!
Re: Problems on Windows Server 2025
It is a File&Print server : there are never any user logged in (except for maintenance) !
And even if an Admin user is logged, he cannot access to the RedirectedFolders of the users (private access).
That's why SYSTEM account is used.
And even if an Admin user is logged, he cannot access to the RedirectedFolders of the users (private access).
That's why SYSTEM account is used.
Re: Problems on Windows Server 2025
OK please contact me via the support email address.
Re: Problems on Windows Server 2025
Syncovery version 11.2.0 has been released today, fixing the problem where the service could not start.
The “Install Service” button will now install SyncoveryCL.exe as the scheduler service, as opposed to SyncoveryService.exe. SyncoveryCL.exe will start up quicker and is more compliant and compatible with Windows Server 2025, as it does not use any hidden window handles and contains zero GUI related code – in contrast to SyncoveryService.exe, which doubles as a Background Scheduler with some basic GUI features (such as the tray icon and a status window).
The “Install Service” button will now install SyncoveryCL.exe as the scheduler service, as opposed to SyncoveryService.exe. SyncoveryCL.exe will start up quicker and is more compliant and compatible with Windows Server 2025, as it does not use any hidden window handles and contains zero GUI related code – in contrast to SyncoveryService.exe, which doubles as a Background Scheduler with some basic GUI features (such as the tray icon and a status window).