Error 0x00000242 when adding x86 printer to x64 Server 2008 Print Server


we attempting replace several printers on our network , i'm working on updating drivers.  x64 driver updates server going fine.  however, when attempt add x86 print drivers 32-bit client, experiencing problems.  here details of process

server - windows server 2008 x86 sp2

printers (though believe unrelated), switching older laserjet 4100 printers kyocera fs-1370dn printers.

client - have tried using vm using windows vista sp2 32-bit, vm using windows 7 sp1 32-bit, , local network client natively running windows 7 (no sp) 32-bit.

i create console , add print management snap-in connecting print server.  navigate installed printer, , "properties" on printer.  when asks if wish install driver, click "no" can browse later.  go sharing tab, , click "additional drivers...".  click x86 check-box, , click ok, @ point browse appropriate folder our drivers.  drivers begin install, finish, , after finishes, receive following:

"unable install kyocera fs-1370dn kx, x86, type 3 - user mode driver.  operation not completed (error 0x00000242)."

i have searched thread error code, in addition standard web searches, , found nothing.  out of ideas, , without knowing error code means, cannot go further.   @ point, if there manual way of copying in x86 drivers print server can around this issue, great.

any information or appreciated.


gets wants. me, wanted sysadmin. , sins --they made me one.

arthur,

we have situation fixed --perhaps things have changed in windows print server history not aware of?

our kyocera tech came out, , asked me if i'd checked x86 box under sharing tab --but server side.  told him hadn't, because best practices aware of involved installing driver x86 client running print management console.

we tried way, , worked.  think error due installing client-side.  i'm still unsure how able install x86 driver direct x64 server, though; prompted me location, specified, , let me, unlike in past, i'd errors unsupported processor type.

it fixed, if best practices have changed, i'd interested know.


everyone gets wants. me, wanted sysadmin. , sins --they made me one.


Windows Server  >  Print/Fax



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607