Page 2 of 4 FirstFirst 1 2 3 4 LastLast
Results 11 to 20 of 39

Thread: KM C1085 Fiery 308 Server Crashing

  1. #11
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default Update for today

    So this morning we printed 2 small jobs with no crashes.

    We printed some covers for a programme SRA3 colour duplex 2up with no crashes

    Now printing body of programme in b/w 44 pages and attaching preprinted cover, 2 crashes so far so we limit the print run to 20 books and then keep printing 20 books and we have stopped the crashes.

    Bugger Crashed again after 5 books printed.
    Last edited by Baldbug; 08-04-2016 at 09:27 PM.

  2. #12
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    The memory available on the C1085 console is running at 3.8% to 1.9% in orange colour.

  3. #13
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    All programmes finished. No more to print today. Replacement HD and RAM to be installed Monday.

  4. #14
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    New HD and RAM installed today. 7.5 hours of Software install done today with auto Windows patches install overnight.

  5. #15
    Steve0 is offline Fiery Forum Expert Contributor Steve0 is on a distinguished path
    Join Date
    Aug 2009
    Posts
    249

    Default

    Assuming success, my advice: immediately clone an image of the known-good working hard disk to a 32 GB jump drive. That way, should the worst happen, and the Fiery has to be reloaded from scratch, it can be done in a hour or two instead of eight.

  6. #16
    Join Date
    May 2009
    Location
    Minneapolis, MN
    Posts
    729

    Default

    I should also say IC-308 v1.1 is also currently supported (since v2.1 is a paid upgrade)

    I see you replaced some hardware, then reloaded v1.1 - then installed all Windows patches.

    But I don't see any mention of updating all Fiery patches via Fiery's System Updates utility. That is critical to do. Please make sure it is done.

  7. #17
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    The Hard Drive has been replaced, the RAM has been replaced, the Windows Software has been upgraded, and The Fiery CWS software is now updated.

    First job ran 20 sheets of 200 sheets and the complete system came to a halt as usual. The C1085 is still on but stalled, the Fiery Workstation is still on but stalled.

    HELP
    Last edited by Baldbug; 08-08-2016 at 06:08 PM.

  8. #18
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    This is a pic before I rebooted.

    ** If anything I think it is worse now than before. We only printed 20 sheets. Stock is a 300gsm Digi flat stock, printed in colour and duplex.

    Last week we were getting more printed before crashes happened.
    Attached Images  
    Last edited by Baldbug; 08-08-2016 at 06:13 PM.

  9. #19
    Steve0 is offline Fiery Forum Expert Contributor Steve0 is on a distinguished path
    Join Date
    Aug 2009
    Posts
    249

    Default

    Quote Originally Posted by Baldbug View Post
    The Hard Drive has been replaced, the RAM has been replaced, the Windows Software has been upgraded, and The Fiery CWS software is now updated.

    First job ran 20 sheets of 200 sheets and the complete system came to a halt as usual. The C1085 is still on but stalled, the Fiery Workstation is still on but stalled.

    HELP
    Updating Command Workstation is less important than patching your Fiery software. Look for Fiery > System Updates in the Programs menu from the Windows Start button. Make sure everything is set to download and install (not just notify), and click on "Check Now". You'll have to reboot the Fiery a few times between patches, but these are more likely the things to keep your Fiery from crashing. Not Command Workstation.

  10. #20
    Baldbug is offline Senior Fiery Forum Contributor Baldbug is on a distinguished path
    Join Date
    Aug 2015
    Posts
    59

    Default

    Quote Originally Posted by Steve0 View Post
    Updating Command Workstation is less important than patching your Fiery software. Look for Fiery > System Updates in the Programs menu from the Windows Start button. Make sure everything is set to download and install (not just notify), and click on "Check Now". You'll have to reboot the Fiery a few times between patches, but these are more likely the things to keep your Fiery from crashing. Not Command Workstation.
    Yes this has been done.

    Just moving the IP Address away from all the workstations and local area PC's Macs and pheripherals are set.

Page 2 of 4 FirstFirst 1 2 3 4 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts