Usually when an execution package fails to start it is due to another already running, then in the event viewer we get a message like this:
Here, we see that the issue is due to another package.
Now I have noticed that we occasionally also get messages like this one:
Difference being that it does not show which ‘other’ package is causing this issue.
Is this a common occurrence?
Best answer by bas.hopstaken
Hi @sierd.zuiderveld ,
You can check in the task manager in the details if there is a timextender.exe process running using PID 10520. You can also see the user that is running this process. If you check the execution log history in all execution packages and you click the ‘Execution Package’ button for each log. You will find the Process ID that this package is/was using. This way you can find the package that belongs to PID 10520.
You can check in the task manager in the details if there is a timextender.exe process running using PID 10520. You can also see the user that is running this process. If you check the execution log history in all execution packages and you click the ‘Execution Package’ button for each log. You will find the Process ID that this package is/was using. This way you can find the package that belongs to PID 10520.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.