Missing System Writer VSSAdmin command results

Good Morning,

I've followed each of the previous posts and run each set of instructions with no luck. I'm receiving multiple VSS errors on a VM that is currently running in ESXi when I try to do a P2V on it from SCVMM 2012. I'm entering my post here because I believe it's a VSS issue, not an SCVMM issue. This server refuses to list the System Writer when I type vssadmin list writers, and I believe that is the cause of the failed P2V.

I've successfully performed a dozen or so of these conversions in the past couple weeks and they've gone smoothly, but this particular one will not convert. It gets to 40% and then gives a VSS error.  At the same time I get VSS errors in the event log:

First a couple of WMI errors appear:

The root\scvmmp2v namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.

Then I get a couple of VSS errors:

This one is an ID 8193:

Volume Shadow Copy Service error: Unexpected error calling routine XML document is too long. hr = 0x80070018, The program issued a command but the command length is incorrect.

Operation:

   Writer Exposing its Metadata

Context:

   Execution Context: Requestor

   Writer Instance ID: {EE02626C-1EE7-45BF-A917-63922AADE6F4}

   Writer Class Id: {E8132975-6F93-4464-A53E-1050253AE220}

   Writer Name: System Writer

This is another 8193:

Volume Shadow Copy Service error: Unexpected error calling routine CreateVssExamineWriterMetadata. hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.

Check the Application event log for more information.

Operation:

   Writer Exposing its Metadata

Context:

   Execution Context: Requestor

   Writer Instance ID: {EE02626C-1EE7-45BF-A917-63922AADE6F4}

   Writer Class Id: {E8132975-6F93-4464-A53E-1050253AE220}

   Writer Name: System Writer

I’m interested to know what might be done to resolve these errors? I’m running a fully up-to-date Windows 2008R2 Enterprise SP1 server. The server functions as a web server.

Thanks,

Joe