InfoPath Managed Form Templates – upload status stuck or remains forever in ‘installing’ or ‘deleting’ state

The standard approach to upload any managed form template is to go to central admin and select ‘Manage form templates’ and upload the form template. The process isn’t complete, the ‘status’ column should show as ‘Ready’, only then we can activate it to a site collection. Once we upload the status shows as ‘Installing’ and once the SharePoint timer job kicks in it completes the installation behind the scenes and the status is changed to ‘Ready’. The same happens with ‘Deleting’ which completes only when the timer job completes it.

This whole process is long and gruesome if we have to repeat for many forms so I posted some time back on how to use stsadm.exe script to upload/delete/update the managed form templates. That works great.

But it didn’t work for few days back, once the upload is done, the status remained as ‘Installing’ forever . I ran the ‘stsadm.exe -o execadmsvcjobs’ command which forces the timer jobs to complete. Even that didn’t help. Just to get rid of the form, I opted to remove the template which changed the status column to ‘Deleting’ which remained like that forever.

I then started looking out for the reasons behind this weird behavior, and I see that either there should be a problem with the form template itself or the server farm. I ruled out the first reason because, I was not able to complete the upload process for none of the forms.

So, the problem is with the server farm, in which we have a single application server, a single front end web server and a database server. For the upload process to complete, the form template has to be propagated properly to all the servers in the farm. For this propagation, there are 2 important services which should be ON and working, they are:
SPTimerV3 and
Run the following command to make sure those services are up and running on the servers in the farm:

  • net start SPTimerV3
  • net start SPAdmin

I checked the both on App and Front end servers and both those services were up and running. I was taken aback because this leads me to no where but back to the problem. After some time I ran those commands on the Database server too and I found that the SPAdmin service was not started on it. Once it is started all my form templates worked like a magic.

So just make sure the above services are up and running on not just the application and front end web servers but also on the database servers. Here is a good post which talks about the same.

UPDATE: I completely missed writing about how to undo the stalled status after uploading the form. Please follow the below instructions as per the post I mentioned above:

From Central Administration, go to the Operations page, under the Global configuration group, click on Timer Job Status.  On that page, look for timer jobs that have the name in the following formatting.  If you filename is FOO.xsn, it will look like:
Windows SharePoint Services Solution Deployment for “form-FOO.wsp”

See if there was a failure.  If so, go back a page, and go to Timer Job Definitions.  Drill down in the timer job definition that you care about and you can perform the following:

>> For the case of status stuck on “Uploading”:
1.       Try to restart the job if that is available.
2.       If restart is not available, delete the job, then attempt to upgrade again.

>> For the case of status stuck on “Upgrading”:
1.       Try to restart the job if that is available.
2.       If restart is not available, delete the job, then attempt to upgrade again.

>> For the case of status stuck on “Removing”:
1.       Try to restart the job if that is available.
2.       Else, Remove the job. (continue to step 3)
3.       Then, go back to the Manage Form Templates and try again to Remove the form template.

In simple terms, open the Timer Job Definitions and open the wsp entry you are having the problem with and delete it. Now go back to the ‘Manage Form Templates’ page and delete the problematic form template.


21 Responses

  1. […] InfoPath Managed Form Templates – upload status stuck or remains forever in ‘installing’ or ‘d… Possibly related posts: (automatically generated)Links (12/6/2007)Sharepoint 2007 BooksOffice 2007, SharePoint Server 2007 and Windows SharePoint Services V3 Link…Deploying pages to Sharepoint Site […]

  2. einqcflv rgyhtplc tbwouac mwilburt zlbanf tcjqksrpu waznkcs

  3. Thank you so much for this post! I had the SPTimerV3 service fail in the middle of an upgrade to a production envirnonment so this has helped me to get things back on track 🙂

  4. I am glad it was helpful. I know how crazy it would be watching that status stuck forever and ever..

  5. Thanks alot It really helped !!!!!!!!!

  6. thx a lot

  7. Hello
    This was verry helpful. I tried one whole day to resolve this. Not able. But wen I got this post it was just minutes job.

  8. Even I’m stuck with the same problem…I came to know that Windows SharePoint Timer Service was not running on my Server farm…u saved a lot of time.Thank you very much…

  9. hello svarukala!

    thank you for posting this… however, i have one big problem/question… in our case, we have a farm with 3 front-end servers and one DB Server. we do not have MOSS installed in the DB Server and thus, the services you mentioned above (SPTimerV3 and SPAdmin) are not running in there.

    as such, i am still stuck with the same problem and do not have ideas on how to proceed. do you have other ideas?

  10. Hi,

    I have the same problem as gezelle. We have 2 WFE, 1 index and 1 SQL. We dont have MOSS installed on the SQL box, so those services dont exist on that server. Any ideas on how to fix, besides installing moss on the server box?


    • Hi,

      Ok, I’ve solved my issue.

      you have to run the stsadm -o execadmsvcjobs on ALL your servers that have MOSS installed.


      • Yep – worked for me – the jobs weren’t running on our MOSS index and query servers.

        Ran the execadmsvcjobs command and it cleared the problems with hanging status.

        Cheers !

    • Dont install MOSS on the DB server. Try to run the following script on all the servers one after the other:

      stsadm.exe -o execadmsvcjobs sleep 5 net stop SPTimerV3 net stop SPAdmin sleep 5 net start SPTimerV3 net start SPAdmin sleep 5 iisreset

      If you dont hv sleep command on the servers.. run each step manually.

  11. Thank!!!

    That was realy help me a lot!

  12. Thanks a lot.. u saved me lot of time.

  13. […] to John Eugene’s Blog. Recently used links. Installing/Upgrading/Deleting InfoPath forms Info path installation Trouble Shooting Possibly related posts: (automatically generated) Hello World!Hello […]

  14. SharePoint is a piece of crap, but posts like yours make it a bit more tolerable for those of us who are stuck using it.

  15. I have tried the above suggestions but it did not work for me.
    I am installing my InfoPath forms via a feature.
    What did work was doing a force install. e.g.

    “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe” -o installfeature -filename “Matrix.InfoPathFormV2.0\feature.xml” -force

    Then doing uninstall. e.g.

    “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe” -o uninstallfeature -filename “sMatrix.InfoPathFormV2.0\feature.xml”

  16. Thank you! You are save my day! 🙂

  17. I am really happy to glance at this blog posts which carries tons of helpful data, thanks for providing these statistics.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: