Using Bartender with Amazon (AWS) RDS Follow

0
Avatar
Nick Powers

So I have installed Bartender on an EC2 instance on AWS.  I set up a SQL Server Standard Edition via AWS RDS.  I am now entering the endpoint into the Bartender Database Setup and I am getting a #1047 error "Connection to SQL Server XXXXX could not be made".  My endpoint looks something like this: 

company-bartender-prod.xxxxxxxxxxxx.us-east-1.rds.amazonaws.com

I can successfully connect to the SQL endpoint using SSMS installed on the EC2.  I also manually created a UDL file on the server and tested the endpoint connection successfully.

Anyone else have this issue and have determined a resolution?

7 comments

0
Avatar
Gene Henson
Moderator

Hi Nick,

I've just tested this with a Server2016 EC2 instance and SQL Express on RDS. It seems to work OK for me. There is one thing to note. According to the following article, you should put the port number on the end of the server string:

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToMicrosoftSQLServerInstance.html

Here's a screenshot of the setup that worked for me (I don't have any databases created, I just wanted to make sure I could connect to the instance): 

Let us know if that helps.

0
Avatar
Nick Powers

Cool.  I am logging in to try that solution.  Will let you know.

0
Avatar
Nick Powers

So I downloaded the latest version of Bartender and are going through the setup process for the database.  The screen that errors out is this - which is not what you are using above.  The endpoint name is too long for the text box.  

 

 

 

0
Avatar
Gene Henson
Moderator

Nick,

I just created a ticket for this. I see the same problem in the system database setup (I was using the document database connection before). This may be a BarTender bug, but we'll look into it for you.

0
Avatar
Nick Powers

Thanks Gene.  I have a feeling that this is a bug based on what I am seeing.  I am trying to get our system administrators to lessen the length of the endpoint under 50 chars.  Once we get that done I will post an update unless you beat me to it with an update.

0
Avatar
Nick Powers

Gene,

 

Reducing the length of the endpoint works.  Unfortunately, just got me to another error, which is related to the permissions needed to install the Bartender database.  The lack of specific documentation on the setup of things sucks.  Additionally, if you go through the wizard and use an already created database (blank) and it fails, the only thing you can do to get back to the wizard is to delete the database, uninstall Bartender (which it doesn't do well, leaves accounts created and Print Portal website still in IIS), and reinstall.

There is a way to manually install the database by using SSMS or other SQL script capability and work you way through the scripts populating the variables correctly and hoping for the best.  I would rather just have this stuff work.

 

-Nick

0
Avatar
Nick Powers

So after going around and around, I ended up going to C:\Program Files\Seagull\Bartender Suite\Database and editing the CreateDatabase.sql file using SSMS.  We had given ourselves the highest level of permissions for a user available on a RDS instance, you have to remember there are things that aren't possible or available on RDS, and could never get the wizard to install the database.  I found as I removed parts of the script and ran it in chunks that the transaction checking/rollback lines caused issues.  I removed those parts, replaced the variable names with the right values and got everything to run.  I then had to go back in and run the wizard.provide the connection information for the RDS instance, select my database (I went with the default name of Bartender), and finish the "setup", which is the wizard setting the configuration files for the applications after it verifies that the database is set up and what version it is.  

So to summarize:

1.  When you create your RDS instance for hosting a Bartender System Database, make sure your endpoint name is less than 50 characters long.

2.  I recommend, going directly to the CreateDatabase script, removing the transaction rollback elements and running the script in chunks, making sure to replace the pass through variables with local variables or hardcoded values and running things through, verifying each step of the way that the database objects are being created correctly.  

3.  Run the Database Creation Wizard and link the Bartender applications to the newly created Bartender database.

Please sign in to leave a comment.