JungleDisk is a WebDAV file sharing service running on the Amazon Simple Storage Service (Amazon S3). It appears when users are using Office 2003 SP3 on a Vista Business SP1 based system, they may not be able to open Microsoft Word and Excel files. The users experience an error similar to:
Could not open ‘http://2667/somebucket/some file.doc’
The JungleDisk Support site (KBID#: 300065) indicates installing the Windows Software Update for Web Folders (KB907306) and rebooting will fix the problem. Unfortunately the reported fix does not appear to work for numerous users. Additionally, connecting to the JungleDisk “bucket” using the naive Windows WebDAV client does not allow saving due to the “read-only” bug.
We discovered the easiest way to work around the Vista/Office 2003 WebDAV limitations was to use a substitute drive. Once the JungleDisk client loads and you can access the JungleDisk network drives, the following command can be use to connect:
subst NewDriveLetter: JungleDiskDriveLetter:\
For example, if the JungleDisk drive letter is “J:\”, you will run the following command to access the share:
subst k: j:\
You should then be able to open files from and save files to the “k:” drive directly.
When your system reboots, you will need to run the subst command again. For our users, we have created a batch file that deletes the virtual drive (subst k: /d) then re-creates it (subst k: j:\). After the user’s system has completely loaded, they double-click on the batch files to create accessible virtual drives.
Incidentally, upgrading to Office 2007 on Vista or running Office 2003 from Windows XP does not appear to have any issues.
Occassionally a workstation will show a mapped network drive as “Disconnected” in Windows Explorer. Double-clicking on the drive does not resume the connection and attempting to unmap the drive will give an error that “The network connection does not exist”.
Additionally you may see your login scripts not mapping other drives.
To correct the problem, download the User Profile Hive Cleanup Service from the Microsoft Downloads site and read the installation/usage instructions:
The Windows Vista Check for System Update Readiness (CheckSUR) tool will try to fix certain Windows Update installation failures.
System resources, such as file data, registry data, and even in-memory data, can develop inconsistencies during the lifetime of the operating system. These inconsistencies may be caused by various hardware failures or by software issues. In some cases, these inconsistencies can affect the Windows Servicing Store, and they can cause a Windows Vista update to fail. When the update fails, it blocks the user from installing updates and service packs. CheckSUR addresses this issue.
When Windows Update detects inconsistencies that are related to system servicing in system files or in the registry, Windows Update offers CheckSUR as an available update package.
Note This Windows Update or Automatic Update package will only be offered if such inconsistencies have been detected on the system. CheckSUR should run automatically after it has been installed from Windows Update.
To manually install and run CheckSUR, follow these steps:
- Click Start , click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- In the User Account Control dialog box, click Continue.
- Type reg add HKLM\COMPONENTS /v StoreCorruptTimeStamp /t REG_SZ /d “0” /f, and then press ENTER.
- Type reg delete
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CheckSUR\, and then press ENTER.
- Download and then install CheckSUR from the Microsoft Download Center.
- As soon as the file has been successfully downloaded, double-click the file to install and run CheckSUR.
We recommend that you restart your computer after you run CheckSUR to make sure that any changes take effect. Additionally, you must try to reinstall any software updates that previously could not be installed. If CheckSUR detected and fixed the cause of the failures, these updates will now install successfully.
CheckSUR creates a log file that captures the issues, if any exist, that were found or fixed. The log file will be located at %WINDIR%\Logs\CBS\CheckSUR.log
CheckSUR is run by Windows Update after you install KB947821. Windows Update can take as long as 10 to 15 minutes to complete this scan. The time may be significantly longer on some computers. However, the Windows Update progress bar is not updated while this process is running, and it will not move. This means that the Windows Update progress bar may indicate that it is 0 percent complete, or 20 percent complete, and so on, for some time. This behavior is expected, and you should not cancel the update. If you cancel the update, some problems may not be identified, and this package may have to run again.