BizHub 500 Lockup

[Guest]

I have 4 BizHub 500 systems and intermittently one of them will completely lockup. The console is somewhat operational and the current job status is set as "Deleting" however nothing ever happens. We have waited over 24 hours for the job to be deleted.

The web interface is accessible and the machine appears to look as though nothing is wrong with it. When we try to delete the locked job (which is already flagged as "Deleting") or any other job it just flags the job as deleting.

Sometimes all jobs will show as "Printing" instead of "Deleting".

The only way to recover from this is to cycle power which causes us to loose 15-20 jobs in the queue.

We have had this problem for about two years and have not been able to track anything down as to what is causing it.

Any help would be greatly appreciated.

Thank you

[konisolver]

What firmware level? If you are using version 31 and printing from Adobe 8 there is a bug with the Visual PS driver. Update the unit to 31GUP and PsVisual to 310.

[Juggy]

If you have a HDD installed try replacing with a new one. We had similar problem in a Bizhub 350 the machine used to freeze and we needed to power off and on to restart.

[jamacdon]

What firmware level? If you are using version 31 and printing from Adobe 8 there is a bug with the Visual PS driver. Update the unit to 31GUP and PsVisual to 310.

The MFP Controller reports 50GA-0100-GUP-31-000 and using PCL Driver 3.01.00.00.

We do use Adobe however many times when it locks up it can be from a print job (word, outlook, adobe) or a copy job as well.

[jamacdon]

If you have a HDD installed try replacing with a new one. We had similar problem in a Bizhub 350 the machine used to freeze and we needed to power off and on to restart.

This sounds like a possible solution however we have 4 systems and they all seem to freeze up. Do you think it could possibly a specific hard drive model or batch even?

On a side note we also have 2 BizHub 600's that do the exact same jobs and have never locked up.

[redhawkpath]

This is definately a firmware issus. Try upping the firmware to the latest version.

Hard Drive Next, but first the firmware.

[redhotrob]

At least with having more then one machine, only one with the problem, you can print off all the user and service setting to see if there is anything odd with that one.
And if you were to try a hard drive you could swap from one machine to the other.

[jamacdon]

At least with having more then one machine, only one with the problem, you can print off all the user and service setting to see if there is anything odd with that one.
And if you were to try a hard drive you could swap from one machine to the other.

Actually they all have the lockup issue. It is not isolated to one machine.

Someone mentioned to me that it could be faulty or bad networking equipment. I can't see this being the case as we have various technologies on our net ranging from linux boxes to voip systems and nothing else has a problem.

[Scott_Lewis]

Take note of which PC/user is at the top of the print queue when the controller locks up. It could be a single mangled computer sending garbage to the copier. He locks one up, then moves on to another.

[ITCHYFINGER]

I have 4 BizHub 500 systems and intermittently one of them will completely lockup. The console is somewhat operational and the current job status is set as "Deleting" however nothing ever happens. We have waited over 24 hours for the job to be deleted.

The web interface is accessible and the machine appears to look as though nothing is wrong with it. When we try to delete the locked job (which is already flagged as "Deleting") or any other job it just flags the job as deleting.

Sometimes all jobs will show as "Printing" instead of "Deleting".

The only way to recover from this is to cycle power which causes us to loose 15-20 jobs in the queue.

We have had this problem for about two years and have not been able to track anything down as to what is causing it.

Any help would be greatly appreciated.

Thank you

I AGREE WITH THE HARD DRIVE REPLACEMENT. I HAVE HAD SEVERAL 200'S AND A 350 LOCK UP SOLID AS WELL A 600. EVERY TIME THE FIX WAS REPLACING THE HARD DRIVE.

[mitchl]

Has anyone else noticed that there's something about a copier that just pisses a HDD off to the max? I have never seen so many bad hard drives in my life since they started using them in copiers, I wonder if it doesn't have something to do with vibration or something along those lines or is it that they are made in China and other less than quality oriented locales?

By the way has anyone done any searching in the knowledge base for similar probs and fixes, if so what did you find? I'm sure if everyone here has seen the problem they must be recommending something or at least one would assume.

[pepper38_cnd]

Just out of curiosity are the machines that are locking up setup to require access codes to copy and print?

[jamacdon]

I AGREE WITH THE HARD DRIVE REPLACEMENT. I HAVE HAD SEVERAL 200'S AND A 350 LOCK UP SOLID AS WELL A 600. EVERY TIME THE FIX WAS REPLACING THE HARD DRIVE.

When your systems would lock up, was the console still operational? Could you still ping the machine and would it still accept jobs? I have been thinking about the hard drive issue and not sure if that would affect the entire operation of the machine or just the job processing.

I almost seems as though the entire machine is working fine except it has gone into a loop trying to cleanup after processing a job.

[pepper38_cnd]

You didn't answer my question about access codes?

The reason I asked is because I have seen exactly what you are describing happen on some other machines when a person tries to delete a print job without entering the access code of the person who sent the print job. The que says deleting and the only way to reset is to power off. This is a firmware issue the machine should say access denied, and continue printing.

[jamacdon]

Just out of curiosity are the machines that are locking up setup to require access codes to copy and print?

They do not require access codes on hte machine itself however there is a 3rd party device used to lock/unlock the machine. We have tried operating without this device hooked up and it still locks up.