Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 0 down vote favorite

I have a sharepoint content deployment job that until recently was working fine. Now however when I click on "run now" the job creates two entries and causes the SharePoint 2010 Timer Service to halt with the following in the event log:

The SharePoint 2010 Timer service terminated unexpectedly. It has done this 1327 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.

its immediately preceded by the following in the application log:

SharePoint Web Services Round Robin Service Load Balancer Event: Initialization Process Name: OWSTIMER Process ID: 3728 AppDomain Name: DefaultDomain AppDomain ID: 1 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:dcc23f2972df4ee38c5a6b12d7f58fcb#authority=urn:uuid:796a9cb5e3aa445db73c2d6c95c15bf9&authority=/Topology/topology.svc Active Endpoints: 1 Failed Endpoints:0 Endpoint List: /dcc23f2972df4ee38c5a6b12d7f58fcb/ProfileService.svc

Any ideas whats causing the timer to fail?

share|improve this question
Do you mind if we close this question, since this seems to be fairly specific to the precise circumstances of someone changing the hostname? – SPDoctor♦ Nov 8 '11 at 16:56
Not at all - feel free to close the question – Mauro Nov 8 '11 at 17:06
thanks......... – SPDoctor♦ Nov 8 '11 at 17:27

closed as too localized by SPDoctor♦ Nov 8 '11 at 17:27

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.

1 Answer

up vote 0 down vote

Never mind, someone had changed the host name entries in sharepoint, clearly there is some urls stored within the database that caused it to think that some urls were inaccessible. I added an Alternate Access mapping to the old url for Central Admin and it all worked magically again.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.