HP M1522nf Multifunction, and the 49 error.

Today we encountered a HP M1522nf Multifunction printer, scanner, copier which was experiencing a 49 error during its power up.

The unit would start up fine, finish its initialization procedure, and about 5 seconds later would issue a 49 error, power off and on, and then reset itself and start the whole thing over again.

I was a bit perplexed on this issue. When referencing the service manual for the printer, it only referred to powering the unit off for 30 seconds, and then powering it back on to see if that would clear the error.

Of course it didn't.

For the follow up, it suggested calling HP service. Usually the service manuals will give you an indication for what parts to swap in an attempt to diagnose the unit. Thinking the formatter was the most likely culprit, I called HP, and they did verify that the problem was most likely the formatter.

However, while on the phone with a HP technician, I noticed that the top bezel that covers the buttons (the bezels are replaceable for the different languages) was not sitting correctly in place. I removed and re-seated the bezel, and the unit is working fine.

It seems the bezel was pushing some of the buttons on the front panel during power up, causing the unit to perform a reset every time it powered up, and then it continued to attempt to reset the unit during its POST procedures.

Hope this can help someone out there. Not the usual repair, but it does make for happy customers, when you can repair a unit in a hour and return it to the customer!

Thanks for reading, and have a great day!

Unable to install SQL Service Pack with various versions of ACT installed.

I need to give credit were credit is due. We had at the store in for service a unit that would give very strange error messages when it would go to install a service pack for SQL server from windows update.

Most customers don’t know, and don’t want to know what SQL server is, or does, but for the rest of us, these types of problems can cause extreme hair loss!

The root of this problem is basically this: ACT locks up the SQL database engine to make sure any important information that you put into the system, can’t be accessed against your wishes. In their efforts to lock down the system to ensure your data’s safety, they also managed to lock out Microsoft’s official patches. They took out the method of installing these patches, which then causes the patch to fail. Not a very easy problem to figure out, and not so simple of a solution. I will say though, without the following link, I wouldn’t have been able to solve this problem. ACT doesn’t acknowledge the problem on their online knowledge base, and the only information I found was on a blog.

Thank heavens for blogs!!

Link: http://www.sqlserverfaq.net/2008/07/15/unable-to-install-security-patch-948109-to-sql-server-2005-express-edition-which-is-installed-along-with-act7-software/

Much kudos’ to SQLServerFAQ.net, and the information that they provided.

Side note: Some of the instructions are a little difficult to follow, and once during my attempts it gave me a strange response. If this happens to you, I suggest you start over again from the beginning. That worked for me!