This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 94%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hello,
I have a batch file that I use to start application from Win 7 client. It will connect to remote SQL Server and start application.
It looks like this
pushd \<server>\MITRE\SoftwareReleases\v23-lfhm
cmd /c start LaminarFlowHoodModule.exe
Note: at the location I have configuration file LaminarFlowHoodModule.config with the name of database, creds and etc. It does not state which driver to use. I assume that it is coded inside LaminarFlowHoodModule.exe
This is the section from LaminarFlowHoodModule.config
<!-- Database settings -->
<add key="DataSource" value="server" />
<add key="InitialCatalog" value="database" />
<add key="TrustedConnection" value="false" />
<!-- Username/password required if TrustedConnection is false -->
<add key="UserName" value="user" />
<add key="Password" value="password/>
Recently it stopped working and it failed to connect to database.
I installed latest SQL Server Native client driver and was able to create ODBC connection e.g. 'connection1' and then connect to database with no problem.
Hence, my question:
Could I create another batch file of modify existing one in order to force LaminarFlowHoodModule.exe to use ''connection1' ?
Thanks
Just a guess but the absence of a driver/provider specification suggests the application is using SqlClient. That driver is part of the .NET framework. You won't be able to change from SqlClient to an ODBC driver unless the app is coded to handle ODBC drivers too. I suggest you research the root cause of the failed connection. Perhaps there is a clue in the SQL Server error log.
@Susja ,
Common troubleshooting steps as next:
resolving-could-not-open-a-connection-to-sql-server-errors
Folks,
I just realized that the issue I'm having with connection is caused by the change our IT did in Group policy for Win 7 for security reason.
Based on that I assume that all my attempts to fix it using some workarounds would be useless.
I am still confused why connection using ODBC works fine … How this type of connection could 'disregard' Group policy.
Anyway … do you think I should stop these efforts and simply replace Win7 for Win 10?
Thanks
What was changed?
Trace the program and an ODBC test with Process Monitor. What's different between the call that works and the one that fails?
Hi @Susja ,
do you think I should stop these efforts and simply replace Win7 for Win 10?
Yes. I do.
However, I still recommend that you communicate with your IT to see what settings he has made that affect the sqlserver connection.
Please verify that the GP has creating a port exception for TCP Port 1433 and UDP Port1434 or not;
Please verify that the GP has one program with exception for sqlservr.exe or not.
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
BR,
Mia
Hi Folks,
I am already in a process of buying / replacing Win7 with Win10.
Meanwhile IT has changed their hypothesis about change in GP and currently they suggest it's due to some on Microsoft update patch.
They are still investigating …
Thanks