+21There could potentially be bug in the RTM v13 release for those that have access to it and are MSPs. After upgrading a test box in my environment, the API/Web Services are not starting for me.
I updated from 12.3.2 version and now have a case open. I know
I will post an update to this thread once I get more details from Support and possible fixes, etc.
+1I upgraded my test environment, and I had no issues. Services, including API Service, are running fine. So maybe not everyone is affected.
Do we have any reports from service providers who already upgraded cloud connect infrastructures?
+21Yeah I am not sure if it was the 12.3 to 12.3.2 before the RTM that caused it but support is working with me on a case. Today I will test upgrade again from 12.3.2 to RTM and I am guessing it will work fine. It is odd but this was a DEV box I hadn't used for quite a while. I just don't want to see it in PROD if we update especially for VCC.
Had a similar problem in my Lab environment. The upgrade itself seemed to work fine, but 2 services did not start at the end. Couldn’t log in to the console afterwards. I have since reverted to a previous snapshot.
This server also has Enterprise Manager installed, and a couple of storage plugins (PureStorage and Dell Compellent, both latest versions of the plugins)
+21Had a similar problem in my Lab environment. The upgrade itself seemed to work fine, but 2 services did not start at the end. Couldn’t log in to the console afterwards. I have since reverted to a previous snapshot.
This server also has Enterprise Manager installed, and a couple of storage plugins (PureStorage and Dell Compellent, both latest versions of the plugins)
Yeah I was able to upgrade two other servers with 12.3.2.4165 to the RTM 13.0.1.180 without issue and all services started. Support is testing my theory about the 12.3.0.310 to 12.3.2.4165 then RTM upgrade to see if that is the cause. I will report back once they get back to me.
Had a similar problem in my Lab environment. The upgrade itself seemed to work fine, but 2 services did not start at the end. Couldn’t log in to the console afterwards. I have since reverted to a previous snapshot.
This server also has Enterprise Manager installed, and a couple of storage plugins (PureStorage and Dell Compellent, both latest versions of the plugins)
Yeah I was able to upgrade two other servers with 12.3.2.4165 to the RTM 13.0.1.180 without issue and all services started. Support is testing my theory about the 12.3.0.310 to 12.3.2.4165 then RTM upgrade to see if that is the cause. I will report back once they get back to me.
I am also experiencing the same problem on a B&R that was on 12.3.0.310. I upgraded to 12.3.2.4165 and then to 13 RTM. RestAPI and Web Services will not start. We had about 20 B&R’s on 12.3.0.310 and only one of them has experienced the problem. We are currently deploying a new machine to resolve the issue for now. I am interested in any updates you have on your case with Veeam Support.
+21Had a similar problem in my Lab environment. The upgrade itself seemed to work fine, but 2 services did not start at the end. Couldn’t log in to the console afterwards. I have since reverted to a previous snapshot.
This server also has Enterprise Manager installed, and a couple of storage plugins (PureStorage and Dell Compellent, both latest versions of the plugins)
Yeah I was able to upgrade two other servers with 12.3.2.4165 to the RTM 13.0.1.180 without issue and all services started. Support is testing my theory about the 12.3.0.310 to 12.3.2.4165 then RTM upgrade to see if that is the cause. I will report back once they get back to me.
I am also experiencing the same problem on a B&R that was on 12.3.0.310. I upgraded to 12.3.2.4165 and then to 13 RTM. RestAPI and Web Services will not start. We had about 20 B&R’s on 12.3.0.310 and only one of them has experienced the problem. We are currently deploying a new machine to resolve the issue for now. I am interested in any updates you have on your case with Veeam Support.
The case was closed out as they were still trying to figure this one out. Also after several reboots the server with the problem seemed to fix itself. So the real “fix” is truly not known. I upgraded several other VBR servers that were already on the 4165 build without issue.
So unsure the real root cause unfortunately.
I found the root cause and fixed the one machine this morning.
Veeam released an Update. The Service timeout is too short. It was set to 30 seconds. Setting it to 60 or 90 seconds resolved the problem
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control" -Name ServicesPipeTimeout -Value 60000 -Type DWord
| 2025-12-1 | VeeamBackup&Replication_13.0.1.180_20251130.iso | This repack modifies the installer only to address the top 2 issues affecting upgrades and deployments of 13.0.1.
|
+21Nice. Yeah they never really told me anything but seems they addressed it in a repack of the ISO file which has a newer date. Thanks for the share
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
