Re: RESTORING CRASHED SITE WEBS



There is (I'm fairly sure) a KB article saying to remove FP extenstions (if
they are already there) before installing WSS and then to add them back
afterwards.

I suspect however that this is just a side issue and that your answer to
your main questions lie elsewhere - anyone know more about that ?

On your new question (FP backups [=smigrate]). Yes (but I'd reinstall WSS
without FP SE first!) but you will lose users and their rights. It will
however give you all your data and the two databases. It does however work -
and work easily and quickly provided you accept the need to re-specify
users/user rights after the site is there.


Mike Walsh, Helsinki, Finland


"Mike" <angelom@xxxxxxxxxxxxxx> wrote in message
news:1116702230.828112.55410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Well, when installing Sharepoint, the installer did display a message
> saying it found frontpage extensions on the default web and I could
> either cancel or continue and extend the default web later. I selected
> continue.
>
> By the way; I also used the backup option in Frontpage2003 before the
> crash; so I a have those backups too. Perhaps I should have just
> installed sharepoint and used the smigrate to restore the web sites.
> That may have rebuilt the SQL databases from scratch.
>
> Mike Walsh wrote:
> > Are you sure about 4 ? You shouldn't be specifying FP 2002 when you
> are
> > installing IIS.
> >
> > Mike Walsh, Helsinki, Finland
> > WSS FAQ at http://wss.collutions.com
> > Please post questions to the newsgroup only.
> >
> >
> > "Mike" <angelom@xxxxxxxxxxxxxx> wrote in message
> > news:1116697360.638501.164780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > My server crashed. I reformatted and reinstalled Windows 2003. I
> want
> > > to restore my WSS System. Everything was backed up prior to the
> Crash.
> > > I have everything kind of restored but can't access the SQL
> databases
> > > from Central Administrator. The error I get is
> > > Login failed for user 'DOMAINNAME\ACCOUNTNAME. (Error code: 18456)
> > > This error comes up when selecting to login with a domain or a
> windows
> > > account. I can't login using any existing accounts. When trying
> to
> > > access using Windows Security the account returned in the failed
> login
> > > message is 'NT AUTHORITY\NETWORK SERVICE'. That account doesn't
> exist
> > > in my Active Directory anywhere. I'm not sure how to proceed.
> Below
> > > is a step-by-step of how I restored the system. Perhaps some kind
> &
> > > knowledgable person can review my procedure and tell me what went
> > > wrong.
> > >
> > > 1. INSTALL WINDOWS
> > > 2. INSTALL WINDOWS SP1
> > > 3. ACTIVE DIRECTORY SETUP (Join domain)
> > > 4. ADD SERVER ROLL (IIS - COM+ - ASP.NET - FP2002)
> > > 5. INSTALL SQL2000
> > > 6. INSTALL SQL 2P3 (Used Domain Account MAC\Administrator)
> > > 7. RESTORE ALL SQL (master) AND WSS DATABASES
> > > 8. RESTORE WEBS
> > > Application Pools: create from XML backup files
> > > WEB Sites : create from XML backup files
> > > 9. INSTALL SHAREPOINT (failed with error)
> > > 10. COPY BACKED UP \INETPUB DIRECTORIE STRUCTURE TO SERVER
> > > C:\INETPUB
> > > 11. REINSTALL SHAREPOINT (repair mode)
> > >
> > > >From here everything looks good. In IIS Manager I can see my web
> sites
> > > and all the config info looks OK. The SQL database is restored and
> In
> > > SQL manager I can open databases.
> > >
> > > 12. RUN SHAREPOINT CENTRAL ADMINISTRATION FOR FIRST TIME
> > > Inital page says I must create or connect to a share point
> > > configuration databse. I put in the database server name and
> existing
> > > database name, check the box to use existing configuration
> database,
> > > check box to use Windows authentication.
> > >
> > > Can't login to database. I try using a domain account that I know
> > > exist in the domain and in the SQL security logins list. Either
> option
> > > returns the Error 18456.
> > >
>


.



Relevant Pages

  • Website Administrator writes two instances of each user into the database
    ... After installing Visual Studio and SQL Express RTM my ... the login link was selected on the homepage. ... So this all made me suspicious and I went into the database and observed ... It was interesting to note the login control would then load ...
    (microsoft.public.vsnet.ide)
  • Website Administrator writes two instances of each user into the database
    ... After installing Visual Studio and SQL Express RTM my ... the login link was selected on the homepage. ... So this all made me suspicious and I went into the database and observed ... It was interesting to note the login control would then load ...
    (microsoft.public.dotnet.general)
  • Re: Logging in irrespective of database access
    ... Sysadmin role members have full permissions, ... SQL Server MVP ... > My problem is that in the Login section of Enterprise Manger I have to> specify that each login has the System Admin ticked under Server Roles> because in SQL 2000 there doesn't seem to a Grant All permissions option> like there used to be in SQL 6.5. ... > What's the point in having the Database Access section if the System Admin> under Server Roles allows you to get into anything?. ...
    (microsoft.public.sqlserver.programming)
  • Re: Logging in irrespective of database access
    ... Sysadmin role members have full permissions, ... SQL Server MVP ... > My problem is that in the Login section of Enterprise Manger I have to> specify that each login has the System Admin ticked under Server Roles> because in SQL 2000 there doesn't seem to a Grant All permissions option> like there used to be in SQL 6.5. ... > What's the point in having the Database Access section if the System Admin> under Server Roles allows you to get into anything?. ...
    (microsoft.public.sqlserver.server)
  • Re: Logging in irrespective of database access
    ... Sysadmin role members have full permissions, ... SQL Server MVP ... > My problem is that in the Login section of Enterprise Manger I have to> specify that each login has the System Admin ticked under Server Roles> because in SQL 2000 there doesn't seem to a Grant All permissions option> like there used to be in SQL 6.5. ... > What's the point in having the Database Access section if the System Admin> under Server Roles allows you to get into anything?. ...
    (microsoft.public.sqlserver.server)