Occasionally our customers will have difficulty opening Argos Manager for one reason or another.
Bear with us on this one, as there can be a number of causes for this common issue.
We’ll need to determine if this is an issue with your Argos permissions, Argos licensing, Argos Manager version or your Manager’s SQL connection (if your computer can’t access the right stuff on the server to open Manager).
Is It Argos Permissions?
It should be fairly obvious in this case, as you’ll see “your login, firstname.lastname@example.org, doesn’t have access to Argos Manager”. As the error suggests, this is because Argos has been told not to allow your Windows login name to access Argos Manager.
You’ll need to access Argos Manager using someone else’s login name in order to grant yourself access, or have someone else do it for you.
The easiest way to accomplish this is to have someone else at your company with Argos Manager access go in and put you in a user group with access, or you can get crafty and press shift>right-click>run as another user right there while you’re logged in (if you have their password available).
PRO TIP: “Run as a different user” is not to be confused with “Run as Administrator”.
Is It Licensing?
We manage your Argos licenses for you in our licensing system, but sometimes an issue can occur with this process or something can change on your database to require the keys be re-cut.
If you try to open Manager and see the Settings window with a warning on the Licenses tab, please contact email@example.com to get your licenses in order ASAP:
Is It Because Of An Upgrade On The Server?
If the Argos database on your server has been upgraded and your Manager is still at the old version, you’ll see this message:
In this case, you’ll just need to browse to \\YourServer\Argos7Installers and run Setuplauncher.exe. This will prompt the upgrade for your Manager and then you should be able to open it successfully.
Argos Manager SQL Connection
In some cases you won’t be able to get in, even with the right licenses and permissions. This is where we need to get a bit more technical. If your computer can’t form a SQL connection to the server, you’ll see this message when you try to open Manager.
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.
Step 4: 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 alias:” box. The format of the entry will be "SERVER_NAME\INSTANCE_NAME" if a SQL instance is defined (default instance is ARGOS) or "SERVER_NAME" if no SQL instance is configured. The "Server name:" field will auto-populate with the same entry.
-Hit “Okay”, “Apply”, and give your Manager connection another shot!
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!