The SharePoint Unified Logging Service (ULS) log files may contain helpful information for troubleshooting issues with deployment of solution packages.
For example, the following error suggests a critical timer job error related to internal SharePoint problems persisting objects to the database. These errors also mention an "update conflict" as experienced when attempting solution deployment. This underlying issue may be preventing solution deployment and should thus be resolved. Contact Microsoft for additional support if presented with this error.
“The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) threw an exception. More information is included below. An update conflict has occurred, and you must re-try this action. The object IndexingScheduleJobDefinition Name=Indexing Schedule Manager on servername Parent=SearchService Name=OSearch is being updated by DOMAIN\username, in the OWSTIMER process, on machine SERVERNAME. View the tracing log for more information about the conflict."
By default, ULS logs are located in the SharePoint hive.
Note: For more information about ULS logging, see the following MSDN article. http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspx.
In your review of the log files, search for logged information during the time range in which the solution was scheduled to be deployed.
To aggregate all log files from SharePoint servers
Use the Merge-SPLogFile cmdlet in a SharePoint Management Shell window.