Hi... I received the following email from Massimo Parini so I'm posting 
it here in...

I can’t write in Alaska news , With update 1803 my application stop.

I use Alaska 1.90.331, and ADS 10.1

My connect connect string was:
oSession := DacSession():New( "DBE=ADSDBE;SERVER=\\SERVER\DIRECTORY”)
now is:
oSession := DacSession():New( "DBE=ADSDBE;SERVER=\\SERVER:6200\DIRECTORY”)
and now Go.

I asked the following followup questions and here they are along with 
the responses...

The workstation that used to connect would not connect after 1803 upgrade?

Yes, before it work, after update don’t work.  I try different ways, 
finally I find the port.

All you did to resolve the problem was specify the port number in the 
connection string?

Yes

What error were you getting before the fix?

oSession_ODBC:isConnected() == .f.

Since you are not using the default 6262 is it possible that you were 
previously using ADS.INI on the workstation in the C:\windows folder 
which would have been replaced after the 1803 upgrade?

I use ADS.ini in the same directory of .exe, the port in ADS.INI is 
6200.  I don’t think so. But I’m not sure.

jonathan.leeming@the-family-centre.com
Edmonton, Alberta, Canada

On 5/16/2018 12:08 PM, Jonathan Leeming wrote:
> Hi... I received the following email from Massimo Parini so I'm posting 
> it here in...
> 
> I can’t write in Alaska news , With update 1803 my application stop.
> 
> I use Alaska 1.90.331, and ADS 10.1
> 
> My connect connect string was:
> oSession := DacSession():New( "DBE=ADSDBE;SERVER=\\SERVER\DIRECTORY”)
> now is:
> oSession := DacSession():New( "DBE=ADSDBE;SERVER=\\SERVER:6200\DIRECTORY”)
> and now Go.
> 
> I asked the following followup questions and here they are along with 
> the responses...
> 
> The workstation that used to connect would not connect after 1803 upgrade?
> 
> Yes, before it work, after update don’t work.  I try different ways, 
> finally I find the port.
> 
> All you did to resolve the problem was specify the port number in the 
> connection string?
> 
> Yes
> 
> What error were you getting before the fix?
> 
> oSession_ODBC:isConnected() == .f.
> 
> Since you are not using the default 6262 is it possible that you were 
> previously using ADS.INI on the workstation in the C:\windows folder 
> which would have been replaced after the 1803 upgrade?
> 
> I use ADS.ini in the same directory of .exe, the port in ADS.INI is 
> 6200.  I don’t think so. But I’m not sure.
> 
> 

I have run into the Windows 10 version 1803 issue with a couple of my 
customers over the past week.  Since the update, they get a 5381 error 
when attempting to launch my application via a mapped network drive.

SAP is aware of the issue.  I found the following article online that 
discusses it:
https://answers.sap.com/questions/507404/ads-unable-to-connect-win10-after-1803-update.html

Some people were able to resolve the issue by creating a ADS.ini file, 
which bypasses the discovery process. We already use a ADS.ini file, so 
that didn't work for me.

I tried passing port number 6262 in my connection string, as others 
suggested, but that didn't work either.

My standard practice for years has been to install my application on the 
server, share the folder the app is installed in, map a network drive on 
the client machine to the shared folder, then create a shortcut on the 
desktop of the client machine to the executable file within the shared 
folder.  That's always worked in the past, but now I'm getting a 5381 
error when I try to launch the program on the client machines that have 
Windows 10 version 1803.

I discovered that if I install my application locally on the client 
machine and configure it to access the database on the shared server 
folder, it works.

I'm still working to find the best solution for this issue. If anyone 
has any information they think might help, please feel free to share it.

Thanks!

Chris