| Author |
 Topic Search  Topic Options
|
WebWiz-Bruce 
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
 Post Options
 Thanks(0)
 Quote  Reply
 Posted: 28 November 2011 at 1:26pm |
Need the detailed ASP error message, not the browsers XML parsing error.
Without the ASP error message can't help you.
|
|
|
 |
dotcom
Newbie
Joined: 11 August 2011
Status: Offline
Points: 28
|
Post Options
Thanks(0)
Quote Reply
Posted: 28 November 2011 at 4:37pm |
|
That is the error that the browser displays when I follow the steps outlined in the two articles you passed to me. If there are other steps that I need to take to get diagnostic information, please can you tell me what they are.
Regards,
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 28 November 2011 at 5:12pm |
The server does appear from your last error that it may be returning the detailed error message, but this would be in HTML format not XML format.
The page that you are calling has a XML MIME type so the browser is expecting XML which is a strict coding standard, when the browser attempts to render the XML and gets the detailed server error which is in HTML the browsers XML parser crashes giving the XML parser error you gave in your previous post.
What you need to do is view the source code of the page so that you can view the HTML that it being sent by the detailed error message from the server.
You should then be able to pull from the source code the parts of teh detailed error message that are needed, which are the reason for the error (eg. VBScript Error xxxx on line 1234).
|
|
|
|
dotcom
Newbie
Joined: 11 August 2011
Status: Offline
Points: 28
|
Post Options
Thanks(0)
Quote Reply
Posted: 28 November 2011 at 5:58pm |
Unfortunately, in source view, you get the same information: <?xml version="1.0" encoding="iso-8859-1" ?>An error occurred on the server when processing the URL. Please contact the system administrator. <p/> If you are the system administrator please click <a href=" view-source:http://go.microsoft.com/fw/?ID=82731 - http://go.microsoft.com/fwlink/?LinkID=82731">here</a> to find out more about this error.
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 29 November 2011 at 8:58am |
|
According to the view source you still do not have detailed error messages enabled on the server.
|
|
|
|
dotcom
Newbie
Joined: 11 August 2011
Status: Offline
Points: 28
|
Post Options
Thanks(0)
Quote Reply
Posted: 29 November 2011 at 10:00am |
Ok, configuration issue solved by making the root directory of the forum an IIS application. I now get the following information from the forum: error '800a000d'
Type mismatch: 'Server.HTMLEncode'
/foro/es/HttpAPI.asp, líne 327
Does that help?
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 29 November 2011 at 11:07am |
That does help allot as now know the line the error is on and the part of the code causing the error.
The part of the code in question has nothing to do with the admin password, but relates to the showing of the Real Name field.
This part of the API has not changed since version 1 so very strange you now suddenly get the error. The part in questing Server.HTMLEncode(rsCommon("Real_name")) uses the ASP's HTMLEncode method to HTML encode the Real Name thus preventing formatting issues or malicious code.
A possible reason for this error is somehow the Real_Name field in tblAuthor has 'null' values for some members. This should not be the case and these 'null' values need to be removed from your database.
|
|
|
|
dotcom
Newbie
Joined: 11 August 2011
Status: Offline
Points: 28
|
Post Options
Thanks(0)
Quote Reply
Posted: 29 November 2011 at 11:52am |
|
Thanks for your reply Bruce. The error that I sent was from using GetMemberByName after I changed the admin password to one that contained no numbers.
I checked the user account in question and indeed, it had no value for the Real Name field. When I added one and retested, no error occurred.
However, since it is not mandatory for a user to give a Real Name in their profile, there will always be cases where that field is null, and the error will occur. It is also possible to create a user via the API without a real name. I would therefore expect the API to be tolerant of this condition, and handle it gracefully.
Furthermore, I am integrating a website with an existing forum which has many user accounts with no real name and I need to be able to use the API against it. Other users of your forum will be in the same position.
Can you release a patch to solve this problem?
|
|
