on 05-17-2013 11:00 AM
Hi Folks,
When ever I am trying the DCN-push from the back end or send notification from work (As manual) also I am getting the error in the queue item as" wating for retry ". And I didnt get the any notification in my simu device. Earlier I used to get the notification as munual way when ever I have tried to push from SAP,Since that time onwords even manual way also I am not getting the notification.(I have deleted workflow and package, redeployed even still the problem persist.
Please refer below screen shot for the reference.
Could you please help to me to figure out the issue.
Appreciate your quick replay.
Regards,
Madhu.
By default, if an operation/object query invocation fails, it will block the queue and retry in 15 minutes (if the error is deemed to be recoverable) or 3 days (if the error is deemed to be unrecoverable). Those retry timeout periods are configurable (via context variables), and you can change the default behaviour to have it send a notification to the client instead of retrying (if you have a reasonably newer version of SUP). It will continue retrying until the operation eventually succeeds or the administrator manually removes the queue item. You can check the WorkflowClient trace logs to determine why it is failing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
David,
--I got a popup on the workspace after sending" send notification" from workspace.
--If I want to see log also,I am unluck guy becase I have only SDK installed in my lappy and deploying apps under the client server. Hence,I can just manitor in SCC.
--I want to know what is the exactly cause for the retry (Transform error) and how can I sort it out?
Regards,
Madhu.
- The popup in your workspace is likely unrelated to the transformer error.
- There are a number of potential causes for the transformer error, from the backend EIS not responding quickly enough, to a deadlock, to invalid authentication, to an update operation that didn't affect the required number of rows, to any of a huge number of other issues. To know for sure, you'll need to look at the server logs. Is there a reason you can't see them from SCC?
Hi David,
I have checked in the SCC server log, when I created the backend workorder(IW31),then I am getting error about resoure leak and admin failed and I dont have any retry error this time (If I check manully from the workspace it is working fine).
Please refer the below screen for your reference.
Thanks,
Madhu.
David,
I am keenly looking into this issue.
Madhu is trying to do DCN without payload. Once he trigger the DCN in SAP some authentication happens and authentication error occurs. He didn't configured any LDAP or SSO. And the MBO package is deployed into the "admin" domain.
I think the authentication happens against the SCC credentials once a notification reaches SUP. How the authentication scenario works based on the notifications?
I'm not sure what you mean by "SCC credentials".
There are a few layers of security here. The first is the authentication for the WF DCN, the credentials coming from the details of the message. The WF DCN will then go into the WorkflowClient module, where it will invoke an object query, passing in credentials as defined by the WorkflowClient.xml for that hybrid app (typically hard-coded, but it is possible for it to send a request for credentials to the client instead). When invoking the object query, the backend EIS will typically be invoked, which involves SUP passing in the credentials based on how it has set that up.
At this point, its not clear to me at which point in that process the authentication is failing.
One thing to note is that if you are using the "admin" domain rather than the "default" domain, you may need to append @admin to the username.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.