Windows could not start the Windows Process Activation Service service on Local Computer.

Got a hit from my IIS 7, which hosts Share Point 2010.World wide web publishing service refused to start as there is a dependency with Windows Process activation service. It just says

The World Wide Web Publishing Service service depends on the Windows Process Activation Service service which failed to start because of the following error: The system cannot find the file specified

Restarting WAS results in

"The Windows Process Activation Service service terminated with the following error:The system cannot find the file specified."

Fortunately Scott Hanselman's blog article comes to the rescue to identify the issue. Some of folders within c:\inetpub was missing and Scott taught the way to locate the problem using Process monitor.



Good to have an additional tool narrow down the issue.

WCF Activation HTTP-Non HTTP Activation fails with Fatal error 0x80070643

Last night while preparing a Windows Server 2008 for the evaluation of SharePoint Server 2010 beta, I've installed all the prerequisites of SharePoint 2010, installed the roles, beta preview binaries and some hotfixes etc. I just wanted evaluate .NET 4.0 beta 1 along with SharePoint 2010.

While adding the features for my server such as .NET Framework 3.0, WCF activation, Window process activation service and desktop experience. Except WCF activation everything wen t smooth. My Server restarted dozen times saying "Configuring updates were failed reverting changes".

After sometime go-ogling the web resulted in the following Microsoft Connect article saying that the .NET Framework 4.0 is the culprit and uninstalling this will resolve the issue. But no luck even after uninstalling .NET Framework 4.0 and .NET 3.5 SP1.

At last I've uninstalled all the prerequisites of SharePoint 2010 related hotfixes, CTP's and beta previews. Now the WCF Activation feature installed like a breeze and finally succeeded in setting up my evaluation copy.

But a beta binary set installation which blocks a Server feature installation is not so good and as usual Microsoft doesn't provide any useful reasonable error message. Moral of the story is build is your box in a clean slate, Add roles and features required to the server and the add up your hot fixes,CTP's and betas.

Hope it helps some one

Fixing UserProfileException while installing SharePoint Server 2010

1. Microsoft.Office.Server.UserProfiles.UserProfileException
   
   The request channel timed out while waiting for a reply after 00:00:18.7285970.
   Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.
   
   One of the clear exception which says what to do while installing the beta product
   
   Navigate to the following path and open the client.config file \14\WebClients\Profile\client.config


2. Find the tag increase the default sendTiemout attribute value to few minutes instead of seconds sendTimeout="00:15:20"


3. Rerun the Psconfig wizard

After a long struggle managed to deploy SharePoint 2010 in a Vmware dev environment

Where is Windows Server 2008 SP1 ?

While preparing a Windows server 2008 virtual machine and as usual I was just looking up Microsoft.com for patching my newly installed operating system(to get the bug fixes).

Interestingly I was not able to find Windows Server 2008 SP1, there is only SP2 available and came to know that the initial OS installation includes the SP1.

FAQ Section of Windows Server 2008 SP1 clarifies the doubt,Following text taken from the FAQ

Are there any prerequisites for SP2?

You must have Windows Vista with SP1 or Windows Server 2008 installed on your computer before installing Service Pack 2. (Windows Server 2008 shipped with Service Pack 1 included.)

Screen shot after the clean installation of Windows server 2008