Add Access Tasks Discontinued with Message "Username is not associated with AccountName"

[n1khil]

Hey folks,

for one of our REST based application, we get getting this error "Username is not associated with AccountName" message in tasks and all the tasks are getting discontinued,

This was working fine before in v5.5, we had an upgrade to 24.1 recently,

Any idea what could be wrong with this?

Thanks

[rushikeshvartak]

• Does account is orphan?
• Make sure account is assigned to user

[n1khil]

It is not orphan, create account it’s working fine and it creates the account for the user but when adding the access the tasks are getting discontinued,

application is entitlements only so only add access task is created

[rushikeshvartak]

How task is generated via rule/request?

[n1khil]

new account tasks are through ars requests

[NM]

Hi @n1khil, worth checking if there is an account with same name in inactive state.

[n1khil]

Nope, it’s happening for all new accounts 

[rushikeshvartak]

Need logs when you ran job

[n1khil]

Looks like the issue was with security system being entitlements only, once I removed that option it started working as expected.

[rushikeshvartak]

if you are REST Connetor then don't use entOnly