none
Program re-run behavior?

    Question

  • I have a mandatory advertisement to install an application at 8:30 PM. Recurrence is set to "None". The program rerun behavior is set to "Rerun if previous failed".

    1:30 PM - The client receives the advertisement (Status Message ID 10002).
    8:30 PM - The client starts the program (Status Message ID 10005).
    8:45 PM - The program completes successfully (Status Message ID 10009).
    8:45 PM - The program will not be run because the previous attempt was successful (Status Message ID 10040).

    Any idea why the client tries to run the advertisement a second time immediately after successfully completing the installation?

    Thanks,

    RS

    mardi 22 février 2011 18:02

Réponses

  • Yes - but, if it is persisting a request to CAS (Content Access Service), then you will probably also need to look there... I have a hunch there is an issue with the content, CAS.log might lead you to Location Serivces (LocationServices.log) as that is who it asks to find the content. If you could coordinate the three logs around the date/timestamp of this entry & post the relevant log snippets from each it would help - especially so if you can tell us the PackageID of the Package the Program is part of. Using the Trace32 tool from the toolkit should allow you to open all three log files simultaneously for this coordination.
    mardi 22 février 2011 23:49

Toutes les réponses

  • Hi,

    Check the exemgr.log on the client, it might give you some more details.


    Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
    mardi 22 février 2011 18:23
  • Thanks for your reply.

    I have looked at the execmgr.log file on the client.  Not sure excatly what I'm looking for.

    The only thing that caught my eye was a line in the log that referred to a "persisting request".  Would it be helpful to post a snip of the log?

    RS

    mardi 22 février 2011 18:38
  • Yes - but, if it is persisting a request to CAS (Content Access Service), then you will probably also need to look there... I have a hunch there is an issue with the content, CAS.log might lead you to Location Serivces (LocationServices.log) as that is who it asks to find the content. If you could coordinate the three logs around the date/timestamp of this entry & post the relevant log snippets from each it would help - especially so if you can tell us the PackageID of the Package the Program is part of. Using the Trace32 tool from the toolkit should allow you to open all three log files simultaneously for this coordination.
    mardi 22 février 2011 23:49
  • Thanks for your reply.  It appears that the behavior is a result of a misconfiguration on the package program I am using.  The application installer I am using restarts the computer after installation completes.  In the Properties~General tab of the program, I had selected "No action required" for the "After running" value.  After changing this value to "Program restarts computer", the behavior was as expected.

    Thanks again for your help.

    RS

    vendredi 25 février 2011 15:23