UiPath Orchestrator Database Issue

orchestrator
error
install

#1

Hello,

I’m trying to install UiPath Orchestrator website on a remote machine running Windows Server 2012. The problem is when i’m trying to introduce the credentials for the SQL Database. The DB is on another machine, and i have access to it through SQL Management Studio with the same credentials that UiPath installer refuses.
The server and the database have all the roles and configuration necessary because there was an Orchestrator instance running on the machine and working correctly a couple of days ago.

Capture

Thank you!


#2

Hi!

If you are sure that the credentials are correct, then, the only that comes to mind is, that either the SQL host is incorrect, or the connection to the host can no longer be established from the server where the orchestrator is running.

Just my guess tho :slight_smile:


#3

@BogdanMocanelu,
You have to debug;).

  • what kind of credentials are you using? SQL authentication or an active directory user?
  • How do you connect? By dns name, ipaddress?
  • Are you connecting to a clean database or new fresh one?
  • Do you have multiple instances on that server? If so, make sure you set the right instance
  • The databasename is case sensitive, make sure it matches exactly!
  • your initial test worked with Management Studio. Was that on the orchestrator server or from another client?

Some checks you can do:

  • always check the SQL connection credentials.
  • Check again the configuration (correct credentials, requirements, etc).
  • Check the eventviewer on the orchestrator machine and/or SQL server. You might can find a notice/warning/error about the connection.
  • from your orchestrator server: run a powershell command to check if the SQL connection is working at all or it might be a issue just in the Uipath installer
    see this for example: https://stackoverflow.com/questions/29229109/test-database-connectivity

can you give an example of the connection you are using? (don’t give real usernames/passwords!)
see: https://files.readme.io/73c96f5-setup_database_settings.png

Problems i had on server2012R2/2016 (it can occur)

  • Don’t use an AD user, but a normal SQL user with at least db_owner rights.
  • Make sure your databasename matches the exact name on the sql server. It is case sensitive.
  • is port 1433 open for the orchestrator server to access the SQL server? (Check firewall rules and TCP connections).

What is your setup?

  • Are you running an upgrade or fresh installation (because you said you had it running before).
  • If a fresh installation: did you remove all the old programs/files? (you can also select that from the installer).
  • Which version of Uipath are you trying to install?

Problems i had with this part is that an active directory user might not work as SQL connection. This problem occurd on 2012R2 as well as on 2016 server. I found out that in the logfiles of orchestrator installation the computername is trying to access the database, instead of the windows user i had set. So please try with a regular SQL user.

SQL connection:

  • Create a new SQL user (SQL authenticationmode, Not an ad user) with db_owner rights and try it again.
  • Orchestrator installation: Try to set the host as a DNS address. If it doesn’t work, use the ipadress of the sql server.

Even when the credentials are correct always check if the database has the tables inserted. Uipath doesn’t check if the credentials are valid when installing.

Have fun debugging:D.

Please post your results or any feedback you have. It can be helpfull to anyone


#4

@ jvanmarion
Thank you for answering,

I am using SQL authentification. I tried both dns name and ip address, none of them works. I’m connecting to a clean database i’ve used before, with the same user. The database name is correcty, case sensitive related. The initial test with Management Studio works both from orchestrator server and another client.

The problem occured when i tried to upgrade from 2018.2.2 to 2018.3.1, i got an error that said that the connection with the database have been refused and the timeout was reached and therefore this deleted the old orchestrator instance 2018.2.2 that worked correctly. Now i’m trying a fresh installation(i tried 2018.1, 2018.2 and 2018.3 with no success). I decrypted the old web.config file, i am sure i’m using the right SQL credentials.

I’m not using an AD user, just a regular one with db_owner rights. The database is fine, i have all the tables and the data correct.


#5

Did you check the eventviewer for details? You have to start somewhere what is causing the issue. If possible, go back to the timeframe where the problem started. You might can find usefull information of the SQL connection error.

In case you want a complete fresh install, this is what i would try/do to rule out any previous issues.

  • Orchestrator: remove all the old files (IIS instance + webfiles)
  • Orchestrator: remove all uipath applications (control panel > uninstall programs)
  • Orchestrator: reboot the machine
  • SQL: create a new database and also a new user which is connected to that database with db_owner rights on that database
  • SQL: or create a user with dbcreator rights so Uipath can create the database by itself.
  • Orchestrator: make sure you have checked everything on this page: https://orchestrator.uipath.com/docs/prerequisites-for-installation
  • Install Orchestrator again (platform installer), (2018.2.x / 2018.3.x / 2018.4.x with the new credentials you have made

if it still fails, you have to check your eventlogs again to see if any notice is popping up about your problem. I don’t have another solution at this point for you.


#6

telnet “computername” 1433 is working, meaninng that the connection between SQL Server and Orchestrator Server is up.

i have removed all the old files from orchestrator server, unistalled all the uipath applications.

I tried every version of orchestrator, still no success.


#7

What about the other things? Did you checked/tested that too?

  • Did you check the eventviewer for details? You have to start somewhere what is causing the issue. If possible, go back to the timeframe where the problem started. You might can find usefull information of the SQL connection error.

  • SQL: create a new database and also a new user which is connected to that database with db_owner rights on that database

  • SQL: or create a user with dbcreator rights so Uipath can create the database by itself.

  • Orchestrator: make sure you have checked everything on this page:

Another thing you can try with the sql user. create a sys_admin sql user. Don’t create a database, but let Uipath create one itself. (I normally would not use a sysadmin account for it), but it could be an sql rights issue.

At this point i don’t have more options for you. It might be network/server related. I don’t have access to your logs, so you have to provide us with that information. I think it is still SQL / account related. The only way i can reproduce this problem is with wrong credentials or wrong servername. Please try the new user to rule out what could be the problem.


#8

I cannot create a new database, i have to use the existent one because it’s related to the preproduction environment on my workplace, it has all the data we need so a new, empty database it’s not an option for me.

In the Event Viewer on Orchestrator server there are 3 errors that occurs repeatedly:

  • Failed to obtain DB connection from data source ‘default’: System.Data.SqlClient.SqlException(0x80131904). Cannot open database “UiPath” requested by the login. The login failed for user “UiPath”.

  • Cannot open database “UiPath” requested by the login. The login failed for user “UiPath”.

  • Cannot acquire database lock on UiPath.Orchestrator.SystemJobs. Cannot open database “UiPath” requested by the login. The login failed for user “UiPath”.