Home  »  Quick tip to make the Veeam Fast SCP work in Windows 7 x64

Quick tip to make the Veeam Fast SCP work in Windows 7 x64


How to fix an error which generates Veeam Fast SCP running on Win 7 x64 platform.

This quite annoying error looks like this:

“Retrieving the COM class factory for component with CLSID [5F1555F0-0DBB-47F6-B10B-0AB0E1C1D8CE} failed due to the following error: 800700c1”

Veeam Fast SCP was back in 2009 my favorite file transfer software to work with ESX/ESXi hosts. When Windows 7 was introduced, like many of IT professionals I went for the 64 bit edition and that’s where the nasty error appears. When running Veeam’s Fast SCP on Windows 7 x64 bit edition. I was still waiting for a fix from the Veeam’s side, which actually never came. There was the option of using Veeam Backup v 5 in trial mode, because after expiration the copy feature still worked….. -;), But I still had a feeling that there might be a solution on the problem. And there is.

Recently I was reading through my Google RSS reader for my favorite blog posts, and I found a nice article on Everything Virtual’s blog. The fix for the Windows 7 x64 systems and Veeam’s Fast SCP is done in like 5 seconds…. -:). And the solution provided is fairly simple. You basically need to download a small exe file from Simon’s blog and run one command as an Administrator from the command prompt.

Here is what to do:

01. Download simple executable program called Corflags.exe from Simon’s Everything Virtual’s blog here and copy it to a folder of your choice (for example C:\Temp)

02. Launch command prompt as an Administrator and browse to c:\temp.  (cd c:)

03.  run corflags “C:\Program Files (x86)\Veeam\Veeam Backup and FastSCP\VeeamShell.exe”  /32BIT+

This does the trick…

Thanks to Simon for sharing this.

How to fix Veeam Fast SCP so it can run without error on Windows 7 x64 platforms

You can also have a look at this page which explains actually what the corflags.exe does:

64Bit applications:

To determine whether an .exe file or .dll file is meant to run only on a specific platform or under WOW64, use corflags.exe at the command prompt. You can also use corflags.exe to change the platform status of an .exe file or .dll file. For more information, see CorFlags.exe (CorFlags Conversion Tool). The CLR header (or COM+ Runtime header) of a Visual Studio assembly has the major runtime version number set to 2 and the minor runtime version number set to 5 (0 in Visual Studio .NET 2003 assemblies). Applications that have the minor runtime version set to 0 are treated as legacy applications and are always executed under WOW64.

Source: Simon’s Everything Virtual’s blog

Enjoy..

.

Vladan SEGET

Vladan is an Independent consultant, vExpert, VCP and owner of this website. This website ESX Virtualization started as a bookmarking site, but very fast found itself many readers and supporters. Feel free to network via Twitter @vladan

More Posts - Website - Twitter - Facebook - LinkedIn - Google Plus

You may also like:

  1. Veeam just released Fast SCP 3 compatible with W7 and 2008R2
  2. VEEAM Backup 3.1 is compatible vSphere 4
  3. Veeam Backup and replication 4 for faster backups and easy recovery
  4. NFR of Veeam products for every VCP, vExpert or VCI
  5. Veeam Backup 3.0 can do a file level restore most Linux systems
  6. Veeam Backup and recovery – Changed block tracking and vSphere API
  7. Using Veeam Backup 3.1 also as a scheduled copy for your VMs
Tagged with: