• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6493
  • Last Modified:

64 Bit HP BiDi Channel Components Installer error code 2753

I'm getting this error on my four Windows 2008 R2 Std terminal servers.  The solution that was posted on the back last year referrs to two online resources that are no longer available.

  • 3
  • 2
2 Solutions
Spike99On-Site IT TechnicianCommented:
I have links to a couple of different pages for the solution, but my links no longer work, either.

We had the same problem.  We never did figure out which HP driver was causing the problem because we have dozens (if not hundreds) installed on our terminal servers.

For us, this issue was not only causing the errors in the event log, but it was also causing the spooler to hog the CPU & then crash on a regular basis. Also, MSIEXEC.exe was running all the time on the servers even when no administrator was installing anything.

But, I remember how we fixed it.   Basically, you just have to create a blank, 0 byte size file & use that to replace the bad MSI file that's causing the problem.

To do that:
1.  start up Notepad
2.  save a blank TXT file.
3.  Then, rename the file to match the file you want to replace (mine was HPZBDI32.msi)
4. Then, go to the path of the original file
5.  Rename the original file by changing the file extension to .OLD.
6.  Then, copy the blank file you created to that path

The file I replaced with 0 byte size file is:

Although, I have never addresssed this issue on a 64 bit system, I think the file in question for you would probably be:

A year or two after that fix, we started seeing similar errors on another HP components installer and the spooler began crashing on regular basis again.  So, this was the second file I did replaced with a 0 byte sized file:

For a 64 bit system, the file is probably:

I hope this helps.

nicklucasAuthor Commented:
Thanks!  This does seem to clear the error, but according to the event logs (informational messages), it still sets off a process to run this now blank file about every 5-10 minutes.  I'm sure it's better than what it was before, but it would be nice to be able to stop this thing from even trying to fire off the installer.

Any ideas?
Spike99On-Site IT TechnicianCommented:
Not sure about that.  I think our servers are still showing that notification in the logs too but we weren't that concerned with that.  We were more concerned about the problem those processes were causing:  MSIEXEC.exe would run all the time & the spooler would crash on a regular basis.

One other thing you might want to check is to make sure the following services are disabled & stopped. Although these processes work fine on a Windows client PC, they can also cause issues with print spooler on a multi-user terminal server:

  HP Port Resolver
  HP Status Server
  Net Driver HPZ12
  Pml Driver HPZ12

Has this issue been causing your print spooler to crash? did you see the installer service running all the time?

nicklucasAuthor Commented:
The HP Port Resolver and HP Status Server weren't even listed in services, but the Net Driver and PML driver were, so I stopped and disabled them.

I had the spooler crash once on one of the servers, and when I checked the event logs, is when I found the original error.  And yes, the installer was running every 5-10 minutes and causing the error.  It looks like it's still trying to run it, but at least it's not really doing anything else and the errors have gone away.

Thanks for the help!
Spike99On-Site IT TechnicianCommented:
No problem, I'm always glad to help! Thanks for the points!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now