Connecting to a Database

eoStar uses connection strings to communicate with a database. Each connection string only needs to be set up once per workstation eoStar is installed on. However, connections strings can be edited at any time if the server or database information changes.

When using a Remote Desktop Server, the connection strings will only need to be set up on the server(s) where eoStar is installed.


Feature Information

  • Functional Area: IT
  • Roles Impacted: Tech Support Team
  • Platform: eoStar
  • Plugins: eoStar Core

How to Set Up a Connection String

  1. Open eoStar.
  2. Click Add Connection.
  3. Enter a Description for the connection string.
    • Usually this should be the name of the database.
  4. Enter the name of the Server the database is on.
  5. Enter the Port to use when connecting to the database. (optional)
  6. Enter the name of the Database.
  7. Enter the User ID for connecting to the server.
    • Disabled when using integrated security.
  8. Enter the Password for connecting to the server.
    • Disabled when using integrated security.
  9. Check Use integrated security to use the Windows logon information when connecting to the server.
  10. Check Use multi-subnet failover to utilize an SQL Multi-Subnet Cluster
  11. Enter the Failover Partner to use if the primary database is unavailable.
    • Only necessary when using multi-subnet failover.
  12. Click Add Connection.

How to Set Up Connection Strings in a Group Policy

A Group Policy can be used to automatically populate the database connection strings for all eoStar users.

Create Group Policy Connection Strings

  1. Using the instructions above, enter the desired connection strings in an eoStar installation on the server where the Group Policy will be created.
  2. Create a new Group Policy.
  3. Go to User Configuration > Preferences > Windows Settings.
  4. Right-Click on Registry > New > Registry Item.GPmanagementEditor.png
  5. Enter HKEY_CURRENT_USER as the Hive.
  6. Enter Software\Rutherford & Associates\eoStar\LoginPopup as the Key Path.
  7. Enter Connections as the Value name.
  8. Enter REG_SZ as the Value Type.
  9. Paste the value of the Key Path as the Value Data:
    1. Press the Windows button + R and run the RegEdit command.
    2. Expand HKEY_CURRENT_USER > Software > Rutherford & Associates > eoStar and right-click LoginPopup > Export.
    3. Save the export to the desktop.
    4. Open the exported file in a text editor (such as Notepad).
    5. Copy all the data between the quote marks.ScreenCap TestRegEdit.png
    6. Paste it into the Value Data field of the Group Policy.
  10. Click OK.
  11. Assign the GPO to the appropriate users and/or workstations.
    • The next time the user’s environment pulls down its GPO’s it should get the updated connection strings.
    • If that doesn’t work, try initiating a GPO pull by entering GPUPDATE into a command prompt to force an update, then reboot.
Note

It is important to remember that this Group Policy will always be the object looked at to populate the Database Connection list.

To permanently add new connections to the list:

  • Add the new database connection(s) to eoStar on the server.
  • Update the Value Data of the Group Policy (Step 9 above).


Troubleshooting Connection Strings

Remotely Connected to Network

If you are having issues connecting because you are remotely connected to your company network, remove the following registry key:

  1. Press the Windows key + R to open the Run window.
  2. Type in regedit.
  3. Click OK.
  4. Expand HKEY_CURRENT_USER > Software > Rutherford & Associates > eoStar.
  5. Select LoginPopup.
  6. Right-click Connections.
  7. Click Delete.
Updated on May 15, 2019

Was this article helpful?

Related Articles