SharePoint Diva

June 6, 2008

GroupBoard Workspace: Bad

I’ve encountered two problems since installing the Microsoft GroupBoard Workspace. One was causing the week-view of the calendar to give an error. The second was anytime I tried to add a content database, I’d get the error:

The specified SPContentDatabase Name=SharePoint_Content Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

There was nothing in SharePoint to upgrade, we’ve already installed the most up-to-date service packs. I found that the problem was the GroupBoard Workspace. Once I un-installed it, as suggested by GPK2005 on the Microsoft TechNet forum, I was able to add my content database without issues.

Thank you GPK2005.

June 3, 2008

Attaching this database requires upgrade…

I’m trying to add a content database to an existing Web Application.  I go into Central Administration > Application Management > Content Databases and Add a content database.  I then get the error: 

Attaching this database requires upgrade, which could time out the browser session.  You must use the STSADM command ‘addcontentdb’ to attach this database.   

The content database gets created in the separate SQL Server (2005).  Running the STSADM command gives the following error in the error log: 

The specified SPContentDatabase Name=blah_Content Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. 

Nothing requires an upgrade, by following the steps in this article, I was able to create the content database and attach it to the web application. 

Reproduced Content from Article (just in case link disappears): 

Step a: Use SQL Query Analyzer to create the database

Use SQL Query Analyzer to create a new content database for use with the virtual server in Windows SharePoint Services. You cannot use the Create Database Wizard in the SQL Server Enterprise Manager tool to create the new database. Instead, run the following two queries in SQL Query Analyzer. When you use the following queries, make sure that you do the following:

·         Replace each instance of WSS_Content in the queries with the name that you want to use for the database.

·         Replace each instance of AdminVsAppPoolIdentity in the query with the account that is the SharePoint Central Administration virtual server application pool identity. This account is also the database owner (dbo) of the database.

·         Replace each instance of ContentVsAppPoolIdentity in the query with the account that is the content virtual server application pool identity.

·         Replace each instance of Domain in the query with the domain name.

Use the following query to create the database: 

– Windows SharePoint Services Content Database Creation Script
– TODO: Change the database name from WSS_Content to the name of the database that you want to use
CREATE DATABASE [WSS_Content] COLLATE Latin1_General_CI_AS_KS_WS
exec sp_dboption [WSS_Content], autoclose, false
GO

 

Use the following query to configure permissions for the database that you created: 

– Windows SharePoint Services Content Database Creation Script
use WSS_Content
– TODO: Change AdminVsAppPoolIdentity to the SharePoint Central Administration virtual server application pool account and change ContentVsAppPoolIdentity to the content virtual server application pool account.

DECLARE @AdminVsAppPoolIdentity nvarchar(128 )
DECLARE @ContentVsAppPoolIdentity nvarchar(128 )
SET @AdminVsAppPoolIdentity = N’Domain\AdminVsAppPoolIdentity’
SET @ContentVsAppPoolIdentity = N’Domain\ContentVsAppPoolIdentity’

EXEC sp_grantlogin @ContentVsAppPoolIdentity;
EXEC sp_grantlogin @AdminVsAppPoolIdentity;

– The following line will fail with error 15007 if @AdminVsAppPoolIdentity is the Network Service account.  This is expected.
EXEC sp_changedbowner @AdminVsAppPoolIdentity;

– The following line will fail with error 15063 if the account is not the Network Service account.  This is expected.
IF NOT EXISTS (SELECT * FROM sysusers WHERE name=@ContentVsAppPoolIdentity) EXEC sp_grantdbaccess @ContentVsAppPoolIdentity;

– The following line will fail with error 15410 if the account is not the Network Service account.  This is expected.
EXEC sp_addrolemember ‘db_owner’, @ContentVsAppPoolIdentity;

Step b: Add the content database to the virtual server

Use Windows SharePoint Services Central Administration to add the content database to the virtual server. To do this, follow these steps.

  1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
  2. Click Application Management, and then click Content databases under SharePoint Web Application Management.
  3. On the Manage Content Databases page, click Add a content database.
  4. In the Web Application area, click the name of the Web application to which you want to add the content database.
  5. In the Database Name and Authentication area, specify the name of the database, the name of the database server, and the authentication method.
  6. In the Database Capacity Settings area, type the number that you want in the Number of sites before a warning event is generated box and in the Maximum number of sites that can be created in this database box, and then click OK.

Note If you configured permissions for the database with the NT Authority\Network Service account, you have to add the Network Service account to the System Administrators role in SQL Server before you can follow this step. You cannot make the Network Service account the database owner (dbo) of the database. You have to add the Network Service account to the System Administrators role before you can add the database to the virtual server. After you add the database to the virtual server, remove the Network Service account from the System Administrators role in SQL Server.

 

 

 

 

 

 

May 29, 2008

Office SharePoint Server Search Service stuck

Filed under: MOSS 2007, SharePoint, Trackback — sharepointdiva @ 11:03 pm
Tags: , , ,

How did I get here? Sometime this morning I was trying to fix an issue with the people search feature not working. While trying to correct that, I got stuck in the limbo of Office SharePoint Server Search remaining in the status of “Stopping” without ever getting to the status of “Stopped”. Apparently this is a common issue, but the recommended fix for it, running “stsadm -o osearch -action stop”, isn’t working for me. 


Changed the “Log On As” to Local System, disabled the service and rebooted. Once back up, re-enabled the service, started it, stopped it. Still showed as Stopping in the Central Administration. Re-ran the command “stsadm -o osearch -action stop”. YAY!


Tried to start: An unhandled exception occurred in the user interface.Exception Information: OSearch (DOMAIN\ShareAdmin)

Change the “Log On As” back to the (DOMAIN\ShareAdmin) and start the service from Central Administration > Operations > Services on Server. Everything was back up. 

Below is a link to one of the options I tried. While it didn’t fixe this particular issue, I’m sure this will come in handy in the future.  

SharePoint Services Timer Service File System Cache

Resetting the file system cache have resolved many issues I had in my SharePoint farm. Microsoft tech support gave me this resolution to fix some issues I had with Usage Analysis. I perform this operation first if I get stuck with any issues related to timer jobs. Good times!

May 27, 2008

Site Directory is Petarded

Filed under: MOSS 2007, SharePoint — sharepointdiva @ 4:36 pm
Tags: , , , ,

I’m using trying to use the Site Directory Template. Out of the box, it creates “categories” for Division and Region. Of course I want to use my own categories and I remove those for my own. Being of a database driven mentality, I of course make my columns lookup columns to be driven from list values that I’ll be using over and over throughout my site; Department and Location. So why can’t I get these new columns to show up in the “Categories” tab?

Because only “choice” columns are made into Categories. And those choices are “hard coded” inside the column definition.

Grrrrr.

May 23, 2008

Trackback

Filed under: MOSS 2007, SharePoint, Trackback — sharepointdiva @ 8:11 pm
Tags: , , , , , , , ,

I’ll be spending a great deal of my Monday learning how to customize the themes and master pages on SharePoint.

CSS Hacks for SharePoint Design

Lately, I am doing lot of design work for a client redesigning their MOSS Intranet solution. I found my self fiddling around with Master Pages, Page Layouts and CSS files more often. During this journey I came across lot of the handy resources, which helped me along the way!

The coolest thing I’ve done today thanks to this blog:

Media Player Web Part

This webpart allows you to play avi, mpg and wmv files with in your MOSS site.

But then in the comments, Daniel A (unfortunately with no link for me to trackback to) wrote:

Rather than going through this heart ache, just add a content editor web part and use the below HTML

<OBJECT id=”VIDEO” CLASSID=”CLSID:6BF52A52-394A-11d3-B153-00C04F79FAA6″ type=”application/x-oleobject”>

       <PARAM NAME=”URL” VALUE=”/Docs/[Your Document Library]/[folder]/[your file.wmv]“>

       <PARAM NAME=”animationatStart” VALUE=”true”>

       <PARAM NAME=”transparentatStart” VALUE=”true”>

       <PARAM NAME=”SendPlayStateChangeEvents” VALUE=”True”>

       <PARAM NAME=”AutoStart” VALUE=”false”>

       <PARAM name=”uiMode” value=”full”>

</OBJECT>

Which I did as well, and it was sweet! I love it when things work exactly as described. Especially on a rainy brain-deadened Friday.

Blog at WordPress.com.