Exchange 2013 & DPM The VSS application writer or the VSS provider is in a bad state

[FN-GM]

Hi,

 

I am having the exact same issue as this. Running the exact same versions of DPM and Exchange. Does anyone have any suggestions please?

 

Thanks

 

https://social.technet.microsoft.com/Forums/en-US/1f86d385-2da5-4578-a06e-d2683ecaa3ed/error-message?forum=dpmexchbackup

[adamf]

The version of ese.dll and eseutil.exe in the DPM\bin folder - are they the same as the versions from your exchange server?

[FN-GM]

Yes I copied them over last night from my exchange server.

[DevilsAdvocate]

I have the same problem (though i'm on CU5 of Exchange).

[FN-GM]

I have the same problem (though i'm on CU5 of Exchange).

 

When did you last install Windows Updates please?

[DevilsAdvocate]

I did some last night and had the error this morning when I got in. I installed quite a few updates - no idea which may have caused this though.

 

[FN-GM]

I installed a years worth before we got the issue. I am new and the previous person didn't patch up. Because I did so many its to track what update is the issue.

[FN-GM]

This is a list of updates I have identified from this month. List is not complete (I think)

 

KB2993958

KB3006226

KB2992611

KB3005607

KB3003743

KB2982998

KB3002885

KB2995387

KB3010788

KB2978127

KB3003057

Edited November 18, 2014 by FN-GM

[adamf]

I'm on CU6 and haven't done November updates yet so it's a safe bet it's one of those. Have you got any free support incidents (like you'd get from a Dreamspark subscription) that you could use? If it's a bug you'll get the incident back.

 

If/When you find out which one, can you post it up here!

[adamf]

Just a thought.... can you do a backup of Exchange with Windows Server Backup? That might eliminate Exchange or DPM as the culprit?

[FN-GM]

I have removed a pile of updates and its working again. We do have the free support tickets. However I am the new NM and waiting for the licencing to go into my name. Until that is done i am stuffed.

[FN-GM]

Apparently its KB3000853 that causes the issue

[DevilsAdvocate]

Will remove that update tonight and see what happens then.

[DevilsAdvocate]

Works fine after removing the above update. Nice one FN-GM.

[FN-GM]

No worries, I can't take the credit someone else told me

[FN-GM]

They have fixed it!!

 

https://support.microsoft.com/kb/3000853?wa=wsignin1.0