Sometimes the SQL connection between Argos Manager and the SQL instance that the Argos database lives in can be disrupted. This will cause Argos Manager not to open properly and display a message like this:
Let’s look together at some of the reasons for SQL connection difficulties:
Reason 1: The Basics
First off, let’s check the obvious:
-Is the SQL Server service (you can view all services at start>run>services.msc on your server) started on your Argos SQL server?
-Are your SQL server\instance info (YOURSERVERNAME\Argos by default), the stored SQL credentials (sa/s3p14_lin3 by default) and database name (Argos7 by default) all correct?
Usually neither of these are the culprit, but I’m glad we checked to be sure!
Reason 2: TCP/IP and Named Pipes Protocols Are Blocked
-First, let’s make sure both the server and workstation are allowing both protocols. On each, type in “cliconfg” at start>run (or just hit the Windows key first on Windows 8/Sever 2012).
-Make sure that “TCP/IP” and “Named Pipes” are set to “enable” on each side and also check the “Enable shared memory protocol” box.
-Next, find SQL Server Configuration Manager under “All Programs” (or just search for it) on the server and make sure that TCP/IP and Named Pipes are both enabled under “Network Configuration>Client Protocols” there as well.
-Try opening Manager once again now that you’re a SQL client configuration pro!
Reason 3: Firewall Blocking SQL Ports
-We suggest turning off your windows firewall for domain/private networks if possible, as SQL uses 1433 TCP and 1434 UDP by default, along with dynamic ports which can vary and even change.
-Here’s our firewall article, at the very least you’ll need to allow 1433 TCP/1434 UDP in for SQL access, but you may still have dynamic ports being blocked after that point:
-Here is some additional information on tracking down the SQL dynamic ports if you wish to leave your firewall on and 1433/1434 don’t do the trick:
-After you’ve opened up the firewall, give your Manager connection another shot. A good way to tell if your firewall is the culprit is to briefly disable it completely in order to test.
IT STILL WON’T CONNECT, EVEN WITH THE FIREWALL COMPLETELY OFF!!
Okay, okay……there’s one other thing we can try.
Reason 4: Need To Create a SQL Alias
-On the workstation, type in “cliconfg” at start>run (or just press the Windows key first on Windows 8/Sever 2012). Yes, this is just like enabling the protocols so far.
-Browse to the “Alias” tab and hit the “Add” button.
-Copy and paste the “Server” field from your Argos Manager settings field into the “Server Name” box.
-Hit “Okay”, “Apply”, and give your Manager connection another shot!
If there are issues with the database connection for Argos Application service components, follow the steps listed in the Argos Application Server Database Connection Issues article.
If none of that gets you in to run your reports, get in touch with us at firstname.lastname@example.org and we’ll take a closer look!