Users may see a pop-up stating they are unable to connect to the database which presents the user with several options. This can be due to a number of factors.

Prior to using any of the tools available in this window:

1. Verify the PC is connected to the network.
   
2. Verify the user can access any information from the mapped JunxureData folder. If they cannot access information in this folder, they will likely be unable to access the database.
   
3. Verify if any other Junxure users are also having issues logging into Junxure or accessing files on the SQL Server.
   
4. A person with access to System Setup > Users within Junxure should verify the User for the person experiencing issues is set to Active.
   




5. Verify the external.config file exists in:
   

C:\Program Files (x86)\CRM Software\Junxure\CodeDN (64-bit Windows)

or

C:\Program Files\CRM Software\Junxure\CodeDN (32-bit Windows)

and that it is set to the correct database with a format of:

Data Source=<SERVERNAME>\<INSTANCENAME>;Initial Catalog=<DATABASENAME>

If the user is connected to the network, is an active user, has an external.config file, and the config file is pointing to the correct database, the next option is to check the user's permissions to the database.

If the Junxure Security Wizard has been run:

Verify the user is logged in as their Domain User. This can be done by running CMD.exe from Windows and typing "set". If the user is logged into the domain the options USERDNSDOMAIN and the USERDOMAIN will be set to that domain.

If part of the domain, verify that the user is in the JXAdmin or JXUsers group. This can be done by running CMD.exe and typing:

net user /domain <username>.

If the user is not in the JXAdmin or JXUsers group, they must have their IT add them to one of the two groups. After the user has been added to one of the groups, the user must log out of Windows and back in for the changes to take effect.

Verify the machine can connect to the instance using an ODBC:

1. In Windows go to Start > Control Panel > Administrative Tools.
   
2. Choose Data Sources(ODBC).
   




3. This will open the ODBC Data Source Administrator.
   




4. Click the System DSN Tab and then click Add.
   




5. This will open the Create a new Data Source screen. Scroll down and select SQL Server (double-click).
   




6. Name the connection "Junxure". You can use the drop-down to select your Junxure SQL server. In most cases this will be the name of your server and then Junxure. For instance if the server was named FinancialServer it would be "FinancialServer\Junxure". Some offices may have a slightly different configuration. If you are not sure, consult your IT Pro or System Administrator. Junxure Tech Support can also get this information for you.
   
7. Click Next to get the below screen and you should be able to immediately click Next again to test the TCP connection.
   




8. It is possible that you may get an error at this point that looks like this. If you do not, skip to Step 11.
   




9. If you do get this error, click OK and then click the Client Configuration button, which will open the "Add Network Library Configuration" screen.
   




10. Click the radio button next to "Named Pipes" as pictured above then click OK. Once back on the previous screen click Next again.
    




11. You should now get to the below screen.
    




12. If Junxure is not listed as the Default Database (as shown above), then click the checkbox at the top, use the drop-down to select Junxure as pictured below, and then click Next.
    




13. On the screen below do not change anything and click "Finish".
    




14. The following screen will pop up. Click "Test Data Source".
    




15. You should get the following screen. When you see "Tests Completed Sucessfully!", click OK.
    

If successful using named pipes but TCP/IP fails, the user's PC is experiencing TCP/IP connectivity issues.

If Named Pipes fail:

• Using the TCP/IP configuration, try using the server's IP address in place of the server name in the instance name. So instead of <Server>\Junxure for TCP it would test <IPAddress>\Junxure.
  
• For Named Pipes trying using IP address in the named pipe string. So instead of
  

\\<ServerName>\pipe\MSSQL$JUNXURE\sql\query

try using

\\<IPAddress>\pipe\MSSQL$JUNXURE\sql\query

• If successful using the IPAddress the machine is experiencing DNS issues. Please contact your IT for further assistance.
  

Verify the user has permissions to the SQL database instance.

If the users are on the domain and security wizard was not run:

• Log into the Junxure Instance on the SQL server, expand Security and right-click Logins.
  
• Click Search and find the Domain User name of the user who is having problems connecting to the database.
  
• Grant that group All Server Roles and all User Mapping roles to only the Junxure database. Do not select any of the 'deny' roles.
  

If the users are on a workgroup:

• Log into the Junxure Instance, expand > Security right-click Logins.
  
• Click Search and find the built-in group of Authenticated Users.
  
• Grant that group all Server Roles and User Mapping roles to only the Junxure database as seen below. Do not check any deny roles.
  
• If Authenticated Users does not work repeat the above for Guest.