|
|
Gregg Dolby
|
|
Jan 15, 2004 14:57:08 GMT
|
|
I have a w2k(sp4) server with 21 HP laserjets installed. All on HP Jetdirect ports.
This server is a Xeon 2.8GHz... however, the CPU is at 100% ALL the time. Because of HPBPRO.EXE (many instances at once) and Spoolsrv. There is no way that spooling print jobs can take that much CPU power. I believe it's a problem with HPBPRO.EXE or the HP Drivers. We have Laserjet 4200 / 4600 / 5M / 4plus installed. and also a Toshiba copy station.
Is there any information on this problem or any solutions?
|
|
|
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
|
|
|
Sort Answers By:
Date or Points
|
|
|
Jeff Longley
|
|
Apr 29, 2004 08:19:18 GMT
Unassigned
|
|
Can't help with solutions but can confirm we're suffering a similar problem at a clients site.
HPBPRO.exe appears to spike every 5 seconds, sending CPU usage up to 100% and eating around 5mb of memory.
We have HP 4600, 4550, 100 and 1300 printers at the site.
Anyone from HP care to comment? |
|
|
Rene Bremer
|
|
Apr 29, 2004 12:53:04 GMT
Unassigned
|
|
We have the same problem at our firm.. We use Laserjet 5m / 4plus / 2200n / color 3500n, and jet direct boxes on some of the equipment..
So if any HP genius out there have some hints... Please reply... |
|
|
Mark Wehling
|
|
May 26, 2004 20:34:46 GMT
Unassigned
|
|
|
I am also experiencing the same issue. We have Laserjet 5, 4000, 4050, 4100, 4200 & 4300 series printers. The only way I can get around it temporarily is to reboot the server. Is there any advice from HP ? |
|
|
Aleksey
|
|
May 27, 2004 02:58:19 GMT
Unassigned
|
|
|
OK! It seems to me that I solved this problem: we have HP1010 on Win XP - so, I switch OFF two HP services from msconfig - printer is working good, and hpbpro no longer available - I am happy ! |
|
|
Matthew Ornawka
|
|
Jun 18, 2004 17:58:06 GMT
Unassigned
|
|
I also noticed this stacking up on my server, and it actually crashed it when I tried to kill the process...
What I did, is I went into DCOM config and took away permissions to run on the server for both HPBOID and HPBPRO...
Seems to work... so far,.... |
|
|
Chris Tseng
|
|
Aug 6, 2004 01:18:10 GMT
Unassigned
|
|
The easiest way is to remove the software accompany from the printer first via the Add/Remove Programs.
Then download the driver ONLY from the www.hp.com.
Reinstall the driver only which should be able to solve this problem. |
|
|
Matthew Ornawka
|
|
Aug 6, 2004 11:23:01 GMT
Unassigned
|
|
The software is IN the driver. This is not a add on peice of software. You can't "uninstall" it.
I was told by HP that they actually have an application that can remove the offending code (called the Automatic Enterprise Configuration Agent, designed to automatically query the hardware to find out its exact configuration and have the driver reflect it) from the driver, because an older version was known to have a memory leak. Newer versions are not affected by this memory leak and should not cause a problem..
Personally I don't want to take the chance anyways... |
|
|
Matthew Ornawka
|
|
Aug 6, 2004 11:28:12 GMT
Unassigned
|
|
Further to that, The best way of getting rid of this software is to go into dcomcnfg.exe and remove permissions for HP Port Resolver and HP Status Server from running on the system.
Then you have to go into the registry and rip out every key that has anything to do with HPBPRO.EXE, HP Port Resolver and HP Status Server, and HPBOID.EXE. If it is a subkey of a key, remove the key and not just the subkey
Then you have to go into every driver (providing you don't actually have the previously mentioned software that works only on the driver, not the installed software) and delete any line that has HPBOID and HPBPRO in it, including any DLL with those two in the name. You will have to do this for every driver you download from HP from now on.
Cleaned up my servers quite nicely.. |
|
|
Marc Holzapfel
|
|
Sep 2, 2004 05:22:15 GMT
Unassigned
|
|
We have W2K (SP3) running as a Printserver. Several Designjets, Laserjets are connected. But our main Problem is that our RIP-Software by Onyx named Postershop V4.5 is not running after some time. I also noted the mentioned tasks. Also I should note that I had an Officejet G95 connected by USB locally to the server. This messed everything up quite a bit. I deinstalled it again, but as I see this deinstallation wasn´t complete. I can see this when I run the Regcleaner or the Process Explorer by Sysinternals. I bid HP to construct some kind of cleaning program to get rid of the rests of the Officejet Drivers and Software as well as the annoying processes HPBPRO.exe and HPBoid.exe. It seems to interfering with the Dongle at LPT1 which needs to run so that our RIP-Software may run stable again. Thanks
Ma |
|
|
john
|
|
Oct 4, 2004 04:52:56 GMT
Unassigned
|
|
|
do you know if following this will break terminal services (citrix) client printer mapping? |
|
|
matthew ornawka
|
|
Oct 4, 2004 10:54:07 GMT
Unassigned
|
|
I dont see why it would... a little confidence in registry spelunking should carry you through...
On the drivers side of things... No it shouldn't...
Perform it on a test box first, not a production...
Me< I had no choice but to perform it on our production servers, all 7 of them. worked just fine |
|
|
John Fleming
|
|
Oct 28, 2004 17:41:39 GMT
Unassigned
|
|
I actually have this issue with several client machines. All of which were XP some SP 1 and some SP2. What I did was go into the MSCONFIG Utility and unchecked two entries.
1. StatusClient "C:\Program Files\Hewlett-Packard\Toolbox\Apache Tomcat 4.0\webapps\Toolbox\Ststusclient.exe /auto"
2. hpbpsttp "C:\Program Files\Hewlett-Packard\Toolbox\hpbpsttp.exe
After removing these from the startup, my issue was resolved. The HPBPRO.exe file was in my system32 directory and still is, but it has not ran since I removed the startups mentioned above.
My issue may be different than everyone elses here, but I hope this helps.
Regards,
John |
|
|
F.Dietrich
|
|
Oct 28, 2004 23:15:37 GMT
Unassigned
|
|
I did the same as John Fleming to my workstations and server, and replicated the action on my customer sites that had the problem. All seems to be printing OK, and performance has improved. I am still nervous though, considering the vast amount of time that can be lost troubleshooting similar problems.
Why hasn't HP commented on this problem? Aren't any HP techs lurking or browsing these boards? What have we missed and are any lingering problems likely to emerge?
Thanks ...
Fred |
|
|
Winston Ojeda
|
|
Nov 2, 2004 19:11:20 GMT
Unassigned
|
|
How come HP is not chiming in here???
I have a very similar problem.
I am connecting via VPN to a 2003 Server and from there on to an XP SP1 workstation via Remote Desktop that happens to have software loaded for a 1300n Laserjet.
The 1300 is on the network but not served by the 2003 server.
When connected, this XP machine about 5-6 times a day seems to drop the connection, the screen goes blank and takes about 10-15mins to come back.
Looking at the system events I am getting quite a few of these:
The server {5A5AA0AA-1DEB-4683-96B0-B43301E83971} did not register with DCOM within the required timeout.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Looking that CLSID key up points to this:
HPPortResolver.hpbpro
What is this? Is HP putting bad software out there again?
Any ideas? |
|
|
MikeC
|
|
Nov 23, 2004 13:25:16 GMT
Unassigned
|
|
|
I am running XP pro on stand alone PC's and rather than use the MSCONFIG facility, which meant the PC identified that this had changed at reboot, and wishing to avoid going in to edit registry entries I uninstalled the HP LJ1300 print drivers and software and reinstalled a customerised version omitting the "toolbox" functionality. The printer works fine, HPBPRO.EXE is no longer on the system and I've avoided the problems reported elsewhere on the page which has taken several weeks to track down. |
|
|
Robert Geller
|
|
Nov 29, 2004 19:32:45 GMT
Unassigned
|
|
Try re-registering the component HPBPRO.EXE. I had a problem with the component re-attempting to run every 60 seconds. I tried the sugggestions in message c00098371 "DCOM Error Message" pertaining to hpbpro.exe, and it solved the problem.
To quote,
"To register the component properly, open a command prompt window by clicking Start then Run. Enter cmd.exe in the Run window.
Change to the System 32 folder by typing "cd\winnt\system32" for Win2K or "cd\windows\system32" for WinXP.
Run the command "hpbpro.exe -RegServer".
Then run the command "hpbpro.exe -Service".
Then type "Exit" and then restart your PC.
I hope this helps with this set of problems. |
|
|
Fotis Varetidis
|
|
Dec 7, 2004 06:02:23 GMT
Unassigned
|
|
|
Do you mean that HPBPRO.EXE is not necessary? So if i get rid of it i will not face any problems? |
|
|
Matthew Ornawka
|
|
Dec 7, 2004 10:43:56 GMT
Unassigned
|
|
No, it is not required... personally, whenever I download an HP driver, I edit the .INF file to remove all entries related to HPBPRO, HPBPROPS, HPBOID, HPBOID and delete the DLL's. The driver will install normally, except it will come up with an "uncertified driver" warning. Ignore it and continue
You will never have to deal with the software again if you are diligent. |
|
|
Dennis Clark
|
|
Dec 8, 2004 10:34:40 GMT
Unassigned
|
|
It appears that when you terminal into a server the process of mapping your local client's printers to the terminal session create the HPBPRO.EXE and HPBOID.EXE processes that never seem to go away.
Go into Terminal Services Configuration under the "Connections" folder go to the properties on "RDP-Tcp".
Via the Client Settings Tab disable the following:
"Windows Printer Mapping"
In my case I had to run pskill to stop the HPBPRO.EXE and HPBBOID.EXE processes a reboot should do the same thing as well. |
|
|
Matthew Ornawka
|
|
Dec 8, 2004 10:47:07 GMT
Unassigned
|
|
We do not map local printers in our environment, and the process was still bringing the server to its knees... I found the only way to keep it off, was to remove it from the installation.
Most HP drivers that are downloaded have the offending files. This is why you also cannot use Windows Update to install drivers. HPBPRO is in those files as well and you cannot remove them prior to installation.
Ever since I started removing these entries and files from the installation directories where I store my drivers, I have not had one single instance of my server crashing, and actually is now running better than it had before. |
|
|
Donald Ziehm
|
|
Dec 9, 2004 08:40:44 GMT
Unassigned
|
|
I too have been having problems with hpbpro.exe.
I am running WIN XP Pro SP1 on a stand alone PC. I have a HP 1012 laser whose driver software installed this garbarge.
My problem was DCOM messages that were hanging up my PC. They appeared to disappear when I removed the printer driver software via Add/Remove programs and then reinstalled it. Now the problem is that the DCOM time-out message appears when I resume from stand-by mode along with a desk top HP popup message. Sometimes it hangs the PC, other times it does not.
I also beleive the slew of messages I have been receiving in my wbemess.log file about SCM Event Log being unable to register is related to this issue. My own theory is that this is a WMI issue caused by one or more recent HP and/or Microsoft security updates.
In any case, I tried the -Regserver option suggested. Yes, it created a service for the HP Port Resolver. However, my application event log shows an info message for same that says it could not find the .dll associated hpbpro.exe and it loads with an event id of "0".
I need a solution on how to correct this missing .dll issue.
Also I am wondering is this is a good solution security wise since a port is being opened up on a permanent basis?
From what I can tell, all this HP Port Resolver does is allow for the icon to display printer status to appear on the lower desktop tool bar. Which in turn, controls those popup messages on printer status such as out of paper, etc. Maybe the best approach until HP cleans up their act is to disable it's loading via Startup menu as noted previously.
I do know regular HP tech support doesn't have a clue what I am talking about on this subject. However, that's seems to be the norm today with them. |
|
|
Matthew Ornawka
|
|
Dec 9, 2004 10:43:32 GMT
Unassigned
|
|
Honestyly folks.. the best way of getting rid of this once and for all, is to remove it from the installation before you install the driver for the printer. Not all HP drivers contain the offending software, but most do.
HP believes that the problem we are all encountering stemmed from a version that leaked alot of memory, but has since, by their claim, been fixed.
Notwithstanding, I will never install the software... stop the spooler, delete all HPBPRO, HPBPROPS, HPBOID, and HPBOIDPS DLL's on your computer, including the ones in the installation directory you saved your drivers to. Remove any entries to the above files from all of the INF files in those installation directories.
Go into the registry, delete the entire keys associated with those above files, and delete any reference to "HP port resolver"
and "HP Status Server"
Your problems will go away, I assure you.
Yes these services jump into your DCOM and their removal from the registry will clean up your DCOM messages and remove them from DCOM. |
|
|
Bob
|
|
Dec 9, 2004 11:35:12 GMT
Unassigned
|
|
|
OK, I have removed all the HP garbage from my print server and it's seems to have made a huge difference. I have a number of users on the network that use both local printers and networked printers. Since they connect to my print server do I need to remove these files, that were installed with the local printers, from the workstations as well? I'm not sure I fully understand how these monitors work. |
|
|
Matthew Ornawka
|
|
Dec 9, 2004 11:40:47 GMT
Unassigned
|
|
No, I wouldn't worry about the montiors on the remote computers... it hasn't caused an issue to date on my end...
These monitors are supposed to talk directly to the printer to make sure the print driver is configured exactly the way the print device is configured, kind of a set it and forget it. Since the users computers cannot change their drivers (only the print preferences) being served by the servers, these files are of no use to the end user and don't operate.
HP has specified that this software is only supposed to run once or run once at the startup of the computer or print spool service (cant remember which)... however I found it running every time someone tried to send a print job to the printer... at 5 MEGS PER PROCESS |
|
|
Donald Ziehm
|
|
Dec 9, 2004 12:12:19 GMT
Unassigned
|
|
Maybe all the registry and system file hacking is OK for the network admins, but I don't beleive a home user should have to go through all that.
HP should issue driver updates for their lasers with an option to install the print server in question along with a warning of the repercusions if they do install the print server.
Also has printer startup and/or elasped print time increased with the removal of hpbpro.exe? |
|
|
Matthew Ornawka
|
|
Dec 9, 2004 13:11:28 GMT
Unassigned
|
|
I have found that it has actually decreased the time, and has increased print server performance.
The software, from the best of my understanding, is only supposed to be used to gather the print device configuration, and then configure the print driver accordingly, nothing more.
<rant on>
I am a firm believer in not having a driver install services beyond that which directly impacts the end user, like accepting a print job for processing... If the driver needs to run a program to gather metrics or configuration information, then run it at the time of installation, or run it exclusively as a discrete program, not a service... don't install a freakin' service that plugs itself into every bloody netherregion of the computer that will run every time it damn well feels like it...
<rant off> |
|
|
Donald Ziehm
|
|
Dec 11, 2004 14:08:45 GMT
Unassigned
|
|
Well in my case, the hpbpro.exe -RegServer option worked. I haven't had a system lockup since I applied it.
Would like to find a way to register this service in my event log since I keep getting that application event log info message about Event 0 Unknown event every time I log on.
Since I have a HP Pavilion PC, I feel this is a safer way for me to go since I have tons of HP crap loaded on this PC and don't want to screw something else up.
I do have a theory that the Remote Registry service might be the culprit. I have it disabled on my PC for security reasons. Suspect that hpbpro.exe might be trying to access my registry when it was starting up.
I do know this is the last time I buy an OEM PC with the OS loaded on it. Full retail MS for me from now on! |
|
|
Tom Warfield
|
|
Feb 3, 2005 12:53:40 GMT
Unassigned
|
|
I know this is an old problem with several solutions but I just thought I'd tell my story.
I installed an HP driver & the toolbox on an XP Pro PC and a Win2000 server. The server did not exhibit any problems but the XP machine did. Every few seconds it was going to 100% utilization; my hard disk was thrashing. My server was registering failed login attempts. I thought I had caught the latest worm. Mid-morning the next day McAfee finally released a new DAT file. A full scan of my hard drive took almost 12 hours but nothing was found. I finally determined it was HPBPRO.EXE; something was firing off 3 copies of it and then it would disappear from the task list.
I searched my hard drive and found three copies. I renamed the one in \system32 and my cpu went to almost 100% constantly. I renamed the other two and my problem went away. I could still print but the toolbox no longer worked - it got an http 500 error.
I wanted to do some research on this program and ended up reading this thread. I wanted to try the simplest solution first. I renamed the three copies back to the original (and the problem came back). I then did what was suggested in the Nov. 30, 2004 posting (executed HPBPRO with the -RegServer option followed with the -Service option. I did not reboot my PC.
HPBPRO is now operating without causing any problems. It is now permanently in the task list - one copy only. It fires up every few seconds but only takes 2-3% of the CPU. The toolbox now works.
I'll see what happens when I reboot the next time. |
|
|
Andy
|
|
Feb 3, 2005 13:23:54 GMT
Unassigned
|
|
|
I had a similar problem last month. It actually turned out to be a number of things. First off XP clients were opening up way too many spools sessions and keeping them open. Microsoft has a hot fix for this. Next, I had to edit most of the print drivers on the server. I edited the registry to make them use the PJL Language Monitor rather than the HP monitors (there are a number of different ones). I also made sure that I had driver that utilized the Windows print drivers UNIDRV.DLL and PSCRIPT5.DLL rather than any HP homebrews. I would also switch them to use WINPRINT for the processor rather than any HP homebrewed ones. As far as the JetDirect ports I switched them all back to using the Standard TCP/IP ports and removed the JetDirect ports and associated files. Remove the HPBPRO.EXE from your server. When I looked I had multiple instances running. I have a similar server 2 XEON 2.8's and about 50 print queues. I was running at 100% all the time. Once I removed ALL the HP crap it droped down to an everage 1%! If memory serves me right it was a 4200 that was utilizing that HPBPRO.EXE. That's where I would start. Remove that process ASAP. |
|
|
Ian Hickey
|
|
Feb 7, 2005 17:49:31 GMT
Unassigned
|
|
|
Do you have the weblink for this hotfix..... |
|
|
Jeff
|
|
Feb 14, 2005 12:36:05 GMT
Unassigned
|
|
Has anyone had a specific driver type not load. What I mean is PS drivers load but not PCL.
I will try to reregister the hpbpro.exe also as I have the DCOM error message also.
Our problem started with the 4200 series I believe. |
|
|
Steve Calandrella
|
|
Mar 14, 2005 18:28:04 GMT
Unassigned
|
|
|
|
Mac
|
|
Mar 14, 2005 20:56:58 GMT
Unassigned
|
|
|
Im just a rookie using MS Server 2003 but I set the permissions for HKEY_CLASSES_ROOT\CLSID\{5A5AA0AA-1DEB-4683-96B0-B43301E83971} to give the guest account the ability to read this reg key. It seemed to clear up the log when people try to print using the Guest account. |
|
|
Jeremy Campbell
|
|
Mar 30, 2005 13:43:01 GMT
Unassigned
|
|
Stumbled onto this thread as i just had 25 instances of hbpro and hpboid.exe running in taskman on my win2k sbs server with sp4. Just wanted to add to this thread, we have 1300's 4050's 4200 (i think the culprit) and a 4500.
Just wanted to advise that i just used pskill.exe (www.sysinternals) to kill both processes and nobody is calling me....
i will research more into the driver editing to remove completely, i have also been seeing the dcom errors on workstations not servers that the above mentioned, this thread has proved very valuable.
** edited to comply with forum guidelines ***
I very much appreciate the time you guys all took to relay your experiences, you will allow me to go home today at 5, rather then doing a bunch of senesless virus scans, as i too was thinking down the worm path.
Jeremy |
|
|
Matthew Ornawka
|
|
Mar 31, 2005 16:18:39 GMT
Unassigned
|
|
Well, after my original post of removing the HPBPRO* and HPBOID* from the driver INF file and deleting all instances of HPBPRO*.* and HPBOID*.*, I did run across an annoying side effect. XP, when configured for security rather than functionality, will not allow users to install unsigned drivers, even when they come down from the server and installed by the system.
So, the only option was in our network was to use the other suggestion and register HPBPRO as a service on the server and set it to automatically start.
This is all well and good, until you install the next driver. When you install a new HP driver for a new model of printer that utilizes HPBPRO, during the installation process HPBPRO is *unregistered* as a service. WHY HP would go and uninstall HPBPRO as a service once it is set in such a way *by the administrator of the server* is really beyond me.
I did discuss the issue with HP about the crashing of the server, and they did say that older versions of HPBPRO *do* have a memory leak (an understatement) that has been fixed in newer versions.
Except for being forced to RE-register hpbpro as a service on the server every time I install a new driver on the system, HPBPRO has not given me any greif, utilizing the latest versions of software drivers. |
|
|
Will Everitt
|
|
Apr 8, 2005 07:19:45 GMT
Unassigned
|
|
Here's another scenario:
I recently installed the full HP suite on my laptop (XP Pro SP2, FAT32) for a HP1320, and had no problems at all. However, on upgrading to NTFS, HPBPRO started to give problems, appearing every 30 seconds or so.
To be on the safe side, I uninstalled everything.
HP seem to be very quiet on this issue... |
|
|
Reed Fife
|
|
Apr 28, 2005 13:34:23 GMT
Unassigned
|
|
There is an easier fix to this problem if the error log tells you which computers are causing the error.
Start dcomcnfg.exe on the offending computer and navigate to "Component Services\Computers\My Computer\DCOM Config"
Right Click on "HP Port Resolver"
Click on the "Location" tab
Change the settings so that only the "Run application on the computer where the data is located" option is checked. |
|
|
Reed Fife
|
|
Apr 28, 2005 14:01:02 GMT
Unassigned
|
|
Additional information:
In our case the server event log identified the users who were causing the problem. Our Server OS is Windows Server 2003. Client computers are running Window XP and Windows 2000 Pro.
The one thing in common on the computers causing the problem was that the client computers all had a copy of HPBPRO installed and running.
Client computers not running HPBPRO were not causing event log errors. |
|
Nir A
|
|
May 1, 2005 14:01:30 GMT
Unassigned
|
|
|
Reed, it would be better to open a new thread on that. Post a link to this thread in ur new one, but post ur own thread, cause this one is getting a little crowded. |
|
|
Nir A
|
|
May 6, 2005 08:35:40 GMT
Unassigned
|
|
|
|
Dan Thomas
|
|
May 10, 2005 15:00:12 GMT
Unassigned
|
|
It's too bad that HP isn't chiming in to this discussion. The short answer I got today from tech support:
1. Uninstall HP printer software from Control Panel, Add/Remove Programs.
2. Go to http://www.hp.com/pond/pnp to download a basic, no-nonsense printer driver for your printer.
No more server crashes. Yahoo!
Dan |
|
|
Brent Heidtke
|
|
May 16, 2005 13:06:37 GMT
Unassigned
|
|
Nir A,
Where can I find HPBPROFIX.EXE, as mentioned in your attached DOC?
I have searched everywhere and I can't seem to located it.
Thanks. |
|
|
Paul
|
|
Jun 1, 2005 21:30:59 GMT
Unassigned
|
|
This software has just killed one of our corporate networks too..
What is HP doing ?? |
|
|
Winston Ojeda
|
|
Jun 1, 2005 22:01:09 GMT
Unassigned
|
|
This problem is years old. HP does not care. They have your money already.
Here is what you do. Tell purchasing next printers you request will be Ricoh.
Do not get any more HPs. We are not, and are a lot happier plus we are saving a bundle. Users love them.
PS. Our servers are down to 20% utilization again since the switch. |
|
|
Rob Saville
|
|
Jun 27, 2005 06:20:53 GMT
Unassigned
|
|
Amen to Dan's comment about using the pnp driver. HP's drivers are bloatware nowadays.
Robert Geller's fix, earlier, worked fine for me on my W2K sp4 workstation, so thanks for that
Rob |
|
|
Harry Gunderson
|
|
Jun 29, 2005 12:34:19 GMT
Unassigned
|
|
|
HP now has a fix for this. Call up support and ask for "Fixhpbpro.exe". |
|
|
Jason Miller
|
|
Jul 5, 2005 14:13:02 GMT
Unassigned
|
|
|
I spoke with HP support and they told me that the fixhpbpro.exe essentially just replaces the leaky version of hpbpro.exe with the latest version. I was told this can also be achieved by downloading/installing the latest printer driver and having the user delete and reattach to the queue which will pull down the newer version of this port resolver to their machine. If you want the file, call HP and they will give you a temporary account to access their FTP site. |
|
|
david cheng
|
|
Aug 3, 2005 12:24:12 GMT
Unassigned
|
|
|
Here's another voice crying out in the HP wilderness. We're seeing HPBPRO.EXE processes attacking our Windows 2003 print server like locusts. Why do we have to call HP to get this fix e-mailed to us when it should be on the website and more easily accessible? |
|
|
Robert Geller
|
|
Aug 6, 2005 21:40:45 GMT
Unassigned
|
|
I have now encountered this problem on two different PCs. On one, registering HPBPRO.exe as above worked. On the other, the old version of HPBPRO.exe and HPBOID.exe and HPBPROPS.dll were in the \windows\system32 directory and the new versions were in various HP directories. The problems got better when I stopped the HPBPRO process through task manager then renamed the old versions to xxx.exe.old or xxx.dll.old and copied the new versions to \system32 then rebooted.
The old version was 1.0.42.0 and the new version was 1.0.45.0. The new version comes with downloadable printer drivers. (I have verified that they come with the driver for the Color Laserjet 2550L and with the driver for the Color Laserjet 4650.)
See what versions you actually have running in \windows\system32. |
|
|
Rob Johnson
|
|
Aug 23, 2005 21:41:40 GMT
Unassigned
|
|
I don't have a solution but am getting pretty ticked off. After reading this thread I contacted HP Tech Support the fixhpbpro file. It took two days and way too long to explain what I was asking for...probably shoulda just reinstalled the driver and been done with it, BUT I'm now seeing version 1.0.48.0 and having the same issues!
We use a product on the client side to monitor performance (EDGESIGHT by REFLECTENT) and it's reporting the module crashing on one customers PC multiple times a day. CPU utilization then goes to 100% and then other apps crash. I understand the need for bug fixes but if new revisions don't fix it what's the point. I'll now try to hack away at a solution because I no longer have faith. |
|
Paul S
|
|
Aug 26, 2005 11:57:13 GMT
Unassigned
|
|
|
Wow what an interesting thread. |
|
|
Jeff Zinkerman
|
|
Sep 22, 2005 20:24:22 GMT
Unassigned
|
|
|
This is interesting. I have this process running on my CITRIX presentation server 4.0 box. It just appeared when I upgraded my Citrix version from Metaframe XP to presentation server 4.0. I am worried that it has something to do w/ Citrix univesal print driver, but I think I am going to just rename the file and see what happens. |
|
|
Håkan Lans
|
|
Oct 25, 2005 18:17:06 GMT
Unassigned
|
|
I have contacted HP support many times but got no solution. For the first time I have now got confirmation that my request âhas been reviewed and forwarded to the proper individuals as requestedâ (see below). If someone are intrested to follow up you can send an e-mail to : LJMono.Support@hp.com and refer to the case number.
Från: HP LaserJet Product Support [mailto:LJMono.Support@hp.com]
Skickat: den 25 oktober 2005 22:47
Till: me
Ãmne: Re: VB: VB: HP Printers - HPBPRO Error Troubleshooting Hewlett Packard Customer Care Email <<#28260-36313#>>
Hello ,
Thank you for contacting Hewlett-Packard's Commercial Solutions Center.
The e-mail message you sent has been reviewed and forwarded to the proper individuals as requested.
As the updated file, we sent did not correct the issue we are currently without a solution for you. You might try uninstalling the software for the HP Color LaserJet 2840 and installing just the print driver from the Web. This will get you print functionality for the time being. We suggest you check the Web or sign up for updates so as new software is released you will be notified.
Once again, thank you for contacting Hewlett-Packard's Commercial Solutions Center. |
|
|
Jared Hedman
|
|
Feb 22, 2006 11:20:47 GMT
Unassigned
|
|
Here everyone, took a long time but this should help everyone.
ftp://hpbpro:patch@hprc.external.hp.com
P.S. I spent 2 months with Microsoft Premier Services getting multiple memory dumps that proves this exe causes a memory leak. |
|
|
Christophe Van Oyen
|
|
Feb 27, 2006 15:26:03 GMT
Unassigned
|
|
Last suggestions did not work tried installing HPBprofix and it does not help.
I have 5 PC's some with a Laserjet 4250dtn connected through my router.
I constantly get every 30 seconds on the pc's the erro 10009
>>
DCOM was unable to communicate with the computer ARCHIMAGO-PC3 using any of the configured protocols.
<<
So what can I do does a simple unistall of Toolbox solve this.
Drivers will be left as well as webadmin ?
Anyone knows ? |
|
|
David Kessel
|
|
Apr 3, 2006 18:54:52 GMT
Unassigned
|
|
|
I tried the solution suggested on April 28 (using dcomcnfg) and this eliminated HPBPRO.EXE from running every 30 seconds. Now all I have to do is find out how to stop msmsgs.exe from running every 45 seconds. |
|
|
John
|
|
Sep 15, 2006 16:48:47 GMT
Unassigned
|
|
I have had the same problem with HPBOID and HPBPRO. The directions with hpbprofix.exe say to call 1-800-HP-Cares for assistance. This turns out to be an oxymoron. The number yeilds a busy signal. Online Chat support simply says they can't help and I should call HP support. HP support yeilds only an endless string of semi-english-speaking reps who don't know the answer. Is there a simple procedure for using hpbprofix_srv.exe ?
Does anyone have the directions to use it?
Why can't HP help with this? |
|
|
D_C_Walker
|
|
Oct 13, 2006 15:08:45 GMT
Unassigned
|
|
|
And yet another version of this problem: I added a LJ1320 to my home office workstation (direct via LPT1). "HP Tools" came with the standard install. Everything looked fine until I started noticing intermittant freeze-ups without taskmanager showing any unusual cpu-busy. It felt like the background AV scanner is running amok. Procexp showed HPBPRO popping in and out and the event log was getting the 10009 errors on a network connected printserver every 35 seconds. After lots of bad advice from the hp support guys, I de-install tools and the problem goes away. I guess that "Tools" is not ready for prime-time. |
|
|
Rob Saville
|
|
Oct 16, 2006 04:42:16 GMT
Unassigned
|
|
2 and 1/2 years on and I still get notifications that this thread is still ongoing...... I wonder how long is too long to sort out a bug?
Rob |
|
|
Russell Byrne
|
|
Nov 21, 2006 14:25:25 GMT
Unassigned
|
|
I continue to experience this problem. Just today I killed 100 instances of both HPBPRO and HPBOID on my server. I have followed the steps outlined above to no avail.
Surely someone, somewhere has the answer to this persistant problem. |
|
|
Dan Thomas
|
|
Nov 21, 2006 15:35:01 GMT
Unassigned
|
|
|
Putting any HP printer software on a server should be avoided. Instead, use the "Add Printer" interface to add just the driver. |
|
|
pedidoc
|
|
Jan 10, 2007 00:16:41 GMT
Unassigned
|
|
Add my name to the list, someone has to be first in 2007. I'm having trouble with HPBPRO.EXE (one instance) tying up the computer 99% CPU - and of course, printer is out of warranty and now they want $25 for tech support.
so yeah, problem still not fixed. Wish me luck! |
|
|
weellio
|
|
Jan 10, 2007 21:52:27 GMT
Unassigned
|
|
something that will work for anyone using a microsoft OS
disable these two files in the firewall (or delete them)
then run this at command prompt
taskkill /im hpbpro.exe /f
taskkill /im hpboid.exe /f
or just a scheduled task to kill the every once in a while. |
|
|
Doug Searcy
|
|
Jan 29, 2007 15:02:23 GMT
Unassigned
|
|
We are having the same issue too and when I talked to HP they had no clue. I was on the phone with them for 2 hours last week.
I think I am going to try the TS settings for "port mapping" and also see if we have clients running the Toolbox. That seems to make the most sense to me at this point.
also here is the .doc that someone (maybe HP) posted up here a few threads up.
HP LaserJet Printers - Multiple Instances of HPBPRO.EXE Running Cause Server Crash or Hangs
___________________________________________________
Introduction
A Windows print server has multiple HPBPRO processes running simultaneously or the HPBPRO process contributes to crashing or hanging a print server.
Some examples of what the enterprise customer may see are as follows:
⢠CPU utilization on Print Server will go to 100% or everything looks fine but blank pages are printing out on printers. During this time if the administrator goes to Task Manager they may see there are multiple instances of HPBPRO running on the server as a process.
⢠A customer has multiple print servers running in their network environment. Various servers are seeing HPBPRO randomly become active for no apparent reason and causing performance problems on the server. Closing or killing the HPBPRO processes or rebooting the server solves the issue for the time being.
Detailed problem description
This problem occurs when following conditions are met:
⢠ToolBox is installed through a HP Printer CD on client machine
⢠Print Server has one or more EAC based Printers shared to clients
⢠Client machine has one to more printer connections (Point and Print) through the Print Server.
When Toolbox is installed and running on a client machine it starts a local HPBPRO process to resolve ports for each of the printers in the Printers folder (including remote printer connections) every 30 seconds. This local instance of HPBPRO will also start an instance of the HPBPRO process on the Print Server through the Point and Print connection. With a slow or busy network the local HPBPRO could leave stale instance of the process on a server. This stale instance will remain an active process until the process is stopped or the system is restarted.
A common scenario is the following: A Print Server is vending a large amount of shared printers (100+) to a large amount of clients (500+). A small number of clients have Toolbox installed and statusclient.exe or hpstatus.exe will trigger multiple (possibly 20+) instances of "HPBPRO" processes on the server. Over period of time these stale instances on the Print Server cause the system to hang or crash.
Solution or Workaround
Have the customer download and install HPBPROFIX on their server. This file will install a newer version of hpbpro (version 1.048.0 or later) that will deny remote access to the HPBPRO process and also will register HPBPRO as a local COM.
NOTE: Even with this fix the Microsoft COM infrastructure on the Server could still log a DCOM error (Even ID 10002) that will be associated with the user(s) who has Toolbox installed. This should not cause any issues on the server other than the logging of multiple DCOM events. A temporary fix is to find the client PC referenced in the DCOM event and completely remove Toolbox from that PC. In the future there will be a Toolbox patch that can be installed on the client to correct this issue.
There are some side effects for running HPBPROFIX:
⢠âUpdate nowâ feature will not work from client machine. Administrator will have to perform âUpdate Nowâ from the server.
⢠9x clients that use a printer connected through a server (Point and Print) will not be able to use EAC component. âUpdate Nowâ will also not work.
⢠Printer connections using âHP Mobile Printerâ driver will not work properly.
⢠The HP Mobile Printer driver will fail when trying to resolve the printer connection using the Printerâs share name. However, the driver will work fine with the IP address of the printer.
How to install HPBPROFIX
Steps for installing HPBPROFIX and configuring it as Local COM at the Print Server is:
1. Log on to Print Server as an administrator.
2. Copy hpbprofix.exe on to the print server.
3. Run following command from the DOS window. C:> hpbprofix
NOTE: If an old version of HPBPRO is locked by a process HPBPRO will pop a message box requesting a reboot to release the old version so that the new file will be copied after the reboot. Run HPBPROFIX again after the reboot.
Steps to Roll Back HPBPRO configuration (for isolated cases where we want to undo what was done above):
1. Log on to Print Server as an administrator.
2. Copy hpbprofix.exe on to the print server.
3. Run following command from the DOS window. C:> hpbprofix ârestore |
|
|
Mark Myerscough
|
|
Jan 31, 2007 00:28:43 GMT
Unassigned
|
|
Jan 31 - I just upgraded my Windows 2000 Server to accept a Windows 2003 Domain Controller (forestprep, etc.).
Immediately, this problem began on the Windows 2000 server. NEVER had the problem before - the Windows 2000 server had not required a non-scheduled restart in over 2 years - now I am restarting the server for the third time in five days.
I'm not getting the 100% CPU utilization - my symptom is that the server slowly stops responding actions. First, I can't start any programs (such as Active Directory Users and Computers, Group Policy Editor, etc.). Then, it stops responding to database queries on Web-pages. Then it stops responding to file sharing / etc.
HP tech folks - your silence is DEAFENING here. |
|
|
Rob Saville
|
|
Jan 31, 2007 07:32:48 GMT
Unassigned
|
|
Just a general comment on HP tech supp in UK - it might as well be non existant. They have problems with simple English comprehension.
I raised an incident re printing PCL to a deskjet from windows. They replied (after 6 emails back and forth) offering advice on printing Postscript from a VMS machine.
Neither of which I had ever mentioned.
I would complain of their obfuscation, but they wouldn't understand that either... |
|
|
Cayce Will
|
|
Jan 31, 2007 09:36:51 GMT
Unassigned
|
|
Does anyone have current instructions to permanently remove HPBOID.EXE and HPBPRO.EXE from starting up on a Windows Server 2003 Terminal Services server?
I can not definitively say that either program is malfunctioning but I do not wish for them to start up and waste system resources.
I've seen 20 to 50 instances of each of these processes cause the spooler process to spike to 100% and then restart. |
|
|
JN Hall
|
|
Feb 2, 2007 18:11:49 GMT
Unassigned
|
|
I just noticed there are a zillion instances of HPBPRO and HPBOID running on my laptop with my C6180 all-in-one install. *sigh* What is it with this HP software? It's a wonderful piece of hardware though, unbelievable for the money.
So, how do I make this not happen? |
|
|
Scott Wierzbicki
|
|
Feb 2, 2007 19:10:16 GMT
Unassigned
|
|
|
You wait till HP gives a crap, meaning 'forget it'. They don't. |
|
|
Ian J Schwamberger
|
|
Feb 11, 2007 09:42:19 GMT
Unassigned
|
|
Ahhh... Finally made some headway on this. My print server was hanging regularly because of this - hpbpro processes spawning all over my server and utilization through the roof. I've got 100+ laserjets and a couple of thousand users. What I did...
1) got the latest hpbpro.exe fix from HP (I believe might be different versions of hpbprofix_srv.exe - the companion document I got was different than what was posted above.
2) set spooler to disabled - rebooted
3) ran patch - started spooler
4) did not see multiple hpbpro.exe instances - but still saw one kicking off about every 30 seconds. This was putting a pretty significant hit (70%+ CPU utilization)on the server each time. Saw that the process had MY userID. Realized thay my print server was acting as both the server - and client since it had the driver installed.
5) Removed StatusClient and hpbpsttp entries from HKLM\Software\M$\CurrentVersion\Run (these are added during the 'Toolbox' install - part of many HP LJ/CLJ drivers) - rebooted.
6) Check for hpbpro.exe - the little @#$%^&^%$%^& is gone and not coming back! My CPU utilization is normal and available memory is not shrinking.
7) warned everyone with admin access to the print server that a future HP driver installs can/will overwrite the patch applied since each install will overwrite and re-register hpbpro.exe.
8) alerted our workstation support team that statusclient.exe may be causing performance issues on client workstations running the driver toolbox (packaged as part of the driver)
**********
I WILL NOT BE POSTING THE .EXE FIX SENT TO ME BY HP. THIS IS PUBLICLY AVAILABLE FROM HP SUPPORT - WHICH I AM NOT. I ALSO DON'T WANT TO DEAL WITH SOME POTENTIAL MORON FROM HP FOR BREAKING SOME SUPPORT AGREEMENT OR DISTRIBUTION LIMITS ON THIS FIX. I HAVE BEEN THE RECIPIENT OF SUCH ATTACKS WHEN THE MFG DOESN'T LIKE THE POST AND DECIDES THE BEST WAY TO DEAL IS TO ATTACK THE CUSTOMER WITH THE PROBLEM RATHER THAN FIXING POORLY DESIGNED/WRITTEN CODE.
**********
READ OR SKIP MY RANT TO READ THE TEXT OF THE COMPANION DOCUMENT THAT CAME WITH hpbprofix_srv.exe
**********
<RANT>
Looks like somebody official stuck their nose in to moderate this posting - really makes me think that SOMEBODY at HP is watching. This is a rotten enough problem - obviously caused because when tested they didn't try a real enterprise environment. This has been enough of a problem - CAUSED BY HP'S DRIVERS - where HP should feel obligated to provide concise, supported instructions to keep their customers running. My environment is too large for this kind of slop - I've got over 500 HP servers, HP SANs, HP Blade Racks, thousands of HP workstation. HP, if you are reading this - maybe this will get you moving on something that would be a SOLUTION - not continuous workarounds - for this situation. As stated above - great hardware - but my experiences over the last couple of years is that HP's support is going to ****. My last episode with them was on a 6-figure cost Integrity server. Even with the highest level support we could purchase from HP, I still wound up with a tech who didn't know the difference between a Proliant and an Integrity server. Maybe it's time to consider moving on. Maybe HP will step in here. But I'm thinking it will only be to have me open a new posting on bad HP support.
To those actually reading my rant... There is a name for the author on the document - Chris Marsden. In my experience HP's email convention is First.Last@hp.com. Hmmm... Maybe as a community we can use this to get somebody's attention... but remember that throwing a tantrum and/or cussing will probably not get anyone anywhere. Remember who is really being unprofessional here and do not lower yourself.
</RANT>
**********
Document Summary
HPBPRO.exe has several instances running at one time on a Server
Who to contact for assistance
Author: Chris Marsden, LaserJet Technical Marketing
Date: 8/11/2005
Security Level: Public
Issue Description:
Multiple HPBPRO processes running simultaneously or the HPBPRO process contributes to crashing or hanging a print server.
HPBPRO versions prior to 2.0.45 have been known to help create multiple instances of the HPBPRO process on the server.
Solution or Workaround:
If you are experiencing the issue described above please contact HP Support at 1-800-HP-CARES. The call agent will assist you with downloading a tool called HPBPROFIX and will assist you through properly using the tool that will install a newer version of hpbpro and deny remote access to the HPBPRO process and also will register HPBPRO as a local COM.
The tool may need to be run on both the server and any client that has toolbox installed.
Detailed Information:
This occurs when following conditions are met:
⢠ToolBox is installed through a HP Printer CD on client machine
⢠Print Server has one or more EAC based Printers shared to clients
⢠Client machine has one to more printer connections (Point and Print) through the Print Server.
When Toolbox is installed and running on a client machine it starts a local HPBPRO process to resolve ports for each of the printers in the Printers folder (including remote printer connections) every 30 seconds. This local instance of HPBPRO will also start an instance of the HPBPRO process on the Print Server through the Point and Print connection. With a slow or busy network the local HPBPRO could leave stale instance of the process on a server. This stale instance will remain an active process until the process is stopped or the system is restarted.
A common scenario is the following: A Print Server is vending a large amount of shared printers (100+) to a large amount of clients (500+). A small number of clients have Toolbox installed and statusclient.exe or hpstatus.exe will trigger multiple (possibly 20+) instances of "HPBPRO" processes on the server. Over period of time these stale instances on the Print Server cause the system to hang or crash.
There are some side effects for running HPBPROFIX:
⢠âUpdate nowâ feature will not work from client machine. Administrator will have to perform âUpdate Nowâ from the server.
⢠9x clients that use a printer connected through a server (Point and Print) will not be able to use EAC component. âUpdate Nowâ will also not work.
⢠Printer connections using âHP Mobile Printerâ driver will not work properly.
⢠The HP Mobile Printer driver will fail when trying to resolve the printer connection using the Printerâs share name. However, the driver will work fine with the IP address of the printer. |
|
|
Ian J Schwamberger
|
|
Feb 11, 2007 23:56:22 GMT
Unassigned
|
|
You gotta love this... In doing some follow-up checking I was looking at things in a bit more detail. The ftp link above yeilds the same files I worked with. But here is the kicker...
The compainion document states, "HPBPRO versions prior to 2.0.45 have been known to help create multiple instances of the HPBPRO process on the server."
The version of the .exe delivered by this fix... 1.0.50.0.
Anyone surprised? |
|
|
Mark Myerscough
|
|
Feb 12, 2007 12:33:11 GMT
Unassigned
|
|
Just a follow up note here.
Matthew Ornawka's note for Aug 6, 2004 works.
My situation started when I opened a remote location, with a site-to-site tunnel via our Cisco PIX. The remote site also had a HP printer installed at it, and the offending HPBPRO software installed.
My best reconstruction of the problem is that users at the remote site still used the Cisco VPN to connect to the central office, even though the site-to-site tunnel rendered this unrequired. At that point the HPBPRO software got confused, and started looking for the printer that was installed on the remote server. Since it was registered two different ways (one by the site-to-site tunnel, the other via the VPN connection) the software had difficulty resolving it. Dropping the VPN connection increased the problem.
Long and short of it was, deleting HPBPRO from my servers, and then editting the registry to remove all the hooks, solved the problem. Restarted both servers and have been up and running now for 13 days without a restart - the way things ought to be.
I now think the conversion to Windows 2003 Active Directory was a false tangent, unrelated to the problem. |
|
|
Jed Davidow
|
|
Feb 17, 2007 02:34:12 GMT
Unassigned
|
|
This is unbelievable.
I bought a Deskjet 6980 to use on my home wireless network.
The installation CD gives me two options; the bloated option and the super bloated option. Choosing the smaller, bloated option gives me no choice but to install a bunch of crap including photo organizing software, editing software, etc.
I went online, and for network use, you need to download the 250MB full install. No separate driver that I could find.
All I want is the driver! So I do the THIRTY MINUTE INSTALL and then uninstall 4/5 HP programs on my Add/Remove list.
After the install I notice 7 additional processes running, and searching on them led me to this forum.
THIS ISN'T EVEN A SERVER!!!
I have been burned by every other HP product I have purchased. When they screwed me on a SCSI CD burner ($400, back in 1997) I swore I would never buy another HP product. But this printer had all the features I wanted and the price was OK. So I gave them a chance. And look what it got me. 4 hours of dealing with this BS.
Hey HP managers, if you are listening: ALL THIS PRINTER NEEDS IS A FREAKING DRIVER. No photo suite software, no process monitors, no software update, imaging suite, no bloated hijack software, etc. JUST A SIMPLE FRICKIN' DRIVER.
You suck HP. I am taking this back on Monday. According to the store policy, I will have to pay to replace the ink I opened. I am using that ink to print this forum to demonstrate how disgusting this product really is. |
|
|
JN Hall
|
|
Feb 17, 2007 22:34:32 GMT
Unassigned
|
|
Frankly I *love* my HP AIO - it is a terrific scanner (assuming you use VueScan, obviously) - and a very convenient printer, especially with the wireless networking.
But I just don't get this thing where I have a couple dozen copies of HPBPRO and HPBOID running now. I gather the number increases as I run more print jobs. This is from a laptop - not a "server." Can it really be that hard to fix this? |
|
|
Noury Goujjane
|
|
Mar 5, 2007 18:33:30 GMT
Unassigned
|
|
I'm in the same situation as Jed. I've dealt with computers for the last 20 years and long for the days when we could but a piece of hardware without getting slammed with all sorts of not-useful and not-functional software! (dell, anyone?).
Perhaps marketing could save us all some money by selling "expert" versions of their hardware without all this software geared to beginners.
I just want my printer to work -- and not at the expense of my computer. |
|
|
Noury Goujjane
|
|
Mar 5, 2007 18:35:02 GMT
Unassigned
|
|
|
I also find it very telling that this thread was started in 2004 -- and now in 2007 we are still dealing with the same crappy software! |
|
|
Michael Livingston
|
|
Mar 29, 2007 11:23:54 GMT
Unassigned
|
|
|
Yeah, I have this also. Seems like we should be looking for no nonsense printers like Lexmark and maybe this will wake HP up. |
|
|
Jed Davidow
|
|
Mar 29, 2007 13:20:00 GMT
Unassigned
|
|
Just an update if anyone else with a consumer-level printer finds this...
I have a 6980, which has built-in wired and wireless networking.
You can then http in to the printer and set up the network options.
I then chatted with support and they sent me a PATCH to fix this problem. It's not available on the printer support page though. Nice.
In any event, the BEST thing to do is to install the generic 990c printer driver anyway. That works over USB and network (although you need to create a standard HP printer port for the network connection).
Good luck. |
|
|
Guido Pinamonti
|
|
Apr 27, 2007 20:32:36 GMT
Unassigned
|
|
We have 2 servers running Symantec Netbackup with SCSI and SANS attached storage. These servers will hang sporadically for maybe 10 minutes or so with a gray console screen and then everything comes back to life. I've also had trouble shutting these systems down from an RDC session. I noticed a number of HPBPRO and HPBOID processes running. Not sure where these came from. I've never seen the processes spike, but do you think I might be experiencing symptoms consistent with others in this thread? thx.
Guido |
|
|
Lloyd Schulz
|
|
Apr 28, 2007 08:57:15 GMT
Unassigned
|
|
Reply to Guido:
If you have multiple instances of HPBPRO running, you can expect it to 'hang' your machine. So yes, you should be interested in the info in this thread. We had trouble with a server locking up / crashing, and when we resolved the situation with multiple instances of HPBPRO the problem went away.
Lloyd |
|
|
Amy Elliott
|
|
May 17, 2007 15:47:53 GMT
Unassigned
|
|
|
I recently started working for this clinic that is having basically the same problem everyone else seems to be having here. In all my searching there seems to be a lot of solutions, but, not a definitive one. I'm guessing because of the variety of software out there. Anyways, the only solution that I found mentioned with any consistancy was to dig the files out of the C: drive and the registry and delete them, then reboot. We have Windows 2000 server running and this worked very well for us. We only deleted the executable files we found. We currently have no instances of the HPBPRO.EXE or the HPBOID.EXE running in our process list. |
|
|
John
|
|
May 17, 2007 17:50:20 GMT
Unassigned
|
|
I've never been able to completely eliminate this problem, despite searching the hard drive and the registry and deleting. HPBPRO always seems to come back when I use my printer, and has to be deleted from the task manager when the instances pile up.
I wonder, has anyone written a script to automatically kill all the processes?
One click would be easier than having to delete and confirm each instance manually.
You would think HP would have helped by now, since the problem is so widespread. I guess they are busy changing directors and such. |
|
|
Gary Delp
|
|
May 17, 2007 18:46:00 GMT
Unassigned
|
|
I have tried removing the executables, and the machine hangs when I try to print. I have tried chatting with HP service and they gave me a zip file with two executables hpbprofix_cln.exe and hpbprofix_srv.exe
The help guy just said to run the zip file. I asked which or both files, and he said both. It didn't work. I have since, with reboots in between, tried running just one, and just the other, and I still have an extra copy of HPBPRO running for every print job. I like the idea of writing a utility to kill all processes names HPBPRO.EXE
if you make a shortcut that has as its target:
C:\WINDOWS\system32\taskkill.exe /IM HPBPRO.EXE
that may well work for you, it does for me. I changed the icon to the HP Logo ;-) |
|
|
Gary Delp
|
|
May 17, 2007 18:53:30 GMT
Unassigned
|
|
Sorry, I left out the force /F in the past post:
if you make a shortcut that has as its target:
C:\WINDOWS\system32\taskkill.exe /F /IM HPBPRO.EXE
that may well work for you, it does for me. I changed the icon to the HP Logo ;-)
Windows tells you it killed them, but doesn't. you can use tasklist to see. |
|
|
John
|
|
May 18, 2007 15:24:19 GMT
Unassigned
|
|
Shortcuts worked well. Thanks.. I made one for HPBOID.exe, which I also have building up along with HPBPRO.exe
Thanks again. |
|
|
sandy_tosh
|
|
Jun 7, 2007 11:43:17 GMT
Unassigned
|
|
Hi,
You can try this. Go to start - run - services.msc - HP Port resolver - disable |
|
|
Cayce Will
|
|
Jun 7, 2007 11:53:15 GMT
Unassigned
|
|
Disabling the service doesn't work (at least not on our terminal server farm). The service re-sets itself and launches.
Unless HP provides a removal tool that strips this piece of shite out of every HP driver it horrifyingly comes with, there is nothing we as administrators can do except manually remove it from the HP drivers and manually stop and then delete the services.
Of course, if printing had ever been in the Top 100 Things To Make Work In Terminal Services when Microsoft programmed it, this all might have been just a bad dream and not the living nightmare that is HPBPRO. |
|
|
Tony Reid
|
|
Jun 30, 2007 23:39:56 GMT
Unassigned
|
|
Try this little script-ette.
It removes HPBPRO,HPBOID and related files, DCOM and registry entries.
** Be careful of lines that wrap round **
If you don't want to remove the files, check the versions of your DLLs and EXEs with the list provided below.
TR
@echo off
@echo ** Remove HP Port Resolver/Staus Server **
@echo includes DCOM and all registry elements
::Tested on Windows Server 2003
pause
::Verions as of July 1st 2007
::HPBOID.DLL 3.1.1.54 (25Kb)
::*HPBOID.EXE 1.0.45.0 (72Kb)
::HPBOIDPS.DLL 3.1.1.54 (8Kb)
::HPBPRO.DLL 3.1.1.54 (39Kb)
::*HPBPRO.EXE 1.0.45.0 (76Kb)
::HPBROPS.DLL 3.1.1.54 (8Kb)
::Also check
::HPBMINI.DLL 1.0.0.19 (237Kb)
::HPCDMC32.DLL 1.0.2.35 (657Kb)
::Obtain (*) files from the "HP LaserJet 4100 PCL 6" driver
::Version 4.27.4100.441 (23 Jul 2004)
::lj4100pcl6win2kxp2003-en.exe
::For Windows Server 2003, Windows 2000, Windows XP
::Follow this link http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=18972&prodSeriesId=83436&prodNameId=29118&swEnvOID=1005&swLang=8&mode=2&taskId=135&swItem=lj-2010-10
::Obtain all the other files from the "HP Color LaserJet 4650 PCL 6" driver
::version 61.071.661.41 (31 May 2007)
::clj4650pcl6winvista2kxp2003.exe
::For Windows Server 2003, Windows 2000, Windows XP, Windows Vista
::Follow this link http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=18972&prodSeriesId=375773&prodNameId=375775&swEnvOID=1005&swLang=8&mode=2&taskId=135&swItem=lj-20533-6
net stop "HP Port Resolver"
net stop "HP Status Server"
reg delete HKCR\AppID\HPboid.DLL /f
reg delete HKCR\AppID\HPboid.EXE /f
reg delete HKCR\AppID\hpbpro.dll /f
reg delete HKCR\AppID\hpbpro.EXE /f
reg delete HKCR\AppID\{55F3F296-4775-4AE9-B0AA-52393842EF3C} /f
reg delete HKCR\AppID\{3B05F114-4087-4557-8952-AAF023709EB0} /f
reg delete HKCR\CLSID\{454CB2AB-0024-4434-A5C0-0DF0FB3C3E74} /f
reg delete HKCR\CLSID\{5A5AA0AA-1DEB-4683-96B0-B43301E83971} /f
reg delete HKCR\CLSID\{8088D54C-C457-4DFD-B77E-449F12675D2A} /f
reg delete HKCR\CLSID\{8AF30D93-D46B-456E-8F70-ED6A07197A3F} /f
reg delete HKCR\CLSID\{D713F357-7920-4B91-9EB6-49054709EC7A} /f
reg delete HKCR\Interface\{8AF30D93-D46B-456E-8F70-ED6A07197A3F} /f
reg delete HKCR\HPPortResolver.hpbpro /f
reg delete HKCR\HPPortResolver.hpbpro1 /f
reg delete HKCR\HPStatusServer.HPBOID /f
reg delete HKCR\HPStatusServer.HPBOID1 /f
reg delete HKCR\HPStatusServer.HPBOID.1 /f
reg delete HKCR\TypeLib\{06333F23-D064-4A34-B2DE-C30630C0B567} /f
reg delete HKCR\TypeLib\{CA2E8A2E-EDEC-4A6C-A92E-79A23A814F25} /f
reg delete HKLM\SOFTWARE\Classes\AppID\hpbpro.dll /f
reg delete HKLM\SOFTWARE\Classes\AppID\HPboid.DLL /f
reg delete HKLM\SOFTWARE\Classes\AppID\HPboid.EXE /f
reg delete HKLM\SOFTWARE\Classes\AppID\hpbpro.EXE /f
reg delete HKLM\SOFTWARE\Classes\CLSID\{454CB2AB-0024-4434-A5C0-0DF0FB3C3E74} /f
reg delete HKLM\SOFTWARE\Classes\CLSID\{5A5AA0AA-1DEB-4683-96B0-B43301E83971} /f
reg delete HKLM\SOFTWARE\Classes\CLSID\{8088D54C-C457-4DFD-B77E-449F12675D2A} /f
reg delete HKLM\SOFTWARE\Classes\CLSID\{8AF30D93-D46B-456E-8F70-ED6A07197A3F} /f
reg delete HKLM\SOFTWARE\Classes\CLSID\{D713F357-7920-4B91-9EB6-49054709EC7A} /f
reg delete HKLM\SOFTWARE\Classes\HPPortResolver.hpbpro /f
reg delete HKLM\SOFTWARE\Classes\HPPortResolver.hpbpro.1 /f
reg delete HKLM\SOFTWARE\Classes\HPStatusServer.HPBOID /f
reg delete HKLM\SOFTWARE\Classes\HPStatusServer.HPBOID.1 /f
reg delete HKLM\SOFTWARE\Classes\Interface\{8AF30D93-D46B-456E-8F70-ED6A07197A3F} /f
reg delete HKLM\SOFTWARE\Classes\TypeLib\{06333F23-D064-4A34-B2DE-C30630C0B567} /f
reg delete HKLM\SOFTWARE\Classes\TypeLib\{CA2E8A2E-EDEC-4A6C-A92E-79A23A814F25} /f
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\HP Port Resolver" /f
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\HP Status Server" /f
reg delete "HKU\.DEFAULT\Software\Microsoft\Windows\ShellNoRoam\MUICache\C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\HPBPRO.EXE" /f
reg delete "HKU\.DEFAULT\Software\Microsoft\Windows\ShellNoRoam\MUICache\C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\HPBOID.EXE" /f
ren %systemroot%\system32\HPBOID.DLL hpboid.dll.old
ren %systemroot%\system32\HPBOID.EXE hpboid.exe.old
ren %systemroot%\system32\HPBOIDPS.DLL hpboidps.dll.old
ren %systemroot%\system32\HPBPRO.EXE hpbpro.exe.old
ren %systemroot%\system32\HPBPRO.DLL hpbpro.dll.old
ren %systemroot%\system32\HPBPROPS.DLL hpbprops.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\3\HPBOID.DLL hpboid.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\3\HPBOID.EXE hpboid.exe.old
ren %systemroot%\system32\spool\drivers\w32x86\3\HPBOIDPS.DLL hpboidps.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\3\HPBPRO.DLL hpbpro.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\3\HPBPRO.EXE hpbpro.exe.old
ren %systemroot%\system32\spool\drivers\w32x86\3\HPBPROPS.DLL hpbprops.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\HPBOID.DLL hpboid.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\HPBOID.EXE hpboid.exe.old
ren %systemroot%\system32\spool\drivers\w32x86\HPBOIDPS.DLL hpboidps.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\HPBPRO.DLL hpbpro.dll.old
ren %systemroot%\system32\spool\drivers\w32x86\HPBPRO.EXE hpbpro.exe.old
ren %systemroot%\system32\spool\drivers\w32x86\HPBPROPS.DLL hpbprops.dll.old
FOR /F "tokens=2 delims=Z" %%A IN ('reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v TEMP') do set $var=%%A
set $var=C:\WINDOWS\TEMP
ren %$var%\????-????-????????_HPBPRO.* ????-????-????????_hpbpro.*.old
ren %$var%\????-????-????????_HPBOID.* ????-????-????????_hpboid.*.old
ren %$var%\????-????-????????_HPBOIDPS.* ????-????-????????_hpboidps.*.old
ren %$var%\????-????-????????_HPBPROPS.* ????-????-????????_hpbprops.*.old
::unREM the following line for Citrix CPS4.x
::REM net stop cpsvc
net stop spooler
del %$var%\*.tmp /F /Q
::unREM the following line for Citrix CPS4.x
::REM net start cpsvc
net start spooler
@echo ** Complete ** |
|
|
Anthony Walter
|
|
Jul 6, 2007 18:47:27 GMT
Unassigned
|
|
We have a Win2k Server running on a P3 800Mhz acting as a bit of a print server for about 40 clients and 14 printers. The printers used are a combination of Dell and HP printers; Dell 5210, 5310, 1710 and HP 6940, 6980, 6122, 6L, and 1000. I had about 5 instances of HPBOID and HPBPRO (each) at about 2mb each, but they didn't interfere or hurt performance. However, there was a slight misconfiguration with ONE printer while I was on vacation, and when I came back and checked why the server was being a little bit slow, and lo and behold, there were *591* processes running on that old machine, with about 6mb ram left. The printer that the users where trying to print to was off, thus wasn't being detected by the HP app, even though there was some sort of connection to it through Windows.
I'm sure that one could easily attack and compromise a production server or computer by queing a bunch of print jobs to a printer that didn't (?) exist.
I fixed the issue by removing the DCOM entries. I didn't touch the registry or edit any .ini files. Oddly enough, msconfig didn't have any startup entries to begin with, and the HP Port resolver processes were stopped and disabled while the issue was occuring.
On a side note, stay away from Deskjet 69xx series printers; I find it hard to believe that my printer 'requires' 300MB of crapware in order to operate 'correctly' The only way to install from the CD is by doing it manually (search for the driver folder, etc) and even then it still adds some crapware. Drivers from HP's website I think are the same.
Dell's 5310 and 5210 printers rock as far as drivers are concerned, though their web-based driver downloads lack a custom GUI and some other miscellanous features that you can only find on the drivers on CD |
|
|
Baz Greenaway
|
|
Jul 18, 2007 10:59:11 GMT
Unassigned
|
|
After installing a HP LaserJet 2820 I had HPBPRO.EXE totally crippling my W2K server after about 2/3 days of use when CPU utilization was going through the roof. Only a reboot would resolve the problem, albeit temporarily until 2/3 days later. It was turning into a nightmare.
After a lot of searching, I found this forum and followed the solution posted by Matthew Ornawka on Dec 9 2004 and it worked liked a dream. All traces of HPBPRO.EXE have now disappeared and server has now been running with no problems whatsoever for over two months. Basically just stick with the HP drivers and do not bother with all of the peripheral crap software that goes with it, especially the HP Port Resolver. |
|
|
John
|
|
Jul 18, 2007 13:09:20 GMT
Unassigned
|
|
|
I used the script posted by Tony on July 1, 2007 and HPBPRO.exe hasn't been back since. The printers are functioning fine on the network. THanks for the fix. |
|
|
John
|
|
Jul 18, 2007 13:09:33 GMT
Unassigned
|
|
I used the script posted above
by Tony on July 1, 2007 and HPBPRO.exe hasn't been back since. The printers are functioning fine on the network. THanks for the fix. |
|
|
Simon C Taylor
|
|
Jul 27, 2007 22:14:52 GMT
Unassigned
|
|
|
This issue was first posted on Jan 15 2004. I find it extremely hard to understand why it is three and a half years later and HP is still selling printers with software that causes all these problems, even on standalone machines with a single printer. Also, I cannot comprehend why, in this particular discussion thread and others concerning HP printer software, there is no entry from an HP person saying how to deal with it. Virtually all of the fixes say disable or uninstall the software and still HP offers no solution. This is probably the last time I will buy an HP printer. |
|
|
PowerMong
|
|
Sep 11, 2007 12:47:25 GMT
Unassigned
|
|
|
|
eldonjon72
|
|
Oct 12, 2007 15:37:52 GMT
Unassigned
|
|
WOW - WOW - I just fixed the problem!!! Don't know if this will fix it for anyone else, but it worked for me, and it is so stupidly simple. I've been fighting this for a year - and I fixed it!!!!! (Sorry, I just can't believe I finally beat this stupid problem!!!!)
Go into the printer's Properties, click on the Advanced tab, and UNCHECK "Enable Advanced Printing Options"
That's it! Instantly the printer started working perfectly! I haven't seen HPBOID.EXE since I did this, and every other problem I've had with this printer disappeared INSTANTLY!!! YES!!!!!! |
|
|
Jeff Smith
|
|
Oct 16, 2007 11:02:43 GMT
Unassigned
|
|
|
|
mkcurtis2z
|
|
Dec 16, 2007 01:24:14 GMT
Unassigned
|
|
How I solved it...
Similar to others here, I was getting duplicate instances of HPBPRO, and HPBOID. A new pair each time I printed. Home PC, WinXP SP2, printing to a new HP C6180 all in one, via network. Noticed problem after un-installing HP fatware that came with C6180, and installing basic driver from HP web site. (ps, also used to have an older HP C8xx vis USB, had deleted its driver).
Used Process Explorer by System internals, (better version of task manager), to see how many instances were loaded.
Tried but did not work:
1) Disabling print driver advanced features.
2) Disabling HPBPRO, and HPBOID Services
3) Deleting HPBPRO, and HPBOID from my system folder.
4) deleting from registry.
This Worked:
1) Changed from printing TO spool to print direct. |
|
|
RJ Bruce
|
|
Dec 18, 2007 13:33:37 GMT
Unassigned
|
|
I have two W2K3 terminal servers. No locally installed printers, just redirected printers that get picked up from the RDP clients. I had around 500 instances (on each server) of HPBOID.exe and HPBPRO.exe. I used taskkill to wipe out the existing instances:
taskkill /f /im hpboid.exe
taskkill /f /im hpbpro.exe
That temporarily rid me of the hpbpro.exe instances, but I started getting the hpboid.exe instances almost immediately again. I downloaded the from the ftp site noted in Jared Hedman's comment from 2/22/2006. I taskkilled again to clean up, then ran the hpbprofix_svr.exe from the zip file.
Since then I haven't seen either hpbpro.exe or hpboid.exe show up. It's only been about 15 minutes and I haven't seen what happens after a reboot, but it's promising.
This is a perfect example of why hp should ALWAYS release a "driver only" package, even for the officejet and photosmart printers. |
|
|
HPJim1941
|
|
Jan 21, 2008 16:22:39 GMT
Unassigned
|
|
|
eldonjon72's solution worked for me using a HP PS C7180 over a network. Uncheck "Enable Advanced Printing Options" on every computer. |
|
|
KentC
|
|
Jan 21, 2008 16:46:09 GMT
Unassigned
|
|
I followed Matthew Ornawka's advice, dated Dec 7, 2004.
Uninstall all drivers.
Edit the INF and remove the reference to the files and delete the DLL's.
Re-install drivers, no problems since. |
|
|
RobbieB
|
|
Mar 19, 2008 19:27:21 GMT
Unassigned
|
|
mkcurtis2z Dec 16, 2007 Your solution worked for me also...
"Changed from printing TO spool to print direct."
FINALLY, we print a lot here and by the end of the day I ended up having anywhere from 100-300 PROCESSES that were just hpbpro.exe and hpbboid. No more!
control panel>printers>right click printer choose properties>advanced tab> select radio option to print direct.
WOOHOO |
|
|
RobbieB
|
|
Mar 20, 2008 15:52:01 GMT
Unassigned
|
|
Okay never mind. Printing direct does remove the duplicate process crap BUT your computer wont do anything else until each page is finishes printing and that's definitely not cool with me.
I tried removing these entries from
HPBOID.exe
HPBOIDPS.DLL
HPBPRO.exe
HPBPROPS.DLL
HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Control>Print>Environments>Windows NT x86>Drivers>Version-3>Dependent Files
But still no success, infact a new process appears hpnra although this one does go away unlike the others.
I tried eldonjon72 Oct 12, 2007 suggestion Go into the printer's Properties, click on the Advanced tab, and UNCHECK "Enable Advanced Printing Options"
This seems to have worked. I'll know more after a full days use if it seems any slower.
In the mean time I think a taskkill batch will be the easiest solution for most people if you just schedule a task once an hour or something.
taskkill /F /IM HPBOID.exe
taskkill /F /IM HPBPRO.exe |
|
|
Mark Myerscough
|
|
Mar 20, 2008 18:20:33 GMT
Unassigned
|
|
Folks - the solution is spelled out in this thread. Matthew's solution works. Multiple users have testified to it. I've used it on multiple servers. Read the ENTIRE thread before posting insane recommendations like print direct.
Follow his post, do what it says to do. If you don't feel comfortable doing it, hire an IT consultant to do it for you. |
|
|
Norman Milburn
|
|
Apr 10, 2008 11:11:24 GMT
Unassigned
|
|
My print server has taken to crashing so I did some checking with Task Manager and saw that HPBPRO was consuming around 100,000 handles per day.
Since I ran HPBPRO -RegServer the total handle count has settled at 61! Too early to say if this will stop the server crashes but thank you to whoever for the tip and to everyone for their comments.
2003 server/SP2, 4GB RAM, lots of disk to which I recently added HPLJ3500 drivers. |
|
|
Sean McPartlin
|
|
Jun 1, 2008 04:42:33 GMT
Unassigned
|
|
|
I'm also having issues with this pile of an app! |
|
|
Sean McPartlin
|
|
Jun 2, 2008 20:58:19 GMT
Unassigned
|
|
OK I did some of the things above and it's made things worse.
I have a file server (win2003) that has a bunch of printers on it.
I went into dcomcnfg.exe and found the HP Port Resolver and HP Status Server and changed the Properties > Location tab >
and checked off the Run Application on the computer the data is located.
I also did :
Run the command "hpbpro.exe -RegServer".
Then run the command "hpbpro.exe -Service".
Now print jobs are comming out really slow and users are complaining about the slow print speeds...
What can I do to cleanly remove this crap? I've got a lot of printers on this server. |
|
|
Sean McPartlin
|
|
Jun 4, 2008 14:25:08 GMT
Unassigned
|
|
|
Well I removed hpbpro.exe from the registry and changed the drivers for the C LJ CP1510ni to use the postscript drivers from the network package and my problems seem to have gone away. |
|
|
KentC
|
|
Jun 4, 2008 15:09:47 GMT
Unassigned
|
|
SOLVED!!!
As I have mentioned before, as did Mark Myerscough.
"I followed Matthew Ornawka's advice, dated Dec 7, 2004.
Uninstall all drivers.
Edit the INF and remove the reference to the files and delete the offending DLL's from the driver folder.
Re-install drivers, no problems since."
Make sure all NEW drivers are treated similarly.
This instructions may sound like they are difficult, but really they are not.
It's just a little tedious.
Try this FIRST before trying anything else!
Thanks,
Kent |
|
|
Sean McPartlin
|
|
Jun 4, 2008 15:26:06 GMT
Unassigned
|
|
While I understand that uninstalling all the drivers and editing the INF will work I've found it wasn't needed in my situation. The solution does sound like it's a lot of work. I don't want to take a production print server down if I can help it. I also don't feel all that work is necessary. I will not install the print drivers from the CD again (usually don't) but it won't happen again.
hpbpro.exe isn't running anymore.. and my system hasn't run out of memory since. So it's safe to say at this point the measures I posted already have worked.
The 2004 solution may be the "correct" or "final" solution but I want to express that smaller changes might just fix other peoples issues. |
|
|
HPJim1941
|
|
Jun 27, 2008 15:30:53 GMT
Unassigned
|
|
Ok, I just renamed hpboid.exe and ran the following in the command window:
cd c:\windows\system32\spool\drivers\w32x86\3<enter>
hpbpro.exe -RegServer<enter>
hpbpro.exe -Service<enter>
Now there are no sessions of hpboid.exe or hpbpro.exe. All advanced print functions work from all my applications. HOWEVER, I cannot print a windows test page. I consider this a minor problem and will live with it to have no multuple sessions of the hpb*.exe while still having full print/scan/fax capability. |
|
|
Daan Van Isterdael
|
|
Jul 17, 2008 07:56:51 GMT
Unassigned
|
|
is this problem ever going to be fixed?
i tryed several things in this thread but no luck yet.
i get the error message at random times and need to reboot the server everytime.
Not fun to reboot a F&P server thats also running 48 netprinters >.< |
|
|
Eric Koch
|
|
Nov 17, 2008 03:29:24 GMT
Unassigned
|
|
Well, this thread is ugly with alot of regedits items and things frankly I did not want to muck with. I have a HP2840 printer via a network with many PCs (XP Pro SP3) talking to it....ala a static IP via Linksys Router. Many of the machines are fine with no DCOM 10009 errors which show a comm error with one of the machines (even though this printer does not hang off it). However, I have alot of PCs that show this error every 30 seconds and my memory goes down 5MB each time ! The solution below solved my problems 100%.
First, I only really needed one machine with HP Toolkit to see the health/status of the networked HP2840 printer. So, luckily for me our Server was fine with no DCOM errors...thus did not need to re-install the full HP software suite. However, for several of my other client PCs (some notebooks, some desktops) I really had not wanted the Toolkit on there but used the CD and had it installed. So, for me the below also helped clean this up too so only the print drivers get installed.
1) I downloaded both the 2840 PCL and Black & White drivers (~3MB) from the HP site. I did not download the postscript. I unzipped and put one in MyDocs directory called HP2840Color...the Black & White to MyDocs HP2840BW.
2) I uninstalled every HP printer, scanner software associated with the 2840...including Toolkit, HP Update, and any other in Control Panel>Add/Remove.
3) I then did search for files: HPBIOD.exe, HPBIOD.DLL, HPBPRO.exe, HPBPRO.DLL and deleted. I cleaned out Recycle Bin and ran my reg cleaner in Norton Systemworks called OBC...you may have different one. It cleaned up alot of links/references, etc. I also rebooted and re-ran OBS to make sure.
4) I went to Printer>Add New Printer. I did NOT chose Network printer...I chose Local but unchecked automatic...then in next step selected STANDARD IP, next step put in my network printer's static IP address and port name, then printer name, then in next step i did NOT select the Company Name HP or loaded driver but rather chose HAVE DISK, then Browsed to the MyDocs folder where the drivers are and selected...next step I told it to replace driver instead of use existing, and finished out. For the HP2840 I did this twice...once for Color driver, once for B&W.
All worked fine...no more errors...or every 30 second HPBPRO or DCOM errors. No issues on security, etc. to worry about also since I'm not hacking the registry or disabling some permission !
Anyway, the above is very...very easy and the install is very quick....maybe 5 minutes tops. The uninstalls and searches do take a little longer but it is well worth the 30 minutes per machine I invested. |
|
|
ken.absolute
|
|
Oct 7, 2009 22:12:28 GMT
Unassigned
|
|
This thread... is not dead
At the commandline:
cscript %windir%\system32\prndrvr.vbs -l | findstr /I /c:"HPBPRO.EXE" /c:"HPBOID.EXE"
will list all the drivers who use those devils.
This lists ALL printer drivers. Those associated with HPBPRO and HPBOID will have their their respective path locations indented on the line below, so they shouldn't be difficult to spot. Just increase your command windows screen buffer size.
If your on terminal server, you may be able to just update c:\windows\inf\ntprintsubs.inf and be done with it, but unfortunately, default drivers don't handle much in the way of advanced activities, like double sided printing and duplexing - so I had to say NO to "HP Laser Jet 4+" on everything
Unfortunately, I have 28 drivers that use HPBPRO.EXE and it and HPBOID.EXE and share the same darn executable's. You'd think I had a pretty bad couple of years, but I just have a script running in the background that does this every hour:
:START
pskill -accepteula HPBPRO.EXE
pskill -accepteula HPBOID.EXE
:: sleep for one hour
ping 127.0.0.1 -n 3600 > nul
goto START
pskill is a tool available from Microsoft. I was having troubles with the native kill command (it didn't seem to want to kill anything running as the user 'System')
Anyway, this comment is a bit premature as I've not read all the threads here yet (100+) so maybe their is a better solution. |
|
|
Riciard1
|
|
Oct 29, 2009 14:54:35 GMT
Unassigned
|
|
Helo, I work in an Hospital in Italy. We have many Deskjet 6940. I downloded latest drives and installed it, but problem with HPBPRO.EXE and EHBOID.EXE reamain. For earch print 4 process are created and when print finish just 2 are stopped.
I revolved this Item stopping all processes HPBPRO.EXE and EHBOID.EXE and deleting them from the PC. Now printing works properly (we print diagnostic report from pdf file or word) and processes are not created anymore.
OS in my clients : Win XP SP3ù
If someone findout other solution more clean please let me know.
regards
richard |
|
|
MickfromMunich
|
|
Dec 11, 2009 16:28:00 GMT
Unassigned
|
|
Hello,
killing the 2 exe-Tasks und deleting all Printers and Printerdrivers worked.
There was a DJ930c installed, I don't know why an wherefrom, but now there are now tasks anymore. It seems, the Deskjet-Driver was the problem.
Greetings from Germany. |
|
Printable version
;)