Error: Sequence contains no elements

[johnbo]

Backing up using veeam agent for windows and backing up to Microsoft One Drive after a few minutes I get this error : Error: Sequence contains no elements
I've included a pic

[HannesK]

Hello,
for technical issues please contact support. Please post the case number for reference.

Best regards,
Hannes

[johnbo]

That's funny I thought the forums helped in that..LOL

[HannesK]

well, this is not a support forum... please see the forum rules

[Dima P.]

Hi johnbo,

The error you've shared shows us that something went wrong on a 'low level', so debug log analysis is required. Free version provides best effort support, so it should be possible for you to raise a support case via Veeam Agent for Windows UI: Control Panel > Support. Please let us know once you have a case ID to share. Thank you in advance!

[johnbo]

Ive posted the question to support yesterday, haven't received an answer yet..

[Dima P.]

johnbo,

Can you please share the case ID? I'd ask QA team to review the logs just in case. Thanks!

[itnotificationhlw]

Hello there,

I know this is a rather old post but I got the same error today after upgrading to the latest Veeam 12.0.0.1420 P20230223. I got the error while running backup copy jobs and opened a support ticket as per your suggestion. Just for reference: the case number is #05931080.

Regards
Ingo

[narf0815]

Same here with few jobs. Not only with windows agent.

[CarloG]

Hello there,
after migrating from v11.0.1.1261 P20230227 to 12.0.0.1420 P20230223 all backup job fails with same error.
Also from new backup job, noyt migrated but create after migration fails with same error: Unable to allocate processing resource. Error: Sequence contains no elements

Regards
Carlo

[CaptinJack]

Google brought me here, same issue after updating v12 to patch P20230223.

Support case opened.

[frankive]

Google brought me here too, same issue after updating v12 to patch P20230223.

Support case opened. #05940804

[BastianR82]

Same problem here after update to 12.0.0.1420 20230223: Veeam Agent Backup fails with "error: Unable to allocate processing resources. Error: Sequence contains no elements". Case-Nr. is 05940857.

Best regards,
Bastian

[Mildur]

Hi @narf0815 @CarloG @CaptinJack

Can you please share your case number with us?

Best,
Fabian

[CaptinJack]

@Mildur

05938983

[joris3112]

@Mildur
Same problem here after update to 12.0.0.1420 20230223: Veeam Agent Backup fails with "error: Unable to allocate processing resources. Error: Sequence contains no elements". Case-Nr. is 05941011.

[Mildur]

Hi guys

Thanks for the case numbers. I will discuss the cases with support management.

In the mean time, can you answer me a question?
Are you using a SMB Share, Dedup Appliance or Object Storage as a backup copy target?
If yes, please disable "automatic gateway server" selection in your repository properties and choose your gateway server you want to use:
https://helpcenter.veeam.com/docs/backu ... #smb-share
After that change, please run the backup copy job again.

Another thing which everyone could check, if backup copy jobs works with specifying a Gateway Server, but automatic selection not.
- Is the same server added twice in Veeam as a managed server? Once per IP, once per Hostname?
Adding the same server twice will lead to a known issue with automatic gateway selection.


Thanks,
Fabian

[frankive]

I am running object storage (Wasabi Immutable) as target for the backup copy job.

[Mildur]

Then I suggest as a workaround to change connection mode from "direct" to "chosen Gateway Server" and try again.

Another thing which everyone could check, if automatic selection does not work for them:
- Is the same server added twice in Veeam as a managed server? Once per IP, once per Hostname?
Adding the same server twice will lead to a known issue with automatic gateway selection.



Best,
Fabian

[frankive]

the gateway server is set to manually gatewayserver, and not direct on my installation.
the server is indeed listed twice, once in Microsoft Windows and one Microsfot Hyper-V (all in one install server).
but the server is registered with dns, not ip on both.

[BastianR82]

If yes, please disable "automatic gateway server" selection in your repository properties and choose your gateway server you want to use:

Changing gateway server from automatic to specific one (local host in my case) did the trick for me.
Was using Agent Backup to Synology NAS via NFS.

Thank you!
Bastian

[joris3112]

Indeed, disabling the choice of gateway in automatic mode is the solution on my side. It works !
Thank you so much !

[GT-Engineer]

The below happened to me upon upgrading to 12.x. But the suggested fix seems to have worked perfectly.

Hi guys

Thanks for the case numbers. I will discuss the cases with support management.

In the mean time, can you answer me a question?
Are you using a SMB Share, Dedup Appliance or Object Storage as a backup copy target?
If yes, please disable "automatic gateway server" selection in your repository properties and choose your gateway server you want to use:
https://helpcenter.veeam.com/docs/backu ... #smb-share
After that change, please run the backup copy job again.

Another thing which everyone could check, if backup copy jobs works with specifying a Gateway Server, but automatic selection not.
- Is the same server added twice in Veeam as a managed server? Once per IP, once per Hostname?
Adding the same server twice will lead to a known issue with automatic gateway selection.

Thanks,
Fabian

[John.Smith]

Hello,

this hint seems to solve my issue, but i have the same Server twice for selecting a gateway server.
But i have this server only one time in managed servers (OK twice, because Veeam is installed on the server itself. The Server is Hyper-V and File-server at the same time) and i run Backups from Hyper-V and Fileservices.
Could this be the issue?

[lrdurda1]

Running into this error on several jobs - primarily ones that are now labelled "Legacy" in console since recent upgrade to Veeam12 and consistently jobs targeting our Cloud Service Provider repository.

Tried disabling Automatic Gateway Server settings and setting to static gateway per the resolution mentioned on some of these posts, however this option is completely greyed out for the Service Provider in question. Any reason for that? I'm sure our cloud service provider is allowing connections from the internet properly as I have 30+ other consoles pointed at it, including some which have already been updated to Veam12.

Any assistance appreciated, thanks!

See case #05943221

[dshah]

I am having the same issue ever since I have upgraded to V12. Our offsite backups (Synology Device) and cloud backups are not working. I tried changing the gateway to manual from automatic and that didn't fixed it for me. I only have one managed server. Any other possibilities that I can try?

Case#: 05928162

[CarloG]

@Mildur suggested tricks seems working for me
After disabling "automatic gateway server" selection in my repository properties and choose a gateway server backup jobs seems work correctly

I don't know why I have the backup server twice in inventory (one with name and one with ip address)
Thanks for suggestion

[nexusdis]

Hello there,
after migrating from v11.0.1.1261 P20230227 to 12.0.0.1420 P20230223 all backup job fails with same error.
Also from new backup job, noyt migrated but create after migration fails with same error: Unable to allocate processing resource. Error: Sequence contains no elements

Regards
Carlo

same here
Backup jobs are working, but no backup copy job runs.

[Mildur]

@nexusdis
Have you tried the mentioned workaround?

[nexusdis]

workround solved these problem. thx