Losing printer drivers?!

Windows Server 2003 DC, hosting about 40 network printers. 350 client
machines, running a mix of Win2K Pro & WinXP Pro.

We've been way behind on our client updates, and recently implemented WSUS
3.0. We've been pushing security & critical updates to our 2000 & XP Pro
workstations. We've noticed we're getting tons of calls saying they can't
print, and when you right-click the printer to get to it's properties, it
says that a driver must be installed. We delete and readd the printer, and
everything's ok until it happens again. This is happening on 3-15 computers
per day, and getting to be a HUGE problem.

I'm assuming this is due to an update of some sort, but endless searching
hasn't turned up anything applicable. I notice in the event logs, I get the
following.

Failed to ugrade printer settings for printer
\\%CLIENT_NAME%\%PRINTER_NAME%,LocalOnly driver
C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\unidrvu i.dll error 126.

Seems like no pattern between clients, rarely the same printer, just similar
problems across the board. Where to start? I'd be glad to post any logs, or
try anything at this point.

> Where to start?


Probably a different newsgroup? ; )

cross-post added to XP Printing...

BTW there is also a specific one for Windows 2000 Printing too
but nothing related for server that I can see.


Good luck

Robert Aldwinckle
---


"Brian - Reno County IT" <> wrote in message
news:3F8DC648-A7E1-4F2F-84D9-...
> Windows Server 2003 DC, hosting about 40 network printers. 350 client
> machines, running a mix of Win2K Pro & WinXP Pro.
>
> We've been way behind on our client updates, and recently implemented WSUS
> 3.0. We've been pushing security & critical updates to our 2000 & XP Pro
> workstations. We've noticed we're getting tons of calls saying they can't
> print, and when you right-click the printer to get to it's properties, it
> says that a driver must be installed. We delete and readd the printer, and
> everything's ok until it happens again. This is happening on 3-15 computers
> per day, and getting to be a HUGE problem.
>
> I'm assuming this is due to an update of some sort, but endless searching
> hasn't turned up anything applicable. I notice in the event logs, I get the
> following.
>
> Failed to ugrade printer settings for printer
> \\%CLIENT_NAME%\%PRINTER_NAME%,LocalOnly driver
> C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\unidrvu i.dll error 126.
>
> Seems like no pattern between clients, rarely the same printer, just similar
> problems across the board. Where to start? I'd be glad to post any logs, or
> try anything at this point.
>
>
>

There is some module missing somewhere
error 126 is:
126 ERROR_MOD_NOT_FOUND

Was the print server updated recently? Check for BUD????.tmp files in the
\windows\system32\spool\drivers\w32x86\3 directory.

Can the client fix the issue by deleting the connection, deleting the print
driver (need to be admin) and making a new connection?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Robert Aldwinckle" <> wrote in message
news:...
>> Where to start?
>
>
> Probably a different newsgroup? ; )
>
> cross-post added to XP Printing...
>
> BTW there is also a specific one for Windows 2000 Printing too
> but nothing related for server that I can see.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
> "Brian - Reno County IT" <>
> wrote in message
> news:3F8DC648-A7E1-4F2F-84D9-...
>> Windows Server 2003 DC, hosting about 40 network printers. 350 client
>> machines, running a mix of Win2K Pro & WinXP Pro.
>>
>> We've been way behind on our client updates, and recently implemented
>> WSUS
>> 3.0. We've been pushing security & critical updates to our 2000 & XP Pro
>> workstations. We've noticed we're getting tons of calls saying they
>> can't
>> print, and when you right-click the printer to get to it's properties, it
>> says that a driver must be installed. We delete and readd the printer,
>> and
>> everything's ok until it happens again. This is happening on 3-15
>> computers
>> per day, and getting to be a HUGE problem.
>>
>> I'm assuming this is due to an update of some sort, but endless searching
>> hasn't turned up anything applicable. I notice in the event logs, I get
>> the
>> following.
>>
>> Failed to ugrade printer settings for printer
>> \\%CLIENT_NAME%\%PRINTER_NAME%,LocalOnly driver
>> C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\unidrvu i.dll error 126.
>>
>> Seems like no pattern between clients, rarely the same printer, just
>> similar
>> problems across the board. Where to start? I'd be glad to post any
>> logs, or
>> try anything at this point.
>>
>>
>>
>
>

We are having the EXACT same issue at three different locations. All Windows
Server 2003 with network printers. We are using WSUS 3.0 and after pushing
updates out all hell broke lose but we don't know which one to uninstall to
fix the issue.

Many of our clients machines are having the issue (2000/XP/Vista all have
the issue). We also have a Citrix impementation and many of the citrix users
are having the same issue. We are in a serious situation here.

I'm not sure which part of the print server you're referring to...
It's patched monthly with Windows Updates, and the entire server was
replaced about 6 months ago.. However the issues didn't start until
about 2 months ago.. Possibly related?

I checked, couldn't find any bud*.tmp files anywhere... But I sure
appreciate that you were the only one to respond!!





On May 29, 1:03 pm, "Alan Morris [MSFT]" <ala...@online.microsoft.com>
wrote:
> There is some module missing somewhere
> error 126 is:
> 126 ERROR_MOD_NOT_FOUND
>
> Was the print server updated recently? Check for BUD????.tmp files in the
> \windows\system32\spool\drivers\w32x86\3 directory.
>
> Can the client fix the issue by deleting the connection, deleting the print
> driver (need to be admin) and making a new connection?
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Robert Aldwinckle" <rob...@techemail.com> wrote in message
>
> news:...
>
>
>
> >> Where to start?
>
> > Probably a different newsgroup? ; )
>
> > cross-post added to XP Printing...
>
> > BTW there is also a specific one for Windows 2000 Printing too
> > but nothing related for server that I can see.
>
> > Good luck
>
> > Robert Aldwinckle
> > ---
>
> > "Brian - Reno County IT" <BrianRenoCount...@discussions.microsoft.com>
> > wrote in message
> >news:3F8DC648-A7E1-4F2F-84D9-...
> >> Windows Server 2003 DC, hosting about 40 network printers. 350 client
> >> machines, running a mix of Win2K Pro & WinXP Pro.
>
> >> We've been way behind on our client updates, and recently implemented
> >> WSUS
> >> 3.0. We've been pushing security & critical updates to our 2000 & XP Pro
> >> workstations. We've noticed we're getting tons of calls saying they
> >> can't
> >> print, and when you right-click the printer to get to it's properties, it
> >> says that a driver must be installed. We delete and readd the printer,
> >> and
> >> everything's ok until it happens again. This is happening on 3-15
> >> computers
> >> per day, and getting to be a HUGE problem.
>
> >> I'm assuming this is due to an update of some sort, but endless searching
> >> hasn't turned up anything applicable. I notice in the event logs, I get
> >> the
> >> following.
>
> >> Failed to ugrade printer settings for printer
> >> \\%CLIENT_NAME%\%PRINTER_NAME%,LocalOnly driver
> >> C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\unidrvu i.dll error 126.
>
> >> Seems like no pattern between clients, rarely the same printer, just
> >> similar
> >> problems across the board. Where to start? I'd be glad to post any
> >> logs, or
> >> try anything at this point.- Hide quoted text -
>
> - Show quoted text -