Dreamweaver problem

I create a simple web site with one aspx page in Dreamweaver 8 on Windows XP Pro SP2. I have the web page in My Documents, and I set the remote server and test server as C:\Inetpub\wwwroot\Test1. I then hit F12 to run the website and I get the following error message:

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.


A name was started with an invalid character. Error processing resource 'file:///C:/Documents and Settings/Fabricio/Local S...

<%@ Page Language="VB" ContentType="text/html" ResponseEncoding="iso-8859-1" %>

Any ideas???
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Saqib KhanSenior DeveloperCommented:
you have Some sort of XML Document?
if yes then the problem might be with the ampersands in the XML file. Replace ampersands with something and debug the File.
For starters, don't set the remote and test servers to the same gig; there's many reasons why they are separate settings. While developing locally, leave remote server settings blank and ensure the test server is set to access: network/LAN. Before you test a webpage by hitting f12, ensure you have saved and syncronised the file you're about to test and allow all dependant files to be sync'd as well.

Check IIS Admin that the test server website folder is set to be a new website and that it is using the ASP.NET application pool.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I've had this problem with Firefox when developing ASP.NET pages.  I looked around the internet for ages but there wasn't a recognised solution or diagnosis.  For me, the problem was caused by an error in my code further down the page.  For some reason, IIS was not 'sending' the page correctly to the browser because it hadn't finished processing when the error occured.  Try the page in an alternative browser and see if you get anywhere.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Adobe Dreamweaver

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.