Publishing

Re: Windows 2003 FPSE 2003 and FrontPage problems...

dafyre — Fri, 12 Oct 2007 13:10:17 GMT

Wow! What a learning experience! We're running 2003 Server Standard (no R2). If we use the R2 CDs to install the server, then FPSE 2002 does *not* work at all! Has anybody else experienced this problem? It makes me wonder what else is b0rked in R2!

So if you're having problems with FPSE 2002, I highly recommend that you confirm whether or not your are running an R2 release of 2003 Server. If you are, then you need to change to just regular 2003. Legally you can do this without having to buy a new license from MS.

We've got our server set up & installed. It's doing updates now (wheeeeeee....). But I've already tested FPSE and it works fine so far...

Let me know if you want me to keep you posted some more!

Thanks!

~Brant

Re: Windows 2003 FPSE 2003 and FrontPage problems...

dafyre — Thu, 11 Oct 2007 20:08:29 GMT

Not sure anymore, lol. We had some other odd issues with the box and decided to reformat (which was fine, because we were setting that server up initially anyhow. I appreciate your input.

I remembered somewhere reading on the OWS_####### and stuff, so I wasn't sure if that was it or not, lol. The error message I got was folder not available.

We just reformatted the box, and I only have IIS & FPSE installed via the configure your server. Anonymous Settings are for IUSR_MYSERVER, and I haven't changed the password. I have Basic Authentication only. I still get the Site Cannot be found error.

I used the Windows Server 2003 R2 Standard CD. I'm gonna format again & try the 2003 Standard CD that was initially released.... This is absolutely ridiculous!

Thanks for the help & Patience! I'll let you know how the install goes.

Re: Windows 2003 FPSE 2003 and FrontPage problems...

robmcm — Thu, 11 Oct 2007 18:37:19 GMT

The IIS site ID of 2137111081 and the FrontPage permissions group of OWS_1951370092_admin use different algorithms for their respective IDs, so there's no problems there. (But it's pretty cool that you picked up on that. ;-] )

It should not matter if the name does not exist in DNS as long as you have the hosts file entry as you specified, (I do that all the time on my development box), but that does illustrate an interesting point - what happens if you simply change the binding on the radio.myhost.com site to 127.0.0.1 with no host header name? Can you open the site using FP2003?

Also, is the following error what you actually receive?

The folder 'http://radio.myhost.com' isn't accessible. The folder may be located on an unavailable volume or protected with a password. For details see C:\TEMP\wecerr.txt.

If so, what does the "C:\TEMP\wecerr.txt" say? (By the way, that's probably in your system or user %temp% folder instead of the physical C:\TEMP path.)

Re: Windows 2003 FPSE 2003 and FrontPage problems...

dafyre — Wed, 10 Oct 2007 19:33:09 GMT

Hey Rob:

Thanks for your response!

I get my hello world page if I visit radio.myhost.com. I did managed to check that! ;-) Anyhow, I've gone through the suggesions that you have. I recreated the site from scratch, and Set it only for Read & Scripts Only. IIS creates the website with an ID of 2137111081, and the group as OWS_1951370092_admin is that a problem?

Before I deleted the site, I did as you suggested the /_vti_bin/shtml.dll & got the right response, but I had to Authenticate first. Could that be a problem?

At any rate, I'm back to that point again. The shtml.dll tells me that it can't run on this page "". However, the most notable difference is that it's not asking me about WebDav or FPSE anymore. It just tells me that the folder http://radio.myhost.com isn't accessible. The folder may be password protected, etc, etc.

Even if I browse to the site and then do Edit with FrontPage.

[I'm using FP2003 here, btw].

I have manually set the IUSR_MYSERVER password myself. The machine is on a domain, but is not a domain controller. It is using the Local IUSR_MYSERVER account.

Any other ideas?

I also have the server listening for a header that does *not* exist in DNS. It is only on the hosts file on my development box and the web server that is running it.

Thanks!

~Brant

Re: Windows 2003 FPSE 2003 and FrontPage problems...

robmcm — Wed, 10 Oct 2007 19:01:44 GMT

Hi Brant,

Since FPSE is installed on your radio.myhost.com web sitem, when you click File -- Open Web in FrontPage 2003 you should not see the Web Site setup screen, which indicates that something is wrong with the server's ability to advertise that FPSE is enabled for the site.

Here are some things to check:

First things first, you should not enable Execute for the site unless absolutely necessary, so I would suggest disabling Execute from the root of the site, but do not tell it to override the settings for the _vti_bin folder.
What happens when you browse to radio.myhost.com, do you see that site or your www.myhost.com site? This would indicate a problem with the name resolution. (I'm pretty certain that this isn't the problen, but it never hurts to make sure. :-] )
When you open My Network Places on your desktop, do you see an entry for radio.myhost.com? If so, go ahead and delete it. This is a "web folder" that will be recreated when needed. The trouble is, sometimes web folders memorize that connection information to a site, e.g. FPSE or WebDAV, and that sometimes makes it difficult to reconnect later.
What happens when you try and browse to radio.myhost.com/_vti_bin/shtml.dll? You should see an error that says 'Cannot run the FrontPage Server Extensions on this page: ""', which inidicates that FPSE is actually working.

Windows 2003 FPSE 2003 and FrontPage problems...

dafyre — Wed, 10 Oct 2007 15:26:07 GMT

Hi All:

I'm using Windows Server 2003 & IIS 6.0, along with FPSE 2002. I use FrontPage 2003 for editing the web sites. My Primary site (www.myhost.com) pointed to C:\inetpub\www.myhost.com. That site doesn't even have FPSE installed on it at all.

I am adding a new site called radio.myhost.com located in C:\inetpub\radio.myhost.com, and it uses the host header radio.myhost.com. This site, I need to install & get FPSE working on. I have created the folder C:\inetpub\radio.myhost.com, and left it empty. I am logged in as MYDOMAIN\Administrator.

I go under the IIS Administration tool, and right click on Websites, and do a new website with Read, Run, and Execute permissions. Then, I right click on the site and Configure Server Extensions 2002 with the owner as MYDOMAIN\Administrator. I leave the Site set up to run as a "Default Application" in the Default Application Pool. I then go back and Check the Server Health, telling it to repair everything. This happens instantly (it's an empty directory anyhow). Then I set the Directory Security to *ALLOW* Anonymous Users, and use BASIC authentication.I set both the Realm and the Default Domain to mydomain.com.

At this point, I should be able to log in as MYDOMAIN\Administrator to the website radio.myhost.com, right?

When I Open FrontPage 2003 and open Site http://radio.myhost.com I get the Web Site setup screen, where I choose FPSE or SharePoint Services. I don't choose Include Subsites or encrypted connection required. I click next, and I get a popup:

"You are unable to import a Website from http://radio.myhost.com. Verify the location and then try again"

What am I doing wrong?

Thanks!

~Brant