Cannot connect to content database error in SharePoint with Event ID 5617

If you encounter the traditional SharePoint cannot connect to database error, with the following from the EventViewer then, run the command "stsadm.exe -o upgrade -inplace -url http://{central%20administration%20site}/"
This process may take a minutes to hours to finish up but it clears up the bug.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 5617
Date: 10/11/2007
Time: 12:14:02 PM
User: N/A
Computer: ESSSHAREPOINT20
Description:The schema version (3.0.149.0) of the database on Servername\OfficeServers is not consistent with the expected database schema version (3.0.151.0) on . Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

SharePoint Solution Package deployment error

If you encounter an error of type "Error 102 An object of the type Microsoft.SharePoint.Administration.SPSolution named "SolutionPackageName" already exists under the parent Microsoft.SharePoint.Administration.SPFarm named "SharePointContentDBName". Rename your object or delete the existing object", then even though if you remove the references of the solution in the sites, SharePoint will not allow to redeploy the solution.

The issue can be solved by, browse to the Central Administration -> Operations -> Solution Management and then delete the wsp file that caused the error and then redeploy the file again.

Office 2003 Add-in Web Parts and Components in WSS 3.0

Microsoft Office Web Parts and Components is a collection of Web Parts, Web Part Page solutions, templates, and data retrieval services that work closely with Microsoft Office 2003 and Microsoft Windows SharePoint Services 2.0. These added features are particularly useful for large organizations that have deployed Microsoft Office throughout their organization and that want to take advantage of the enhanced functionality and efficiencies these Web Parts and components provide for their sites.

These webparts can be used in Windows SharePoint Services 3.0. To install these webparts in WSS 3.0 use the "stsadm.exe -o addwpack" command. The web part can be added to your page from the Web part gallery.

It works fine for me. However if you encounter any error try the workaround specified in the following knowledge base article.
http://support.microsoft.com/kb/929320

SAP's Webdav connector for WSS

WebDav is Web-based Distributed Authoring and Versioning Protocol. The Webdav connector is used to integrate SAP with Windows SharePoint Services.

The Connector is a plugin that is available for download in the following Microsoft site

http://www.microsoft.com/isv/sap/technology/interop/ep.aspx

The connector provides full access to all Windows SharePoint Services based document libraries. Provides full support for custom properties / meta data. Full support for Windows SharePoint Services' Versioning capablities.

SPIisWebsiteUnprovisioningJobDefinition Error while deleting a Web Application in SharePoint

The following error might occur while deleting a web application in SharePoint "An object of the type Microsoft.SharePoint.Administration.SPIisWebsiteUnprovisioningJobDefinition named "Unprovionsing PWN" already exists under the parent Microsoft.SharePoint.Administration.SpWebservice named "". Rename your object or delete the existing object."

A possible solution for this issue can be,

• Navigate to the Central Administration Site,
• Go to the Operations tab
• click on the Timer Job Definition
• Delete the Unprovisionning web application from the list
• Go ahead and Delete the Web application.

Integrate SharePoint 2007 and CRM 3.0 (SQL 2005)

The CRM List Web Part can be downloaded from the below link.
http://www.microsoft.com/downloads/details.aspx?FamilyId=BC9B3526-DECF-4057-A530-91840C0D5401&displaylang=en

Though this webpart was developed for the earlier version of SharePoint, it can be used in MOSS 2007 with the workaround specified in the following link,

http://blogs.msdn.com/mscrmfreak/archive/2007/01/16/microsoft-crm-and-moss-2007-workaround.aspx

To start using the web part follow the following steps after the workaround process,

• Goto Command Prompt and navigate to the path where the Stsadm.exe is present ( c:\Program Files\Common Files\Microsoft Shared\Web Server Extension\12\Bin )
• Type -> stsadm.exe -o deletewppack -name MicrosoftCRMListWebPart.cab
• This will unistall the currently installed web part cab package.
• To install it in the GAC Type the following command;stsadm.exe -o addwppack -globalinstall -force -filename "MicrosoftCRMListWebPart.cab"

The web Part should be installed in the GAC, Now try to put the web part in the page there wont be any issues.

Shrink SharePoint content database size

To free up the SharePoint Content Database space, you can use the following SQL command

dbcc shrinkdatabase(WSSContentDatabaseName)

Auditing in SharePoint

You can enable auditing at the site collection level, to enable monitoring the following in SharePoint 2007

• Documents opened


• Documents downloaded


• List items viewed


• List item properties viewed


• Items edited


• Document checkout


• Document check in


• Items Edited


• Items Deleted


• Items restored


• Content types Editing


• Searching site content


• Editing user accounts


• Editing permissions