Skip to main content
Solved

Error pushing agent to windows server 2012 r2


Morning all,

Am getting this error when trying to push agent to win svr 2012 r2 :

Error 1920. Service <display_name> (<service_name>) failed to start. Verify that you have sufficient privileges to start system services.

I have tried the solutions given in KB1059 but still fails, anyone with idea how to solve this?

 

Regards,

Best answer by Iams3le

Furthermore, 1920 error code that means that the service refused to start! I will advise re-entering the password in the service's log-in information. Here is an example on how this is done: https://techdirectarchive.com/2022/02/24/no-connection-can-be-made-because-the-active-machine-rejected-it-an-exception-occurred-in-the-service-when-handling-the-control-request-error-1064/

View original
Did this topic help you find an answer to your question?

18 comments

JMeixner
Forum|alt.badge.img+17
  • On the path to Greatness
  • 2650 comments
  • May 21, 2022

Are you usimg a domain account or a local account?

Has the account access to the system shares on the target system?

 


  • Author
  • New Here
  • 4 comments
  • May 21, 2022
Kip_ke wrote:

Morning all,

Am getting this error when trying to push agent to win svr 2012 r2 :

Error 1920. Service <display_name> (<service_name>) failed to start. Verify that you have sufficient privileges to start system services.

I have tried the solutions given in KB1059 but still fails, anyone with idea how to solve this?

 

Regards,

@JMeixner i have tried both


JMeixner
Forum|alt.badge.img+17
  • On the path to Greatness
  • 2650 comments
  • May 21, 2022

OK, these two topics are often the cause for this problem.

Which version of the agent are you trying to push to the target system?

 


  • Author
  • New Here
  • 4 comments
  • May 21, 2022

am pushing from VBR v11 so i guess it should be the latest 5.0.3


JMeixner
Forum|alt.badge.img+17
  • On the path to Greatness
  • 2650 comments
  • May 21, 2022

Ok, there are several patch level of V11. The latest is V11a P20220302.

Did you see kb4142? There is a neccessary patch for Windows 2012 mentioned. The agent version mentioned in this article is not the latest, but perhaps give it a try.

https://www.veeam.com/kb4142


  • Author
  • New Here
  • 4 comments
  • May 21, 2022

Yes we applied the patch


JMeixner
Forum|alt.badge.img+17
  • On the path to Greatness
  • 2650 comments
  • May 21, 2022

🙂 Then you should open a support case with Veeam

You can do this even if you are using community version.


Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 603 comments
  • May 21, 2022

Hi @Kip_ke 

  • Have you restarted the sever and resumed installing agent?
  • What errors are or logged in the server event viewer when you try to install agent?

Can you past on the error?
Thank you m8


  • Author
  • New Here
  • 4 comments
  • May 22, 2022

Hello M8,

Attached the errors


MicoolPaul
Forum|alt.badge.img+23

Can you confirm you followed the KB that @Link State mentioned?

 

If so, can you check for logs in C:\programdata\veeam as these should be most relevant.


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1377 comments
  • May 23, 2022

@Kip_ke, kindly take a look at this guide: https://www.veeam.com/kb1059. All what have been suggested and many more possible solutions are available in the guide. Some of which are

  • Restart pending on the server due to applied windows update
  • Antivirus may be preventing the service from starting. See KB1999 etc

MicoolPaul
Forum|alt.badge.img+23

@Iams3le that KB is for VBR whereas this seems agent related, but the KB does link to KB4142 which is more relevant for agents. The error is the transport service not starting based on those screenshots too.

 

We need more info!


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1377 comments
  • Answer
  • May 23, 2022

Furthermore, 1920 error code that means that the service refused to start! I will advise re-entering the password in the service's log-in information. Here is an example on how this is done: https://techdirectarchive.com/2022/02/24/no-connection-can-be-made-because-the-active-machine-rejected-it-an-exception-occurred-in-the-service-when-handling-the-control-request-error-1064/


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1377 comments
  • May 23, 2022
MicoolPaul wrote:

@Iams3le that KB is for VBR whereas this seems agent related, but the KB does link to KB4142 which is more relevant for agents. The error is the transport service not starting based on those screenshots too.

 

We need more info!

Ops! Thank you very much for pointing this out. I was focused more on the error code as possible suggestions mentioned could help him resolve it. 


JMeixner
Forum|alt.badge.img+17
  • On the path to Greatness
  • 2650 comments
  • May 23, 2022

And he said that he has applied the patch suggested in KB4142 😀

So, we definitely need more information 😎


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1377 comments
  • May 23, 2022
JMeixner wrote:

And he said that he has applied the patch suggested in KB4142 😀

So, we definitely need more information 😎

I agree with you😀! Good to know some of these have been suggested before. We need to hear from @Kip_ke on how he is resolving this generic Error 1920 code! This is very vital…  


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • May 24, 2022

If anything else was already did, this seems an error that got resolved just by reboot server.


Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 603 comments
  • May 24, 2022
Link State wrote:

Hi @Kip_ke 

  • Have you restarted the sever and resumed installing agent?

 

marcofabbri wrote:

If anything else was already did, this seems an error that got resolved just by reboot server.

😜


Comment