Online Training On SharePoint
                      
Showing posts with label Access Denied error while executing the configruation wizard. Show all posts
Showing posts with label Access Denied error while executing the configruation wizard. Show all posts

Friday, 20 November 2009

Error while working with PowerShell

I was trying to put my hands around PowerShell and I was encounring a strange error. I was running one cmdlet Get-SPWebApplication in Windows Server 2008 Server and it was throwing this error:
"Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permissions to access the database before trying again."


I tried all the cmdlets but the same error keep coming. After some more investigation I found that the solution and it was that the PowerShall needs to be executed as Administrator. While running powershell it shows 2 option:


If we just click the open it will open a PowerShell window and this message will come:


and all the cmdlets will show the error message as shown. To run the PowerShell scripts we should use the second option of running as Administrator.

Sunday, 26 July 2009

Error While Adding a WFE to the existing SharePoint Farm

We have build a new Server to add in existing SharePoint Farm as Web Front End Server. We installed SharePoint 2007 in the server having Windows Server 2003 as the operating System. While running the configuration wizard there was a error and the server could not be added into the farm.

In the SharePoint Logs following entries were there:

07/27/2009 09:36:30 8 INF Now joining to farm at server MOSSDBServer database SharePoint_Config
07/27/2009 09:36:38 8 ERR Task configdb has failed with an unknown exception
07/20/2009 09:36:38 8 ERR Exception: System.Security.SecurityException: Access denied.

Since we were using the farm admin account when attempting to join the new WFE, all the required privileges were there.

On further investigation we found that there was a application pool in IIS which was not getting used anywhere and was having a password which was expired. Because of this application pool this issue was coming. We have deleted this app pool. Again the config wizard was executed and it ran successfully.
Related Posts with Thumbnails