Cannot re-detect HP OfficeJet L7500 Scanner

A client could not start her Ethernet based Officejet Pro all in one scanner.  And here is what worked for me.

First uninstall all HP all in one software from the PC.

To completely uninstall the software, run the uninstaller at level three using these steps:

1. Turn the All-in-One off and disconnect any USB/Ethernet cable from All-in-One to computer.

2. Insert the all-in-one CD-ROM into the computer. Cancel any installation windows that appear.

3. Click Start on the taskbar and then click Run.

4. In the command box type the following command and press Enter key:


(X: is the CD-ROM drive letter of that the all-in-one CD-ROM is in)

1. Please click on the link directly it directly takes us to the webpage titled ‘HP Full Feature Software and Drivers’

2. Scroll down the webpage and please click on the download only option . When it prompts for save, save it on the desktop of the computer.

3. Please wait till the saving process it takes nearly 20 minutes depending on the computer speed. Save it on the desktop only so that it is easier to find later.

4.After completion of the download, double click on the file which we have downloaded and then we will have 3 options: Install, uninstall and add a device. on install. Please follow the onscreen instructions and it will take nearly 15 – 20 minutes to complete installation.

8.Click on finish when it prompts to complete the installation.

9.Restart the computer and then open the HP solution center or HP director applicable.

That worked for me.

Windows SBS 2008 DNS Name Resolution causes disconnects

A client was on a SBS 2008 network and strangely enough Outlook was taking a long time to connect to the Exchange server, one the affected clients we discovered that pinging the server would reply with the RRAS adapter address.  We diagnosed the problem without official Microsoft help but later discovered this article that described the issue.

A computer that is running Microsoft Windows 2000 Server or Microsoft Windows Server 2003 may exhibit connectivity issues if the server is configured in the following manner:

  • The Routing and Remote Access service is configured to permit incoming connections.
  • The Domain Name System (DNS) or Windows Internet Name Server (WINS) service is installed and configured on the server that is running Routing and Remote Access. Read the rest of this entry »

Windows SBS 2008 clients recieving 1030 and 1058 erros in application log

We were working on a Windows SBS server 2008 network.  The client was having frequent disconnects and network interruptions.  On desktop client computers we noted errors 1030 and 1058 (See Below) were logged in the application log.  

Error 1030 source userenv:

Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

Error 1058 source userenv:

Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=servername, DC=local. The file must be present at the location <\\servername.local\sysvol\servername.local\Polici es\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted. Read the rest of this entry »

Internet explorer creates multiple windows

A client would click on a mailto tag and then Internet Explorer would spawn windows (displaying with the error Action Cancelled ) until the PC would run out of memory for the process.  After doing some research I found an article that discuses the issue and how to solve it.

A brief synopsis of the article is seen below.

When you click on a mailto: URL in Internet Explorer, multiple instances of Internet Explorer opens (more than 60 windows) with the error Action Cancelled and the mail client is not invoked. You may also see the following error:

“Could not perform this operation because the default mail client is not properly installed”

Root cause

1.     Mailto handler is not correctly set.

2.     Missing URL Protocol registry value.

3.     Incorrect registry permissions for the mailto key. Read the rest of this entry »