|
domls -> RE: Just need to make a new site... (4/17/2007 12:56:52)
|
I have had some success (finally) in setting up the server and the new web site. Here's what I've learned so far (when this is all done, I will post a complete "How To" so that others can benefit from my struggles): A) Whatever you do, DON'T install the FrontPage extensions on a Windows Server 2003 x64 Standard Edition operating system. It led to 3 days of trouble-shooting, knowledge base article reading, and trying to fix broken issues. Just FYI, the Server is running on an AMD64 processor. B) Once I uninstalled the FPSE's, I was able to get the web site that I had created in IIS to work properly (right-click browse or using IE). C) Now, if I right-click Properties on the web site in IIS, I get the ASP.NET tab. I then clicked on the Edit Configuration button in ASP.NET, and selected Forms from the Authentication Mode dropdown. Of course the Login URL for the login page that I was trying to create was simply Login.aspx. I clicked Apply, then OK. D) I then found a very nice walkthrough for creating a very simple login at http://authors.aspalliance.com/aspxtreme/webapps/simplecookieauthentication.aspx E) I edited the web.config file in the root of my web site, following the sample at the walkthrough. I then created the Login.aspx and Default.aspx files as described, using Notepad in the root of the web site. I also discovered that, since I don't have VS 2005 on the server itself, obviously I can go ahead and create any ASP.NET application locally and then transfer the files (duh) to the server as needed. This will allow me to create a much more sophisticated login and other app's that I need. The walkthrough has laid a nice foundation for understanding what is needed, where it goes, and what it's doing. With that aside, however, there is still one looming problem that I just can't get past. It would seem to be a universal issue that anyone using EW would have. Simply put, when I try to publish my web site using Remote Web Site-->Publish, I get the error shown in the attached screen captures. First, it tells me that FPSE's or SharePoint services are not installed. This, I believe, is not the real issue, however (as stated, you do not want to install FPSE's on this server as it will lead to very bad things, and second, the SharePoint services are installed and allowed). The real issue lies in the details screen. (BTW, I'm using WebDAV in EW as my connection method.) The details show error 403.3: Write access is denied. Obviously, this would be the case, since Guests only have Read permissions. So, here's the BIG QUESTION! How do you get EW to ask for a login so that the permissions, when properly logged in, can be changed to allow write permission. With FrontPage (which I use for my own company's web site that is hosted elsewhere), when it fires up my www, it stops and asks for a login username & password. Then, I have full access to my web site. I can't seem to find anywhere in EW to set this up, and even though I've now got this very simple login procedure (that does fire up properly for anyone accessing the web site), EW never shows this login etc... So, does anyone know how to setup EW so that it can actually write to the web site? Thanks! domls
|
|
|
|