Featured post

Automation | Powershell scripts

Automation | Powershell scripts Xenapp 6.5 Health check script XenAppServerHealthCheck Report through Script  ## XenAppServerHealthCheck ## ...

Tuesday, 4 December 2018

Windows could not start the World wide web publishing service Error 1068

Windows could not start the World wide web publishing service Error 1068


Solution:
Open RegEdit
And move to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WAS\Parameters
Check the ‘ConfigIsolationPath’ and make sure the path is present and it has proper rights.
Now open services.msc and try starting the service. It should work.

For me, I didn’t have ConfigIsolation Path in my registry, but the Windows Process Activation Service was looking for c:\inetpub\temp\apppools\, which I did not have. Creating this folder got things going again. This article was very helpful in tracking down the problem, “Windows Process Activation Service (WAS) Is Stopping Because It Encountered An Error”.

NOTE:- Path  c:\inetpub\temp\apppools and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WAS\Parameters
Check the ‘ConfigIsolationPath’ should be same .

No comments:

Post a Comment