Veeam backup fails with "Cannot start service"

-
I've cut and pasted this from http://social.technet.microsoft.com/Forums/windowsserver/en-US/9cf42e8a-2a33-47c5-a797-269330e9ba1a/vss-writer-fails?forum=winserverfiles

This solves an issue we were seeing when using Veeam to backup an Exchange 2010 CAS server.  The job failed with error:

Processing 'ServerName' Error: Cannot start service. Machine [IP].Service[VeeamVssSupport]. Cannot start service. Win32 error: The system cannot find the file specified. Code 2.

We found this link and in the middle of the forum this snippet:

"Please open the Disk Management console, located at "Server Manager\Storage\Disk Management" and see which partition has been marked as Active volume. If the Active volume is different from the volume in which you install the operating system, try changing the Active volume to the volume containing the operating system by using the following commands:

1. Open a command prompt as Administrator.
2. Run diskpart.
3. At the diskpart> prompt type "list disk" (without quotations), see which disks are listed there
4. At the diskpart> prompt type "list volume", see which volume is the volume containing operating system
5. At the diskpart> prompt type "select disk 0" <enter>.
6. At the diskpart> prompt type "select volume 2" <enter> (I assume the volume 2 is the volume containing operating system).
7. At the diskpart> prompt type "active" <enter>."

Worked for me :)

Comments

Post a Comment

Popular posts from this blog

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine
Read more

Intune installation requires a wire...or does it?

-
If you are using Intune (great!) it assumes you have a wired connection (not great) - this is more of an issue as some machine now no longer have built in ethernet ports. It is possible to connect to your wireless - albeit in a slightly awkward way.....here's how During the OOBE hit SHIFT+F10 to get a command window and type either; start ms-settings: To get the settings window or start ms-availablenetworks: To see the network fly outs. Thanks to  Using a wireless network connection with Windows Autopilot white glove – Out of Office Hours (oofhours.com)
Read more

Powershell VPN connections - PEAP with MSCHAPv2

-
Messing around with VPNs last week I found that it is easier (sometimes) to have a one liner for VPN creation! Here's how I make a PEAP\MSChapV2 VPN profile...using the users Windows creds! Change ServerAddress, DnsSuffix and choose a better L2tpPsk!! $a = New-EapConfiguration -UseWinlogonCredential $b = New-EapConfiguration -Peap -TunnledEapAuthMethod $a.EapConfigXmlStream Add-VpnConnection -Name "VPN (SSL)" -ServerAddress vpn.fqdn.com -AuthenticationMethod Eap -DnsSuffix my.domain.com -EapConfigXmlStream $b.EapConfigXmlStream -EncryptionLevel Maximum -Force -RememberCredential -AllUserConnection -TunnelType Sstp Add-VpnConnection -Name "VPN (L2TP)" -ServerAddress vpn.fqdn.com -AuthenticationMethod Eap -DnsSuffix my.domain.com -EapConfigXmlStream $b.EapConfigXmlStream -EncryptionLevel Maximum -Force -RememberCredential -AllUserConnection -TunnelType L2tp -L2tpPsk "shared secret key"
Read more