• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1835
  • Last Modified:

SBS 2008 IIS Backup / Restore

We are testing sbs 2008 and the built in backup and restore.  We have noticed that you can restore IIS which sounds like a fantastic feature although it does not work.
Scenario
1      We connect to owa and test internal websites.
2      We then backup the server
3      We delete the default website and SBS Web Application
4      We try and connect to the websites and obviously it is broken
5      We launch sbs restore and select application restore
6      We chose IIS and the wizard says complete
7      We see that the directories are back within IIS but the web pages are still not accessible

We have also tried manually backing up using the appcmd.exe but again after backup and restore the web pages are not accessible.  The only way that these are accessible is but doing a full server restore.
As I said we are just testing SBS 2008 this is not a live site so we can try suggestion without fear :)
Thank you in advance

Dan
0
capnet
Asked:
capnet
  • 2
1 Solution
 
bhanukir7Commented:
hi,

have you restarted the IIS service after the restore.

What are the errors that you receive when you try to open a web page. What are the errors you see in the IIS manager and windows events.

what are the kind of sites you are hosting on IIS. is it only OWA or anything else

bhanu
0
 
capnetAuthor Commented:
Hi Bhanukir7,
Thanks for the quick response,
Yes we restarted IIS service and even the server, although i think the appcmd.exe restore restarts the service for you.  When trying to browse:
https://localhost/Remote  or
https://sites/owa
just got a generic "Internet Explorer cannot display this webpage" with no error code. we just picked these 2 sites becuase we knew they worked before we did the delete and restore.

Here are the warnings and errors logged in system log directly after the deletion and restoration:

Log Name:      System
Source:        Microsoft-Windows-HttpEvent
Date:          30/04/2009 15:33:43
Event ID:      15300
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      2008AD.capnet.local
Description:
SSL Certificate Settings deleted for Port : 0.0.0.0:443 .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-HttpEvent" Guid="{7b6bc78c-898b-4170-bbf8-1a469ea43fc5}" EventSourceName="HTTP" />
    <EventID Qualifiers="32768">15300</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-30T14:33:43.751Z" />
    <EventRecordID>22615</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="68" />
    <Channel>System</Channel>
    <Computer>2008AD.capnet.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="DeviceObject">\Device\Http\ReqQueue</Data>
    <Data Name="SocketAddress">0.0.0.0:443</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          30/04/2009 15:35:39
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      2008AD.capnet.local
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
 to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="49152">10016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-30T14:35:39.000Z" />
    <EventRecordID>22643</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>2008AD.capnet.local</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{61738644-F196-11D0-9953-00C04FD919C1}</Data>
    <Data Name="param5">NT AUTHORITY</Data>
    <Data Name="param6">NETWORK SERVICE</Data>
    <Data Name="param7">S-1-5-20</Data>
    <Data Name="param8">LocalHost (Using LRPC)</Data>
  </EventData>
</Event>

I fixed the 10016 error using the following method I found.
http://seasideit.blogspot.com/2009/01/dcom-error-10016-on-sbs-2008.html

Reset the server, no warinings or errors in event log but problem persists. Still says cannot display webpage.
0
 
bhanukir7Commented:
hi

as far as this error goes

Log Name:      System
Source:        Microsoft-Windows-HttpEvent
Date:          30/04/2009 15:33:43
Event ID:      15300
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      2008AD.capnet.local
Description:
SSL Certificate Settings deleted for Port : 0.0.0.0:443 .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

this is a classic error where the connection status of SSL is not known.  

Can  you check if there are any more errors like Event id 15021 -  if you find event id 15021 for the same source

check this technet article

http://technet.microsoft.com/en-us/library/cc727844.aspx

post back the results also verify if IIS is listening on the right ip

0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now