Print Wizard Frequently Asked Questions - Error messages

Error while installing on Server 2003

LPD fails with winsock error

I am getting a printer error.

My file prints, but the overlay does not.

I get an error when I try to use the WePO control.

Error while installing on Server 2003

This is an issue that appears ONLY in Server 2003. It is an issue with Anzio Lite v. 16.2, AnzioWin v. 16.2, and Print Wizard v. 3.3. It is a problem with a security feature called DEP. The way our programs do their online registration causes a conflict with this feature in Server 2003. Here's how to solve the problem: 1) Log on with administrative privileges. 2) Go to the Control Panel, System item. 3) Click on the Advanced tab. 4) Under Performance, click Settings. 5) Click on the "Data Execution Prevention" tab. 6) Click on the "Add..." button. 7) Navigate to the program that will be doing the registration. Assuming standard installation locations: For Print Wizard: c:\program files\printwiz30\pwui.exe For Anzio Lite: c:\program files\anzio16\anzio32r.exe For AnzioWin: c:\program files\anzio16\anzio32.exe 8) Click "OK" on everything. 9) Try again to register.

LPD fails with winsock error

Winsock errors normally come from some network problem that has occurred. Most often causes fit into two different categories: hardware (bad network cards, bad cabling, network down, ..) and software (firewall blocking inbound traffic, Internet security software blocking inbound traffic, personal firewall blocking port traffic, software already using a specific network port, .).

If network traffic seems normal, i.e. your web browser seems to be working, the most common problem is software related. Two major problems occur frequently, there is some security software blocking inbound and outbound network port traffic, or there is some software already using the network port Print Wizard Services, such as LPD needs.

Personal firewalls and internet security suites, such as McAfee or Symantecs, or Microsoft's own Windows firewall maybe blocking port traffic for the LPD service.

The best first test is to disable the firewall portion of your security software and see if the LPD service will run. If so, turn back on the firewall or security software and check to see if you can add the network port to an exceptions list, or add the Print Wizard program to the application exceptions list (PWLPD.EXE for Print Wizard Service or PWSERVICES.EXE for the Windows Service).

I am getting a printer error.

Printer errors, especially those in the 5000 range, usually indicate that we are sending data to the printer that the printer cannot understand. A good example would be sending PCL codes to a non-PCL printer or sending Okidata escape sequences to an H/P Laserjet, or sending raw data to a Windows-only-printer.

By default, the Print Wizard engine will determine if the file contains printer-specific escape sequences and then try to send the data in either spooler or raw print level. Many Windows-only printers cannot accept raw data and this will cause a printer error.

Likewise, if Print Wizard determines the file has Okidata escape sequences in the data stream, and you try to print it on an H/P Laserjet, the printer driver will generate an error.

My file prints, but the overlay does not.

Make sure there is not a problem with the overlay printing with the specific type of file. As mentioned elsewhere, if Print Wizard were to see escape sequences, Print Wizard may push the data out in raw or spooler mode, and the overlay file may not work in these cases.

Check with us if you run into problems here. You may need to change the file format on the overlay.

I get an error when I try to use the WePO control.

There are several items you need to be aware of in trying to troubleshoot WēPO.

1. For each version of WēPO, there is an unique class identifier, clsid, that is called by the web page. This object, the referenced version number and the codebase referencing a specific .CAB or .OCX file, all combine to make sure you are running the correct ActiveX component. They must match up or your ActiveX component will not be called. Everytime you receive a new version of WēPO, be sure to check our web site to make sure you are using the correct classid.

<OBJECT classid="clsid:659D3554-54CD-46BC-B0F1-D88C4CCFD10C"
codebase="http://www.mysite.com/controls/printwizocx.cab#version=2,7,0,0"
....

2. The web browser needs to be able to print to some printer. This is usually not an issue, but we have seen a few Windows and Internet Explorer installs come back with no default printer. Make sure you have a default printer designated at the Windows level and that Internet Explorer can see this printer under the File menu and Print...

3. The file being rerferenced by the "mainurl" parameter must be available to be fetched by the web browser. Have your web administrator check permissions if you suspect problems here.

<OBJECT classid="clsid:659D3554-54CD-46BC-B0F1-D88C4CCFD10C"
codebase="http://www.mysite.com/controls/printwizocx.cab#version=2,7,0,0"
...
ID="Pwbuttonx1" VIEWASTEXT>
<param name="mainurl" value="http://www.mysite.com/reports/myreport.txt">
<param name="caption" value="Print">
</OBJECT>

4. Lastly, any personal firewall security may cause a problem, as well as certain settings within Internet Explorer's Options. Check to be sure yopur security settings a) allow a download and install of the ActiveX, and b) they do not prevent ActiveX from running.