For more information see the Backdoor.Sdbot.AT Virus Outbreak [ID: 71246] Windows Support troubleshooting case.

The Prinergy Evo client doesn't work as expected if you're running it on Mac OS X 10.4.

For more information see the Prinergy Evo troubleshooting case [ID: 67131].

We recommend that you do not install Mac OS X v10.4 on mission-critical Prinergy client computers until this testing is completed.

For more information see the Prinergy troubleshooting case [ID: 67092].

The Prinergy Evo client doesn't work as expected if you're running it on Mac OS X 10.4.

For more information see the Prinergy Evo troubleshooting case [ID: 67131].

You are unable to run Preps on Mac OS X v10.4.

For more information see the Preps troubleshooting case [ID: 67164].

We recommend that you do not install Mac OS X v10.4 on InSite client computers until our testing is complete and any InSite updates that are required are available.

For more information see the Synapse InSite troubleshooting case [ID: 67165].

Two problems may be encountered when running InSite after upgrading to the Mac OS v10.3.9.

For more information see the Synapse InSite troubleshooting case [ID: 66760].

Apple® Computer, Inc. recently released Java® 1.4.2 Update 1. Do not install this update on a Macintosh® client computer running Brisque® 5 software

For more information see the Brisque troubleshooting case [ID: 55507].

This problem can occur with newly created job ticket templates and migrated job ticket templates. After exiting Preview, the job goes into the Failed queue. No error messages appear.

For more information see the Brisque troubleshooting case [ID: 55211].

After you upgrade to QuarkXPress^® 6.1, printing on Mac OS X sometimes causes error messages to appear regarding corrupted fonts.

For more information see the Brisque troubleshooting case [ID: 50610].

For more information see the Safety Alert From Creo: Trendsetter Autoloader and Trendsetter NEWS plate bay hinges.

Symptom:
When you send a PDF 1.3 file to the Brisque RIP, spot colors drop off the file and CT Quality fails to process during CT Resolve.

For more information see the Brisque troubleshooting case [ID: 49762].

Symptom:
Selecting Flexo Media in the jtt window in Screen2Go can result in unnecessary fetches or abrupt drop-offs in vignettes and drop shadows.

For more information see the Brisque troubleshooting case [ID: 46077].

Symptom:
There is a possibility of the Oracle database within the Prinergy system becoming corrupted under specific conditions.

Cause:
The Oracle database may become corrupted when any of its datafiles extend onto a 4 GB boundary, that is, if the datafile grows to become 4 GB, 8 GB or 12 GB in size. This is only an issue with Prinergy 2.1 systems. Prinergy 2.0.7 and below are not affected by this bug because it was not possible for a datafile to extend onto a 4 GB boundary in those releases.

For more information see the Prinergy troubleshooting case [ID: 44474].

Symptom:
The Preps 4.2.3 Updater cannot update a prior version of Preps.

Macintosh error: "The default location for this install cannot be found. This install will be cancelled."
Windows error: "The Preps 4.2.3 Updater could not find a prior installation of Preps to update. Please ensure that a valid copy of Preps 4.2 has been installed in the location specified by the Destination Folder field."

Cause:
The Preps 4.2.3 Updater can update only Preps 4.2.2; it cannot update any other version of Preps.
Or:
If the name of the application is changed, the Preps 4.2.3 updater does not recognize it.

For more information see the Preps troubleshooting case [ID: 80774].

This Alert applies to Synapse InSite, Prinergy, Prinergy Powerpack, and iMPAct.

Microsoft has issued a Security Alert to inform its customers about a new worm, named W32.Blaster.Worm, which is spreading quickly. This virus is also known as W32/Lovsan.worm, WORM_MSBLAST.A, and Win32.Posa.Worm.

Symptoms include the system rebooting every few minutes without user input and/or the presence of the file msblast.exe in the Windows\system32 directory.

For more information see the W32.Blaster.Worm troubleshooting item.