Unable to create a Collaboration Portal Site Collection

I have a strange issue.  I can create any other type of site collection EXCEPT a collaboration Portal.  Even the Publishing Portal works.
I get an error that just states that I need to contact the System Administrator.  Unfortunately that's me.
Any thoughts?
The only thing that changed recently was that I could not get into the SSP (I got an error when trying to get to the site) and the only way to fix it was to restore a previous version of the web.config file.
Thanks
Ron
LVL 1
Capt_RonIT Solutions ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
AlMothanaAlOmariCommented:
ok , go to web.config and change the custom error= Off to On, and also callstack from false to true ,
and send us the error then we can help you
0
 
Capt_RonIT Solutions ManagerAuthor Commented:
This is the only error:
 
 This page has encountered a critical error. Contact your system administrator if this problem persists.  
 
I've made the changes to the web config and that's all I get.

Here is the Event Viewer entry that I think applies to this:
Event log message was: 'The site template was not provisioned successfully. Delete this site collection in Central Administration, and then create a new site collection.'. Exception was: 'Microsoft.SharePoint.WebPartPages.WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.
   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded()
   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.IsSafeControl(Type type, String& unsafeErrorMessage)
   at Microsoft.SharePoint.WebPartPages.TypeCache.get_Item(Type type)
   at Microsoft.SharePoint.WebPartPages.WebPart.WriteXmlGlobal(Boolean disableSafeControlsCheck)
   at Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.Serialize(PersonalizationScope scope)
   at Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.get_Links()
   at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartToStore(WebPart webPart, Int32 viewId, String viewGuid)
   at Microsoft.SharePoint.WebPartPages.SPWebPartManager.AddWebPartInternal(SPSupersetWebPart superset, Boolean throwIfLocked)
   at Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager.AddWebPartInternal(WebPart webPart, String zoneId, Int32 zoneIndex, Boolean throwIfLocked)
   at Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager.AddWebPart(WebPart webPart, String zoneId, Int32 zoneIndex)
   at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.CreateSampleDashboardWebParts(SPWeb parentWeb, SPFile dashboardFile, String kpiListUrl, String excelWorkbookUrl)
   at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.CreateSampleDashboard(SPWeb parentWeb, SPList reportsLibrary, SPFile sampleWorkbook)
   at Microsoft.SharePoint.Portal.ReportCenterSampleDataFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
   at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
   at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
   at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtWebInternal(SPWeb web, String sFeatures, Boolean fMarkOnly)
   at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass7.<EnsureFeaturesActivatedAtWeb>b__6()
   at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)
   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, CodeToRunElevated code)
   at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtWeb(Byte[]& userToken, Int32 nZone, Guid siteid, Guid webid, String sFeatures)
   at Microsoft.SharePoint.Library.SPRequestInternalClass.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId)
   at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId)
   at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(String strWebTemplate)
   at Microsoft.SharePoint.SPWeb.CreateWeb(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean bCreateUniqueSubweb, Boolean bConvertIfThere)
   at Microsoft.SharePoint.SPWeb.SPWebCollectionProvider.CreateWeb(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean bCreateUniqueSubweb, Boolean bConvertIfThere)
   at Microsoft.SharePoint.SPWebCollection.Add(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean useUniquePermissions, Boolean bConvertIfThere)
   at Microsoft.SharePoint.Portal.ReportCenterCreatorFeatureReceiver.CreateReportCenter(SPWeb parentWeb)
   at Microsoft.SharePoint.Portal.ReportCenterCreatorFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
   at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
   at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
   at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtSiteInternal(SPSite site, String sFeatures, Boolean fMarkOnly)
   at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClassa.<EnsureFeaturesActivatedAtSite>b__9()
   at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)
   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, CodeToRunElevated code)
   at Microsoft.SharePoint.SPFeatureManager.EnsureFeaturesActivatedAtSite(Byte[]& userToken, Int32 nZone, Guid siteid, String sFeatures)
   at Microsoft.SharePoint.Library.SPRequestInternalClass.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId)
   at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId)
   at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(String strWebTemplate)
   at Microsoft.SharePoint.Publishing.PortalProvisioningProvider.CreatePortal(String xmlFile, SPWeb rootWeb)'
0
 
Capt_RonIT Solutions ManagerAuthor Commented:
I ended up calling MicroSoft and this was the solution:  (not an answer but a fix)

Create a new web application
Remove all content databases from "bad" web application
Add them to the new web application
(remember to restart iis after EACH database add)
Change the Alternate Access Mappings of the old web application to something else (doesn't really matter what, you'll end up removing the web app anyway)
Change the Alternate Access Mappings of the NEW web application to the URLs from the old one
Remove the host headers in IIS on the old web application
Add the host headers to the new web application
restart iis
Set the Search server in each of the content databases in the new web application

OK.  Now why did this problem happen in the first place?  No one knows.  MS recommended this course of action mainly because it would have taken a huge amount of time to research the problem.  We do know that there was something wrong in the Safe Controls section of the web.config.  But we couldn't find it.
I'm thinking that it also could have been a corrupt DLL in the BIN that was being referenced by the web.config and when we created the new web app and moved everything over it was fixed.

Maybe We'll never know...
Is 2010 out yet??? :-)
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.