Hey all,
Hope all are good. I'm seeing a weird message on certain machines and my
VFP app.
It may be runtime based but it's not consistent.
On a 64-bit machine (Win7) at a client, when trying to print, I get
Error Loading Printer Driver for network printers. It can't get the
device context.
I've even just tried creating a report directly in VFP and still get the
same results.
Now, doing the same thing on a another computer works fine.
Part of me seems to think this is network security related but I can't
be sure. The project occurs even if I launch VFP as Admin.
Has anyone seen this before?
TIA
Andrew
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/536DDF81.2090007@aksel.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Possibly...
I've had a problem with printing failing on Win7 64-bit systems that
have not been rebooted for several weeks. Reboot, problem goes away on
that system. I don't remember the exact error message, but in an
environment where the same application is running on over 150 Win7
systems, the printing fail problem will pop up about every 6 to 8 weeks
on random systems.
By the way, when the printing problem occurs, none of the apps on that
particular computer will print. All of the printers are
network-connected...none are directly attached to the workstation (via
USB or parallel.)
Hope this helps.
Mike Copeland
Andrew MacNeill wrote:
> Hey all,
>
> Hope all are good. I'm seeing a weird message on certain machines and
> my VFP app.
> It may be runtime based but it's not consistent.
>
> On a 64-bit machine (Win7) at a client, when trying to print, I get
> Error Loading Printer Driver for network printers. It can't get the
> device context.
> I've even just tried creating a report directly in VFP and still get
> the same results.
> Now, doing the same thing on a another computer works fine.
>
> Part of me seems to think this is network security related but I can't
> be sure. The project occurs even if I launch VFP as Admin.
>
> Has anyone seen this before?
>
> TIA
>
> Andrew
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/536DE553.4030705@ggisoft.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Hi Andrew,
make sure that in Windows there is at least one printer (a virtual printer is ok) and that there is a "default" printer.
Gianni
On Sat, 10 May 2014 04:12:49 -0400, Andrew MacNeill <lists@aksel.com> wrote:
Hey all,
Hope all are good. I'm seeing a weird message on certain machines and my
VFP app.
It may be runtime based but it's not consistent.
On a 64-bit machine (Win7) at a client, when trying to print, I get
Error Loading Printer Driver for network printers. It can't get the
device context.
I've even just tried creating a report directly in VFP and still get the
same results.
Now, doing the same thing on a another computer works fine.
Part of me seems to think this is network security related but I can't
be sure. The project occurs even if I launch VFP as Admin.
Has anyone seen this before?
TIA
Andrew
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/3n7sm9pqcqk9eppo5tfaevcrovk9licu5d@4ax.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
I bet it's either a HP printer or a printer that is using M$'s own built in drivers. Check the manufacturer to see if there are a set of drivers made for Win7
Dave
-----Original Message-----
From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Andrew MacNeill
Sent: 10 May 2014 09:13
To: profoxtech@leafe.com
Subject: Printing Issues with 64-bit Win and VFP
Hey all,
Hope all are good. I'm seeing a weird message on certain machines and my VFP app.
It may be runtime based but it's not consistent.
On a 64-bit machine (Win7) at a client, when trying to print, I get Error Loading Printer Driver for network printers. It can't get the device context.
I've even just tried creating a report directly in VFP and still get the same results.
Now, doing the same thing on a another computer works fine.
Part of me seems to think this is network security related but I can't be sure. The project occurs even if I launch VFP as Admin.
Has anyone seen this before?
TIA
Andrew
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/18725B8CD2D5D247873A2BAF401D4AB22A4EC2BD@EX2010-A-FPL.FPL.LOCAL
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Lol. HP printer drivers have been a pain since windows first started. When
will they learn
Al
-----Original Message-----
I bet it's either a HP printer or a printer that is using M$'s own built in
drivers. Check the manufacturer to see if there are a set of drivers made
for Win7
Dave
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/001e01cf6db7$a2cb29e0$e8617da0$@com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Mon, May 12, 2014, at 08:36 AM, Dave Crozier wrote:
> I bet it's either a HP printer
+1
It will likely be HP PCL6 drivers. Use PCL5e or Postscript versions.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1399881855.5922.116288381.24B52BDE@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2014-05-12 12:30:37 Link
On 2014-05-12 04:04, Alan Bourke wrote:
> On Mon, May 12, 2014, at 08:36 AM, Dave Crozier wrote:
>> I bet it's either a HP printer
>
> +1
>
> It will likely be HP PCL6 drivers. Use PCL5e or Postscript versions.
PS drivers have never let me down.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/029a31c30dcd782f5a9d9b595c9b1955@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Andrew MacNeill
Posted: 2014-05-14 02:48:50 Link
On 5/12/2014 3:36 AM, Dave Crozier wrote:
> I bet it's either a HP printer or a printer that is using M$'s own built in drivers. Check the manufacturer to see if there are a set of drivers made for Win7
>
> Dave
>
Nope - it's any printer on the network - they are using Dells but in
fact, I get it even with an Adobe printer driver. Now, if I install a
32-bit driver on a local version, it appears to work but I can't control
that on the server.
Another part of the message says "I don't have permissions to work with
this printer" (or something to that effect) - but every other app prints
fine. Attempting to do a PageSetup gives the message "cannot get IO Device"
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53731FE2.7060404@aksel.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Andrew MacNeill
Posted: 2014-05-14 02:52:33 Link
On 5/10/2014 8:46 AM, Gianni Turri wrote:
> Hi Andrew,
>
> make sure that in Windows there is at least one printer (a virtual printer is ok) and that there is a "default" printer.
>
> Gianni
>
Hi Gianni. There are existing printers (all using 64 bit drivers) and
the default is set on the machine. I am thinking it's 32 bit driver
related but another machine works fine.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/537320C1.8040404@aksel.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Sat, May 10, 2014 at 4:12 AM, Andrew MacNeill <lists@aksel.com> wrote:
> Hope all are good. I'm seeing a weird message on certain machines and my
> VFP app.
> It may be runtime based but it's not consistent.
>
> On a 64-bit machine (Win7) at a client, when trying to print, I get Error
> Loading Printer Driver for network printers. It can't get the device
> context.
> I've even just tried creating a report directly in VFP and still get the
> same results.
> Now, doing the same thing on a another computer works fine.
>
> Part of me seems to think this is network security related but I can't be
> sure. The project occurs even if I launch VFP as Admin.
>
> Has anyone seen this before?
>
>From the first error you describe, I'd think the print server lacked the
32-bit drivers: http://technet.microsoft.com/en-us/library/cc732946.aspx
When you say "doing the same thing on another computer works fine" is it
also a 64-bit Win7 machine, and also accessing the same printer?
VFP runs as a 32-bit app, which causes 64-bit windows to run it through an
emulation, Windows on Windows or SysWow64. Shades of Win32s, right? So,
essentially, the remote printer server sees a 32-bit machine requesting
32-bit printer driver software, which sometimes isn't installed by default.
OTOH, if the two machines really are "the same" then, yes, that means the
problem is something else, perhaps with user account priviledges (can you
try logging in as the same user to each machine?)
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4tkHKodEdx+TzYW2B64QOLnH7kJ59oAUFcDpFJq=-VUDQ@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.