"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
  • 267 Views
3 REPLIES 3

k_lutz
Giga Sage

2 weeks ago

hi @KHKSriram 

 

Where is that URL string coming from? In the KB2670715 on the HI site, it mentions these three endpoint URLS:

 

In our setup for credentials / connections we are using the first one for North America.

 

Are you getting a token when you check your connection?

0 Helpfuls

KHKSriram
Giga Contributor
In response to k_lutz

yesterday

Hello @k_lutz  ,

 

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 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

k_lutz
Giga Sage
In response to KHKSriram

4 hours ago

Hi @KHKSriram 

 

We are still on Yokohama but will be testing the upgrade to Zurich in April...so it's good to know there is that issue around the organization ID and will check it out when we do our testing.

 

Glad to hear that you were able to get it working!

0 Helpfuls