All Replies

• Monday, November 30, 2009 1:01 AMMike OryszakMVP

   
  

  0

  Sign In to Vote
  With the basic install it provisions a top level site collection as part of the process.  With any other install process you need to do it.  If you log into the Central Administration site you can finish the setup tasks.  I can't remember if you need to provision the main application or not, but I think you might.

  ---

  SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com
  • Reply
  • Quote

   
• Monday, November 30, 2009 10:08 AMDrew1872

   
  

  0

  Sign In to Vote
  Thanks for getting back to me Mike, I've created the default SSP and applications, now I'm trying to create a site collection that is the same as the default.aspx page that you get in a stand alone configuration. When I goto create the site collection I assume that I want a Publishing Portal but when I attempt to create it I am getting the following Runtime Error:
  
  
  

  Server Error in '/' Application.

  ---

  Runtime Error

  Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
  
  Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
  
  

  <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly"/> </system.web> </configuration>

  
  Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
  
  

  <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="On" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

  
  
  
  Can you or anyone else advise me of the Steps I need to perform post Installation to get a homepage up and running, I am just looking for an appropriate top level page from which I can build the company structure from.
  
  Thanks for your help, as you will be able to tell, I'm new to Sharepoint.
  
  Regards
  Drew
  • Reply
  • Quote

   
• Monday, November 30, 2009 12:24 PMDrew1872

   
  

  0

  Sign In to Vote
  Just incase its any help to anyone in the future, I found what the issues was, I was getting Event ID: 4965  when trying to create a Publishing Portal
  
  The following blog helped me troubleshoot this and resolve the issue:
  
  http://www.sharepointcomic.com/archive/2008/12/20/event-id-4965-publishing-provisioning-error.aspx
  
  
  

  Reason For Error:
  
  This error is happening because the account servicing the application pool which your site is in does not have sufficient access.  When you are trying to enable the Publishing feature, it's creating a job definition that does not have access to the SharePoint_Config Database. 

  
  Work Around / Solution:

  To enable the Publishing feature, you need to temporarily change the App Pool service account to be the same account as the Central Administration App Pool account.

  1. Change App Pool account to Central Admin Account
  2. Recycle App Pool
  3. Enable Feature
  4. Change App Pool account back to original account
  5. Recycle App Pool

  • Marked As Answer byLu Zou-MSFTMSFT, ModeratorTuesday, December 01, 2009 7:35 AM
  •  
  • Reply
  • Quote