Comments on: DPM Error ID 30111 (Ox800423F4) https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/?utm_source=rss&utm_medium=rss&utm_campaign=dpm-error-id-30111-ox800423f4 A blog about Azure Kubernetes Service (AKS) and more... Tue, 27 Nov 2018 13:34:31 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Marc https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/#comment-260 Tue, 27 Nov 2018 13:34:31 +0000 https://pixelrobots.co.uk/?p=11813#comment-260 Absolute hero. Surprised this information isn’t anywhere else or that Microsoft dont even suggest it as a fix.

]]> By: Joey Goembel II https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/#comment-251 Fri, 09 Nov 2018 14:37:49 +0000 https://pixelrobots.co.uk/?p=11813#comment-251 Awesome solution to bothersome issue. The simplicity of it is astounding. Thanks so much!

]]> By: Malli https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/#comment-235 Tue, 09 Oct 2018 04:54:45 +0000 https://pixelrobots.co.uk/?p=11813#comment-235 Hi Sir,

I have performed same above but still I am getting below error.

C:\>vssadmin list writers
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Error: A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.

C:\>

]]> By: Pom2Ter https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/#comment-207 Thu, 16 Aug 2018 12:37:04 +0000 https://pixelrobots.co.uk/?p=11813#comment-207 Thank you so much! You save my day!

]]> By: Pixel Robots. https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/#comment-187 Tue, 24 Apr 2018 21:30:49 +0000 https://pixelrobots.co.uk/?p=11813#comment-187 In reply to Russ Morse.

Thanks for the comment. Glad the post helped.

]]> By: Russ Morse https://pixelrobots.co.uk/2018/03/dpm-error-id-30111-ox800423f4/#comment-186 Tue, 24 Apr 2018 21:25:47 +0000 https://pixelrobots.co.uk/?p=11813#comment-186 Thank you so much for this. We were having the same issue in our Hyper-V cluster environment and I have been battling this for a while. This simple solution is a lifesaver.

]]>