"No log id created for Process Chain"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2015 02:07 PM - edited 07-05-2021 04:04 AM
SAP jobs getting error occurred with log stating "No log id created for Process Chain"
- Labels:
-
Other Wireless Topics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2015 09:33 AM
I have no idea what your asking? Provide more detail to your issue so that we can better understand your environment and the issues at hand.
-Scott
*** Please rate useful posts ***
*** Please rate helpful posts ***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2016 08:17 AM
Did you ever resolve this issue? I have one SAP job that triggers a process chain that has had this error twice today.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2016 11:57 PM
I tried removing, and adding the PC again in the tidal . In some of cases it worked however for some SAP jobs it didnt work. best i could think, referring the PC to SAP to verify.
i would auggest you to delete jon and create again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2016 04:23 AM
Thanks for the reply. I had one job that returned the message "No log id created for Process Chain" twice in one day. Last night it ran normally without making any changes. If it returns to error-ing out when attempting to run I will try recreating the job as you suggested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2016 04:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2016 05:33 AM
I did find out that someone on our SAP BW team happened to modify and reactivate that specific process chain last night, so it seems that is likely what corrected the issue enabling the Tidal job to run properly this morning.
If we encounter this issue again I am planning on having them reactivate the process chain to see if that corrects it.
