Skip to main content
  • EN

Hello, I want to run backup job, which was already working. It was (dont know how) interrupted, but when I run job manually or with scheduler automatically.

Actual version: 8.1.0.3503

Starting job: M365 backup...
[03.03.2025 11:52:52.261]      8 (1) Error: The job is already running.
03.03.2025 11:52:52.261]      8 (1) Type: System.ServiceModel.FaultException
<03.03.2025 11:52:52.261]      8 (1) Stack:
c03.03.2025 11:52:52.481]      1 (1) Error: The job is already running.
n03.03.2025 11:52:52.481]      1 (1) Type: System.ServiceModel.FaultException
E03.03.2025 11:52:52.481]      1 (1) Stack:
103.03.2025 11:52:52.481]      1 (1)    at Veeam.SPP.Communication.TypeProvider.InvokeResult.ThrowIfError(Boolean enableRpcErrors)
03.03.2025 11:52:52.481]      1 (1)    at Veeam.SPP.Communication.TypeProvider.InvokeResult.GetResultOrException(Boolean enableRpcErrors)
o03.03.2025 11:52:52.481]      1 (1)    at Veeam.SPP.Communication.TypeProvider._RemoteProxy.Invoke_TReturn_WithParametersoTReturn](InvokeArg invokeArg, String methodName, Objecto] parameters)
d03.03.2025 11:52:52.481]      1 (1)    at VCF.RuntimeAssembly.Proxy.1d24188e-84fc-4fec-9f0b-6c4bed4924cf.GetIntTaskResult(Guid)
b03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Client.Services.ArchiverAdminConnection.GetIntTaskResult(Guid taskId)
n03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Client.Services.Wrappers.ArchiverAdminWrapper.GetIntTaskResult(Guid taskId)
A03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Client.Tasks.ArchiverRemoteTask`1.ArchiverRemoteTaskContext.GetResult()
o03.03.2025 11:52:52.481]      1 (1)    at Veeam.Engine.Communication.RemoteTask.ConnectionTrackerDecoratorForRemoteTaskContext`1.GetResult()
o03.03.2025 11:52:52.481]      1 (1)    at Veeam.Engine.Communication.RemoteTask.RemoteTask`1.GetResultFromServer()
m03.03.2025 11:52:52.481]      1 (1)    at Veeam.Engine.Communication.RemoteTask.RemoteTask`1.SafeSetResult()
m03.03.2025 11:52:52.481]      1 (1) --- End of stack trace from previous location ---
]03.03.2025 11:52:52.481]      1 (1)    at Veeam.Engine.Communication.RemoteTask.RemoteTask`1.GetResultAsync()
a03.03.2025 11:52:52.481]      1 (1)    at Veeam.Engine.Communication.RemoteTask.RemoteTask`1.GetResultAsync(CancellationToken cancellationToken)
R03.03.2025 11:52:52.481]      1 (1)    at Veeam.Engine.Communication.RemoteTask.RemoteTask`1.GetResult(CancellationToken cancellationToken)
u03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Client.Services.ArchiverAdminClient.StartJobs(IReadOnlyCollection`1 startConfigs, FullSyncConfig fullSyncConfig, CancellationToken cancel)
l03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Shell.MainWindow.Organizations.Tasks.StartJobsAsyncTask.Run(IProcessObserver observer, CancellationToken cancellationToken)
s03.03.2025 11:52:52.481]      1 (1)    at Veeam.Presentation.Async.VisualAsyncTask.Execute(IProcessObserver observer)
03.03.2025 11:52:52.481]      1 (1) --- End of stack trace from previous location ---
e03.03.2025 11:52:52.481]      1 (1)    at Veeam.Presentation.Async.VisualAsyncTask.VerifyTask()
/03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Shell.List.JobsActionsController.StartJobs(IEnumerable`1 jobs)
:03.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Shell.List.JobsController.StartJobs(IEnumerable`1 jobs)
303.03.2025 11:52:52.481]      1 (1)    at Veeam.Archiver.Shell.List.JobsCommandsViewModel.Start()
e03.03.2025 11:52:52.481]      1 (1)    at Veeam.Core.AsyncSafe.Call(Action action)
J03.03.2025 11:52:52.481]      1 (1)    at Veeam.Presentation.ViewModel.SafeCommand.SafeCall(IMessageService messageService, Action commandAction)

It looks like the job is stuck or a previous session hasnt finished properly. This can happen if a backup or replication task is still running in the background, or if a previous job didnt close correctly.

Have you tried restarting the Veeam services or checking for any active VeeamAgent.exe processes in Task Manager? You might also want to review the logs for more details on whats causing this.

Since you mentioned in the post that the job was interrupted, it seems like its not just a stuck process. Have you checked if there are any orphaned sessions in the Veeam console? Sometimes, even after a job is stopped, a hidden session can still be running in the background.

Can you provide more information about your setup? For example, does this happen with a specific job or multiple jobs?

 

You can also open a case with Veeam support.

Hi ​@pdolejsi ,

have you tried the solution suggested in this R&D post?

https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/jobs-looks-to-be-stuck-and-won-t-run-t95478.html

Thanks

Hi ​@pdolejsi ! 
 

I would like to know if you were able to execute any of the suggested options or if you managed to resolve the issue. If you were successful, please share with us what you did, its always helpful to know solutions in similar scenarios so that, if it happens again, we’ll know which path to follow. If you’re still facing issues, please send us more information about the environment, routines, and logs, it’s going to be a pleasure to help you.

It's just set one job, there are no other jobs. Periodically runing at 11 pm every day.

I found, that there was problem with permissions for application in Microsoft 365, but after fix of this (I tried to edit organisation settings, now its working). Dont know why it worked for years, if there was permission problem.

I restarted the whole server and all services separately, too.

But still i cant to run job.

On same server is Backup & Replication. No other app is there installed. Windows is updated, Veeam M365 is updated, too.

The job might be stuck in a queued or pending state. Try stopping all Veeam services, clearing the job queue by deleting the contents of the streams folder located at C:\ProgramData\Veeam\Backup365\nats\jetstream\$G, and then restarting the services.

The job configuration might be corrupted. Consider recreating the backup job to eliminate potential configuration issues.

 

After this try, I cannot start “Veeam Backup for Microsoft 365 Service” and in log is that:

>04.03.2025 14:59:42.722]     11 (1) Deleting streams without a proxy pool...
<04.03.2025 14:59:42.725]     11 (1) Streams without proxy pool are deleted
e04.03.2025 14:59:42.851]     18 (1) Error: LogFailedServiceInitialize

Hi ​@pdolejsi ,

maybe is better to reach the support team.

Let us know, thanks.

Comment


Terms & Conditions