Archive for August, 2008

MOSS 2007: Site Usage Report Error



When click on “Site Usage Reports” under “Site Administration” in “Site Settings” page, the following message displayed:


Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing must be enabled to view usage reports. Please contact your administrator to ensure that these services are enabled.




You have to enable two options. Open “Central Administration” -> “Operation” and click on “Usage analysis processing” under “Logging and Reporting” and check “Enable Logging”. Then, move to “Shared Service Provider”, Click on “Usage reporting” under “Office SharePoint Usage Reporting” and check both options.

Comments (3)

STSADM: addcontentdb error



We created a web application and tried to replace the content database with another database. When run command:


stsadm –o addcontentdb –url http://abc –databasename WSS_ABC.


Following error displayed:


An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=SharePoint – 41272 Parent=SPWebService is being updated by domain\loging, in the OWSTIMER process, on machine ABC. View the tracing log for more information about the conflict.




The solution was to force cache refresh. This can be done as under:


1. On Central Administration machine, move from C\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\ GUID.

2. Copy cache.ini file to another location.

3. Open the file and replace the current integer with 1.

4. Restart “Windows SharePoint Services Timer” service.
5. Run the command again.


Hope this workJ.

Comments (5)

SharePoint Upgrade Error on Individual sites – Gradual Approach

When we tried to upgrade individual site from SharePoint 2003 to MOSS 2007, individual site upgrade resulted error:
Please refer to the upgrade log at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log and the trace log for additional information.

Status Job failed
Mode Side-By-Side
Elapsed Time 
Starting object SPMigratableSiteCollection Parent=SPManager
Current object 
Current action 
Step within the action 
Total steps in this action 
Server  ABC
It gave me two options, either resume or delete. I checked Upgrade.log and it has following entry:

[SPSiteCollectionMigrator] [DEBUG] [7/30/2008 3:08:01 PM]: ————- Begin SPMigratableSiteCollection ————-
[SPSiteCollectionMigrator] [DEBUG] [7/30/2008 3:08:01 PM]: SPSite Url=http://abc/sites/xyz
[SPSiteCollectionMigrator] [DEBUG] [7/30/2008 3:08:01 PM]: ————– End SPMigratableSiteCollection ————–
[SPServerSequence] [DEBUG] [7/30/2008 3:08:01 PM]: [SPServer Name=SQL10 Parent=SPFarm Name=SharePoint_Config] BuildVersion =
[SPServerSequence] [DEBUG] [7/30/2008 3:08:01 PM]: [SPServer Name=SQL10 Parent=SPFarm Name=SharePoint_Config] SchemaVersion =
[SearchServiceInstanceSequence] [DEBUG] [7/30/2008 3:08:01 PM]: [SPServer Name=SQL10 Parent=SPFarm Name=SharePoint_Config] SchemaVersion =
[SPServerSequence] [DEBUG] [7/30/2008 3:08:01 PM]: [SPServer Name=SQL10 Parent=SPFarm Name=SharePoint_Config] BuildVersion =
[SPServerSequence] [DEBUG] [7/30/2008 3:08:01 PM]: [SPServer Name=SQL10 Parent=SPFarm Name=SharePoint_Config] SchemaVersion =
[SearchServiceInstanceSequence] [DEBUG] [7/30/2008 3:08:01 PM]: [SPServer Name=SQL10 Parent=SPFarm Name=SharePoint_Config] SchemaVersion =
[SPUtility] [DEBUG] [7/30/2008 3:08:01 PM]: File C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Template\sql\store.sql, Time out = 600 sec
[SPSiteCollectionMigrator] [DEBUG] [7/30/2008 3:08:17 PM]: PregrowTempDatabase: computing the size of temp db.
[SPSiteCollectionMigrator] [DEBUG] [7/30/2008 3:08:17 PM]: PregrowTempDatabase: target size 20 MB.
[SPSiteCollectionMigrator] [DEBUG] [7/30/2008 3:08:17 PM]: SPContentDatabase2 Name=EnPointe1_SITE Parent=SPDatabaseServiceInstance FullTextSearchEnabled: True
[SPManager] [ERROR] [7/30/2008 4:08:18 PM]: Migrate [SPMigratableSiteCollection Parent=SPManager] failed.
[SPManager] [ERROR] [7/30/2008 4:08:18 PM]: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
[SPManager] [ERROR] [7/30/2008 4:08:18 PM]:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)
   at Microsoft.SharePoint.Upgrade.SPContentDatabase2.set_FullTextSearchEnabled(Boolean value)
   at Microsoft.SharePoint.Upgrade.SPSiteCollectionMigrator.Migrate()
   at Microsoft.SharePoint.Upgrade.SPManager.Migrate(Object o, Boolean bRecurse)
[SPManager] [DEBUG] [7/30/2008 4:08:18 PM]: Elapsed time migrating [SPMigratableSiteCollection Parent=SPManager]: 01:00:17.0340845.
[SPManager] [INFO] [7/30/2008 4:08:18 PM]: Gradual Upgrade session finishes. root object = SPMigratableSiteCollection Parent=SPManager, recursive = True. 1 errors and 0 warnings encountered.
[SPManager] [DEBUG] [7/30/2008 4:08:18 PM]: Removing exclusive upgrade regkey by setting the mode to none


When you have the situation where “Resume” and “Delete” buttons are available for site upgrade. Open “upgrade.log” and look for [ERROR]. Check the line preceding the line where [ERROR] is written and you will find entry with a GUID like following:
[SPWebTemplateSequence] [DEBUG] [7/30/2008 3:08:01 PM]: Template SPSSITES#0: Activating feature a311bf68-c990-4da3-89b3-88989a3d7721 in site with URL “http://abc/xyz“, force=False.
Note GUID:a311bf68-c990-4da3-89b3-88989a3d7721. Go to STSADM.exe and run the following command:
stsadm –o activefeature –id GUID –url http://abc/xyz
Click on resume button and if the status remains same, repeat this until error is removed.

Leave a Comment

MOSS 2007: LoadBalancer.RegisterLauncher failed


Event Viewer of MOSS 2007 server machine filled with “LoadBalancer.RegisterLauncher failed” error after almost every 30 to 40 seconds. Description is as under:

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Launcher Service
Event ID: 6102
Date:  8/18/2008
Time:  8:45:52 AM
User:  N/A
Computer: ABC
LoadBalancer.RegisterLauncher failed:  Unable to connect to the remote server

For more information, see Help and Support Center at


One workaround is to restart the service and this will work fine until the next restart of the machine. Other is to move from Central Administration -> Operation -> Service Account. Select the service “Load Balancer Service” and select the account “Network Service”.

Comments (1)

After upgrade, Internet Users Cannot Access SharePoint 2003 sites


Our SharePoint 2003 URL is exposed to internet. Let it be .

 Our SharePoint 2003 was running on port 80. When we upgraded using gradual approach, SharePoint 2003 was moved to another port, say, 42154 and new MOSS 2007 started running on port 80.

Now, the functionality is that when we try to access a SharePoint 2003, we are redirected. Like if when we tried to access http://share.compantname/sites/abc , we were redirected to SharePoint 2003 and URL turns out to be http://share:42154/sites/abc. This works find for intranet users but for internet users http://share:42154/sites/abc is not Fully Qualified Domain Name (FQDN), so they get stuck with page not found error.



What we did was used SSL for port 42154. One can do this by going to IIS Manager, select Web Site running SharePoint 2003. Right click and click on properties. In front of TCP PORT: 42154, you have SSL Port: test box. Write 443. You will be able to access SharePoint 2003 sites using httpS://


What went wrong?

When started Upgrade by clicking on “Begin Upgrade”, we didn’t put host header name and did not exposed that host header to internet



For more explanation, kindly visit the heading “Determine and create new domain names (gradual upgrade only)” at the following link:

Leave a Comment