Problem Background(if you just need the answer jump to conclusion in the end):
The forms which are browser enabled need to be deployed via central admin. I had this problem with my form template when I tried to deploy this via central admin and it hanged there for ever on deploying status and if you try to do other operation like 'Remove' SharePoint complains about running one job at a time. So you cannot really do anything except waiting there or digging this further to know why is this happening.
So I picked the second choice and start drilling this down further.
When you deploy the form template via central admin SharePoint does the following activiates for you in the background:
1). Deploying the solution with specific naming convention i.e. forms - form template name - version number.wsp
2). Adding a feature - for form template content type.
when SharePoint performs the first step it adds the solution into the solution store by creating a timer job on one of the farm servers and waits until the job gets executed.
For some bazzare reason(Sharepoint Administration Service stop state/failure) the server cannot peform the job. The result is, the job is in the queue and solution deployment/retraction/upgradation is hanged for ever.
So if we clear this job somehow it will fix the whole thing.
First see which server is responsible for this timer job, which seems itself very trickey. So try to execute manually all timer jobs on all front end servers first by using the following stsadm command
stsadm -o execadmsvcjobs
i'm sure on few servers you will see operation completed successfully without any job but on one of the servers you will find the solution deployment/reaction/upgrading job will execute in result.
As soon as you find the job executed successfully you will see the solution deployment is changed to deployed rather deploying so as the Form Template status back to 'Ready'
Conclusion:
If your infopath form template deployment is hanged with infinite status(Deleting, Upgrading, Deploying etc.)
run the following command on front end servers first(then application servers if you cannot find any job).
stsadm -o execadmsvcjobs
Hope this will help!
Majid
I'm senior Developer/Consultant and passionate about Microsoft Technologies including Microsoft 365, SharePoint and .NET. I have been working in this industry for well over 10 years. This blog is all about sharing unique scenarios and tips of my project work which someone else might find handy too.
Subscribe to:
Post Comments (Atom)
Iconise ‘Add Picture’ control in PowerApps
Default look you get for ‘Add Picture’ control is not very appealing for end user and there is no OTB way of specifying icon for this con...
-
There's a very good article on business connectivity services which puts you on the right direction to start things with it. But when a...
-
Powershell command start-job does support running the script block under specified user. The command also supports various other feature w...
-
Popular SQL Grim - How to get around with it: After a long when when I tried to run Share Point on my laptop - rather me seeing the centr...
No comments:
Post a Comment