Server busy

[roho]

Hello! I'm dealing with a customer who has multiple copiers, Canon and Sharp. The problem is the Canon copiers cannot be reached thru RUI. The message "server busy" appears. The only unaffected Canons are the only 2 connected to a Fiery. Has anybody encountered this before?
Any suggestions?
Thanks for taking the time to read this post!

[alex@wocltd.com]

where does the message appear?
have you tried laptop with crossover?
more info please!

[Guest]

Hello! I'm dealing with a customer who has multiple copiers, Canon and Sharp. The problem is the Canon copiers cannot be reached thru RUI. The message "server busy" appears. The only unaffected Canons are the only 2 connected to a Fiery. Has anybody encountered this before?
Any suggestions?
Thanks for taking the time to read this post!

What kind of canon machines they have? This can happen if firmware is corrupted. Try clearing MMI, if that don't work clear MCCON and reload firmware, pay attention to rui as it installs.

Also as alex suggested try the laptop first before doing anything.

[KenB]

It's been quite a while, but I remember seeing this when various components of the firmware were "mismatched", meaning the wrong version of the RUI compared to the Main Controller, etc...

If connecting via a notebook and crossover doesn't work, you may want to consider flashing all of the MFP firmware. That way, you can be certain that every component will "talk to" all the others.

[bnmand]

It's been quite a while, but I remember seeing this when various components of the firmware were "mismatched", meaning the wrong version of the RUI compared to the Main Controller, etc...

Yeah. This can happen if firmware isn't updated properly. This could be when a network kit is installed or when updating the firmware for some other reason. You can check in Service Mode to see if the right version of RUI is installed (if at all) e.g. on the IR3300 go to service mode (press * then 2,8 together then *). Go to Copier > Display > Version. Check that your RUI version is the correct version that goes with the version of MN-CONT you have installed. If you need to use SST, to make sure firmware is overwritten select overwrite.

If connecting via a notebook and crossover doesn't work, you may want to consider flashing all of the MFP firmware. That way, you can be certain that every component will "talk to" all the others.

If the machine is very old it may need a nethawk (special canon usb-to-parallel cable) cable or a parallel IEEE1284 cable.

[roho]

We've tried conx with a laptop and xover cable. The models in question are ir5055, irc 3480. The crunch to this is that different m/cs at one location have this problem at the same time. None of the m/cs have been flashed. They are recent installs, within last 6 months. I'm thinking maybe a setting the cust changed, or n/work condition. Thanks for your suggestions so far!

[bnmand]

We've tried conx with a laptop and xover cable. The models in question are ir5055, irc 3480. The crunch to this is that different m/cs at one location have this problem at the same time. None of the m/cs have been flashed. They are recent installs, within last 6 months. I'm thinking maybe a setting the cust changed, or n/work condition. Thanks for your suggestions so far!

Can you ping the copier? I'd still try flashing via SST if all the other suggestions have failed. It could still work.

[roho]

Actually they print-just the RUI is a problem, and only on the m/cs with out a Fiery. The 2 m/c with a Fiery work fine!

[Guest]

Actually they print-just the RUI is a problem, and only on the m/cs with out a Fiery. The 2 m/c with a Fiery work fine!

I would check RUI in system settings and see if its turned on.
I would flash it as well, RUI could be corrutped.

There was a case with this model where as the HDD had to be formatted, and all of the software needed to be flashed, to resolve this issue on a iR5055.

[roho]

Thanks for all your suggestions! I've benn able to dtgermine the latest fware for the models in question. I've flashed 1 copier for now, to see if it makes any difference. Still think something on their n/work changed, as it would be a coincidence for these problems to show up simutaenously.