I have migrated an existing system B40Cc4mcr0 over to a new server with Unix/Oracle. OS went from Sun 2.6 to 2.8. I used the baan conversion utility to move user and printer data over to new box. Unix admin has set up the printers on unix and I have moved all the drivers over from the printinf directory. When I try to print from Baan, I get a 'bad printer' error. Does anyone have any suggestions?
Thanks,
bb

Are there any errors showing up in $BSE/log files like log.filter6.2? Please post any entries --thanks!

I have migrated an existing system B40Cc4mcr0 over to a new server with Unix/Oracle. OS went from Sun 2.6 to 2.8. I used the baan conversion utility to move user and printer data over to new box. Unix admin has set up the printers on unix and I have moved all the drivers over from the printinf directory. When I try to print from Baan, I get a 'bad printer' error. Does anyone have any suggestions?
Thanks,
bb


Hello,
an idea,
maybe the UX printerqueues on new server are not identical to the old ones ?
Are you able to print from unix with lp command ?

What kind of UX printers (remote, network based) ?
Update your profile please.

Regards

Hi-
There are no current entries in any log files. The print queues are identical on both servers. We are using HP laserjet printers and they are set up as 'printer' in Baan. The print daemon is running and there are no errors in that log either. I had this exact same 'bad printer' problem once when I was learning to create a new driver. :D But, the driver files appear to be identical. Oh, the lp command works from unix.
Here is something. When I set up the printer as 'Direct' and give the lp options, I am able to print from Baan. This confused me and I thought maybe the print daemon is not working properly.

any reason why you're using type "printer"? that's technology from 1908
i believe..

As far as the bad printer error goes, i would actually do a "diff" between
the two files. there could be an extra space somewhere causing the problem.

otherwise it may be a bug in the pdaemon (since you're the only one using it anymore... =) ) it may not have been noticed.

Dave

Well, you learn something new everyday. I didn't realize pdaemon wasn't wildly popular. :D
I had to restart the pdaemon several times and reset device status to get it to work.
Thanks for your help.
bb

heheh sounds about right! =)

Dave