"SAM - Import Adobe User Subscriptions" failing with no thrown error

KHKSriram
Giga Contributor

3 weeks ago

Hi all,
Does anybody have any idea on this?

We’re facing an issue with the scheduled job SAM – Import Adobe User Subscription, which has been failing immediately since the Zurich upgrade.

Based on our investigation, we found that the Organization ID was missing on the connection page, and we added it again. But this time, the scheduled job does not fail immediately — it runs for about 5 minutes and then fails without any error message. We can see that it updates the subscriptions during that time but is not able to complete its job.

For further understanding, we checked the outbound HTTP logs, where we found that the URL adobeusermanagement is returning 401 and 429 responses. Does anybody have any idea on this?

We even tried updating the plugin Software Asset Management - SaaS License Management to the latest version.

Thanks in advance!

0 Helpfuls
  • 332 Views
3 REPLIES 3

dreinhardt
Kilo Patron

3 weeks ago

Hi @KHKSriram ,

we had a similar issue with Adobe after the upgrade and the advice was to setup a new direct integration for Adobe and this solved it. Give it a try, if not pls raise a case and share the solution with us.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

KHKSriram
Giga Contributor

Wednesday

Hello @dreinhardt ,
Thanks for your reply.

We raised a case with ServiceNow, and they confirmed that the issue was caused by the Zurich upgrade, where the Organization ID attribute was not inherited on the child alias connection form.

To resolve this, we created a new connection for the child account, after which the Organization ID became visible on the form, and the jobs started completing successfully.
Also it was confirmed by them, that these issue will be resolved in the next release(Australia).
Regards,
KHKSriram.



0 Helpfuls

KHKSriram
Giga Contributor

Wednesday

Hello @dreinhardt ,

 

We raised a case with ServiceNow, and they confirmed that the issue was caused by the Zurich upgrade, where the Organization ID attribute was not inherited on the child alias connection form.

 

To resolve this, we created a new connection for the child account, after which the Organization ID became visible on the form, and the jobs started completing successfully.

Also They confirmed that there are some issues with the Saas integrations in Zurich and they will be resolved in Australia release.

Regards,
KHKSriram.

 

0 Helpfuls