Insufficient memory or disk space, cannot display the requested font

Error while printing a specific e-mail? Getting the following error? Insufficient memory or disk space, cannot display the requested font.

pesan-error-2

Check out if the used font is available at the clients system/terminal server. Fonts can be found at C:\Windows\Fonts.

I’ve downloaded the custom font and installed it. Problem was solved after rebooting the system (just to be sure).

 

VEEAM: Unable to release guest. Error: Unfreeze error / A VSS critical writer has failed.

Somehow an SBS2011 server was unable to backup as an image by VEEAM. Also creating a manual snapshot via Vpshere Console failed everytime!? In the event viewer i see the following event id’s: 8230, 2138, 3760 -> VSS or SharePoint.

4/9/2016 8:01:14 AM :: Unable to release guest. Error: Unfreeze error: [Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [Microsoft Exchange Writer]. Class ID: [{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}]. Instance ID: [{f25c19c2-7918-4c32-80e6-16228a39b24a}]. Writer’s state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f2].]

4/9/2016 8:03:55 AM :: Error: Unfreeze error: [Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [Microsoft Exchange Writer]. Class ID: [{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}]. Instance ID: [{f25c19c2-7918-4c32-80e6-16228a39b24a}]. Writer’s state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f2].

After changing DCOMCNFG permissions i tried a total different thing which i did before. The problemen was VSS which was failing everytime with alot of event viewer logs.. I’have runned my former fixvss.bat script.. Save the following script to a bat file and run it in an elevated command prompt. Maybe you’re Lucky!🙂

rem FILENAME: FIXVSS08.BAT
rem
net stop “System Event Notification Service”
net stop “Background Intelligent Transfer Service”
net stop “COM+ Event System”
net stop “Microsoft Software Shadow Copy Provider”
net stop “Volume Shadow Copy”
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ATL.DLL
regsvr32 /s comsvcs.DLL
regsvr32 /s credui.DLL
regsvr32 /s CRYPTNET.DLL
regsvr32 /s CRYPTUI.DLL
regsvr32 /s dhcpqec.DLL
regsvr32 /s dssenh.DLL
regsvr32 /s eapqec.DLL
regsvr32 /s esscli.DLL
regsvr32 /s FastProx.DLL
regsvr32 /s FirewallAPI.DLL
regsvr32 /s kmsvc.DLL
regsvr32 /s lsmproxy.DLL
regsvr32 /s MSCTF.DLL
regsvr32 /s msi.DLL
regsvr32 /s msxml3.DLL
regsvr32 /s ncprov.DLL
regsvr32 /s ole32.DLL
regsvr32 /s OLEACC.DLL
regsvr32 /s OLEAUT32.DLL
regsvr32 /s PROPSYS.DLL
regsvr32 /s QAgent.DLL
regsvr32 /s qagentrt.DLL
regsvr32 /s QUtil.DLL
regsvr32 /s raschap.DLL
regsvr32 /s RASQEC.DLL
regsvr32 /s rastls.DLL
regsvr32 /s repdrvfs.DLL
regsvr32 /s RPCRT4.DLL
regsvr32 /s rsaenh.DLL
regsvr32 /s SHELL32.DLL
regsvr32 /s shsvcs.DLL
regsvr32 /s /i swprv.DLL
regsvr32 /s tschannel.DLL
regsvr32 /s USERENV.DLL
regsvr32 /s vss_ps.DLL
regsvr32 /s wbemcons.DLL
regsvr32 /s wbemcore.DLL
regsvr32 /s wbemess.DLL
regsvr32 /s wbemsvc.DLL
regsvr32 /s WINHTTP.DLL
regsvr32 /s WINTRUST.DLL
regsvr32 /s wmiprvsd.DLL
regsvr32 /s wmisvc.DLL
regsvr32 /s wmiutils.DLL
regsvr32 /s wuaueng.DLL
sfc /SCANFILE=%windir%\system32\catsrv.DLL
sfc /SCANFILE=%windir%\system32\catsrvut.DLL
sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL
net start “COM+ Event System”
net start “System Event Notification Service”
net start “Background Intelligent Transfer Service”
net start “Microsoft Software Shadow Copy Provider”
net start “Volume Shadow Copy”

Note! While running on a SBS2008 or SBS2011 server you should check the dependencies for the Com+ Event System service. This will stop your DHCP and DFS services. Also while running a DHCP or DFS server as a role/feature on your server.

{Delayed Write Failed} Windows was unable to save all the data (UNC/Network traffic)

So, somehow the following event is showing up in the event vwr:

  • Event ID: 50
  • Source: MRXSMB
  • Type: System
{Delayed Write Failed} Windows was unable to save all the data for the file \data\domainname.nl\~user@domainname.nl.pst.tmp. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Let me explain the situation. We are running an W2012R2 server which has Office 2013 installed. The office applications are published as a remote app for some users. Their personal data and business data is stored on a different server (W2008R2). Those two virtual machines/servers are running on a different host wich are both connected to the same (gigabit) switch.

Tekening1

 

As you see we are using 2 different virtual network adapters. The E1000 adapter is a older, slower network card. Upgrading the network card to a VMXNET3 adapter would be a great solution. The VMXNET3 adapter supports up to 10GB/s. Unfortunately our switch has a maximum speed of 1GB/s.. So i had to move one of the virtual machines to the same hosts as the other virtual machine is running on. This might decrease the network traffic/time/latency between two hosts and virtual machines. The traffic between the virtual machines is now all internal traffic on the same host!

See the following article for more information about E1000 and VMXNET3 network adapters:

Update:

Moving the VM’s to the same host and upgrading the network cards did not solve the issue.. We moved the .PST files from the POP3 mailboxes to the same server as our Office applications are running. They are now “local” data. .PST files on a network share/UNC path is not a good idea!

Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed.

A common issue I have come across with Veeam is that sometimes you get the error message shown below when backing up a domain controller. In my case an SBS2011 server.

Unable to release guest. Error: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{850442eb-2b2e-47c2-b6a6-a8abfdba0b31}]. Writer’s state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]

To cure the problem check for a failed NTDS Writer by doing the following :

Run an elevated command prompt and type “vssadmin list writers”. You should see that the NTDS writer is in a FAILED or UNSTABLE state. If it says failed then reboot the server and then try the backup again. This is the most simple solution which would not work always..

If the backup still fails then open an elevated command prompt again and open diskpart manager by typing “diskpart”. Within the diskpart command line tool you type: “automount enable”. Then try the backup again.

Still failing then this last step normally resolves the issue. Enter the registry and go to the following key. Here are all local profiles stored. HKEY_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

In there your see a whole load of GUID’s. Delete all the ones with .bak at the end. Some administrators like me rename the old profiles with an underscore.. So simply removed the unneeded profiles.

Reboot the server and all should be good.

Source : Veeam KB1697