My J740 is hooked up locally to my machine (WinXP) and prints fine for me.
I've shared the printer, and it appears correctly for other (WinXP) users on my network. When they print, the document shows up in the print queue, but it never actually prints and it can't be deleted. Here's the kicker -- as soon as I restart my machine all the queued documents print!
Any suggestions for printing their docs without my having to reboot each time. As you can imagine it's a little annoying...
I posted something which is very similar to this just now so I am interested in the response you get also.
I have a user who connects via Terminal Server and when she tries to print to her local J740 printer the jobs que but never print and they cannot be deleted either. However in her case a reboot is not applicable.
I also have the exact same problem on my home network. I have a win 2003 machine hooked up directly to the printer, and three laptops hooked up wirelessly to the shared printer. Whenever any of them sends a job, it just sits in the queue, any additional jobs sent after that just sit there. ALTHOUGH, when you restart the print spooler service, the jobs will come out, each and every one. For some reason the driver does not talk to the spooler service properly when sent through the shared object. Still looking for a resolution on this.....
I am sharing the printer as "Dell Inkjet Printer J740" from a Windows XP Professional machine with Fast User switching enabled. Local printing seems to work fine. Network printer causes a white bar to display in the center of the desktop of the machine sharing the printer.
If I hit the ESC key, the box goes away and printing works. I noticed that there was an instance of DWWIN.EXE running (I believe this is the Dr Watson error reporting tool) and killing it also makes the box disappear and printing resume. I disabled Error Reporting on the machine with the printer installed and lo-and-behold, the print job went right through! The Event log contains an application error that states: "Faulting application dlbjjswx.exe, version 1.0.0.0, faulting module dlbjutil.dll, version 1.0.2.0, fault address 0x0000e6eb."
When printing to the machine when nobody is logged in, the print job blocks until reboot, or, logging in to administrative account and pressing ESC when a garbled display box is present (probably the same as above).
My assumptions as to the problem:
The DELL print spooler is causing a fault condition (dlbjjswx.exe) - perhaps trying to display the printer status dialog?
Dr. Watson detects the fault and tries to display a message box but does not have a valid user context to display the error message (probably related to why it is faulting)
Pressing the ESC key dismisses Dr. Watson and resumes the faulting module.
Turning off Dr Watson (Error reporting) causes the fault to be ignored and printing resumed.
Perhaps someone from Dell Tech can look into this?
I'm having the same XP sharing problems with the Dell J740 Inkjet printers. I have about 35 of them in one building, each connected to a brand new Optiplex and shared for two other identical brand new Optiplex's. I've called Dell numerous times and they've sent me back and forth between printer and software support. Now we've reached a point we're they want me to to talk to Dell's advanced support team for $230 per incident! I’ve just taken these machines and printers out of the box and I’m expected to pay for support now too?!
These printers are terrible and the support for them is even worse! This issue is only going to get get bigger as consumers purchase this product and attempt to use it in a network environment. Dell reads these postings and yet they still have not provided a solution! WHAT ARE YOU GOING TO ABOUT THIS DELL !?!?!
I have the identical problem. Kudos to DumbLuck for eloquently describing the problem. When I disabled error reporting, I get a different error dialog box:
The instruction at "0x008de6eb" referenced memory at "0x00000020". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------
When I click OK, printing starts up and completes properly. This looks like a bug that only impacts Windows XP Pro systems when the printer is shared. I can reproduce the error 100% of the time. If anyone from Dell is reading these posts, I am willing assist you with any diagnostic you would like me to perform.
I just wanted to post to let you know that I got word that these symptoms are being looked into. I have no ETA on this but I will post more information as it becomes available.
The failure occurs when I share my printer with XPro as the local computer to other computers on my network. The Dr. Watson program is detecting an error in the program DLBJPSWX.exe (two exist with the same name). It seems that one of these two of file is trying write to memory incorrectly; maybe to allocated memory. You can view the error by disabling Dr. Watson in Control Panel\Performance and Maintenance\System\Advanced Error Reporting and disable error detection. My network computers are able to print by doing the following:
Search for DLBJPSWX.exe these three file should appear.
1. DLBJPSWX.exe-#######D.pf
2. DLBJPSWX.exe in the file C:\Windows\system32\spool\drivers\w32x86\3
3. DLBJPSWX.exe in C:\Windows\system32\spool\drivers\w32x86\dell_j740obb50
Rename the second DLBJPSWX.exe to DLBJPSWX.exe.tmp or what ever you would like. Just disable the .exe. Don't delete the file just in case this doesn't work for you. You can correct the .exe.
Try to print. I found so far; that the only thing that doesn't print is my print test page function on the computer connected locally. My other computers seem to print fine including print test page.
MarkWare
7 Posts
543
0
Posted November 10th, 2003 14:00
I posted something which is very similar to this just now so I am interested in the response you get also.
I have a user who connects via Terminal Server and when she tries to print to her local J740 printer the jobs que but never print and they cannot be deleted either. However in her case a reboot is not applicable.
Mark