Project Server 2007 has damaged MOSS 2007

Question

We have a server running MOSS2007 with all websites and content in SQL on same server, we have full systems and SQL and stsadm backups of the db's

Project Server 2007 was installed but errored - posted elsewhere and resulted in the search reporting as unlicensed, thinking the simple answer was to remove Proj Serve r2007 when went with that - and now it gets more problematic:

The Central Admin site has been removed from IIS and when we run the Microsoft Offer Server -> SharePoint Products and Technologies Configuration Wizard is errors after confirming we're okay with stopping services, the error is posted at the end of this post

It is my understanding that if we get the wizard to run it will rebuild the missing site and get us back where we started - is this so?

TIA
Tony

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.SharePoint.SPEvaluatorModeProvisioning.ValidateSite(SPSite site)
   at Microsoft.SharePoint.SPEvaluatorModeProvisioning.TryGetIsSiteProvisioned(String template, String relativePath, Nullable`1 port, SPSite& provisionedSite, SPWeb& provisionedWeb, Uri& provisionedUri)
   at Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.ShowNextFormForServerRoleSingleServer()
   at Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.PsconfigBaseFormNextButtonClickedEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

Answer 1

This was posted in the Sharepoint forums as it's sharepoint that's damaged and needs to be recovered