Thursday, July 2, 2009


It's 3.00 AM in the morning; I was browsing Internet and came across a news article that said that Michael Jackson was dead. I was shocked. I mean, he was so young. I know life is uncertain and that death is always sudden. But Michael Jackson? It was one of the cruelest twists of fate. He was scheduled to perform a comeback tour next month in U.K. which was touted to be the greatest comeback tour ever..! The fact that fate robbed him of his last opportunity of regaining his lost glory makes his demise even more painful.

I know it sounds selfish but I wish that MJ would have lived long enough to enthral his fans one last time..! He certainly didn’t deserve to die in this ignominy and loneliness. For an MJ fan, his untimely death, just before his farewell concert is devastating. Words seem to elude me and I am groping for expressions that would describe my anguish for this loss. Life has been so unfair to him. And for all the horror that he had to endure courtesy the media and the relentless paparazzi, MJ deserves more than a post from an obscure blogger.

For me, It would take some more time to come into terms with the fact that the King of Pop is no more and that he would not slide his shoes across the floor.. Ever..!

I relayed this news to my colleagues and managers in office immediately and that started a long discussion on MJ and his Jacko-Whacko lifestyle and infamous surgeries. People may give different names to his madness but for me he was a moon walker who stormed the earth by his talent.

He may have died early but he proved that life is not about the years it’s all about life in those years........May Allah bless his soul......Ameen

Wednesday, June 24, 2009

Event IDs 7000 and 7009, The service did not respond to the start or control request in a timely fashion."Timeout"

Windows SharePoint Services upgrade gets failed. When we checkin the SharePoint Central Administration site it shows the site needs an upgrade.

1.) Run “stsadm -o upgrade -forceupgrade” to force the upgrade.

We see the following events in the System Event log when the Administration service fails to start:-

Event IDs 7000 and 7009 in System Log:-

"The SharePoint Portal Administration service failed due to the following error:The service did not respond to the start or control request in a timely fashion.""Timeout (XXXXX milliseconds) waiting for SharePoint Portal Administration service to connect."

1.) We changed the following registry settings:HKLM\SYSTEM\CurrentControlSet\Control add/change DWORD value ServicesPipeTimeout and assign a decimal value of 60000 (i.e. 60 thousand which means 60 seconds)

2.) Increase the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control string value WaitToKillServiceTimeout to 120000 (120 thousand which means 120 seconds)

3.) Now REBOOT the server as the new timeouts will not take into effect until server is restarted.

The service did not respond to the start or control request in a timely fashion Timeout

Windows SharePoint Services upgrade gets failed. When we checkin the SharePoint Central Administration site it shows the site needs an upgrade.

1.) Run “stsadm -o upgrade -forceupgrade” to force the upgrade.
We see the following events in the System Event log when the Administration service fails to start:-
Event IDs 7000 and 7009 in System Log:-

"The SharePoint Portal Administration service failed due to the following error:The service did not respond to the start or control request in a timely fashion.""Timeout (XXXXX milliseconds) waiting for SharePoint Portal Administration service to connect.

1.) "We changed the following registry settings:HKLM\SYSTEM\CurrentControlSet\Control add/change DWORD value ServicesPipeTimeout and assign a decimal value of 60000 (i.e. 60 thousand which means 60 seconds)

2.) Increase the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control string value WaitToKillServiceTimeout to 120000 (120 thousand which means 120 seconds)

3.) Now REBOOT the server as the new timeouts will not take into effect until server is restarted.

Wednesday, June 10, 2009

Upgrade MOSS 2007 Standard to Enterprise Edition

Upgrade MOSS 2007 Standard to Enterprise Edition ******************************************************
Moss 2007 being a paid product (Unlike it’s predecessors WSS 2.0 & WSS 3.0) is available in two editions
1. Enterprise Edition
2. Standard Edition

Upgrading Moss 2007 Standard Edition to Enterprise Edition is as easy as making 2 minutes Maggie noodles .Upgrade a SharePoint install from the Standard edition to Enterprise: just change the license key!!! Wonderful !! Thatzz it..
Change the License Type

===================

Go to Central Administration ==> Operations ==> Select Convert license type ==> Enter the license key for the Enterprise Edition

Enable Enterprise Features

====================

==> Go to Central Administration ==> Operations ==> Enable Enterprise Features ==> Choose Enterprise and click Ok.

Enable Enterprise Features (Existing Sites)

===============================

Go to Central Administration ==> Operations ==> Enable Enterprise Features on Existing Sites Check the box and click Ok.


P.S. - (Once you upgrade, you can’t downgrade to Standard again)

Tuesday, June 9, 2009

B2B upgrade fails with error Upgrade object too new in upgrade.log

MOSS 2007 upgrade fails Upgrade object too new in upgrade.log after B2B upgrade
*********************************************************************************
Problem Description
******************
[SPManager] [INFO] [2/17/2009 8:04:29 PM]: Resetting the status of PersistedUpgradableObject: SharedDatabase Name=KNETSSP_DB Parent=SPDatabaseServiceInstance to Online.[SPManager] [INFO] [2/17/2009 8:04:29 PM]: Finished upgrading SharedDatabase Name=KNETSSP_DB Parent=SPDatabaseServiceInstance.[SPManager] [INFO] [2/17/2009 8:04:29 PM]: Preparing to upgrade PersistedUpgradableObject: SearchSharedDatabase Name=KNETSSP_Search_DB Parent=SPDatabaseServiceInstance. This object's current status is Online.[SharedSearchDatabaseSequence] [ERROR] [2/17/2009 8:04:29 PM]: Upgrade object too new (build version = 12.0.6219.1000, schema version = 12.0.0.0). Current server (build version = 12.0.4518.1016, schema version = 12.0.0.0).[SPManager] [ERROR] [2/17/2009 8:04:29 PM]: CanUpgrade [SearchSharedDatabase Name=KNETSSP_Search_DB Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [2/17/2009 8:04:29 PM]: The specified SearchSharedDatabase Name=KNETSSP_Search_DB Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [2/17/2009 8:04:29 PM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)[SPManager] [ERROR] [2/17/2009 8:04:29 PM]: ReflexiveCanUpgrade [SearchSharedDatabase Name=KNETSSP_Search_DB Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [2/17/2009 8:04:29 PM]: The specified SearchSharedDatabase Name=KNETSSP_Search_DB Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [2/17/2009 8:04:29 PM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
====================================================
It will be a bad value, probably RTM listed in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\BuildVersionPer this line in upgrade log:Upgrade object too new (build version = 12.0.6219.1000, schema version = 12.0.0.0). Current server (build version = 12.0.4518.1016, We changed the value from 12.0.4518.1016 to 12.0.6219.1000, and this allowed the upgrade to move past this error.