Feedback
Did this article resolve your question/issue?

   

Article

Setup SequeLink to access the database from a Network Share

Information

 
TitleSetup SequeLink to access the database from a Network Share
URL NameSetup-SequeLink-to-access-the-database-from-a-Network-Share
Article Number000185286
EnvironmentProduct: SequeLink Socket Server
Version: 6.0
OS: Windows
Database: MS Access, MS Excel
Application: All support applications
Question/Problem Description
Connection refused while accessing MS Access or MS Excel database from a network share using SequeLink socket server, connection works if database file is copied to the local system driver.
Steps to Reproduce
Clarifying Information
Error MessageConnection refused
Defect Number
Enhancement Number
Cause
Resolution
Follow the below steps to setup SequeLink Socket Server to access the database from a Network Share
Bring up the windows Services and find SLAgent60 and SLSocket60.

  User-added image

Right click on both services one by one and go to the Log on Tab in Properties
Enter the User and Password that has rights to the Network File Share.

   User-added image

Stop and Restart both Services.

  User-added image

The above steps only has to be done one time when setting up the SequeLink Server services.  

The Following Needs done on each connection:
Set up your ODBC System DSN for the desired database, using the mapped drive letter.

   User-added image

DISCLAIMER: Edit the Registry at your own risk. Inappropriate changes to the Windows Registry can disable the operating system! To safeguard against such an accident, we recommend that you back up your existing registry by choosing Registry » Export Registry File after launching the Registry Editor and before making any changes.

Run regedit from the Start Menu

   User-added image

Find the ODBC DSN you created above in your registry under HEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI

   User-added image

Double click on the DBQ entry on the right hand side

   User-added image

Replace the driver letter with UNC path

 
Workaround
Notes
Last Modified Date5/4/2016 6:38 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.