Hi
I have an .asp site that I am unable to preview in Dreamweaver MX. I used to run the site on an old machine using PWS and everything worked fine. However, I have moved the site to a machine using XP Pro with IIS and can not get it to preview in a browser nor give me a live data view. All the files are present on the testing server, which I can access, I can also connect to the actual server with no problems. However, when I try to preview the site I get a “HTTP 500.100 - Internal Server Error - ASP error Internet Information Services” error message.

I have disabled Anonymous authentication for the Localstart.asp file and verified that the user who is logged on is a member of the local Administrators group. But still I am unable to preview the site!
As always any help would be much appreciated.

Cheers
Burnsie

Originally Posted by Burnsie

I have disabled Anonymous authentication for the Localstart.asp file and verified that the user who is logged on is a member of the local Administrators group. But still I am unable to preview the site!
As always any help would be much appreciated.

It shouldn't matter who's logged into the computer - you can configure what user IIS runs under, with network service being the default. ( Maybe that started with v 6? )

Usually an error 500 is a programming error, I think. It's been a while since I've done clasic asp, but I think that usually indicates a null value from the database that wasn't planned for, or something to that extent.

Can you see other asps in the same folder?

Hi
The site worked perfectly with pws. All I have done is put the entire site onto a new machine. I can see all the files in the tesing server and access them. But not being able to preview them makes working on the site v. hard work. I have not altered a single line of code since moving the site!

Cheers
Burnsie

Originally Posted by Burnsie

The site worked perfectly with pws. All I have done is put the entire site onto a new machine. I can see all the files in the tesing server and access them. But not being able to preview them makes working on the site v. hard work. I have not altered a single line of code since moving the site!

So that means it's not a code problem. Some kind of difference between the way the two machines are configured...

Can you give a few more details? What version of IIS are you using, or if you're not sure, what operating system? Ideally these are the same on both computers, but I wouldn't be surprised if it's Windows Server 2003 ( IIS 6 ) and Windows XP Pro ( IIS 5.2 ). That's not a problem at all - actually that's how things are set up at my job.

Are you using ASP "Classic" or ASP.NET? If it's the latter, can you make sure both machines are using the same version of the .NET Framework? You'd check that in the IIS mgt application, under the site's properties. It's possible ( but not likely ) your code is using a feature of .NET 2 and the server is using 1.1 to process the code.

You might want to check the NTFS permissions on the files that make the site up. It's also possible the web server doesn't have access to them - it's probably running under NETWORK SERVICE.

Otherwise, I need more details to give you better / more specific advice.

Hi
Yes I am running asp NOT .asp. I can view pages on the testing server that have a .htm extension but not any asp files so there appears to be a problem with permissions for asp type pages. I have uninstalled my virus checker and firewall as I read that these may be responsible but this has made no difference!
So i guess i need a way to allow asp pages to be prossesed by the tesing server!

Cheers
Burnsie

Open the IIS MMC, Right Click Default Site and pick Properties

Open the Home Directory tab, in Application Setting check there is an application name, if not click the Create button and set Execute Permissions to "Scripts Only". Apply & Ok the dialog and try to open http://localhost

also in your browser (assuming IE) use:

Tools -> Internet Options -> Advanced tab -> Browsing section -> Uncheck "Show friendly HTTP error messages"

You can also try connecting using http://IPAddress or http://MachienName