Re: EMERGENCY: Portal creation failed, yet no log to look at
From: SizzleMaster (larry_at_datasculpting.com)
Date: 11/08/04
- Next message: DonnM: "RE: Moving sites between two Sharepoint 2003 Portal Servers"
- Previous message: greg: "Re: have sql on a different box"
- In reply to: Bill English [MVP]: "Re: EMERGENCY: Portal creation failed, yet no log to look at"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Nov 2004 13:40:48 -0800
Thanks Bill. I had already tried to rebuild the farm several times with a
new config.db and to restore the production databases as well a a backup of
the databases but I received the error below both times. I do have a dated
backup that I restored successfully. I understand that the indexes in
question are not on the SQL server. What would cause them to not be
rebuildable post defrag on the SQL server then? Also, why did the portal
creation log fail to be created upon the failure to restore? Is there any
trick to force it's creation? Are there utilites to check the integrity of
the databases to determine what failed?
Thanks again.
"Bill English [MVP]" <bill@mindsharp.com> wrote in message
news:up6bBfUxEHA.1308@TK2MSFTNGP09.phx.gbl...
>I don't understand. The portal indexes are not held in the SQL database,
>rather they are on the file system. The site indexes are held in the SQL
>database, so perhaps you're referring to them.
>
> Removing and reinstalling the binaries on the WFE servers is nearly
> irrelevant to the restoring of a portal server. I'm not trying to be mean
> or demeaning with that statement, just trying to help everyone who reads
> this post to understand that the entire architecture of SharePoint is
> modular. As you describe, the problem is with the integrity of the
> databases.
>
> Do you have a backup of the databases from before your defrag operation?
> If so, restore that copy.
>
> I had this same problem earlier this week in Atlanta - in front of the
> entire class. In addition, even though I could open the shared services
> portal, the error message in the backup program stated that the virtual
> server wasn't properly extended. Hmmm........
>
> So, it ended up that the only way I could re-build to a working state was
> to tear down the farm and work with a new configuration database. This
> didn't include re-installing the binaries, but instead, removing all the
> servers from the current farm, creating a new config db, then assign the
> servers to the new farm and restore the databases.
>
> This took about 1.15 hours. It's not difficult, but it is a bit time
> consuming.
>
> HTH.
>
> --
>
> Bill English
> www.mindsharp.com
> www.mindsharpblogs.com
> sharepointdiscussions@yahoogroups.com
>
>
> "SizzleMaster" <larry@datasculpting.com> wrote in message
> news:elxtA58wEHA.1976@TK2MSFTNGP09.phx.gbl...
>> Any help would be GREATLY appreciated.
>>
>> After defragging my SQL server box, the indexes were blown out. I
>> removed SharePoint on the front end web server and re-installed it yet
>> can't restore one of my portals. I can restore one of the two and it
>> logs it successfully. I recieve the error: Portal creation failed.
>> Please see the portal creation log for more details. I click the link
>> and it says file not found. I've searched for the log and it wasn't
>> created. I also looked at the other computer logs and no mention of a
>> any problem.
>>
>> Any suggestions would be helpfull. I'm rather desperate here. The
>> portal's been down all day.
>>
>
>
- Next message: DonnM: "RE: Moving sites between two Sharepoint 2003 Portal Servers"
- Previous message: greg: "Re: have sql on a different box"
- In reply to: Bill English [MVP]: "Re: EMERGENCY: Portal creation failed, yet no log to look at"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
