[Box Backup] VSS on 64bit not working with 32bit binaries

[Achim]

Hello Chris:

I tried the latest VSS build we worked on last week (3026 I believe) 
under 64 Vista Home, and unfortunately it does not work out of the box 
(as probably could have been expected). I include the details below.

The reason is that 32bit programs cannot use VSS on 64bit Windows, as 
explained in this thread [1]

I will now try to build a x64 version now and report back on the 
results.

Best regards, Achim

[1] 
<http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/eadf5dcd-fbd1-4224-9a56-b5843efebb15/>

bbackupd.log
============
TRACE:   BackupDaemon::NotifySysadmin() called, event = backup-start
NOTICE:  Beginning scan of local files
TRACE:   timer KeepAliveTime (0085C7C4) initialised for 0 secs, will 
not fire
TRACE:   Set maximum diffing time to 120 seconds
TRACE:   Set keep-alive time to 120 seconds
TRACE:   timer KeepAliveTime (0085B90C) initialised for 120 secs, to 
fire at 14:22:23.000000
TRACE:   timer KeepAliveTime (0085C7C4) initialised from timer 
0085B90C, to fire at 1318940543.0
TRACE:   timer KeepAliveTime (0085B90C) destroyed
INFO:    Not deleting unused entries - none in list
ERROR:   VSS: Failed to initialize for backup: Catastrophic failure 
(0x8000ffff)
WARNING: Failed to access directory: C:\: Permission denied
ERROR:   VSS: BackupComplete() failed: IDispatch error #8449 
(0x80042301)
INFO:    Saved store object info file version 2 
(c:\bb_conf\bbackupd\bbackupd.state)
TRACE:   timer KeepAliveTime (0085C7C4) destroyed
TRACE:   BackupDaemon::NotifySysadmin() called, event = backup-ok
INFO:    Not notifying administrator about event backup-ok, set 
NotifyScript to
do this in future
NOTICE:  Finished scan of local files
NOTICE:  File statistics: total file size uploaded 0, bytes already on 
server 0, encoded size 0, 0 files uploaded, 0 dirs created
TRACE:   BackupDaemon::NotifySysadmin() called, event = backup-finish
TRACE:   Wait on command socket, delay = 1024000000




Eventviewer
===========
Source: bbackupd -----------------
ERROR: VSS: Failed to initialize for backup: Catastrophic failure 
(0x8000ffff)
-----------------

Source: VSS, event id 8913 -----------------
Volume Shadow Copy Service error: Unexpected error calling routine 
CoCreateInstance.  hr = 0x80040154.

Operation:
  Instantiating VSS server
-----------------

Source: VSS, event id 32 -----------------
Volume Shadow Copy Service error: The VSS Coordinator class is not 
registered.  This may be caused due to a setup failure or as a result 
of an application's installer or uninstaller.

Operation:
  Instantiating VSS server
-----------------


VSSadmin
========
E:\bin>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line 
tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'System Writer'
  Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
  Writer Instance Id: {804d68e9-3ae1-4806-94e8-5c44b7eccd0a}
  State: [1] Stable
  Last error: No error

Writer name: 'MSSearch Service Writer'
  Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
  Writer Instance Id: {7e2b1042-0602-458c-b08d-685417e0b190}
  State: [1] Stable
  Last error: No error

Writer name: 'BITS Writer'
  Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
  Writer Instance Id: {05e5821e-5519-42b2-988d-e78ff4f564c1}
  State: [1] Stable
  Last error: No error

Writer name: 'ASR Writer'
  Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
  Writer Instance Id: {b00bcefb-020e-419b-a9ff-5ac3afb68e85}
  State: [1] Stable
  Last error: No error

Writer name: 'WMI Writer'
  Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
  Writer Instance Id: {1be43abd-35f1-49a1-9613-cefc4ee8a94b}
  State: [1] Stable
  Last error: No error

Writer name: 'Registry Writer'
  Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
  Writer Instance Id: {d13a4d1c-504f-4791-8702-870868f6d81d}
  State: [1] Stable
  Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
  Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
  Writer Instance Id: {305d56d7-0978-4db6-b151-2f7ae7dbdabf}
  State: [1] Stable
  Last error: No error

Writer name: 'COM+ REGDB Writer'
  Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
  Writer Instance Id: {42152f9b-7740-4c71-b3f8-74c679bbf3b6}
  State: [1] Stable
  Last error: No error