ConnectorError] {ExceptionType=java.lang.RuntimeException, LocalizedMessage=no schema specified for account create} (requestId: 9bdd6a62df754704aca6435413765e8c) why this error is coming can somenone pls help? it is coming for feed file connector
I would suggest tailing the saas connector logs using the SailPoint CLI and the command
sail conn logs tail
That should give you some additional context to where the aggregation is failing
check provisioning policy and account schema one more time.
Error:
“ConnectorError] {ExceptionType=java.lang.RuntimeException, LocalizedMessage=no schema specified for account create}”
This is likely occurring because the account schema for the connector has not been properly configured or discovered. This error suggests that when attempting to create an account, the system cannot find the necessary schema information.
To resolve this issue, ensure that the account schema and the create provisioning policy is properly configured for your connector.
I’ve just started seeing this in an environment I’m working on too. While I agree with the ideas in some of the other comments - I’m not convinced that this is an isolated issue and wouldn’t be surprised if there’s something bigger going on.
I’m seeing it on a flat file source we’re trying to open tickets for. What kind of source are you seeing it on?
hey @KevinHarrington your case is exactly the same i configured a SD for SNOW for ticketing purpose and attached a delimited file to that SD and then tried to request entitlement for that delimited file thorugh request center for a user and i am getting this eror
Has anyone submitted a ticket to SailPoint yet? Seeing it as well.
Check provisioning policy, account schema and the account ID attribute configuration.
Hey @KevinHarrington any update on this issue?
I’ve done digging on my side. From search, I can see that the request is getting all the necessary attributes, so I think it has something to do with the ticketing interface and not the source itself at all. And I misstated things a bit before - we’re ticketing from a JDBC source, not a flat file.
Since this was working until the middle of last week, I’m blaming changes to the ticketing process in general. Maybe this is wishful thinking, but the ticketing implementation of ISC needs a total overhaul. I have a ticket opened with SailPoint and I’ll keep this thread updated with any progress we make.
1 Like
great @KevinHarrington basically i havent change the configuration in service desk but still the error is coming. Today i found a strange thing one request geenrated ticket but other request gave me a error
Same error here, did you get any update from Sailpoint?
This config should be just simple but i`m stuck in the same issue.
Hi @KevinHarrington , I am facing same issue, were you able to solve the issue?
Hi @Rakesh_Singh_1234 ,
Any luck on this?
We’ve passed along logs and turned on debugging for the SaaS ticketing integration. No word yet.
I have a ticket with Sailpoint as well, the Engineering team is working on it!
Has anyone gotten a response back from SailPoint yet? We’ve also submitted a ticket that’s “under investigation”.
Just that the Engineering team is actively working on it! I message CSM, called SP tried everything because i have a go live soon!
Got a message that the fix has been put in place. Initial testing looks good. Hopefully things start working for you all as well.
1 Like
I found an issue here: When I configure a role with entitlements from distinct sources that goes through Service Desk, it gives an error when requesting this role:
sailpoint.connector.ConnectorException: expected 1 result
But if I request those entitlements directly, it works. So, I believe that it still needs some fixes!