VSSadmin list writers will show the failed component - maybe it is from a previous backup software as dbeato suggested

Could try Acronis VSS Doctor on the host - link

Try unchecking Backup Integration Services in the Management --> Integration Services area to get a crash-consistent backup at minimum and see if it works.

This link says the issue will be fixed in Server 2016, 2012 R2 applies to this message, but is not mentioned for fix...

Re-Install up-to-date Guest Integration services on the Guest VM

@jasgot
Run this on EMS:
netsh http show sslcert

0.0.0.0:443
0.0.0.0:444
127.0.0.1:443

should have the same Certificate Hash / Thumbprint
(take a screenshot)

Whichever one doesn't match - delete

netsh http delete sslcert ipport=0.0.0.0:444 (for example)

Then reload that with the right cert

netsh http add sslcert ipport=0.0.0.0:444 appid='{app id}' certhash=<correct thumbprint>
(or whichever ip/port didn't match earlier)

Then run netsh http show sslcert again to confirm the change!

@gjacobse

We had something similar recently, with Server 2022 and Bartender server.
The printer had to be installed under the AD Service Account that the Bartender app is installed under, on that app server.

Then the calls to our print server, where the printer is pointed to in the app itself, worked properly. Otherwise, there would be a 3 min timeout before even the labels from the app would print.

So try to install it locally under the account that the SAP app was installed under.

Try to reset the printer, and the web server via the printers web gui if possible also.

Our issue was with the older Xi4's not the newer ZD621.
Our print server is Win Server 2022 Core.

There is a ppd you can use for cups in the Mac driver.

Primera LX900 - ColorLabelSugned - Payload~~ - Library - Printers - PPDs - Contents - Resources - CL900.ppd

In CT USA from Comcast Business, we had paid approx. $500/mo for a PRI Trunk, 20 DID's "free", and another 20 DIDs at $5/month (total). This was as recently as this spring, plus $10/mo per Toll-Free line.

@jasgot
Run this on EMS:
netsh http show sslcert

0.0.0.0:443
0.0.0.0:444
127.0.0.1:443

should have the same Certificate Hash / Thumbprint
(take a screenshot)

Whichever one doesn't match - delete

netsh http delete sslcert ipport=0.0.0.0:444 (for example)

Then reload that with the right cert

netsh http add sslcert ipport=0.0.0.0:444 appid='{app id}' certhash=<correct thumbprint>
(or whichever ip/port didn't match earlier)

Then run netsh http show sslcert again to confirm the change!

You may have to install the SMB v1 client - Control Panel -> Programs --> Turn Windows Features on or off --> SMB 1.0....and SMB 1.0 Auto Removal if SMB 1 isn't used for 15? days

If someone in the neighborhood is using MoCA, you could put this adapter on the business' incoming cable line, before the first split or amplifier. It would block their interference. link

@JaredBusch
You can use BareMetal VHD loader to mount a vhd/vhdx on a network drive at startup, and Crashplan will see that as a local drive. link

There is a link to a cumulative update for Exchange 2013, not sure if the workaround will apply to Exchange 2016:
MS Support link

You may be able to ask your designer if they have a Pantone Color Bridge guide - link - and if they can give you the values listed for each PMS color you need.
This is Pantone's closest "guess" for each PMS color for CMYK, RGB, etc, and they will have a guide for coated and uncoated stock.
Different output devices will print differently anyway, even when calibrated.
Attached is a Photoshop best guess for 287c for example, showing the color is out of standard print and display ranges (circled):
image url)

VSSadmin list writers will show the failed component - maybe it is from a previous backup software as dbeato suggested

Could try Acronis VSS Doctor on the host - link

Try unchecking Backup Integration Services in the Management --> Integration Services area to get a crash-consistent backup at minimum and see if it works.

This link says the issue will be fixed in Server 2016, 2012 R2 applies to this message, but is not mentioned for fix...

Re-Install up-to-date Guest Integration services on the Guest VM