DeutschDelf
Fri Sep 07 06:52:02 PDT 2007
Here's what I can contribute to this error message... the root cause for this
occurring, in my case, is that at some point of the server build, I extended
the central admin web application (to give it a DNS alias) and, and this was
a big mistake, I removed the pre-installed â??SharePoint Central Administration
v3â?? web app. This (original web app) is what the backup procedure is looking
for when it attempts a catastrophic backup. Silly that MOSS allows you to
delete the central admin web site in the first place and then does not adjust
where its backup routine for the the only existing admin site points to â??
maybe a fix for a service pack?
Without deeper knowledge of this product, the only way for me to fix it
seems to be a server re-build, but I decided against that, as the
catastrophic backup backs up pretty much everything else, and in an event of
a very bad disaster, I would start out with a fresh web front end server
anyways that has a new Central admin running on it. Then, I would manually
configure the admin site and restore all the other items captured in the
catastrophic backup. Hope this helps...
Delf
"BeigeBond@gmail.com" wrote:
> On Aug 8, 11:13 am, "dietmarhan...@aol.com" <dietmarhan...@aol.com>
> wrote:
> > I have installed WSS 3.0 alongside companyweb on sbs 2003. The user
> > account i have used is the domain administrator account on the server,
> > which i have used throughout the installation/deployment and backing
> > up of WSS 3.0. I am trying to perform a full system backup via the
> > Central Administration, and i have ticked all the boxes to get the
> > whole farm backed up. I have tried backing up just the 'SharePoint-
> > 80' web application but i get the same error
> >
> > Part of the log file that was created (up until the error is thrown)
> > is shown below
> >
> > [8/8/2007 1:02:47 PM]: Verbose: The backup/restore process included
> > the following objects:
> > [8/8/2007 1:02:47 PM]: Farm\
> > [WSS3]\
> > WindowsSharePointServices Web Application\
> > SharePoint- 80\
> > WSS_Content_d888afb99db149579a1e8877bca74ba8\
> > [WSS_Administration]\
> > [Web Application]\
> > SharePoint_AdminContent_18bc7c08-2644-4353-
> > b3a2-9388ca3a401e\
> > WindowsSharePointServices Search\
> > [Search instance]\
> > [WSS_Search_MARS_8966ff679ea74c49867114c50bffc7ba]\
> >
> > [8/8/2007 1:02:47 PM]: Verbose: AddingSharePoint- 80 to Backup list.
> > [8/8/2007 1:02:47 PM]: Verbose: Adding
> > WSS_Content_d888afb99db149579a1e8877bca74ba8 to Backup list.
> > [8/8/2007 1:02:47 PM]: Progress: Starting Backup.
> > [8/8/2007 1:02:47 PM]: Start Time: 8/8/2007 1:02:47 PM.
> > [8/8/2007 1:02:47 PM]: Verbose: Requested by MICRONAV\Administrator.
> > [8/8/2007 1:02:47 PM]: Verbose: Backup/Restore Settings:
> > Backup
> > Backup Method: Full
> > Top Component: Farm\WindowsSharePointServices Web Application
> > \SharePoint- 80
> > Directory: \\mars\transfer
> > Progress updated: 5
> > [8/8/2007 1:02:47 PM]: Backup threads created: 1
> >
> > [8/8/2007 1:02:47 PM]: Verbose: AddingSharePoint- 80 to Backup list.
> > [8/8/2007 1:02:47 PM]: Verbose: Adding
> > WSS_Content_d888afb99db149579a1e8877bca74ba8 to Backup list.
> > [8/8/2007 1:02:47 PM]: Verbose: Starting OnPrepareBackup event.
> > [8/8/2007 1:02:47 PM]: Verbose: Starting object: Farm.
> > [8/8/2007 1:02:47 PM]: Verbose: Saving SPPersistedObject State
> > [8/8/2007 1:02:47 PM]: Verbose: Starting object: WSS3.
> > [8/8/2007 1:02:47 PM]: Verbose: Saving SPPersistedObject State
> > [8/8/2007 1:02:47 PM]: Verbose: Starting object: WindowsSharePoint
> > Services Web Application.
> > [8/8/2007 1:02:47 PM]: Verbose: Saving SPPersistedObject State
> > [8/8/2007 1:02:47 PM]: Verbose: Starting object:SharePoint- 80.
> > [8/8/2007 1:02:47 PM]: Verbose: Saving SPPersistedObject State
> > [8/8/2007 1:02:47 PM]: Error: ObjectSharePoint- 80 failed in event
> > OnPrepareBackup. For more information, see the error log located in
> > the backup directory.
> > KeyNotFoundException: Thegivenkeywasnotpresentin thedictionary.
> > [8/8/2007 1:02:47 PM]: Debug: at
> > System.ThrowHelper.ThrowKeyNotFoundException()
> > at System.Collections.Generic.Dictionary`2.get_Item(TKeykey)
> > at
> > Microsoft.SharePoint.Administration.SPWebApplication.OnPrepareBackup(Object
> > sender, SPBackupInformation info)
> > at
> > Microsoft.SharePoint.Administration.Backup.SPBackup.RunPrepareBackup(SPBack-upRestoreObject
> > node)
> >
> > Hope this helps you to help me,
> >
> > Regards,
> >
> > Dietmar
>
> First off, the quick fix: use the site collection backup form of
> stsadm -o backup instead of catestrophic for the URLs that fail with
> this error. For example:
>
> stsadm -o backup -url
http://www.essentialsharepoint.com/ -filename
> esp2007.bak
>
> That will get you an initial backup and alleviate a lot of worry.
> Next, try to resolve the "KeyNotFound" exception. I'm not sure, but I
> think this relates to web applications that were renamed after they
> were created. You might try this:
>
> 1. Detach the content database from the web application.
> 2. Delete the web application (remove SharePoint from it).
> 3. Create a new web application with the appropriate host header or
> port/name combo.
> 4. Attach the existing database to the new web app.
> 5. Try the full backup again.
>
> Please post back here if that does or doesn't work as this does seem
> like a common problem (bug?).
>
> Good luck,
>
> Jeff
>
>