Closed Bug 397164 Opened 17 years ago Closed 17 years ago

Error on opening any URL

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 396815

People

(Reporter: hsiegelman, Unassigned)

References

(
URL
)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7

On clicking on any URL I receive the following error: "Windows cannot find '(null)'.  Make sure you typed the name correctly, and then try again.  To search for a file, click the Start button, and then click Search." With the OK button.  A few seconds later, the URL page opens in Foxfire. This started only after I updated to 2.0.0.7 and never occurred before.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
This just started this morning (9/22/07) after updating AdBlock Plus to 0.7.5.2.  I suspect that it is the culprit, but I hate to disable it and get all of those annoying ads.
I have exactly the same problem with my accessing of URLs.  However, if my link is only local (to a the router on my network, say) Firefox acts normal.  I only get the error message (Same as Harvey's) when accessing something on the internet.  The oddity started sometime yesterday (21 Sept). I then reinstalled Firefox and get the same result. This is an HP desktop with XP Pro SP2, up to date.  My HP laptop has the same software (except XP Media Version) and does not exhibit the peculiarity.

I can live with it, but would like to eliminate the error message if I can.  
Thank you Ria Klaassen.  Your suggestion and the link fixed my problem.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Resolution: FIXED → DUPLICATE
I remembered that I had installed Sitehound form Firetrust last week.

I uninstalled Sitehound and my Firefox operations returned to normal.
It came back again.  I guess Sitehound was not the culprit.  Now I'll try Ria's solution. I'll let you know if it works.
Ria's solution worked. Yea!
You need to log in before you can comment on or make changes to this bug.