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

manjit.1486 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.

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

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.

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.

I agree with you. I deploy the application with service account that's why it is working fine in other environments.

Does this mean I need to change this to "Run as whoever designed this process model" and republish the process?

Yes, that's what I would do. 

Thanks for the information. I just did the same. Let' see what happened. I will keep posted here.

Hi Luis Beteta  It worked. Thank you so much.