IIS Problems
|
Prev: Unable to receive some faxes
Next: w32time Event ID 29
From: Scott Shinnie on 4 Oct 2006 07:44 Jim, Thanks for your help made some good progress last night. Unfortunately I had no backups of the metadatabase.xml file, file must have been skipped as it was in use. Will configure shadow volume copy shortly and scheduled backups will be taken of IIS. I backed up my sharepoint site and performed a reinstall of the Intranet component as per KB829114. Restored company web and I am happy with Sharepoint. SSL and authentication types are wrong on many of the virtual directories below the default web site. I recreated the exchange ones using KB 280823 and the majority of my problems have been resolved. Can you advise if there is a way to confirm settings for default web site on SBS2003. I have downloaded IIS Diagnostic tool but need to investigate further tonight. Two issues: 1 RWW is now available via the web but when you select OWA instead of going to the mail it is being redirected to the OWA logon page and domain\username details are not accepted. Authentication must be wrong on Exchange or OWA virtual directory. 2, On my default site, IIS advises that Sharepoint is installed. Is this normal, there is an option to remove the frontpage 2002 extensions but this was a step too far - last night. Thanks for the help, I am back up and running and can continue to look at ways to make companyweb available via the web to external users. Thanks Scott "Scott Shinnie" wrote: > Jim, > > Unfortunately I don't have ISA. > > I had a MS article which described publishing a sharepoint site to external > users. I created a test site in order to not affect my current setup (failed > miserably there) it advised to create a new certificate (generated > internally) and apply this to the new site. Once applied it advised to > reimport the original certificate to the default web site whcih was exported > before the work began. This was done, I have tried to remove these > certificates completely but the wizard only allows to remove/replace on the > current site. > > Leaving the office in an hour or so and will try the advice you have given > me, I will let you know how I get on. Thanks for all your help, you have > given me some hope that all is not lost (yet!) > > "Jim Martin [MSFT]" wrote: > > > Scott, > > > > Changing the account settings for the app pools definitely can cause > > issues. As a reference the default app pool should be running under > > Network Service. > > > > Did you try backing up your current configuration and rerunning the CEICW? > > > > You said "My problems started as soon as I started trying to apply a new > > SSL > > certificate to a specific sharepoint site." Doed that mean you have more > > than one Sharepoint site? Did you apply a cert to the Companyweb site? > > Was it a public cert or one that was created internally? > > > > You don't have ISA by chance do you? That makes publishing Companyweb > > easier. > > > > Jim > > > >
From: Jim Martin [MSFT] on 5 Oct 2006 09:14 Hi Scott. The best way to verify the correct settings on the default website is to compare it to a box that was cleanly installed and preferably one on which the CEICW was run. I would be happy to verify some of the settings for you. I think you are correct in that some authentication settings must be wrong for OWA to behave that way. Here are settings on my test machine on the Directory Security tab of the properties of the Exchange virtual directory: - first edit button: - only 'Basic..." checked and default domain is just a backslash (\) - second edit button - granted access selected - view certificate button - since you do not have ISA the certificate name should be the self-signed one with the public name that was originally created by the CEICW (which I think you said you exported then imported) - third edit button - require ssl and require 128-bit checked - ignore client certificates selected Here are settings on my test machine on the Directory Security tab of the properties of the ExchWeb virtual directory: - first edit button: - only 'Enable anonymous..." checked - second edit button - granted access selected - view certificate button - since you do not have ISA the certificate name should be the self-signed one with the public name that was originally created by the CEICW (which I think you said you exported then imported) - third edit button - require ssl and require 128-bit checked - ignore client certificates selected You mentioned earlier that you wanted to delete extraneous certificates. You can do that by opening the Certificates MMC... - start, run, mmc - File, add/remove snap-in - add button - select Certificates and click Add - select "computer Account" and click next - "local computer" and click finish - close button - OK button - in the left-hand pane navigate down to: Certificates Personal Certificates (click on this) - you will see the certificates in the personal store on this computer - you can right-click and delete extraneous ones from here, but be careful which ones you delete (you can export them first) I would not choose to remove frontpage server extensions If you have an ASP.Net tab on your websites you might want to make sure they are running version 1.1 and not 2.0. I hope this helps. Jim
From: Scott Shinnie on 6 Oct 2006 07:30
Hi Jim, Thanks for your all your advice, glad to say the OWA problem was resolved when I changed my settings to match those of your test server. I also have my sharepoint site accessible via the web which was my original goal. As with everything I know far more about IIS, RWW and OWA as a result of the problem. If anyone else is reading this post - Reply to this post if you have a similar problem and I will try my best to help. THANKS SCOTT ;o) "Jim Martin [MSFT]" wrote: > Hi Scott. > > The best way to verify the correct settings on the default website is to > compare it to a box that was cleanly installed and preferably one on which > the CEICW was run. I would be happy to verify some of the settings for > you. I think you are correct in that some authentication settings must be > wrong for OWA to behave that way. > > Here are settings on my test machine on the Directory Security tab of the > properties of the Exchange virtual directory: > > - first edit button: > - only 'Basic..." checked and default domain is just a backslash > (\) > - second edit button > - granted access selected > - view certificate button > - since you do not have ISA the certificate name should be the > self-signed one with the public name that was originally created by the > CEICW (which I think you said you exported then imported) > - third edit button > - require ssl and require 128-bit checked > - ignore client certificates selected > > Here are settings on my test machine on the Directory Security tab of the > properties of the ExchWeb virtual directory: > > - first edit button: > - only 'Enable anonymous..." checked > - second edit button > - granted access selected > - view certificate button > - since you do not have ISA the certificate name should be the > self-signed one with the public name that was originally created by the > CEICW (which I think you said you exported then imported) > - third edit button > - require ssl and require 128-bit checked > - ignore client certificates selected > > You mentioned earlier that you wanted to delete extraneous certificates. > You can do that by opening the Certificates MMC... > - start, run, mmc > - File, add/remove snap-in > - add button > - select Certificates and click Add > - select "computer Account" and click next > - "local computer" and click finish > - close button > - OK button > - in the left-hand pane navigate down to: > Certificates > Personal > Certificates (click on this) > - you will see the certificates in the personal store on this computer > - you can right-click and delete extraneous ones from here, but be careful > which ones you delete (you can export them first) > > I would not choose to remove frontpage server extensions > If you have an ASP.Net tab on your websites you might want to make sure > they are running version 1.1 and not 2.0. > > I hope this helps. > > Jim > > > > > |