You mentioned 'reporter' DB somewhere on above. Do you have Veeam One also installed on same P/V by any chance? I think yes bcz 'reporters' db name is of Veeam One and not BEM from my memory. The upgrade order is> VBEM, Veeam One and then VBR. I just upgraded successfully from BEM 11.0.x to BEM 12.2 and no issues after that i.e. VBEM communicated with 13 VBRs out there at v11.0.x (i.e. data collection went fine), and also with Veeam One at v11.0.x (all sql express). My VBEM and Veeam One are on same VM (but no VBR on it). Next when i ugpraded Veeam One from v11.0.x to V12.2 (it was successfull upgrade & i was happy), i launched veeam one client and was able to see my 13 VBRs, data, etc. but i had a issue with reporter as it would never launch on port 1239 (default for Veeam One). Tried all options. 'Reports' from within Veeam One client won't launch either. Firewall was off, ports were open but no luck. But i felt relieved when SSMS had my reporter DB instance in it present, so i knew i had all the reports intact but couldn't launch the report from SSMS bcz customer did not had access to the DB (different issue). Net-net: Firefox on port 1239 worked & chrom worked on port 2741 but not on 1239. First, make sure you take your backups of VBEM and/or Veeeam one also via SSMS. Also, if it's a VM, take its snapshot.
Statistics: Posted by ssdn108 — Sep 09, 2024 1:49 am
