Could be Firewall related. If you are utilising Windows Firewall, check it is not blocking VEM from making outbound communications on those ports. 

Thats the reason I said that I already test communication between VEM and VBR.

If any firewall is crossing this connection my telnet test on ports 9392 and 9405 would be not ok I presume

@wolff.mateus  Have you checked all used ports for EM as dcoumentation?

https://helpcenter.veeam.com/docs/backup/em/used_ports.html?ver=120

Sometimes you can get Windows Firewall blocking the application itself so telnet will work but traffic from the Application will be blocked. 

Firewall windows is disable now.

I found this on logs:

3:28.504] <29> Info         Adding server [BKPSRVXXX. under [bs4it]
[21.03.2023 17:43:28.510] <29> Info         Connecting to backup server "BKPSRVXXX".
[21.03.2023 17:43:28.969] <29> Info         Obtain version of backup server "BKPSRVXXX".
[21.03.2023 17:43:29.020] <29> Info         Version is "12.0.0.1420".
[21.03.2023 17:43:29.113] <29> Warning      Failed to open session.
[21.03.2023 17:43:29.651] <29> Error        Error adding backup server info. SessionId: [dc0d2d8d-1e1a-4ab1-9691-49aae2a5f9ad], ServerInfo: [BKPSRVSXXX:9392, vVeeam.Backup.Interaction.Reporting.CVbServerVersion, bs4it]
[21.03.2023 17:43:29.651] <29> Error        Failed to connect to backup server "BKPSRVSXXX". (Veeam.Backup.Common.CRegeneratedTraceException)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.Common.CExceptionUtil.RegenTraceExc(Exception originalExc, String formatString, Object[] args)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollectorLib.CVbSrvDialer.ConnectToBackupSrv(CVbServerCfg srvCfg, X509Certificate2 certificate)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.Enterprise.Core.CBackupServersDataSource.AddServerInfo(CVbServerInfo serverInfo, Boolean force, Boolean overrideOldEM)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseServices.CEnterpriseWebService.AddBackupServerInfo(CEnterpriseSessionId sessionId, CVbServerInfo serverInfo, Boolean force, Boolean overrideOldEM)
[21.03.2023 17:43:29.651] <29> Error        Failed to open session. (System.Exception)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollector._61.CEmToVbrProxy.WrapMethodCalling[t](Func`1 func, EndpointAddress remoteAddress)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollector._61.CWcfVbSrvSessionRetryableWrapper`1.<>c.<ObtainSession>b__4_0(T p)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.Common.CWcfRetryableProxy`1.Invoke[u](Func`2 func)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollector._61.CWcfVbSrvSessionRetryableWrapper`1.ObtainSession()
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollector._61.CVbSrvSession.<>c__DisplayClass3_0.<.ctor>b__0()
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Common.Remoting.CRemoteObjRefResolver.Initialize()
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollector._61.CVbSrvSession..ctor(IVbSrvSessionRetryableWrapper sess, Version vbSrvVersion, CProductApiVersion vbrApiVersion)
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollector._61.CVbSrvWcfServiceProxy.Veeam.Backup.EnterpriseCollector.Common.IVbSrvService.OpenSession()
[21.03.2023 17:43:29.651] <29> Error           at Veeam.Backup.EnterpriseCollectorLib.CVbSrvDialer.ConnectToBackupSrv(CVbServerCfg srvCfg, X509Certificate2 certificate)

Are you trying to connect to a V11 or V12 VBR server?

VEM v12 connecting VBR v12.

Both running PG database.

In your log it looks like VEM is trying to connect to port 9392 although V12 is using 9405. On the VBR server can you check which process is actually listening in that port?

Is the VBR server able to accept connections? I’m guessing you tried connecting using FQDN and IP with the same result?

On v12 is used only 9405?

I can see both ports on netstat:

Yeah, same result by fqdn or ip. 

mmmmm I think there is a database issue…. is VBR server new as EM or is an upgrade version?

And, sorry for stupid question, are both db SQL server?

This log is not so descriptive enough (perhaps, I am looking at it via by handy)! Since you have eliminated connectivity issues, perhaps the event log can help. 

• Are all the Services running?! 

Please take a look at the Event log of both servers.

@Andanet, he said both are ruining PG!

I have also seen this in my homelab where the FQDN did not work, but IP did.  I would check your DNS to ensure you can resolve the FQDN from the VEM server.  I had to make adjustments to my DNS stuff.

Try using the IP address instead of FQDN.

I think there is a bug with PG with this for some reason, as I saw this in my lab.  I cannot recall if I tested it with GA release or if it was RTM.

The same happening by IP address. I both multiple VBR servers too.

I need to fix a license trouble on this customer yet. After that, I will open a case for support.

Yeah, it will be interesting to see what support says so post back here since I ran in to the same problem and just fiddled through to fix it.  

I had the same problem with v12 in my home lab. To resolve it using FQDN\IP, I explicitly defined the user I was attempting to use to add the Backup Server to Enterprise Manager as a Backup Administrator within Veeam Backup and Replication under Users and Roles. I then removed the Built-in Administrators Group.

Hope this helps!

Nailed it! You were right on your answer. It worked here too.

Thanks!

It is interesting that it is taking this into account now in v12.  I wonder if it relates to the new MFA piece and why you need to do this.  

I had the same problem when I upgraded from v11 to v12 using SQL DB. Before troubleshooting, my Veeam server died and I rebuilt Veeam from scratch on a new server last night with PG database and had the same issue. Totally clean install with no restore from old Veeam server backup config. 

So an issue when using PG as a database. Good to know.

Might be worth letting Veeam Support know as well

No, the issue existed for me before using PG database.

Hello 

Can anyone tell me why am i getting this error on my server 

Hello 

Can anyone tell me why am i getting this error on my server 

 

Could you check if Veeam Enterprise Manager services are running?