Skip to main content
manjit.1486
manjit.1486
June 4, 2024
Solved

The connected system data source does not exist or you have insufficient permissions to perform the requested operation.

  • June 4, 2024
  • 10 replies
  • 0 views

Hello everyone,

I am getting this error. 

The connected system data source does not exist or you have insufficient permissions to perform the requested operation.

I have already followed below steps:

1. Tested connection system - working fine.

2. Executed stored procedure - Working fine

Please suggest.

Thanks

    Best answer by luisb730547

    Got it! From my experience in all the projects I've been part of, we configure a 'System' swim lane with "run as designer" in that lane we would have write to db nodes, queries, or any other database related operations. When deploying to higher environments, always use compare and deploy, or deploy using a service account that will never be deactivated. This ensures that in higher environments your process models will continue to run smoothly. In your dev environment, all you would need to do is republish that process model, and things should return to working order.

    The issue with "run as initiator" is that it doesn't take into account if assignment changes, also if the particular user currently assigned the task gets deactivated it can break the process.

    Now, I know there are different schools of thought on this, but what I described above is what I've observed through my experience.

    10 replies

    davidj137213
    davidj137213
    June 4, 2024

    I guess the user you are using doesn't hace permissions to use the connected system,

    Try changing the user to admin, and testing again.....

    manjit.1486
    manjit.1486Author
    June 4, 2024

    It was working before as I am admin. It suddenly stopped working.

    L
    luisb730547
    June 4, 2024

    [mention:734d485eba7242aeab9bb03aafa409b0:e9ed411860ed4f2ba0265705b8793d05] when exactly are you seeing this error?

    I would suggest verifying the permissions of the user credentials used in the data source connected system. It's possible that the credentials you are using might not have the necessary permissions to execute queries against the specific table or view you're trying to access.

    A good way to check this is by trying to run a query directly against that table or view in the database using the same credentials. This can help confirm whether the issue is with permissions at the database level.

    Give it a try and let us know.

    manjit.1486
    manjit.1486Author
    June 4, 2024

    I have tested and executed procedure in database that is working fine.

    I got an issue with the node permission.

    It was:  Run as whoever designed this process model

    I changed this to "Run as whoever started the process"

    It would be appreciated if you can answer this - if this is a right way of changing this permission. Because the process was designed by someone else and his account is deactivated. Although this process was working fine after deactivating the account. But suddenly it misbehaves so I changed this node permission "Run as whoever started the process".

    FYI: this issue comes in DEV only. TEST and PROD is working fine.

    Please advice if it's good to change the permission from "Run as whoever designed this process model" to "Run as whoever started the process"?
    Thanks
    L
    luisb730547Answer
    June 4, 2024

    Got it! From my experience in all the projects I've been part of, we configure a 'System' swim lane with "run as designer" in that lane we would have write to db nodes, queries, or any other database related operations. When deploying to higher environments, always use compare and deploy, or deploy using a service account that will never be deactivated. This ensures that in higher environments your process models will continue to run smoothly. In your dev environment, all you would need to do is republish that process model, and things should return to working order.

    The issue with "run as initiator" is that it doesn't take into account if assignment changes, also if the particular user currently assigned the task gets deactivated it can break the process.

    Now, I know there are different schools of thought on this, but what I described above is what I've observed through my experience.

      Terms & ConditionsAccessibility statement