Network printing fails; get popup to send report to Microsoft

[NRGeti]

My system has recently developed this error: when I try to print to a network printer using the Print button from various Windows applications such as IE or Word, I get a dialog box stating that there was an error in this application and do I want to send a report to Microsoft.

I am running Lantastic and Windows XP SP 1. This used to work but I have installed some software which could have caused the problem. But I cannot be sure since it was several days later when I tried to print. New apps included Visual Interdev from Visual Studio v6.0 as well as the automatic Office upgrade.

The network printer works fine from some of my applications as well as from the server which is directly connectd to the printer which is an HP Laserjet 4ML.

I have reinstalled XP and SP1 as well as tried all of the drivers from Microsoft and HP. Nothing helps.

 

[gargouille]

Event Viewer would probably give you a clue...right click on My Computer and choose manage and look at the logs.
Here's a link to demystifying them:

http://www.eventid.net/

Actually the go home and tell MS has a diagnostic messaqe in it, and it might be de-crypted by feeding it into Tech Net search. Invoke the error and explore finding the exact message and we can look it up...you can look it up, too.

http://www.microsoft.com/technet/default.asp

For sure, having endured the days of AutoCAD and Office conflicting, there are "orders" to installing apps that work and those that don't.
Some creative partitioning/installing MIGHT prevent them from conflicting so much that they cripple each other...
sounds like putting a bunch of beasts in the same cage and expecting them to play well together, doesn't it? LOL

No joy in telling you the only answer will likely be an experimentation method of installing and trying and seeing if things work as they should and then proceeding.

Just a SWAG, but I'd put the Visual Interdev stuff on last...and Office can cause all kinds of problems.

 

[NRGeti]

Here is a typical message from the log file for applications:

"Faulting application iexplore.exe, version 6.0.2800.1106, faulting module msvcrt.dll, version 7.0.2600.1106, fault address 0x000327e8."

The text from the report itself includes information such as Exception Information:
Code: 0xc0000005 Flags: 0x00000000
Record: 0x0000000000000 Address: 0x000000000077c427e8

Then there is a list of around 80 modules showing various parameters. I suspect that these modules are just in the chain of logic as the system backs out of the calls.

I am wondering if the server must also be an XP machine. When I install the printer driver on the client PC, I get a message that the driver on the server is incorrect but the system goes ahead and installs anyway.

 

[roamer1]

Download the XP version of the printer software (2k might work too)

IN YOUR CLIENT MACHINE, the one you CAN'T print from:
Rename the current network printer to distinguish it from the one you will soon install. I will call it P1

Go into properties on P1 choose the Ports tab, and observe the port that P1 is using .

Install The software on the CLIENT machine. Hopefully it will support a network install (usually in "custom Install", if you get it). If so follow the yellow brick road, using the port that P1 was using. if not:

it will probably install to LPTx or USBxx (You may have to temporarily connect the printer to a local port for install)

Go into properties on the new printer choose the ports tab and redirect the current port to the one that P1 was using.

"Okay" your way out and print a testpage.

you should be well. Delete P1.

If not, you may have to enable network spooling on the server machine. Read the Manual. The methods are varied, but will be accessable from your printer's properties pages on the server. "Enable Network Spooling" or "Allow Spooling from Other Printers" or something similiar.

-Bruce

 

[roamer1]

I am sorry, I didn't see that you had already installed the drivers on the client, assumed you had "added" the printer from the network. That's what I get when I A$$ume.

 

[NRGeti]

Yes. I installed the XP version of the driver and it doesn't help.

As of today I have uninstalled Visual Interdev, Frontpage extensions, Microsoft Office and XP SP1. This should account for any installs that I have done since I lost my network printing function. So far nothing has helped.

I may have to break down and pay for a service call from Microsoft.

 

[ImaKatLover2]

SpartaCom.com has a support database for Lantastic. Their Problem Report Number T20220 discusses losing network printing on an XP system.

 

[NRGeti]

Last year when I was trying to solve this problem, I discovered that it was caused by Lantastic. At that time I talked to the sales rep who indicated that Lantastic does not run on Windows XP and that they didn't know if they ever would fix it.

I will check into their web site to see what has been going on since then.