If Argos Manager won't open and shows a database connection error, the SQL connection between Argos Manager and the SQL instance hosting your Argos database has likely been disrupted. Work through the following checks in order.
Reason 1: Basic Configuration
- Confirm the SQL Server service is running on your Argos SQL server. You can check this under Services (
services.msc). - Verify your SQL server\instance name (
YOURSERVERNAME\Argosby default), stored SQL credentials, and database name (Argos7by default) are all correct in Argos Manager's settings.
Reason 2: Create a SQL Alias
- On the workstation, open the SQL Server Client Network Utility (
cliconfg). - Go to the Alias tab and click Add.
- Copy the Server value from your Argos Manager settings into the Server Name field.
- Click OK, then Apply, and try opening Argos Manager again.
Reason 3: TCP/IP and Named Pipes Protocols Blocked
- On both the server and the workstation, open the SQL Server Client Network Utility (
cliconfg). - Confirm TCP/IP and Named Pipes are both enabled, and check Enable shared memory protocol.
- Confirm Force protocol encryption is unchecked.
- On the server, open SQL Server Configuration Manager and confirm TCP/IP and Named Pipes are also enabled under Network Configuration > Client Protocols.
- Try opening Argos Manager again.
Reason 4: Firewall Blocking SQL Ports
- SQL Server uses 1433 TCP and 1434 UDP by default, along with dynamic ports that can vary. See our firewall article for the specific rules to add — at minimum, allow 1433 TCP and 1434 UDP inbound for SQL access. You may also need to allow the dynamic port range if the issue persists.
- To confirm whether the firewall is the cause, you can temporarily disable it for testing. Re-enable it afterward and add the specific port rules rather than leaving it off.
If none of the above resolves the issue, contact us at support@sepialine.com and we'll take a closer look.
0 Comments