asked on

Server side printing from ASP/WSH

Hello. This is a follow up from a previous question. System is Windows 2000 server, Classic ASP, VBscript 5.6

I am attempting to print from the server using either ASP, or WSH.

In ASP when I try the following:

Set objFS = CreateObject("Scripting.FileSystemObject")
Set objWSHNet = CreateObject("WScript.Network")

objWSHNet.AddWindowsPrinterConnection "//MyPC/HPDescJet970c"

I get an "Access denied" error on the AddWindowsPrinterConnection line.

Anyone know why? The printer address is correct.

Is this the way to do is or would it be better to create a WSH COM object and use that ? Would there be any advantage in that?

Any help appreciated.

ASKER CERTIFIED SOLUTION

joeposter649

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

colly92002

ASKER

I shall look into this tommorrow. Thanks for the reply.

SOLUTION

davidlars99

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

colly92002

ASKER

Hello again.
The Problem is

objWSHNet.AddWindowsPrinterConnection "//MyPC/HPDescJet970c"

if I do it ONCE (as DOS in WSH):

objWSHNet.AddPrinterConnection "LPT1", "//MyPC/HPDescJet970c"

and then open up a file system object and print it to it, followed by a ctrl J, its OK (from WSH).

I can only add it once. Because then it is the registery (via FSO) I can access it via "LTP1:".
The next time it tells me the post is already assigned.

BTW I do have to add ALL permission to the printer on the server so joeposeter is correct.

This is means I can print to LPT1 via a WSH COM object from ASP but this is surely rubbish?

This seems too complicated, surely this is easy ?

All I want to do is print to A PRINTER anyway

Also, it gets stuck up waiting for the next CTRL J.

There must be a better way of doing this ?

Thanks for your answers BTW.

webwoman

There isn't a better way, and it's DELIBERATELY not easy. Would YOU want everybody in the world accessing your printers?

SOLUTION

joeposter649

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

colly92002

ASKER

Hello everybody.

I have workes this out. I knwe it was easy!

To print to a network printer from asp, simply open up a FSO object pointing at the printer:

strPrinterPath = "//MyPc/MyNetworkPrniter"
Set objFS = CreateObject("Scripting.FileSystemObject")
Set objPrinter = objFS.CreateTextFile(strPrinterPath, True)

objPrinter.Write("Hey this is a test!")
objPrinter.Write vbFormFeed
objPrinter.Close

Thats it! Easy!

If you want to DYNAMICALLY add the printer to the server before printing, then you MUST use WSH (as a COM object) and use:
Set objFS = CreateObject("Scripting.FileSystemObject")
Set objWSHNet = CreateObject("WScript.Network")
objWSHNet.addwindowsprinterconnection "LPT1", strPrinterPath ' this creates a port LPT1 pointing to the printer network name
Set objPrinter = objFS.CreateTextFile(strPrinterPath, True)
objPrinter.Write("Test on printer not set up on server until now")
objPrinter.Write vbFormFeed
objPrinter.Close
objWSHNet.RemovePrinterConnection "LPT1:" ' Essential or you cannot add LPT1 again

However I am yet to think of a situation where I would want this, as I am addind the neccessary printers to the server by hand.

I have split the points to all useful commentors, I hope this is acceptable.

colly92002

ASKER

In the second example above, the line:
Set objPrinter = objFS.CreateTextFile(strPrinterPath, True)

should read:
Set objPrinter = objFS.CreateTextFile("LPT1:", True)

I hope this helps someone in the future.