Solution deployment stuck at "delploying" stage
Hi,
We attempted to deploy a couple SharePoint solutions and they are both stuck at "deploying (scheduled at ...)" and we could not figure out how to resolve the problem.
Here is the background story on what led to this problem.
We have a SharePoint 2007 Form Server running on Windows Server 2003 hosting various sites such as help desk for intranet use.
Since we never created a development/staging server for SharePoint, our management decided to create one using the production SharePoint server as the blue print so all future development of SharePoint solutions can be done on the development server first.
The development server is a virtualized server created by our administrator using VMWare tools to replicate the production SharePoint server.
After the virtualized SharePoint server was created and given a different domain name, I noticed that its SharePoint Central Admin page is still pointing to the original SharePoint server although I can manually type in the correct domain name in the URL to connect. However, the databases used by the virtualized server is still the same production database used by the original SharePoint server.
Because I didn't want to make any accidental changes to the production database used by the virtualized server, I asked our administrator about re-creating the virtual server with a clean install Windows 2003 and then I will install SharePoint 2007 and re-configure everything manually. However, the admin suggested me try to "uninstall" SharePoint 2007 on the virtualized server and see if that would give me the clean Windows 2003 environment to start over.
So I agreed to do that but that turned ou to be a mistake.
I uninstalled SharePoint 2007 Form Server and Windows SharePoint Server components in "Add or Remove Programs" in the control panel.
After SharePoint 2007 is uninstalled on the virtualized server, we noticed that solutions previously deployed on the production SharePoint server all became "Not Deployed". As the result, several Infopath form templates used for intranet sites such as help desk request no longer load properly.
I attempted to re-upload the form template and deploy other solutions that need to be deployed and that is how we are stuck at the solution deployment stage.
Our administrator attempted and restored both the production SharePoint server's system drive image and databases used from previous day's backup but we continue to have the same problem.
It would be greatly appreciated if anyone can provide information on how this problem can be resolved.
Thank you very much.
Jason
Answers
- Hi Lambert,
Thank you for your information.
We didn't have the chance run SPSReports that you mentioned.
We went back to SQL Server and identified two more databases we did not restore: SharePoint_Config and SharePoint_Admin Content.
I think they are the default names used when our SharePoint server was originally installed by another admin.
Once these two databases were restored, Central Admin page still show the two solution at "deploying" stage. However, results generated by "stsadm -enumsolutions" command indicated that the solutions in question were already DEPLOYED so I ran "stsadm -retractsolution" command to retract the solutions then I was able to deploy them on the Central Admin web site.
So far everything appears to be normal now.
Jason- Marked As Answer bysaiyan0123 Monday, November 16, 2009 7:07 PM
All Replies
Hi Jason,
As the solution deploy is handled by timer jobs, please try to run the stsadm -o execadmsvcjobs on all of your SharePoint servers to force the administrative timer jobs immediately to run.
If this is not helpful for your issue, please help me to collect SPSReports on all of your SharePoint Servers to me for further investigation.
Workspace URL: (https://sftasia.one.microsoft.com/ChooseTransfer.aspx?key=7a1a158c-74c1-4887-a2fc-777622a1fc72)
Workspace Password: _cs^LWOyv2VoiKix
To capture SPSReports, please follow the steps:
1) Download the SPSReport tool from http://spsreport.codeplex.com/
2) Run the SPSReport.exe on the WFE and Application Server.
3) Choose option 3 (Full).
4) On your system a CAB file will be generated in the %systemroot%\SPSReports\Portal\rpt\Cab directory called %COMPUTERNAME%_SPSReports.CAB.
5) The CAB file will contain the reports generated by the SPS Reporting Tool.
6) Send the cab file to the workspace above.
Lambert Qin
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact mtngfb@microsoft.com
Sincerely,Lambert QinPosting is provided "AS IS" with no warranties, and confers no rights.- Hi Lambert,
Thank you for your information.
We didn't have the chance run SPSReports that you mentioned.
We went back to SQL Server and identified two more databases we did not restore: SharePoint_Config and SharePoint_Admin Content.
I think they are the default names used when our SharePoint server was originally installed by another admin.
Once these two databases were restored, Central Admin page still show the two solution at "deploying" stage. However, results generated by "stsadm -enumsolutions" command indicated that the solutions in question were already DEPLOYED so I ran "stsadm -retractsolution" command to retract the solutions then I was able to deploy them on the Central Admin web site.
So far everything appears to be normal now.
Jason- Marked As Answer bysaiyan0123 Monday, November 16, 2009 7:07 PM
