Vista 64 installs printers, won't print

I see no mention of Intuit in the OP's post as seen here on the message
from the MS NNTP server. This message seems to have come through a gateway
to this newsgroup.

Regardless-

The failure sequence might have been: function/system call -> printer driver
failure -> spooler failure (possibly involving a prior RPC) -> failure of
all printer drivers.

If the fault only appears in conjunction with the Intuit program, perhaps
some help can be had from them.

Scant help, I know but that's all I can say given the OP's information as
seen here.
--

Tom
MSMVP 1998-2007




"ddlnick" <guest.RemoveThis@unknown-email.com> wrote in message
news:68e6160e305315471b3d231f284f8836@nntp-gateway.com...
>
> We develop software and we are convinced that this is not an Intuit
> problem, but a bug in VISTA 64.
> In particular a Windows API DocumentProperties function call to get
> size of DEVMODE record for printer properties. See,
> 'On Vista x64, DocumentProperties fails from UAC-elevated process -
> MSDN Forums'
> (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2677398&SiteID=1)
>
>
> It does not affect all VISTA 64 users or all applications. Since it
> affects some Intuit users it appears to point to Intuit.
>
> You need to report this to Microsoft. Loudly.
> When the bug appears, it affects all printers installed on that
> computer. So it is not a printer driver problem.
>
>
> --
> ddlnick

I am the original poster-- I did not mention Intuit because, in fact, I
have no Intuit software on my computer. However, this does appear to me
to be a VISTA 64 issue, and it does, in fact affect all printers
installed on the computer. After many hours in chat with the Microsoft
Vista online support people, the problem does appear to be connected to
spooler functions, but we were not able to solve it. I finally used my
backup and system restore to restore my system to a point two weeks ago,
and my printing seems to work again.

The only significant additional software I added to my computer in the
past two weeks was Rogue Amoeba's Airfoil for Windows, which I was using
to stream foobar to a couple of airport express's. I have no idea if
the problem is connected to that, but I sent an email to Rogue Amoeba's
customer support.

I don't know how long this 'fix' is going to work or whether I solved
anything in the long run by restoring from an earlier point, so if
anyone has insight into this problem, please tell me!


--
neatokino

Some more notes based on our experience with VISTA64 and printing
problems. First, 32 bit applications run on a 'virtual environment'
called WOW64 in the VISTA64 system. This might be important.

As neatokino noted, a 'restore' to some previous point does work,
sometimes. For us, downloading Windows updates returns the problem.

The difficulty is convincing Microsoft that there is a problem with
their system. In general, for previous reports of the problem,
Microsoft cannot reproduce the problem, so the case is 'closed', and the
suffering software application trying to print is blamed. The problem
only appears on some computers. From a programmer's perspective, it
appears to be an 'initialization' situation, ie. the memory where some
data variable/s happen to be stored, on a particular computer, may or
may not have default value/s that are favorable or unfavorable to a
function call's result. As programmers, we are taught to initialize all
data to some known value, usually 0. So if the data happens to be
assigned memory that happens to have a proper initialized value, the
problem does not appear. On another computer, the data may be assigned
to memory with some random value, which may cause the function to return
'failure'.

In this case, we traced the call to DocumentProperties() which is used
to retrieve properties of a selected printer. There are two calls. The
first call is a simple request for the size of the DEVMODE structure
that the printer driver will need to fill with that printer's
properties. The application uses the size to allocate memory for the
properties which are filled in by a second call to DocumentProperties().

It is the first call that fails, no matter which printer is selected.
It is a very simple request, and one 32 bit integer value should be
returned in the range of 500 to 5000 or so. A -1 is returned, when the
bug manifests itself. A call to 'GetLastError()' does not indicate any
error.

Microsoft also provides a 'PrintDlg()' method in a comdlg32.dll which
provides a convenient 'wrapper' for the 'OpenPrinter()' and
'DocumentProperties()' and other printer management functions. Using
PrintDlg(), the error returned from CommDlgExtendedError() is
CDERR_MEMLOCKFAILURE 0x0000000a which seems to indicate that a 'lock'
on allocated memory of -1 size (-1 is also 0xffffffff a very large
number) is failing.

These are hints for the Microsoft programmers to check. I don't see a
whole lot of code to check. The size of DEVMODE request would seem to
be a straight 'pass through' to the printer driver identified by the
'handle' received from previous 'OpenPrinter()' call. Since all
printers fail, when the bug manifests itself, then the software code
'to' and 'back' from the printer driver call needs to be reviewed.


--
ddlnick

I have the same EXACT problem. After many many hours on my own and with HP
phone support(which was no help at all) I finally figured out that it's the
Airfoil program that causes the problem. Once it's screwed up I was unable to
fix it and had to do a complete restore to the initial factory setup (twice).

I've e-mailed Rogue Amoeba to see if there's a remedy but haven't heard from
them yet.

HP pavillion desktop
Vista home premium (64bit)
HP C5280 photosmart printer

"neatokino" wrote:

>
> My Vista 64bit system has suddenly decided to not print at all. I had
> no problems in the past, but last week I started to receive an error
> notice with programs: 'before you print, you need to select a
> printer...' (wordpad and adobe pdf reader); if I try to print a
> document in Word 2007, I get an error message that reads: 'windows
> cannot print due to a problem with the current printer setup.'
>
> I have tried deleting all my printers (a Canon all in one and an HP
> Laser Jet 1320) and reinstalling them. That worked once, but the
> problem recurred shortly thereafter. Now, if I delete and reinstall, I
> still can't get the printers to work, and I get the same old error
> messages.
>
> How does one go about fixing a problem like this? Can I use my
> original Vista install disk to fix just the printer function and leave
> everything else alone? This is, as you can imagine, a debilitating
> problem.
>
>
> --
> neatokino
>

Neatokino has indicated that printing problem affects well known
programs including ones from Microsoft own 'stable of programs' -
Wordpad and Word 2008. And other well known programs Adobe .pdf Reader,
Mozilla Firefox browser. I have noted 64 bit printer problems on
Intuit's (Quicken and Quickbooks) forum.

This NOT an individual application problem, but a VISTA 64 bit problem,
and Microsoft needs to 'take notice' and fix the problem. I have posted
on Microsoft's developer - MSDN - forum, but no response from Microsoft.

It is time to start taking the 64 bit systems back to 'Best Buy' or
similar, and tell them to replace with a system that works, i.e. 32 bit
VISTA.


--
ddlnick

Same problem. I have added no new software. I have Vista Home Premium
x64 on the computer.

How do I go back? What upgrade in Vista caused the errors to occur?
Can I restore to the day before that and turn off the auto update vista
system?

I am not a technical computer guy. I make plastic bottles for a
living, but I need to print.....


--
kevintheenginee

kevintheenginee;900529 Wrote:
> Same problem. I have added no new software. I have Vista Home Premium
> x64 on the computer.
>
> How do I go back? What upgrade in Vista caused the errors to occur?
> Can I restore to the day before that and turn off the auto update vista
> system?
>
> I am not a technical computer guy. I make plastic bottles for a
> living, but I need to print.....

It appears that Microsoft does not have a 'handy web form' or email
address
to send 'bug' reports to. They used to have such a way to report
problems.
Either they were 'swamped' with reports, or have decided that there are
no
more 'bugs' in any Microsoft product?

We 'googled' 'Printing problems in 64 Bit VISTA' or similar and found
three
'forums' with discussions on the subject. We figured a moderator would
take some interest and action to investigate. Apparently in this case,
Microsoft did a brief investigation, could not 'reproduce', and thus
'closed
the case'.

Microsoft's 'developer' forum. This forum has the best chance of
'getting
attention'. We have traced the problem to the specific Microsoft API
(DocumentProperties()) that fails to return the expected results.
'On Vista x64, DocumentProperties fails from UAC-elevated process -
MSDN Forums'
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2677398&SiteID=1)

Some users of Intuit's Quicken 2008 have the same problem. Maybe
someone at
Intuit has some contacts at Microsoft? Some 'work arounds' discussed.
'Quicken Community - Solution to Printing Problems Vista 64 Quicken
2008'
(http://www.quickencommunity.com/webx/Forums/Quicken%20Personal%20Finance%20Software%20Forum%20for%20Windows/Printing%20in%20Quicken/531/36)

'www.vista64.com' (http://www.vista64.com) seems to be 'official
looking', and appears to be good place
to
collect and discuss problems on VISTA 64.
http://www.vistax64.com/vista-print-fax-scan/192645-vista-64-installs-...nters-w

In our case, we have 32 bit software that runs fine on all versions of
Windows starting with Windows 95. The printing interface used is
provided
in the official Microsoft Foundation Classes (MFC). We use Visual C++
6.0
(getting a little 'old' perhaps, but works fine for our purposes). We
can
reproduce the problem on a HP 64 bit VISTA touch screen tablet pc -
state of
the art.

Some work arounds have been discussed on the forums mentioned.
Lowering the
'execution level' from Administrator to Standard level seems to fix the
problem for us, until Windows Updates 'kick in' on their daily
downloads.
Some of our customers report that a 're-boot' (power off/on restart)
fixes
the problem until Windows Updates. The forums lists other 'tricks'.


--
ddlnick

Same problem just appeared on my system (vista home premium running on
laptop with AMD Turion 64 x2). Every program I've tried to print from
(currently MS Word, Adobe Acrobat, Netscape) has it. Printers look
installed, and will print a test page if you go to the printer from
control panel, and select "properties" off the file panel and then click
print test page. Haven't tried rebooting yet, nor contacted MS; the
problem just appeared. Looks like a problem MS needs to fix, quick--it
has me thinking maybe I'll try a Mac next time. Will post a fix if I
find one that works for me.

hbarnum


--
hbarnum

After multiple calls to Microsoft Vista's service pack 1 support
line.... I found a "fix". I have no idea how, but the printer was able
to scan back to the computer. I was able to determine the Port used by
the printer was "DOT001" I changed the port for the printer to that
port and it started to work again.

Microsoft support was horrilbe. All they did was unload and reload the
drivers a number of times. Then they said I had to contact the OEM of
the computer to get a set of discs with Microsoft Vista and reload the
entire system.


--
kevintheenginee

"hbarnum" <guest RemoveThis @unknown-email.com> wrote in message
news:68561aabbdd64f54c71b93b352ee9ea1@nntp-gateway.com:

> Same problem just appeared on my system (vista home premium running on
> laptop with AMD Turion 64 x2). Every program I've tried to print from
> (currently MS Word, Adobe Acrobat, Netscape) has it. Printers look
> installed, and will print a test page if you go to the printer from
> control panel, and select "properties" off the file panel and then click
> print test page. Haven't tried rebooting yet, nor contacted MS; the
> problem just appeared. Looks like a problem MS needs to fix, quick--it
> has me thinking maybe I'll try a Mac next time. Will post a fix if I
> find one that works for me.

What printer do you have? Where did you get the driver? How is the
printer connected? It is probably not a Microsoft issue, the drivers are
typically supplied by the printer manufacturer.

Regards,
Bob Headrick, MS MVP Printing/Imaging

'Bob Headrick [MVP Wrote:
> ;912325']"hbarnum" <guest RemoveThis @xxxxxx-email.com> wrote in message
> news:68561aabbdd64f54c71b93b352ee9ea1@xxxxxx-gateway.com:
> > > >
> > > Same problem just appeared on my system (vista home premium running
> > on
> > > laptop with AMD Turion 64 x2). Every program I've tried to print
> > from
> > > (currently MS Word, Adobe Acrobat, Netscape) has it. Printers look
> > > installed, and will print a test page if you go to the printer from
> > > control panel, and select "properties" off the file panel and then
> > click
> > > print test page. Haven't tried rebooting yet, nor contacted MS; the
> > > problem just appeared. Looks like a problem MS needs to fix,
> > quick--it
> > > has me thinking maybe I'll try a Mac next time. Will post a fix if I
> > > find one that works for me. > > What printer do you have? Where did you get the driver? How is the
> printer connected? It is probably not a Microsoft issue, the drivers
> are
> typically supplied by the printer manufacturer.
>
> Regards,
> Bob Headrick, MS MVP Printing/Imaging

Mr. Bob Headrick, please review the previous posts from me, 'ddlnick',
which
describes a problem we can duplicate on an brand new HP 64 bit tablet
pc.
Not all our customers with Vista 64 bit computers have the problem.
Probably fewer than 1 in 10. But when the problem occurs, it is
re-producible.

In summary, we traced the call to API function DocumentProperties()
which is
used to retrieve properties of a selected printer. There are two calls.
The
first call is a simple request for the size of the DEVMODE structure
that
the printer driver will need to fill with that printer's properties.
The
application uses the size to allocate memory for the properties which
are
filled in by a second call to DocumentProperties().

It is the first call that fails, no matter which printer is selected.
It is
a very simple request, and one 32 bit integer value should be returned
in
the range of 500 to 5000 or so. A -1 is returned, when the bug
manifests
itself. A call to 'GetLastError()' does not indicate any error.

Microsoft also provides a 'PrintDlg()' method in a comdlg32.dll which
provides a convenient 'wrapper' for the 'OpenPrinter()' and
'DocumentProperties()' and other printer management functions. Using
PrintDlg(), the error returned from CommDlgExtendedError() is
CDERR_MEMLOCKFAILURE 0x0000000a which seems to indicate that a 'lock'
on
allocated memory of -1 size (-1 is also 0xffffffff a very large number)
is
failing.

In our case, we develop 32 bit software that runs fine on all versions
of
Windows starting with Windows 95. The printing interface used is
provided
in the official Microsoft Foundation Classes (MFC). We use Visual C++
6.0
(getting a little 'old' perhaps, but works fine for our purposes).

We have found an Intuit forum and describes similar problems for some
users
of Intuit's Quicken 2008.
Quicken Community - Solution to Printing Problems Vista 64 Quicken 2008

MSDN forum has more technical details
'On Vista x64, DocumentProperties fails from UAC-elevated process :
Security for Applications in Windows Vista : Software Development for
Windows Vista : MSDN Forums'
(http://social.msdn.microsoft.com/forums/en-US/windowssecurity/thread/3f2e63de-3c57-48c6-a734-1e0bef6f3147/)

One of our posts on MSDN:
The call to OpenPrinter() returns a printer 'handle' value, and I would

presume it is ok. It is the next rather uncomplicated call to
DocumentProperties that fails in 64bit VISTA for some applications on
some
computers. We have also confirmed that lowering execution 'elevation'
down
from 'administator', the 'bug' 'goes away'. This is clearly a Windows

issue and not application program trying to print. To remind everyone,
when
the 'bug' appears, it affects all printers on that computer - LaserJet,

Canon InkJet, CutePDF virtual printer, Microsoft FAX, and Word XPS
Document
Writer in my case.

//
// 12 Nov 2008
// Call windows API.
//
int nResult = :: OpenPrinter(
pPrinter, // LPTSTR printer name 0 terminated string - NOT
unicode.
&hPrinter, // LPHANDLE returned - looks ok
NULL // LPRINTER_DEFAULTS
);
.
.
//
// A zero for last param fMode returns the size of buffer needed for
the
// information to be returned.
//
long lSizeDevMode = :: DocumentProperties(
NULL, // HWND hWndParent
hPrinter, // handle to printer object
pPrinter, // LPCTSTR printer name
NULL, // PDEVMODE output
NULL, // PDEVMODE input
0 // DWORD fMode
);
ASSERT(lSizeDevMode >= 0);

lSizeDevMode is -1 and GetLastError() does not return any error.


--
ddlnick

I have a similar problem
Vista 64 Bit Prints a test page to my remote Samsung SCX-4100 connected
to a Windows 2000 box as a print server and even prints all files from
the Mandriva Linux 2009 Open Office software on the same machine (dual
boot). But will not print from any word processor or office software in
Vista premium 64bit other than a test page from the Jobs window. So it
definitely is the 64 bit Vista.


--
bartonmain

bartonmain;916110 Wrote:
> I have a similar problem
> Vista 64 Bit Prints a test page to my remote Samsung SCX-4100 connected
> to a Windows 2000 box as a print server and even prints all files from
> the Mandriva Linux 2009 Open Office software on the same machine (dual
> boot). But will not print from any word processor or office software in
> Vista premium 64bit other than a test page from the Jobs window. So it
> definitely is the 64 bit Vista.

We agree that there is a Vista64 printing problem, and it only affects
a small percent of Vista64 users, but if you are one of the few, it is
very annoying and frustrating, and Microsoft does not seem to care.

Anyway, make sure you have a 64bit printer driver installed on your
Vista64 system. You might 'get lucky' and become one of the many that
do not have a printing problem. We did NOT 'get lucky' using official
64 bit printer drivers.

Our analysis of the API calls to 'DocumentProperties' documented in
previous posts.


--
ddlnick