By pchan - 12/10/2014
Howdy,
We are trying to run a test on a remote server. We have set up the test and when we call it up we see the start page. When we click on start we get an error message that says: html.xmlns="http://www.w3.org/1999/xhtml" lang="en" - element name contains invalid characters. This appears twice and the third message says missing closing tag.
Where does the error arise and how do we fix the problem?
|
By Dave - 12/10/2014
This is a generic xhtml error message. Nothing of particular value about the cause can be gleaned from it alone. You will have to provide more details regarding your concrete setup as well as links to the start page on the remote server.
"element name contains invalid characters" may indicate just that -- the use of invalid characters somewhere in any of your XML / XHTML files or the script you are trying to run. If it is the script, validating it using Inquisit Lab should allow you to identify the offending element and correct the error.
The part about the "missing closing tag" indicates that either (1) any of your XML or XHTML files are broken or (2) the script you are trying to run is mistakenly treated as XML (and may be faulty in addition). Here, too, if the issue is in the Inquisit script, validating it in Inquisit Lab should let you pinpoint the missing closing tag(s).
All of this guesswork, though, without any further details.
|
By pchan - 12/10/2014
Howdy,
The script is now working. We tested another script and it worked fine. We were using the exact same files but in a different order. Then we reloaded the original script and it now works properly. It should be noted that all the files and scripts were tested on our internal server before we tried to load them on the live site. That's why we couldn't figure out what the problem was. In fact, the improper code does not appear in any of our files. The only place the code appears is in the file we downloaded from Millisecond to put on our server, however, the code in that file appeared to be correct.
|
By Dave - 12/10/2014
Hmm, weird. The only thing I could think of would be a corrupted up- or download. At any rate, glad to hear it's working now & thanks for the update.
|
|