My IT Experiences - Microsoft 365, SharePoint & Azure

I received this error while creating the SSP for a MOSS 2007 SP1 farm: Command createssp failed for SSP 'SharedServices2' Microsoft.SharePoint.SPException: Unable to connect to database. Check database connection information and make sure the database server is running. ---> System.Runtime.InteropServices.COMException (0x81020024): Unable to connect to database. Check database connection information and make sure the database server is running I tried both from GUI of Central Admin and also createssp command of stsadm, both failed with the same error. I checked the ULS logs and found the above error. In event viewer I could see the event id 6141: Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID: 6141 Description: The site /ssp/admin could not be created. The following exception occured: Unable to connect to database. Check database connection information and make sure the database server is running. No matter wh...

Here is a list of MOSS patches, corresponding versions, and release month and year: Office SharePoint Server 2007 : 12.0.4518.1016 October public update (2007) : 12.0.6036.5000 Service Pack 1 : 12.0.6219.1000 Post Service Pack 1 rollup : 12.0.6300.5000 Infrastructure Update (IU) : 12.0.6320.5000 (July 2008) August Cumulative Update : 12.0.6327.5000 October Cumulative Update : 12.0.6331.5000 (October 2008) December Cumulative Update : 12.0.6335.5000 (December 2008) February Cumulative Update : 12.0.6341.5002 (February 2009) Service Pack 2 : 12.0.6420.1000 (April 2009) April Cumulative Update : 12.0.6504.5000 (April 2009) June Cumulative Update : 12.0.6507.5000 (July 2009) August Cumulative Update : 12.0.6514.5002 (September 2009) October Cumulative Update : 12.0.6520.5000 (October 2009) December Cumulative Update : 12.0.6524...

I got this error while trying to browse my SharePoint site from within the server. I tried in both my front ends and application server and got the same error. I double checked to make sure the user I'm trying to login to the site had enough permission and also that password had not expired or account locked. Nothing seems to help. Then I came across this excellent article by Spencer Harbar which talks about this issue. This error is caused by a feature in Windows Server 2003 SP1 and above called loopback security check. This feature prevents access to a site using its FQDN (Fully Qualified Domain Name) from the server that hosts the website. Here is Spencer's blog post: http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx There is also a Microsoft KB article that gives a solution to this problem. There are two solutions, disable loop check through a registry entry (not recommended for production servers) ...

To restore a SQL server database from multiple files we can use the RESTORE DATABASE T-SQL command. Before we do the restore process it is good to know the name of the “.mdf” and “.ldf” files in the backup set. To find this out we can run the RESTORE FILELISTONLY command in the following syntax: RESTORE FILELISTONLY FROM DISK = 'E:\Db_Backups\FILE1_FULL.BAK', DISK = 'E:\Db_Backups\FILE2_FULL.BAK', DISK = 'E:\Db_Backups\FILE3_FULL.BAK' In the above example I assume the full backup consists of 3 files, “FILE1_FULL.BAK”, “FILE2_FULL.BAK”, and “FILE3_FULL.BAK”. The files in this case files are locate in E drive “Db_Backups” folder. The above command will output the name of the “.mdf” and “.ldf” files contained in the backup set. Once we get those we can run the actual restore command in the following way: RESTORE DATABASE My_DB FROM DISK = 'E:\Db_Backups\FILE1_FULL.BAK', DISK = 'E:\Db_Backups\FILE2_FULL.BAK', DISK = 'E:\Db_Backups\FILE3_FULL.BAK...

I saw that this error was appearing multiple times on my SharePoint front end server: Event Type: ErrorEvent Source: Windows SharePoint Services 3 Event Category: Database Event ID: 3351 Date: 9/28/2010 Time: 12:06:00 PM User: N/A Computer: WFE2 Description:SQL database login failed. Additional error information from SQL Server is included below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp I did some research and it turned out the error occurs because "Windows SharePoint Services VSS Writer" service in that SharePoint box was running "Local System". I changed this to a domain service account and the error vanished.

We had an issue with our Index server running out of disk space. The server was old and didn't have slots available to add more storage. The approach I took had a disadvantage that I had to do a Full Crawl again. Here are the steps I followed: 1. Setup MOSS server with all pre-requisites; do not add server to farm Note: It is important not to install .NET Framework 3.5 SP1 on this server, please read my previous blog post for more details. It can be installed after setting up search. 2. Reset all crawled content from Central Admin. We may choose to remove the existing Index server from farm if required 3. Run PS Config wizard on new Index server and add the server to farm. If you have done a complete installation of MOSS the Web Application service and Incoming Email service would have started. Before configuring search we may choose to stop these services. 3. Start search service from Services on Server page of Central Admin - Operations and do the configuration. 4. Navigate to S...

While trying to configure Search Settings in my new Index Server, I received this error when I clicked "Search Settings" from SSP: In my farm I was planning to run both Index and Query services on same server. I did some research and found that this could be because of corrupted SSL for the Office Web service. The reason it seems to be .NET Framework 3.5 SP1 !! Yes it seems if we enable search service or configure Index server on a box which has .NET Framework 3.5 SP1 the SSL of the Office web service in IIS would go corrupted. I had a similar situation; I was replacing the Index server in my MOSS farm version 12.0.0.6219 I brought up this new server with same OS and framework patch level as the existing index server. That was a mistake because my existing Index server was setup in 2008 and that time there was no .NET Framework 3.5 that time. It got installed later during a patching window. But in my case when I made the patch level same on my new server I installed all frame...