Unable to install printer Error Message
Les
the LPT1 port, I get the message "Unable to install Printer. Operation could
not be completed."
The wizard does not see the printer, but lets me pick one from a list,
installes the driver, then gives me the error message. The event viewer then
records that the printer was deleted. No printer related errors in the
event log.
There are no printers listed in my printers folder. (There USED to be an
Okipage 14e, but it hsa disappeared.)
The computer WILL print from a DOS screen.
Things I've tried:
I uninstalled & Reinstalled the LPT port. (Even though windows reported it
as functioning properly)
Tried different cables & different physical printers (as mentioned above.)
(The cables & printers work fine on another PC.)
I waded through 3000+ messages on this board and have tried deleting
ntprint.pnf & printupg.pnf as suggested in another message here.
Any suggestions short of reloading Windows?
Les
installed (I tried reinstalling it already). Logged in locally as an
administrator. I tried 2 different administrator accounts (I created the 2nd
one) since I've seen weird things happen in XP and W2K that are user
specific.
"Les" <lvi...@hereintown.net> wrote in message
news:v7jkokq...@corp.supernews.com...
Robert Orleth [MSFT]
weird reason ended up in the XP system folder. I suggest you run "sfc
/scannow".
Another reason can be that your PATH environment variable has been modified
to NOT include "%windir%\system32\wbem" (%windir% expands to something like
c:\windows if you type "set PATH" from a comment prompt.
Let us know if that doesn't fix the problem.
I think I better go put together a troubleshooting list for that kind of
failure... Weird as those corner cases sound, in each case I've seen more
than one instance.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Les" <lvi...@hereintown.net> wrote in message
news:v7jlc0a...@corp.supernews.com...
Paul Rodden
news:uFO6YVw7...@TK2MSFTNGP10.phx.gbl...
> I have seen that happen in one case where mscms.dll from Windows 95 for
some
> weird reason ended up in the XP system folder. I suggest you run "sfc
> /scannow".
>
> Another reason can be that your PATH environment variable has been
modified
> to NOT include "%windir%\system32\wbem" (%windir% expands to something
like
> c:\windows if you type "set PATH" from a comment prompt.
Hi - I have the same problem, and have gone through similar steps as Les
has.
I've just checked both of the above. For me, the Mscms.dll shows its
version as 5.1.2600.1106, which is consistent with other dlls in the
system32 folder (although it's date is newer than most of the other dlls).
I do have C:\Windows\System32\Wbem in my path.
Unfortunately, "sfc /scannow" doesn't do me much good, as it wants the XP cd
(which isn't supplied with my system, as the mfr elected to just supply one
of those piece of junk "recovery" cds - arrggh!).
Any other suggestions?
Thanks,
Paul
Les
The "piece of junk recovery cd" (I call it something worse then that, but
want to keep it clean here. <g>) is how Microsoft WANTS the manufacturer to
ship OEM versions of Windows. I dislike the policy, that's why any time I
buy a computer, I insist on getting a full copy of windows with it. (My
manufacturer calls it a "DSP" version.) It costs a little more, but it's
worth it IHMO.
Les
"Paul Rodden" <nospam_...@jwscorp.com_nospam> wrote in message
news:F9pea.2$A85.1...@newssvr11.news.prodigy.com...
Les
Path statement is correct, the MSCMS has the same date stamp & version as
other DLLs in the system folder.
Ran SFC /scannow. It still is giving me tyhe same trouble. I rebooted the PC
(Just in case it might help after running SFC) and tried installing a
printer again, with the same error.
A troubleshooting list is a GREAT idea. (BTW, I searched Microsoft.com for
this problem and found nothing related to XP for this problem. My search
only turned up problems for NT, which were fixed by a service pack.)
Les
"Robert Orleth [MSFT]" <ror...@online.microsoft.com> wrote in message
news:uFO6YVw7...@TK2MSFTNGP10.phx.gbl...
Robert Orleth [MSFT]
the log. That seems to indicate the driver got installed OK, the queue got
created but when the driver was called to let it know that it's supposed to
handle that queue, it failed and hence the queue gets deleted.
Are those drivers that you're trying to install the inbox drivers ? Signed,
no popups during the driver installation ?
Assuming the answers are yes, I am out of ideas - any chance I could debug
your machine, through the remote assistance feature of Messenger ?
We can take this offline - to do so, take the online. off my return
address...
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Les" <lvi...@hereintown.net> wrote in message
news:v7kf2pp...@corp.supernews.com...
Robert Orleth [MSFT]
something that needs replacing. You can check the event viewer to find out
what that file is, and you should be able to scrape that off the recovery CD
somehow (no idea what layout yours comes with, and I am not sure that this
is indeed the MS recommendation).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Rodden" <nospam_...@jwscorp.com_nospam> wrote in message
news:F9pea.2$A85.1...@newssvr11.news.prodigy.com...
Les
nobody was able to find a fix. The people I asked are all in the computer
field, some are MCSE's. I got frustrated over the weekend & re-installed
windows to fix it.
If you do create a troubleshooting checklist for similar problems, I'd love
to have a copy of it.
Les
"Robert Orleth [MSFT]" <ror...@online.microsoft.com> wrote in message
news:exRPI#A8CH...@TK2MSFTNGP11.phx.gbl...