Skip to content

Troubleshooting

Troubleshooting

  • Service Startup Failure: Check the sm_out.log file in the logs folder of the BotCity Studio SDK. Alternatively, review the Event Viewer under Windows Logs > Application.
  • Configuration Issues: Ensure all settings are correctly defined and match the system specifications.
  • "Incorrect password" (STATUS_LOGON_FAILURE [0xc000006d], STATUS_ACCOUNT_LOCKED_OUT [0xc0000234]): Type the password manually in the terminal, without using ctrl+v (copy and paste).
Access Denied when running bots through the Session Manager

Problem scenario

When running bots through the Session Manager, the Access Denied error occurs. This issue is generally related to the permissions of the folders used by the Runner and the SDK during bot execution.

Common cause

The Session Manager and the Runner do not need to be run as administrator.

However, if the Runner was run as administrator at some point, or if the SDK installation was performed with elevated privileges, some essential folders may have been created with restricted permissions.

The affected folders include: logs, venv, run, and bots.

When the Runner is run without elevated privileges, the bot cannot access these folders, resulting in the Access Denied error.

Note

Installations made directly at the root of C: often require administrator privileges to create and manipulate files. For this reason, it is not recommended to install the SDK directly on C:. Prefer user directories or folders with appropriate permissions.

Recommended solutions

Option 1: Delete the problematic folders

  1. Close the Runner and the Session Manager.
  2. Delete the logs, venv, run, and bots folders.
  3. Restart the Session Manager and run the bot again.

The SM will recreate the folders with the correct permissions, allowing execution without administrative privileges.

Option 2: Reinstall the SDK

  1. Close the Runner and the Session Manager.
  2. Reinstall the SDK without running it as administrator, preferably outside the C: root.
  3. After installation, run the Runner normally.

This approach ensures that all folders created by the SDK and Runner have permissions compatible with users without elevated privileges.

Best practices

  • Avoid running the Runner or the Session Manager as administrator, except in specific maintenance cases.
  • Install the SDK in directories that do not require administrative privileges (avoid C:\).
  • If you need to change permissions manually, check the ownership of the logs, venv, run, and bots folders.

For further assistance, contact our support team.