CODEWITHSUNDEEP
xmlparsingcoldfusioniis-6
eggwater
eggwater

Reputation: 162

Error on xmlParse - ColdFusion IIS 6

I've tried to find an answer to this for a couple of days but struggling now.

I have a coldfusion MX 6.1 application set up running in windows 2003 iis6. A few days ago trying to fix another issue I somehow managed to remove permissions mappings for various directories on the application, which after much sweat, I have given up on trying to restore.

My solution has been to duplicate the application and reconfigure the permissions under iis.

This has worked but when I now try to access the application it will no longer parse XML (RSS feeds).

The application has not been changed so I think this is a config issue in iis6.

The error is: Next character must be ">" terminating declaration "%HTML.Version".

But I think this is a red herring. I'm sure I had this issue when I originally deployed the application but I cannot remember what the solution is. Is it a MIME types issue?

I should also add that when I try to parse the files that are in the original site from the new site (i.e. I use port 8080 for the new site and port 80 for the old site) this also works. As soon as I switch old site off and change port on the new site to port 80 the xmlParse throws the error.

Can anyone help or point me in the right direct?

Upvotes: 0

Views: 258

Answers (1)

K_Cruz
K_Cruz

Reputation: 729

To troubleshoot, you'll need to be able to manually run the function that parses your XML, and have a known working file that's erroring when you use it. For ease, I'd make your XML file as simple as possible so as to not have to drill down in multiple parts of your file trying to find where your error is.

Start by removing all of your data in your XML file, leaving only your DTD and your first level data tag, which should be empty. If that fails to run successfully, your problem is likely in your configuration settings; otherwise it's in your XML.

If it's in your XML, then start adding data back in, one level at a time, with the deepest drill-down remaining empty and run it again until you encounter your error; that would be the part of the file causing the problem. If you can't see what the error is in your known-working XML file, than present it here and someone should be able to figure it out.

Upvotes: 1

Related Questions