uProduce 5.0 FATAL ERROR

[Brooks]

We recently upgraded to 5.0 and have started getting the following
error almost every time we try to generate print output: Fatal generic
system error: XMPieOnNewRecordsCommand. exception - Export Error: The
Adobe Print Engine has failed to output your data due to an unknown
problem.

I've reinstalling both uProduce and Adobe InDesign Server CS5 to no
avail. We are a Xerox/XMPie customer and I have opened a case with
ASG, but I wanted to see if anyone else has had this issue and if so,
has been able to resolve it. Our digital print production is at a
stand still at the moment, any help would be greatly appreciated.

[modsyn]

We just upgraded yesterday and are seeing the same thing. We haven't
had enough time to figure it out. I would be interested in hearing if
you found a cause for the error (or, even better, a fix for it).

On Oct 5, 7:09 am, Brooks <brooksbal...@gmail.com> wrote:
> We recently upgraded to 5.0 and have started getting the followingerroralmost every time we try to generate print output: Fatal generic
> systemerror: XMPieOnNewRecordsCommand. exception -ExportError: The

[ed kotnik]

Hi-
I can't take the credit for this tip. Brooks helped me find this
solution in the 5.0.1 Release Notes PDF page 33.

Known Issues and Limitations in Version 5.0.1
Production
1. Unique with Inline optimization might cause production flaws.
As a precaution, this optimization is disabled.
2. On uProduce systems that use InDesign Server CS5, Documents that
contain
transparency effects (including shadow, blur etc.) sometimes fail to
produce
Print Output files. This happens only at the early production stages.
If you
follow up with another production, the new production job does
succeed.
If this is the case, the failure might be caused by InDesign CS5
startup issues.
As a workaround, you can use a registry key named InDesignRestartSleep
to set uProduce to wait longer for InDesign CS5 to start up properly.
This
normally resolves all issues. A value of 3 seconds is a good default
setting,
which does not cause significant production delays (note that this
“sleep
time” is not applied to all production jobs, only to a very small
amount).
To set the InDesignRestartSleep key, proceed as follows:
a) Open the Registry Editor (Start > Run > Regedit).
b) In the Registry Editor window, under My Computer, go to one of the
following
folders:
 For 32 bit systems:
HKEY_LOCAL_MACHINE>SOFTWARE>XMPie>XMPie uProduce Server
Object>1.00.000
 For 64 bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\XMPie\XMPie
uProduce Server Object\1.00.000
c) If the InDesignRestartSleep property is not listed, configure it
now:
Right-click the 1.00.000 folder, select New > String Value from the
context
menu and set the new property’s name to InDesignRestartSleep.
d) Set the InDesignRestartSleep property to the desired sleep time in
1/1000 of a second. For example, to set the value to 3 seconds, double
click
it to display the Edit String window and set Value Data to 3000.

[modsyn]

Thanks, that seemed to have worked!

[modsyn]

I take it back. We're still getting the error. Only now it's only on
SOME of the jobs.
For instance, we split one job into 9 batches and only 3 will
complete. The rest give the unhelpful error:
"Fatal generic system error: XMPieOnNewRecordsCommand. exception - The
server threw an exception."

So, it's back to the drawing board for us...

[Jan N]

We had the some error after the last upgrade and in our situation it
was a problem of licenses. We have a base server and an extension
server and there was something switched. The baseserver tried to run
four processes at the sametime and the extensionserver one. Before th
it should be the update it was the other way around. After fixin' no
fatal errors anymore. Perhaps in your case this is also the problem.

[modsyn]

Well, it seems like we have found out how to stop the errors. It's
very strange, but setting the priority to greater than normal (either
high or immediately) seems to allow all of the jobs to complete with
no errors. If we use normal priority about two-thirds of the batches
error out with the generic error message. I'm not sure why that works
but for us it has been the reliable solution.

So, for anyone else seeing this error add that to the list of things
to try.