SOLVED Configuration Manager SMS_TEM Error

[Keith Craig]

Hi. I was wondering if anyone had experienced this. I noticed that a number of ongoing software update deployments had reverted from 100% complete back to 0% complete. Having looked through the system status information there are no obvious errors relating to this issue. The only thing that appears to be wrong is that SMS_TEM is inaccessible. Configuration Manager Server Manager shows the service but with no status information. It can't be stopped or started and I can find no log for it. The information on SMS_TEM seems fairly limited so I'm not clear if its related but its the only thing I have seen so far that appears to be not working properly.

Any ideas where to start looking? Or any ideas how to reinstall SMS_TEM so I can at least rule that out as a possibility?

Thanks,
Keith

 

[Youssef Saad]

Hi Keith,

SMS_TEM has nothing with software update deployment, I suggest to you to start the troubleshoot with checking UpdatesHandler.log and UpdatesDeployment.log files in the client.

However, under Monitoring>System Status>Components Status, right-click on the SMS_TEM component and check the information & errors existed.

 

[Keith Craig]

Thanks Youssef. I've had a look at the logs. The UpdatesDeployment.log is showing errors on all clients that have already successfully deployed the updates.

Job error (0x87d00665) received for assignment ({3F455133-D43D-4A8F-AB2D-D02B8AA256ED}) action

I've created some new update jobs for these clients and they seem to work, but the older ones still error. I plan to delete the older ones and recreate them to see if that solves the problem. Still not sure what has caused the problem.

 

[Keith Craig]

The new jobs ran correctly. I am still no wiser as to what caused the old ones to reset and attempt to rerun.

 

[Youssef Saad]

The issue is solved?

 

[Keith Craig]

The issue is solved?

Yes thanks. The problem is solved, although why it occurred in the first place is still a mystery.