-
- Novice
- Posts: 4
- Liked: never
- Joined: Jun 21, 2021 11:15 am
- Contact:
Error: "Timed out requesting agent port for client sessions." (CASE ID 04916794)
Hello everyone!
I'm using Veeam B&R as well as Veeam Agent for several customers and within my own infrastructure for many years now. It keeps me happy für 98% of the time.
But now using Agent 5.0.0.4301 on one desktop causes strange trouble - I never encountered similar problems on this machine and it has been backuped with Veeam Agent since version 1.5.
System is a Windows 10 Enterprise 21H1 machine with AMD Ryzen and 32GB RAM. It should do file level encrypted backup to a local NAS.
I am always encountering:
"Error: Timed out requesting agent port for client sessions. --tr:Failed to initialize agent ( specified agent path: [C:\Program Files\Veeam\Endpoint Backup\x64\VeeamAgent.exe], arguments: [ -g"2500-5000" -i"{fd77a8ad-1426-4acf-b8f3-cceb77c68646}" -l"flush,C:\ProgramData\Veeam\Endpoint\Komplettsicherung/Agent.Komplettsicherung.Target.log" --fipsMode -f 25 --vddkLogLevel 1 --maxPendingBlocks 10000 -n -x"{ac9abd52-c11c-4f32-a833-8bb7f4ebc479}" --mgmtConnKey "AQAAAAAAAAAjAAAATWFuYWdlciB0byBBZ2VudCBjaGFubmVsIGV"
Logfile says: "ERR |'Failed to enter FIPS 140-2 mode of operation' (error:2D07808C:FIPS routines:FIPS_module_mode_set:unsupported platform)".
Solutions I already tried:
- deleting and rebuilding the backup job
- recreating Veeam's database via registry
- un- and re-installing Veeam Agent completely
Nothing of these changed the situation, but if I downgrade to Version 4.0.1.2169 the problem disappears.
Any help would be appreciated!
I'm using Veeam B&R as well as Veeam Agent for several customers and within my own infrastructure for many years now. It keeps me happy für 98% of the time.
But now using Agent 5.0.0.4301 on one desktop causes strange trouble - I never encountered similar problems on this machine and it has been backuped with Veeam Agent since version 1.5.
System is a Windows 10 Enterprise 21H1 machine with AMD Ryzen and 32GB RAM. It should do file level encrypted backup to a local NAS.
I am always encountering:
"Error: Timed out requesting agent port for client sessions. --tr:Failed to initialize agent ( specified agent path: [C:\Program Files\Veeam\Endpoint Backup\x64\VeeamAgent.exe], arguments: [ -g"2500-5000" -i"{fd77a8ad-1426-4acf-b8f3-cceb77c68646}" -l"flush,C:\ProgramData\Veeam\Endpoint\Komplettsicherung/Agent.Komplettsicherung.Target.log" --fipsMode -f 25 --vddkLogLevel 1 --maxPendingBlocks 10000 -n -x"{ac9abd52-c11c-4f32-a833-8bb7f4ebc479}" --mgmtConnKey "AQAAAAAAAAAjAAAATWFuYWdlciB0byBBZ2VudCBjaGFubmVsIGV"
Logfile says: "ERR |'Failed to enter FIPS 140-2 mode of operation' (error:2D07808C:FIPS routines:FIPS_module_mode_set:unsupported platform)".
Solutions I already tried:
- deleting and rebuilding the backup job
- recreating Veeam's database via registry
- un- and re-installing Veeam Agent completely
Nothing of these changed the situation, but if I downgrade to Version 4.0.1.2169 the problem disappears.
Any help would be appreciated!
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Error: "Timed out requesting agent port for client sessions." (CASE ID 04916794)
Windows 10 Enterprise 21H1 Is not officially supported yet. You should to wait for Veeam V11a and the new agents. Should be released in august 21.
Product Management Analyst @ Veeam Software
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jun 21, 2021 11:15 am
- Contact:
Re: Error: "Timed out requesting agent port for client sessions." (CASE ID 04916794)
Alright, thank you Mildur for your posting.
Nevertheless it seems strange to me that Agent 4.0.1 does run on 21H1 and 5.0.0 does not.
Nevertheless it seems strange to me that Agent 4.0.1 does run on 21H1 and 5.0.0 does not.
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Error: "Timed out requesting agent port for client sessions." (CASE ID 04916794)
Some pre-setup checks were added to v5 to block the installation on the 'unknown' Windows builds but we will have remover those in the upcoming update (as well as provide official support for 21H1). Thanks!
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jun 21, 2021 11:15 am
- Contact:
Re: Error: "Timed out requesting agent port for client sessions." (CASE ID 04916794)
Hallo and sorry for reopenig this old thread, but after waiting patiently for 5.0.1.4584 with 21H1 support I am encountering the same error again:
Error: Timed out requesting agent port for client sessions. --tr:Failed to initialize agent ( specified agent path: [C:\Program Files\Veeam\Endpoint Backup\x64\VeeamAgent.exe], arguments: [ -g"2500-5000" -i"{a7c9364d-308e-41a9-b52b-bb2208f01bac}" -l"flush,C:\ProgramData\Veeam\Endpoint\Komplettsicherung/Agent.Komplettsicherung.Target.log" --fipsMode -f 25 --vddkLogLevel 1 --maxPendingBlocks 10000 -n -x"{4b58e80f-cd50-444b-99ce-08a61150940a}" --mgmtConnKey "AQAAAAAAAAAjAAAATWFuYWdlciB0byBBZ2VudCBjaGFubmVsIGV
Since I opened this case I mitigated the problem by using version 4.0.1.2169 and it worked flawlessly.
What is wrong with agent version 5 and my system?
Error: Timed out requesting agent port for client sessions. --tr:Failed to initialize agent ( specified agent path: [C:\Program Files\Veeam\Endpoint Backup\x64\VeeamAgent.exe], arguments: [ -g"2500-5000" -i"{a7c9364d-308e-41a9-b52b-bb2208f01bac}" -l"flush,C:\ProgramData\Veeam\Endpoint\Komplettsicherung/Agent.Komplettsicherung.Target.log" --fipsMode -f 25 --vddkLogLevel 1 --maxPendingBlocks 10000 -n -x"{4b58e80f-cd50-444b-99ce-08a61150940a}" --mgmtConnKey "AQAAAAAAAAAjAAAATWFuYWdlciB0byBBZ2VudCBjaGFubmVsIGV
Since I opened this case I mitigated the problem by using version 4.0.1.2169 and it worked flawlessly.
What is wrong with agent version 5 and my system?
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Error: "Timed out requesting agent port for client sessions." (CASE ID 04916794)
NoBackupNoMercy,
Any chance you've raised another case with the logs from newly installed v5.0.1? Please share the case ID and I'll ask QA team to take a look. Thank you in advance!
Any chance you've raised another case with the logs from newly installed v5.0.1? Please share the case ID and I'll ask QA team to take a look. Thank you in advance!
Who is online
Users browsing this forum: No registered users and 19 guests