Error Connecting to the MKS: Error Connecting to the /bin/vmx process – Veeam, VMware

We had a VM on VMware ESX that kept locking up mysteriously once or twice a week.  The server would become inaccessible, we would have to shut it down to get it back and running.

Upon investigation, and while looking on the vCenter we noticed that error message.

“Error Connecting to the MKS: Error Connecting to the /bin/vmx process”

We were unable to login to the Windows VM to see what is happening inside.  The server was un-ping-able either.  We thought of corruption in the beginning.  But Veeam turned out to be the culprit.

We use Veeam backup and replication 8.0 in the environment.  We discovered a snapshot for that VM sitting on VMware.  Every time Veeam finished up the backup or replication  for that VM, it go through “snapshot consolidation” that would lock the server for about 15 minutes.  We removed that snapshot and the VM now is no longer locking up.

We didn’t check with Veeam on that.  We didn’t need that old snapshot either.  Removing the snapshot was all we needed to rectify the issue.

OneDrive issues users 90 day notice

Microsoft has given its users of there cloud storage service OneDrive, their 90-day notice. Microsoft is shrinking its free storage size from 15GB to 5GB in late July. That is a 67% reduction in storage size. The reduction will take effect on July 27,2016.

As part of the storage space cuts, Microsoft eliminated two paid plans that had offered 100GB for $2 per month and 200GB for $4 a month. Instead, it now offers only a 50GB Plan for only $2 a month.

If you are effected by the shrinking we recommend backing up all OneDrive data.

Shortcuts disappearing – Windows 7 desktop – Network drives

If shortcuts including network drives links are disappearing randomly from Windows 7 Desktops, here what you can do to address issue:

1)) Apply the following hotfix from Microsoft


2)) Disable “System Maintenance troubleshooter” Control Panel.  Go to Control panel

  • In control Panel (Change view to  Category).  Under System and Security, click Find and fix problems.
  • Click Change settings on the left side and change Computer Maintenance to Off.


3)) Go to the Scheduled tasks in Accessories and delete any entries related to Windows troubleshooting or clean-up.


4)) Try to rebuild the Icon Cache.

  • First, change Folders View to show hidden files – this can be found under Folder options
  • Go to %USERPROFILE%\AppData\Local
  • Find the IconCache.db file, and rename it to IconCache.db.back.  Close and restart.

Multiple WiFi APs – WAPs – Same SSID – Zero hand-off


If you are looking to have a reliable WiFi solution where you will have multiple WAPs covering a wide physical area, and would like them to broadcast the same SSID, you can accomplish without even considering a WiFi controller.   Fairly easy and affordable.  Worked great every time for us.

Consider Cisco WAP 551.

It costs a couple hindered dollar for each Cisco WAP551.  They are P0E.  Once you configure the first one which usually takes 10 minutes, configuring the 2nd one would take less considering you can enable the “Single Point Setup” which acts as a cluster, so once you assign the 2nd WAP an IP address, and join it to the cluster,  all configuration will replicate from first WAP to the 2nd.

Pretty easy and straight forward setup.  Works perfectly especially for those who are looking for zero hand-off when roaming through the space.  This is what we have experienced.  Some people have reported 1-2 seconds for hand-off.


Veeam error – Cannot complete the operation because the file or folder [] already exists

You are getting this error in Veeam replication.


Processing Server01 Error: Cannot complete the operation because the file or folder [] already exists


Preparing replica VM Error: Cannot complete the operation because the file or folder [] already exists
Error: Cannot complete the operation because the file or folder [] already exists



Open VMware vCenter and connect to the remote site (the DR site where the VMs are replicated to), and right click on the replicated VM that is having the issue and choose Delete from disk.

This will allow that VM to replicate again without issues.