I followed the instructions, installed on Win2003 Server (w all updates), set up in IIS as described in help, but get
File Not Found
...when hitting the virtual directory. When I add "default.htm" with some text, I do get that file. So it seems maybe it's a .Net config thing, or a setting, but I am running out of time to track this down. I love CS but this has been a pain...have tried to find this specific issue but I guess nobody's as lowly a newbie as I am :(
can anyone help? I really appreciate it!
Did you setup the Virtual Directory as an Application?
WGB Enterprises - Freelance Community Server and other DevelopmentopenSourceC.org
Yes. Gave permissions to the entire directory just in case. What's weird is that a normal html file works but default.aspx says file not found...
It sounds like you changed something on the Documents tab. Is the Enable default content page checked and is default.aspx one of the items in the list box?
Yes, it is. I haven't changed anything. I'm considering commenting out the entire page, then going line by line to debug. If default.htm can be found, there'snothing different about default.aspx...using .Net 2.0 btw
I am having the exact same problem. I went through the entire installation process, didn't change anything. And even from IIS Manager, trying to "Browse" the default.aspx page, I get a "Page not found" error page.
The only other thing that I can think of is did either of you run the IIS Lockdown Tool? If so, check the Application Configuration and make sure that the .aspx extension is still registered under Application extensions. If it isn't, you will need to add it back in. If the entry is there and default.aspx is registered on the documents tab, then I have no idea as to why you your are getting a Page not found error. In your web.config, try setting the customErrors mode attribute to Off (case sensative) and then post the error page here.
Bill,
I am having the same problem. Everything looks good. I have it set up as a website and it works fine, I need it as a virtual directory under a main site and it won't work. 404 error.
Clean install on a clean server....Any more thoughts?
James
James,
Can you post the web.config on the root website? I am assuming that you trying to run CS in a folder like /cs/ from the root of the site, correct?
Take it easy,Bill
With mine it turned out to be a problem with the "wwwStatus= xxxxx" parameter. For some reason my test server which is MS virtual server did not like the thing set to anything other than "Ignore".
I run my own bank of servers, I control my own DNS, and everything is rock solid as far as DNS, host hearders and the like. Some bug in Windows 2003 server 64x running MS virtual server 2005 with a plain jane Windows 2003 server 32 bit running IIS6 and CS....
I can re-create it, just can not explain it.
Hey James,
Actually, this is pretty easy to explain. You are either missing a DNS entry and/or a Host header value entry in IIS. You have the DNS record for <your-domain>, but do you have a record for www.<your-domain> that points to the same address? You need to have both records and they both need to point to the same address in order for CS to work properly. Also, you need to make sure that you have a Host header value entry in IIS for each DNS entry as well. A missing Host header value entry can cause a 404 error as IIS will be looking at the wrong site.
Take my word for it. All the DNS records are complete and correct. I think that there is something very subtle on the way Virtual server handles the DNS re-route between the virtual NIC and its configuration and the physical NIC in the Host. It may also be an issue with the host being x64.
All the host headers are also correct. I don't have the time to hunt it down so for now I just have the param set to Ignore. Interesting is the fact that with the exact same configuration on my production IIS server which is a stand alone Win 2003 Server it works fine. Same sub-net, same DNS server.
Because it works on the one and not the other without the change, I do think it is some odd duck thing. How many folks out there are running my set up ? Not very many I suspect.
If you're installing on Server 2003, this can be caused by failing to enable .NET Web Service Extensions - this is turned off by default in 2003, and if you are used to development boxes with XP or Vista you might not be aware of this. I wasn't, and it's been driving me nuts for about an hour.
Open up computer management, IIS Manager. Open "Web Service Extensions". Select the ASP.NET version that you're running and click the Allow button.
Presto, now I get a configuration error page. Which is fine - I can figure that one out :-)
tutorgarden1: If you're installing on Server 2003, this can be caused by failing to enable .NET Web Service Extensions - this is turned off by default in 2003, and if you are used to development boxes with XP or Vista you might not be aware of this. I wasn't, and it's been driving me nuts for about an hour. Open up computer management, IIS Manager. Open "Web Service Extensions". Select the ASP.NET version that you're running and click the Allow button. Presto, now I get a configuration error page. Which is fine - I can figure that one out :-)
Oops, that was me - forgot to log out of the company account
Jim
Thankyou for your note.
I am setting up a duplicate IIS 6 server (not community server) and some sites worked but the first 2.0 had exactly this problem:isapi not allowed or even listed. Discovered, from the other server I have, that the file required is
..\windows\microsoft.net\Framework\2.0.50727\aspnet_isapi.dll
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com