My stored procedure sql is working in attended but not working in unattended or remote debugging unattended, so how to fix this, any suggestions please
Hi @Sathish_Kumar5 ,
If your SQL stored procedure runs fine in Attended mode but fails in Unattended mode
it is usually because the unattended robot runs under a different user account that does not have the required database or environment permissions.
Also you can check with the following details:
- Grant SQL/database permissions to the Unattended robot Windows user, or
- Use SQL Authentication instead of Windows Authentication
- Store the connection string in an Orchestrator Asset
- Ensure required SQL drivers are installed for the unattended robot
2 Likes
i will check and let you know
1 Like
Hi @Sathish_Kumar5 ,
This is usually due to environment or authentication differences, and it’s a verified issue. In attended mode, the bot runs under your user context, but in unattended it runs under the robot service account, which may not have access to the database. Fix it by ensuring the unattended robot account has the same DB permissions, connection string, and network access. Also verify SQL authentication vs Windows authentication, firewall rules, and that the connection does not rely on user-specific settings (like trusted connections).
1 Like
Are you using same user profile in both modes ?
When you want to run in unattended mode, it should be in service mode.
If the UiPath robot is installed in service mode , a service with the name "UiPath Robot " should be visible in services.msc .
Also, please note that for the Unattended Robot, we properly log off/sign-out from the Robot machine and not disconnecting before triggering the job.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.