Dear Experts,

Had a query, I am unable to Deploy a WSP file on SP-2010 Farm. Farm has 1 WFE, 1 APP, 1 DB. Initially the farm was 2 -Tier which we later made 3-tier by adding additional machine. I am getting Local Farm not accessible message, and some times access denied. I checked by Disabling User Acounts Group. and checked all server account was added to Local Admin Group. Previous Administrators were able to do so. Am I missing something.

Thanks,

Ajgar..

What account are you using to install the WSP and what scope is the solution targeted at?

It's possible that the addition of another server has caused the problem but if you haven't previously installed WSPs then it's most likely to be permissions based.

Dear Alex,

Thanks for your reply, we have installed WSP in 3-Tier but was done by a previous Admin profided if he might used any special account that was created manually for the purpose. I have used all high privilege accounts like, Sp-Farm, SP-Admin. Strange thing is I get Access Denied when I try to perform an IISRESET, I need to select "run it as Administrator" for it work. Can you point what permission I need on DB and other two machines.

Thanks,

Kunal Jaiswal 

With Windows Server 2008/Vista, by default, even if you are a Local Administrator, you do not have an Administrator token, so with things such as the SharePoint Management Shell (or running iisreset) which require Local Administrator rights, you need to "Run As Administrator".

The account you're using should be a Local Administrator as well as Farm Administrator in order to use the SharePoint Management Shell.  Instead of using "the" Farm Administrator (SP-Farm?), add your account to the Local Administrators group on all SharePoint servers, then add it to the Farm Administrators group in Central Administration, then using SP-Farm one last time to run the SharePoint Management Shell, add your user account using the cmdlet 'Add-SPShellAdmin "domain\username"'.

Hi Trevor,

Still no go, added user to Local Admin, in all SP-servers, run the powershell, and added the user to Content DB as db_Owner.  I tried rebooting the machine after that which un-fortunately didn't helped. Any checks that i would be missing.

Thanks,

Kunal Jaiswal

Are you upgrading an existing WSP or adding a new WSP ?

are you using powersheel to upgrade or add ?

We are upgrading an existing wsp, with new updates provided by a supplier as bug fix phase 1.  Supplier have given us a batch file which internally runs a powershell script.  :(

Batch script with the powershell commands to upgrade solution ? If yes then - there should be some issues with the commands in that, which u need to debug.

Open the batch script and check the commands.

are you running the batch script in sharepoint powershell console ?

If the existing WSP has any config file in Layouts folder and if that file is in Use when connecting to a custom database, this deployment error occurs.

The wsp file got deployed to QA farm which is a 2-tier, when doing that I need to restart the Timer Service to push that in two tier, but it gives error in 3-tier. Do you think it's an issue with codes of config files.  Do you think deployment for 2-tier solution and 3-tier solution are diffrent the way codes are written.

Solution that help me to resolve :-

There is an additional set of Security provided on Win 7 and Win Server 200 R2. You can disable this by :-

2.      In Control Panel, click User Accounts.

3.      In the User Accounts window, click User Accounts.

4.      In the User Accounts tasks window, click Turn User Account Control on or off.

5.      If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.

6.      Reduce the slider to minimum.

7.      Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window

Donot forget to restart the computer, else you can't deploy your solution.

Hope this may help you.