This has been resolved , and was a .NET issue. On the machines that failed, .NET Client Profile installed, machines that were working had the .NET Full Framework installed. An install of the Full Framework on the machines in question resolved the issue.
↧