Fiery Rip with Xerox 800 - Crashes and then "unable to connect"

[Guest]

Press running fine and then fiery crashed. Tried to reconnect and got this.

Unable to connect to (Fiery). The server name or ip address may be invalid.

I thought I'd try to change ip address of the press. Does anyone know how to do that or have any other ideas?

Thanks!

 

[Guest]

OK... so we reinstalled command workstation and can now connect the fiery to the Xerox 800. However, now we cannot get our paper list catalog to populate on the Fiery. Is there some way you have to link the firey to the color press to display this list in the media job properties drop down?

 

[pacart]

do you connect to the fiery from another computer or are you working directly from the fiery?

 

[pacart]

This might have something to do with permissions, try logging in as administrator if you aren't already and see if that helps

 

[Guest]

The tray error turned out to be a software conflict. When we recovered from the crash we installed fiery server 1.1 but should have been 2.2.
Xerox second level tech in all day today. Completely rebuilt Fiery with all new windows install from scratch. About an hour after he left, it crashed again right in the middle of a press run.
Something seriously wrong in the fiery box. Bad hard drive? Bad power supply? Any ideas???

 

[PricelineNegotiator]

Probably a bad motherboard or PSU. Perhaps clearing the memory by unplugging the box and holding the power button for 30 seconds and or resetting the CMOS could clear any resonant bugs. But if he formatted the drive with Windows again and new software, this shouldn't really do anything. Sounds like a hardware issue.

 

[dabob]

We are having the same type of issues with out 770 . . . service man due in again today . . .

 

[gig0]

Kringle, can you define "crash"? Does the Fiery Server reboot or just the application? If the server is shutting down, you want to uncheck Automatically Restart under the Startup & Recovery options in Windows. This will give you a Bluescreen (of Death) when it crashes but will help point in a direction of the failure.

 

[Guest]

It completely and instantly shuts down the software and the shuts down the computer as though somebody hit the "shutdown" button. Come up with the wheel and says "shutting down"

We found that the dvd drive was defective and we unplugged it last night. Haven't had a crash since then, but it's still early in the day here. Let's hope that is was the problem. Can a defective dvd drive with no disc inserted cause this issue?

 

[gig0]

Drivers can become corrupt (or incompatible) with Windows updates. I had a secondary display driver for remote connections (specifically, Logmein) cause my Windows 7 box to crash immediately after a Windows update about two months ago.

If you really want to get to the root of the problem, try reconnecting the DVD but disable the driver in the device manager and go from there.

 

[Guest]

All of our crash and reload down time put us really far behind. Luckily the press is back up and running now. I'm a bit gun shy to try anything until we get caught up. But when we do, I'll give that a shot. Thanks for the direction!