Problems with installation from Orchestrator in AWS

Help
, ,
1

Hi Guys,

we are try to install the UiPath Orchestrator on a AWS Server. During the installation from the Orchestrator, we get this issues:

Ensure that the following user have these permissions on the database:

User Database Permission

[SQL User] uipath_user uipath Create, Write, Read

If you cannot provide the Create_Database permission, ensure that the databases are created before starting the applications.

Proceed with the installation?
[Y] Yes [N] No [?] Help (default is “Y”): y
Ensuring IIS URL Rewrite 2.0 Module is installed
IIS URL Rewrite 2.0 Module is already installed
New-Object : Exception calling “.ctor” with “1” argument(s): “Format of the initialization string does not conform to specification starting at index 116.”
At C:\Users\Administrator\Downloads\UiPathOrchestrator\Migration-Utilities.psm1:96 char:23

  • … ngBuilder = New-Object System.Data.SqlClient.SqlConnectionStringBuild …
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidOperation: (:slight_smile: [New-Object], MethodInvocationException
    • FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

Cannot index into a null array.
At C:\Users\Administrator\Downloads\UiPathOrchestrator\Migration-Utilities.psm1:104 char:2

  • $connStringBuilder["Initial Catalog"] = "master"

  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidOperation: (:slight_smile: , RuntimeException
    • FullyQualifiedErrorId : NullArray

Check-DatabaseConnection : Cannot bind argument to parameter ‘connectionString’ because it is an empty string.
At C:\Users\Administrator\Downloads\UiPathOrchestrator\Migration-Utilities.psm1:107 char:66

  • … ection = Check-DatabaseConnection -connectionString $masterConnString
  •                                                     ~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidData: (:slight_smile: [Check-DatabaseConnection], ParameterBindingValidationException
    • FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Check-DatabaseConnection

User ‘EC2AMAZ-3J77EUL\Administrator’ can not access the database server instance.

Someone who can help us with this issue?
I would appreciate any hints or help.
In advance thanks for your support.

kind regards,

Sven

2

Any ideas?

3

Hi Sven,

Please try this:
After installation, run from the sql console the following code (replace UiPath-Test-X with your database name and UIPATH\OVI$ with the name of your domain and machine).

CREATE LOGIN [UIPATH\OVI$] FROM WINDOWS
GO

Use [UiPath-Test-X]
GO 
EXEC sp_addrolemember 'db_owner', N'UIPATH\OVI$'
GO
4

Hi,

thanks for your response.
But the problem is, that it crashes during the installtion routine. Result is, the db is empty.
We want to login at the db with a SQL user and not with a user from the AD, linke in the installation manual.

kind regards,

Sven

5

Hello Sven. I’m guessing that you are using the “Install-Orchestrator.ps1” script? We’ve discontinued the official support for that script, so the recommended way of installing would be using the UiPathPlatform.msi installer. Could you please tell me what version of Orchestrator are you trying to install? I’ll provide a link with the MSI to install that specific version.

6

Hi,

we’ve used version 2017 of the orchestrator.

7

We’ve try to install first the UiPath Platform msi. During the Installation, we get the following error:

Orchestrator Database Settings:

Failed validate SQL connection.
Format of the initialization string does not conform to specification starting at index 100.

8

Here is the error message with the msi package:

orchestrator_Error1

After that failed, we have used the manual from that url:
https://orchestrator.uipath.com/docs/installation-using-scripts

The ODBC Conneection test was succesfully.

orchestrator_Error2
orchestrator_Error2817×455 19.3 KB

9

Anything new for that Support Ticket?

10

Hi Sven,

Please open a ticket using the link below, as private information may be required in order to figure out what’s causing the error:

Note that you’ll have to submit the ticket using your company email address. And please provide the link to this post in the details.

Thanks,
Viorela

11

We’ve fixed the problem and were now able to install the orchestrator.

12

Can you share here how you solved it?

13

There was a invalid special sign in the password for the database user. The error message was not clearly!

14

Hi sven_85, how safe is it installing the orchestrator on a cloud? By any chance if AWS is hacked, data you are processing on the terminals can be leaked right? if the data on the terminals is NPI(confidential) data, then it sould be security violation right? Please let me know if my question is wrong.

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.