The first error message indicates that
CLSIDFromProgId for "VBScript" returned CO_E_CLASSSTRING. The second error means that
CoCreateInstance for the VBScript CLSID ({B54F3741-5B07-11cf-A4B0-00AA004A55E8}) returned ERROR_KEY_DELETED. I'm not sure what could cause this (scripting in Visual Build does depend on the
ActiveX Scripting environment). One other user did report this behavior on Win2008 -- in their case, the problem apparently started after IT installed a networked file system (SAN) and set up automatic backups. We haven't been able to reproduce this behavior, having run continuous builds for multiple days on Windows 2008 without errors.