Bizhub C552 Fiery / Account Track - Scan to Email Problem Help

[stryder]

Hey Guys,

I have a problem with scanning to email with account track on. I've setup the machine to scan to email with the fiery using crossover cable and everything works fine. But once I turn on account track, the scan to email fails. I try to configure the fiery on browser but theres an error loading with java and I've tried on 5 different pc and mac and it didn't work. Any help and inputs is appreciated, thanks.

[emujo]

Don't use the Fiery for scanning, use the Emperon controller. Emujo

[stryder]

Don't use the Fiery for scanning, use the Emperon controller. Emujo

Yes, I am using the Emperon controller to scan to email. But as soon as I enable account track, it disables scan to email functions which was working with no account track on. So with the account track on, scan to email through emperon fails...

[slimslob]

I am not a Bizhub tech nor am I familiar with Account Track. Based on what I know from Ricoh machines, does Account Track require SSL and does the email provider require SMTP over SSL? With Ricoh, you can only use SSL with one function, either SMTP over SSL or an APP that requires SSL. I don't know if this will help but maybe.

[TheOwl]

Does the Account Track disable the scan settings or are you not able to select Scan to Email at all?

[Mr Spock]

Does the Account Track disable the scan settings or are you not able to select Scan to Email at all?

This could be the issue. Under the account track settings (or registration of new code) you can specify which options are allowed. Under main settings it is a global definition under account setup they are account specific.

[stryder]

I can press the buttons, it'll just fail after I try to send it. With account track off, everything sends out fine.

[kingarthur]

What reason does it give for failing..."server connect error", "login error", etc

[stryder]

It says something like Failed to complete job if I remember correctly.

[TheOwl]

Job Deleted Due to Error is a generic error, you will need to go into the job log on the machine, select the job that failed and press on Details which will give you more information.

You should also print out a Job Log from the Fiery as well.

Both of these should give you some further insight into your problem.