SharePointed

When creating my SharePoint 2010 sandbox farm I wasn’t able to get past connecting to the database server.  This is the error I was seeing:

An error has occurred while validating the configuration settings.  An exception of type System.ArgumentNullException was thrown.  Additional exception information: The errorData argument cannot be null or zero length.  Parameter name: errorData

I logged into my SQL Server 2008 R2 VM and updated the Start Mode of SQL Agent and SQL Serve Browser to Automatic.

What / Where / How

Start –> All Programs –>SQL Server XXX –>Configuration Tools –> SQL Server Configuration Manager

After it opens select SQL Server Services, right click on SQL Server Browser, select properties, click on Service, then set Start Mode to Automatic.  Repeat these steps on SQL Server Agent service.

After doing this I restarted the server.

——– edit

if you are having trouble finding your SQL Server, Server Name try looking here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER

SNI10.0 — LastConnect

There you will find the name of your SQL Server

Total noob error on my part.

rebooted my test box and started to see this error:

NTLRD is missing

Turned out that my system was trying to boot from an external hard drive I had connected to the box. Unplugged the drive and rebooted and the system is back to normal.

Windows Server 2008 R2

http://sharepoint2010.microsoft.com/try-it/Pages/Trial.aspx

not exactly sure what day they will release the bata version.

The jump from 2003 to 2007 wasn’t that bad. But I have a feeling that people are going to have fun with the new interface in SharePoint 2010, not to mention the changes to SharePoint 4.0 Central Administration. This should be fun!

Log Name:      Application

Source:        Windows SharePoint Services 3

Date:          6/26/2009 10:23:11 AM

Event ID:      3351

Task Category: Database

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      sharepointed

Description:

SQL database login failed. Additional error information from SQL Server is included below.

Windows SharePoint Services VSS Writer

I updated the Log On from Local System account to one of the Farm admin accounts.

(The specified address was excluded from the index. The crawl rules may have to be modified to include this address. (The item was deleted because it was either not found or the crawler was denied access to it.)

 We were using the Robots.txt file to block search engines from indexing our public site. When I first tried to index the site from the SSP it would only crawl a small part of the site.  After messing with permissions and other items I was informed that we had added a Robots.txt file to the site.  Once we removed the file from the C:\inetpub\wwwroot\wss\VirtualDirectories\YourSiteName folder and rebooted the server, I was able to index the entire site from the SSP. The following day is when the trouble began. I tried doing a Full Crawl and the crawl status would change from Crawling to Idle within a few seconds and would display the error above. 

 Here is how I fixed the problem.  In the content database create this Stored Procedure (you can delete it later).

What does it do? The stored procedure will allow you to search all the tables in a database.

Create PROC [dbo].[SearchAllTables]

(

      @SearchStr nvarchar(100)

)

AS

BEGIN

      CREATE TABLE #Results (ColumnName nvarchar(370), ColumnValue nvarchar(3630))

      SET NOCOUNT ON

      DECLARE @TableName nvarchar(256), @ColumnName nvarchar(128), @SearchStr2 nvarchar(110)

      SET  @TableName = ”

      SET @SearchStr2 = QUOTENAME(’%’ + @SearchStr + ‘%’,””)

      WHILE @TableName IS NOT NULL

      BEGIN

            SET @ColumnName = ”

            SET @TableName =

            (

                  SELECT MIN(QUOTENAME(TABLE_SCHEMA) + ‘.’ + QUOTENAME(TABLE_NAME))

                  FROM INFORMATION_SCHEMA.TABLES

                  WHERE             TABLE_TYPE = ‘BASE TABLE’

                        AND   QUOTENAME(TABLE_SCHEMA) + ‘.’ + QUOTENAME(TABLE_NAME) > @TableName

                        AND   OBJECTPROPERTY(

                                    OBJECT_ID(

                                          QUOTENAME(TABLE_SCHEMA) + ‘.’ + QUOTENAME(TABLE_NAME)

                                           ), ‘IsMSShipped’

                                           ) = 0

            )

            WHILE (@TableName IS NOT NULL) AND (@ColumnName IS NOT NULL)

            BEGIN

                  SET @ColumnName =

                  (

                        SELECT MIN(QUOTENAME(COLUMN_NAME))

                        FROM INFORMATION_SCHEMA.COLUMNS

                        WHERE             TABLE_SCHEMA      = PARSENAME(@TableName, 2)

                              AND   TABLE_NAME  = PARSENAME(@TableName, 1)

                              AND   DATA_TYPE IN (’char’, ‘varchar’, ‘nchar’, ‘nvarchar’)

                              AND   QUOTENAME(COLUMN_NAME) > @ColumnName

                  )

                  IF @ColumnName IS NOT NULL

                  BEGIN

                        INSERT INTO #Results

                        EXEC

                        (

                              ‘SELECT ”’ + @TableName + ‘.’ + @ColumnName + ”’, LEFT(’ + @ColumnName + ‘, 3630)

                              FROM ‘ + @TableName + ‘ (NOLOCK) ‘ +

                              ‘ WHERE ‘ + @ColumnName + ‘ LIKE ‘ + @SearchStr2

                        )

                  END

            END  

      END

      SELECT ColumnName, ColumnValue FROM #Results

END

Once you have created the stored proc execute this command:

Exec SearchAllTables ‘Robots.txt’

You will see a single record returned.

Then run this command:

Delete from AllDocs

Where LeafName = ‘Robots.txt’

After this I rebooted the server and went to lunch.  Why lunch? Well, for some reason SharePoint takes a little time to propagate the change (timer job I’m sure).

If you are having an issue where only part of your site is being indexed try adding crawl rules.

example:

http://www.sharepointed.com/*

include

then select the default account or use one that has read access to the site.

For one reason or another, Central Administration wouldn’t come up and the only thing i could see was HTTP Error 503. The service is unavailable..

easy fix.

Check the Application Pools for SharePoint Central Administration v3 and make sure it’s running.

done!

After upgrading to Windows 7, I’m unable to view List’s in Datasheet View.

Error:
The list is displayed in Standard view. It cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls, or support for ActiveX controls is disabled.

Solution

I was running IE 8 (64 bit), when I tried editing the list in Datasheet view with the 32 bit version, everything was back to normal.

It appears a 64 bit version of Office will be out for the 2010 release.

http://arstechnica.com/microsoft/news/2009/04/confirmed-office-2010-will-come-in-32-bit-and-64-bit.ars

This is the connection string I use for all my BDC files.  Once the file is imported into the BDC, I then assign permission accordingly.

<LobSystemInstances>
<LobSystemInstance Name=”BDC_Unique_Name_RI”>
<Properties>
<Property Name=”DatabaseAccessProvider” Type=”System.String”>SqlServer</Property>
<Property Name=”AuthenticationMode” Type=”System.String”>RevertToSelf</Property>
<Property Name=”RdbConnection Data Source” Type=”System.String”>Database_Server_Name</Property>
<Property Name=”RdbConnection Initial Catalog” Type=”System.String”>Database_Name</Property>
<Property Name=”RdbConnection Integrated Security” Type=”System.String”>SSPI</Property>
<Property Name=”RdbConnection Pooling” Type=”System.String”>false</Property>
<Property Name=”RdbConnection Trusted_Connection” Type=”System.String”>false</Property>
<Property Name=”RdbConnection User ID” Type=”System.String”>User_Name</Property>
<Property Name=”RdbConnection Password” Type=”System.String”>User_Password</Property>
</Properties>
</LobSystemInstance>
</LobSystemInstances>

In SQL Server I assing User_Name Select permissions on the items referenced in the BDC file.

NOTE

Make sure your default search account has access to the BDC file once it’s imported.  I applied Execute and Selectable in clients permissions on both the Application and Entity.

“How do I find the default accout?”

Shared Services Administration: SSP1 > Search Administration > Default content access account

If your site is missing the Search Web Parts, make sure you have the Feature enabled on your site.

Site Collection Administration–>Site Features

Office SharePoint Server Search Web Parts

Office SharePoint Server Standard Site Collection features