0x80070057 (NS_ERROR_ILLEGAL_VALUE) error in BrowserBot

[MartinRaymond]

I am getting this error, running Selenium 2.5.0. Here is the complete error: 

[info] Executing: |verifyElementNotPresent | //font[@color='red'] | | [error] Unexpected Exception: [Exception... "Illegal value" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js :: BrowserBot.prototype.locateElementByXPath :: line 1670" data: no]. toString -> function toString() { [native code] }, message -> , result -> 2147942487, name -> NS_ERROR_ILLEGAL_VALUE, filename -> chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js, lineNumber -> 1670, columnNumber -> 0, inner -> null, data -> null, location -> JS frame :: chrome://selenium-ide/content/selenium-core/scripts/selenium-browserbot.js :: BrowserBot.prototype.locateElementByXPath :: line 1670 2) User_Access

This Selenium script was running OK a few months ago, so I'm wondering whether it is a known problem with either the current release of Firefox or the current release of Selenium.

If anyone can help with this I would be very grateful.

Thanks, Martin

[Akash Srivastava]

i think the xpath is not correct that's y it is giving this error...

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/03877bfd-81a1-432f-a9c2-d54e1500f8bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Akash Srivastava

[MartinRaymond]

Hi Akash,

Thanks for responding, and many apologies for the long delay in acknowledging your reply.

The line in our Selenium test script is: verifyElementNotPresent  //font[@color='red']

So all the rest is just internal Selenium code.

The good news is that I just ran a couple scripts which include this line, and they both ran through OK.  So, while it would be nice to be able to account for the error, at least it is no longer preventing our Selenium test runs from completing.

Thanks again,

Martin