Solutions Deployment Hungs up on Deploying/retracting in MOSS 2007

Problem: During the execution of a retraction/deployment the timer job may hang showing ‘Retracting’ or ‘deploying’ and never completes

Cause: This is cause from one of the WFE not being able to finalize the retraction or deployment.

Solution: For each WFE in the farm execute a stsadm.exe -o execadmsvcjobs. I had follow up these two good articles to come out from deploying /retracting status.

http://msmvps.com/blogs/shareblog/archive/2007/12/27/process-appears-hung-when-deploying-retracting-solutions.aspx

http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx

But what next when I try to deploy/retract the solution again. It hung’s up.  So I tried to figure out whats the problem causing this thing. I checked in my Timer job status (Central Administration>Operations>Timer Job Status) and it show that the Solution is tried to deploy on my one WFE and the index server.   I had not found any deployment on my other WFE So I had executed the command stsadm.exe -o execadmsvcjobs manually on the other WFE server. And it works like a charm the solution deployed/retracted successfully.

Also I had tried to check the time of my servers and my CA web application to confirm that they both are on the same time zone sometime this may also create a problem for deploying/retracting the solutions on the servers. In my case they are on the same time zone. To check the time zone for your CA site just

GO TO

Central Administration>Application Management>Web Application General Settings

Select your central administration web application. In Default Time Zone just checks out the time to match with your servers. If it’s not matched then select the appropriate time zone and click OK.

Thanks.

Feedback appreciated.

refrences :

http://www.alexthissen.nl/blogs/main/archive/2007/07/18/removing-malfunctioning-windows-sharepoint-services-solutions.aspx

http://msmvps.com/blogs/shareblog/archive/2007/12/27/process-appears-hung-when-deploying-retracting-solutions.aspx

http://www.sharepointps.com/blog/?tag=/deployment

Event ID 7888, Event ID 5555

Category : Office server General

Event Id : 7888

 

 

A runtime exception was detected. Details follow.
Message: A duplicate site ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (http://xxxxxxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.

Technical Details:
Microsoft.Office.Server.UserProfiles.ProfileSynchronizationDuplicateSiteIDException: A duplicate site ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (http://xxxxxxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.RegisterSitesForSynch(Guid[] rgGuid, Int32 nGuids, Object dummy)
at Microsoft.Office.Server.UserProfiles.SynchCollection`2.FlushAdds()
at Microsoft.Office.Server.UserProfiles.SynchCollection`2.Add(T objAdd)
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.AddRemoveSites(String strFirstChangeToken, SPChangeToken lastChangeToken)
at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentDB()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

 

Category: User Profiles

 

Event Id: 5555

 

 

Failure trying to synch web application xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx , contentDB xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Exception message was A duplicate site ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx(http://xxxxx) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm –o preparetomove. If this is the cause the stsadm –o preparetomove command can be used with the –oldcontentdb command line option to resolve this issue.

 

stsadm -o sync -ListOldDatabases 0

stsadm -o sync -deleteolddatabases 0

 

Deleted sync information for DB f112b6ea-4589-4859-b81d-26c9962a0ef0

Deleted sync information for DB 97b34344-77b0-405d-b99c-46bf429b8189

Deleted sync information for DB 61bba9f6-0162-4b51-91b5-68fade5edfe6

Deleted sync information for DB 0e95be0c-cb73-4b4e-8f06-03f07d4e09f7

Deleted sync information for DB fdc41cfd-9ad9-463b-86ee-067d09ecdc50

Deleted sync information for DB 02629f3d-26ae-4e8e-b3ac-06940f098a16

Deleted sync information for DB 25aaf049-afb1-42de-b773-1e854e636c62

Deleted sync information for DB 89b6c448-2d11-4121-9f87-282690b24ed0

Deleted sync information for DB 16746235-41f2-4296-ac9c-29123e17e87a

Deleted sync information for DB 518f7fa4-d7e0-4dd5-86ec-2fb4e2673c04

Deleted sync information for DB 6cae50c9-1e82-4699-849c-42def07acc26

Deleted sync information for DB 16413071-01c5-4dbc-9231-4465befaa8f7

Deleted sync information for DB e9b2fc09-a10e-447a-a4a9-4778b6c933d4

Deleted sync information for DB 0f35bc2b-954b-4bcf-9f71-48a2e9baf511

Deleted sync information for DB 333759c8-832d-4365-92cc-5cebc99b0bb1

Deleted sync information for DB 62c953d9-2a5b-4d7f-9ad2-65cef454fa1f

Deleted sync information for DB 76131bfd-c709-4cfc-a7e0-6c6351f2f89b

Deleted sync information for DB 2cb015f1-47e5-41e0-880d-6d1bf1f6c662

Deleted sync information for DB 17749ae9-8f6c-4bf6-9f04-7545ebc03cb1

Deleted sync information for DB 2ed4aa45-849d-4bcf-bee9-7c2d61b8328d

Deleted sync information for DB 09232a6d-7ea1-4e8e-a003-8248b124ca10

Deleted sync information for DB 9558a565-18d6-4426-9c41-964af8d2619b

Deleted sync information for DB 61b0eb8f-46ab-4454-afa5-abe1a4f4dfb9

Deleted sync information for DB 6f50d830-fc75-41b4-b4d3-c164739a79e5

Deleted sync information for DB a89ceb7d-b1c2-4a41-ac28-d9184e0d082d

Deleted sync information for DB bf31d2b7-ac56-4977-a7bd-d91c49095fe0

Event ID 7078, Event ID 7079

I am getting two warnings for event id 7078,7079 in my Event viewer on my moss servers on regular time intervals and these bugs me up.

The warnings are 

Event Type: Warning
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 7078
Date: x/xx/xxxx
Time: 8:14:14 PM
User: N/A
Computer: abcdef
Description:
Job ‘Distribution List Import Job’ failed. It will be re-tried again in 120
second(s).

Reason: Failed to obtain crawl status.

Techinal Details:
Microsoft.Office.Server.UserProfiles.UserProfileException: Failed to obtain
crawl status.
at Microsoft.Office.Server.UserProfiles.SRPSite.IsImportInProgress(String
contentSourceName)
at
Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.IsProfileImportInProgress()
at
Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.IsImportInProgress()
at Microsoft.Office.Server.UserProfiles.DLImportJob.Execute()
at Microsoft.Office.Server.Administration.JobHandler.Execute(Object
state, Boolean timedOut)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 7078
Date: x/xx/xxxx
Time: 8:14:14 PM
User: N/A
Computer: abcdef
Description:
Job ‘Distribution List Import Job’ failed after 3 tries and 180 second(s).
Will not try again.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp

 

Resolution :

Go To Central Administration > Application Management > Manage this Farm’s Shared Services

check all the SSP’s that it is set up with index server. The warning is thrown because the index server of one or more of ssps are not set up.

you can check the index server by follow this steps for each SSPs.

1. Mouse-over name of your Shared Services Providers.
2. Select Edit Properties of the SSP in menu.
3. Assign an INDEX to the SSP  at bottom of page.

HOPE THIS WILL HELP YOU GUYS. Please COMMENT ON IT iF ITS HELP TO YOU.