Monday, July 27, 2009

Features of SharePoint 2010

New features Sneak Preview of SharePoint 2010
Though the features and look and feel of the new product is farely good, I will not be surprised to find double the bugs in that product as SharePoint 2007.

Upgrade and Central Administration is quiet a relief to look at but then again it depands on how smoothly it works on large enterprises where already a lot of customization is done. Microsoft has still not released anything on SharePoint 2010 Basic installation or upgradation path from that type of installation. Will have to wait and watch......

Monday, July 20, 2009

Capture Site Collection deleted immediately

Even though SharePoint 2007 has a wonderful feature of Recycle Bin, its disadvantage is that it does not capture Site Collections Deleted. If we have to restore the deleted Site Collection, get it from the backup and if no backup, forget the site and re-create again.

I hope that archiving of a Site Collection feature is introduced in SharePoint 2010, but in the mean time, we can still use an open source tool, easy to deploy on the SharePoint FARM given by CodePlex.

This tool will capture the deleted site collection immediately and send a mail to the Site Administrators with the name of the person who deleted the site. Also allowing you to restore the site if needed immediately.

Microsoft IT Site Delete Capture LE 1.0

Monday, July 13, 2009

Event ID 5586, Cannot generate SSPI context

You get "Cannot connect to Configuration database" while accessing Central Administration or any SharePoint sites.

In Event Viewer we get the below error on the SharePoint server.

Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category:
Database Event ID: 5586
Date: 7/13/2009
Time: 12:36:31 AM
User: N/A
Computer: COMPUTERNAME
Description:Unknown SQL Exception 0 occured. Additional error information from SQL Server is included below. Cannot generate SSPI context.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

While trying to connect using connect.udl file, it gives the same error "Cannot generate SSPI Context"

On the SQL 2005 Server we get the below error.

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17836
Date: 6/25/2009
Time: 11:51:45 PM
User: N/A
Computer: COMPUTERNAME
Description:
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT:IP of SP Server]


Quick Resolution:- Reboot the SQL Server 2005

Error Troubleshooting:-
How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889

This is related to some SPN configurations gone incorrect on the SQL server.

Resolution:-
Logon to the server using Domain Admin rights.
Download Setspn.exe from Microsoft site to set the SPN's for the SQL server.

At command prompt go to the location where setspn.exe was installed.
C:\Program files\support tools>setspn -L MyDomain\MyUserName
Registered ServicePrincipleNames for CN=MyUserName Service Account, OU=Service Accounts, DC=MyDomain,DC=com: mssqlsvc/MyServer1.MyDomain.com:MyPort mssqlsvc/MyServer2.MyDomain.com:MyPort mssqlsvc/MyServer3.MyDomain.com:MyPort

If you are getting the error (Cannot generate SSPI context), you will not find the SQL server name in the list displayed by the command.

To Register your SQL server type the following command.
setspn -A MSSQLSvc/MyServer.MyDomain.com:1433 MyAccount

Note:- MyServer will be the SQL server name to which you are not able to connect.

Again run the setspn -L MyDomain\MyUserName command, you should find your SQL servers FQDN registered.

Checklist before Planning System requirements for Deploying Sharepoint

Questionnaire

=> Access SharePoint sites from Internet (Y/N) If Yes,
No. of Current users who will be accessing SharePoint sites.
No. of Users projected to Access SharePoint sites by next 5 yrs.

=> No. of Current users who will be accessing SharePoint sites. (Intranet)
=> No. of Users projected to Access SharePoint sites by next 5 yrs. (Intranet)

=> Data to be uploaded on the SharePoint sites (in GB/TB)
=> Data to be uploaded on the SharePoint sites (in GB/TB) in next 5 years

=> No. Of Geographical Site locations

=> Requirement of Incoming Email Libraries (Y/N)
=> Requirement of Search Functionality (Y/N)

=> Search Usage (Heavy/Average)
Heavy - Using Customised/Enhanced Search/Federated Search
Heavy - Support for searching external data stores.
Average - Out of the box Search Functionality

=> Use of InfoPath Services and Excel Services (Y/N)
=> Usage of MySites (Y/N)
=> Usage of Business Data Catalog (Y/N)

=> Sites Redundancy/Failover Requirements?
=> Plan to Customize SharePoint Sites (Y/N)

=> Support for Multiple Language (Y/N)

=> Recovery Server Hardware and then restore sites on Production site.

Note: Some questions may not relate exactly to the hardware, but it will depand on performance suggesting to add more WFE servers to the FARM or no

Glitch after installing Service Pack 2 on MOSS

As usuall Microsoft has done it again and I am not surprised. There is no single patch or Service Pack released by Microsoft which is uncontroversial. Even after Service Pack 2 release of MOSS, it makes sure that they keep getting calls to PSS support.

When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly
http://support.microsoft.com/kb/971620

Link to download WSS 3.0 SP2
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

Link to download SP2 for MOSS 2007
http://www.microsoft.com/downloads/details.aspx?FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082&displaylang=en

Read more information on SP2
http://technet.microsoft.com/hi-in/office/sharepointserver/bb735839(en-us).aspx

Total Pageviews