Service content update not working after SP26 - impacts EWA

[Former Member]

Something has changed in the realm of "service content" with SP26.

I have the job "SM:SERVICE CONTENT UPDATE" scheduled daily.

Its settings are to download and apply any service content updates it finds when it checks.

The job runs early in the day - should I change it to run late in the day?

Is something else checking for service content updates?

Both "self diagnosis" and "SM:EXEC SERVICES" are reporting outstanding content updates ("SM:EXEC SERVICES" by dumping DYNPRO_SEND_IN_BACKGROUND).

Should "SM:SERVICE CONTENT UPDATE" and "SM:EXEC SERVICES" run back to back?

Ken

[JaredS · Accepted solution]

I usually recommend that the Service Content update run around 30-45 minutes before sm:exec services.

This way, it will have the latest data.

Regards,

Jared