2 Answers
2

Is there anything in the ULS logs? I have seen the deployment hang when the services don't have the correct access to a box, or the services aren't running (ie: setup account must be local admin on all boxes in the farm, and the timer service must be running), but it'll typically come back after a period of attempts and tell you it failed.

If you're getting an access error like that I'm assuming you're running the deployment under your personal credentials, and not the setup account. Log on to the box using the setup/install account (which will have the correct permissions), and retry the deployment.
–
webdes03Aug 23 '12 at 13:37

Make sure that the Timer job is running on ALL servers in the farm, not merely the server you are running the commands on. Beyond that, make sure that the account that you are logged in on has sufficient permissions on the farm.

I just have one server running like wfe/app.
–
shreyasAug 22 '12 at 19:08

In that case, set your Diagnostic logging to Verbose/Verbose, rerun the deployment, giving it about 5 minutes to run, then look at the latest logs in 14/LOGS for any errors or other unexpected results. ULS Viewer (archive.msdn.microsoft.com/ULSViewer) helps considerably with this task!
–
Dave WiseAug 22 '12 at 19:17

I assume you are running this as your user account so the quickest way to get around it is to run the SharePoint Command Console as the Farm account (Shift-right click on the link and select Run As User) and attempt the deployment under that account. If that works, then you will need to do some troubleshooting to determine exactly where the permissions for your user account are falling short as you really don't want to make it a habit of logging in under the farm account.
–
Dave WiseAug 22 '12 at 21:02

Thanks Dave, I had fixed this issue in main server (using powershell commands) but still needs to fix it in dev server.
–
shreyasAug 27 '12 at 18:28