IMPORTANT TECHNICAL BULLETIN FOR FDR/UPSTREAM, UPSREAM RESERVOIR and UPSTREAM/SOS

UPSTREAM Client V3.5.0C users
A problem resulting in an OS crash and a "blue screen"; has been discovered with FDR/UPSTREAM, UPSTREAM/SOS, and UPSTREAM RESERVOIR client version 3.5.0C and Windows XP SP2 caused by a bug introduced in Visual Studio 2005. The problem occurred with most (but not all) of the executables in version 3.5.0C.

The workaround for customers that have FDR/UPSTREAM and UPSTREAM RESERVOIR client version 3.5.0C installed on a Windows XP SP2 system is to apply Windows XP hotfix #KB921337.

The name of the file is WindowsXP-KB921337-x86-ENU.exe and it can be obtained from the INNOVATION FTP site and is in the

\public\download\upstream\windows folder.

Users may also try to downgrade to version 3.5.0.
This problem with FDR/UPSTREAM version 3.5.0c may also affect Windows 2000, but there is not a hotfix for Windows 2000 from Microsoft yet. If a user is having the problem on Windows 2000 they should downgrade to UPSTREAM version 3.5.0.

Those executables that were built with a manifest caused the problem. A manifest is a set of metadata that is added to an executable so that it runs as administrator in VISTA.

The next release of FDR/UPSTREAM 3.5.0D due sometime in December 2007 will correct this problem and allow UPSTREAM to run without crashing an unpatched Windows XP/SP2 system and still runs as administrator in VISTA.

UPSTREAM/SOS Users
Problems have also been discovered with UPSTREAM/SOS and intermittent error conditions performing backups through the local backup volume resulting in the following error

UST288E FDRSOS LOCAL BACKUP ERROR VOL=E#026D I/O ERROR READING/WRITING DISK

A patch can be obtained from EMC. The patch can be identified as fix number 36244 for 5772.83 and higher. It will only be applicable to microcode family 5772 and should not be needed for 5671 or 5771 and lower.
This problem only occurs immediately after initializing a local backup volume, not if you just use a previously initialized volume. If most customers do not re-init their volumes often, then most customers should be unaffected by this issue.

We will not know what GA microcode level will contain fix 36244 until the fix goes through regression testing for that level. Until the patch is GA in a release, the customer's local EMC C/S team would have to request an E-pack containing fix 36244 for 5772.83.