Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Solutions Not Deploying...

  Asked By: Alec    Date: Dec 15    Category: Sharepoint    Views: 3465

I have deployed a solution using the deploysolution stsadm command.

When I look at the solution management page in central
administration, I see that a timer job has been created and is set to
deploy at the time I ran the deploysolution stsadm command.

However, this timer job is never executed. I have waited 15-20
minutes so far and nothing has happened. The timer job is not
executed even if I run the execadmsvcjobx stsadm command. Actually,
it reports that the job is execute but nothing happens.

Has anyone seen this before? Can anyone explain what may be
happening?

The way I am deploying the solution has not changed in the last few
days and it worked then.

Any help will be greatly appreciated.

Share: 

 

7 Answers Found

 
Answer #1    Answered By: Ross Watkins     Answered On: Dec 15

Is SPTimer Running?
What domain credentials is it running as?

Go into Services from the Control panel and find Windows SharePoint
Timer. If it is running, you may want to even restart it and see if it
starts the job.

What does your event log say?

 
Answer #2    Answered By: Jeremiah Wallace     Answered On: Dec 15

Also try the command:

net start SPAdmin

 
Answer #3    Answered By: Tony Freeman     Answered On: Dec 15

That is odd, i'm having the same issue. I have tried all of the commands
suggested below, but the results are the same. I'm using a local account with
admin access to the server.

Here are the error messages i'm seeing:

There is already an object named 'LookupItems_ID_PK' in the database. Could not
create constraint. See previous errors. at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean
breakConnection) at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj) at
System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName,
Boolean async) at
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result,
String methodName, Boolean sendToPipe) at
System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at
Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command) at
Microsoft.SharePoint.Deployment.SPExport.SerializeLookupListMap() at
Microsoft.SharePoint.Deployment.SPExport.SerializeSettings() at
Microsoft.SharePoint.Deployment.SPExport.Run()

The changeToken refers to a time  before the start of the current change log. at
Microsoft.SharePoint.Deployment.SPExport.ThrowInvalidChangeTokenError(DateTime
minChangeTime, Int32 minChangeNumber) at
Microsoft.SharePoint.Deployment.SPExport.GetIncrementalChanges() at
Microsoft.SharePoint.Deployment.SPExport.CalculateObjectsToExport() at
Microsoft.SharePoint.Deployment.SPExport.Run()


Any ideas on a possible cause?

 
Answer #4    Answered By: Danny Shaw     Answered On: Dec 15

Did a solution  deployment/feature activation fail in the middle, leaving
remnants behind that are now considered duplicate?

 
Answer #5    Answered By: Benjamin Wright     Answered On: Dec 15

The last content deployment was about a month ago, and succeeded. All of the
features that have been activated have been running since the environment was
setup, and i'm the only one with access to the servers, so additional changes
are not likely. Is there anyway to clear out any leftovers from past jobs that
may be causing problems?

 
Answer #6    Answered By: Royce Orr     Answered On: Dec 15

Are you up to date with all your patches? Daylight savings used to end
on the last Sunday in October, which was two days ago...

 
Answer #7    Answered By: Laura Walker     Answered On: Dec 15

And discussions that I have seen today seem to indicate that the patches
may have only "fixed" the new start times for daylight savings.

I have not seen a definitive answer on this, but we had some solution
deployments go flaky yesterday and so did others on the boards.

 
Didn't find what you were looking for? Find more on Solutions Not Deploying... Or get search suggestion and latest updates.




Tagged: