{"id":697,"date":"2019-09-25T19:47:35","date_gmt":"2019-09-26T00:47:35","guid":{"rendered":"http:\/\/zewwy.ca\/?p=697"},"modified":"2019-09-25T19:47:35","modified_gmt":"2019-09-26T00:47:35","slug":"fixing-veeam-veeam-service-wont-start","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2019\/09\/25\/fixing-veeam-veeam-service-wont-start\/","title":{"rendered":"Fixing Veeam (Veeam Service won’t Start)"},"content":{"rendered":"

<\/span>Veeam Won’t Start<\/span><\/h1>\n

Yeap, the one thing you don’t want can happen at the worst time. For me I was testing a hypervisor upgrade scenario, and my host sure enough failed to come up successfully. Well…. shit.<\/p>\n

While I was going crazy trying to bring my host back up (the stock ESXi images wasn’t good enough cause…. RealTek, yeah… this Mobo I picked was an overall bad choice, sad cause it’s ASUS… anyway…<\/p>\n

I went to go restore some VMs from backup onto other hosts till I could recover my main host (find that custom ESXi install image) and to my dismay… Veeam console failed to connect…<\/p>\n

Failed to connect to the Veeam Backup & Replication server:\r\nNo connection could be made because the target machine actively refused it :9392<\/pre>\n
ughhhh, what? this is a standalone server, not domain joined, no special services account or MSAs, or separate servers, like what gives?<\/p>\n
Event viewer is literally useless… as nothing shows anywhere for any hints.<\/p>\n
<\/span>First Fix Attempt<\/span><\/h2>\n
OK so, the usual, google, and let’s see here<\/a>…<\/p>\n
Like other symptoms not much help and a generic console error, so this fix was worth a shot, what I took away from it was how to do a manual DB backup<\/a> (assuming this is all the settings and configurations if re-install required) and some registry keys used by Veeam and that this<\/a> was not the problem (not the droids you are after). I thought maybe I had updated and not tested, as I do tend to do shutdown instead of reboot, with my limited resources and well windows is heavy on resources.<\/p>\n
HKEY_LOCAL_MACHINE\\SOFTWARE\\Veeam\\Veeam Backup and Replication\\SqlServerName (This is the server name where SQL is running)\r\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veeam\\Veeam Backup and Replication\\SqlInstanceName (This is the instance name needed for the connection, which is in the format Servername\\InstanceName)\r\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Veeam\\Veeam Backup and Replication\\SqlDatabaseName (This is the database name in the Databases folder once you connect)<\/pre>\n
\"\"<\/a><\/p>\n
But sadly no good, as I guess my issue is not related to any lock files on the SQL DB… ok so what else is there…<\/p>\n
<\/span>Second Fix<\/span><\/h2>\n
So I started reading this one<\/a> and at first I was thinking, yup same problem, and reading along, I like Foggy but them not sharing the answer was rather annoying… then after some others reported the solution and my jaw literally dropped (probably why they tell you call support, cause this is some dirty laundry…)<\/p>\n
as Tommy stated<\/p>\n
“It is very likely to caused by the changing of the host name, do refer to the following link, i managed to my Veeam service started again.”<\/p>\n
What….<\/p>\n
sure enough running the req query command and hostname showed I had indeed changed the hostname to something more suitable AFTER installation.<\/p>\n
\"\"<\/a><\/p>\n
Why they’d rely on a reg key vs a simply enviroment variable is really beyond me, cause the problem with using a reg key for this is pretty clear here….<\/p>\n
So let’s try to fix this, thanks to the second guys reply by spacecrab:<\/p>\n
“I know this is an old post, but thank you for replying with this information. I installed Veeam Backup and Replication before changing the default generated hostname, and it was really throwing me through a loop. The fix noted at that url worked perfectly after I rebooted to reset the services. I’ll relay the content here in case that sources goes away.<\/p>\n
In my case I had renamed the computer from a default WIN234dfasd type name to a \u2018much\u2019 better alternative. Veeam refers to the local computer name in a couple of registry entries and promptly stopped working \u2013 which we didn\u2019t notice until later.<\/p>\n
The keys are:<\/p>\n
\n
HKLM\\SOFTWARE\\Veeam\\Veeam Backup and Replication\\SqlServerName\r\nHKLM\\SOFTWARE\\Veeam\\Veeam Backup Catalog\\CatalogSharedFolderPath\r\n<\/code><\/pre>\n<\/div>\n
Backup of the site\u2019s Virtual Machines is now running again.”<\/p>\n
alright let’s update some keys to be Veeam…. I just used reg edit to do this vs figuring out the exact query (although I probably should figure out a query in-case other keys but meh….<\/p>\n
and after a reboot… Woah! all the Veeam services are running, sure enough I can connect to my standalone Veeam Server! Wooo thanks Spacecrab!<\/p>\n
 <\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
Veeam Won’t Start Yeap, the one thing you don’t want can happen at the worst time. For me I was testing a hypervisor upgrade scenario, and my host sure enough failed to come up successfully. Well…. shit. While I was going crazy trying to bring my host back up (the stock ESXi images wasn’t good … <\/p>\n
Continue reading “Fixing Veeam (Veeam Service won’t Start)”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[8,236],"tags":[237,82],"class_list":["post-697","post","type-post","status-publish","format-standard","hentry","category-server-administration","category-veeam","tag-fix","tag-veeam"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=697"}],"version-history":[{"count":1,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/697\/revisions"}],"predecessor-version":[{"id":698,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/697\/revisions\/698"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}