Hello,
In a PC where windows was updated to version 1803, any application 
stopped working with 5381 ADS error.

Does anyone else experienced this?
Any solution?
Best Regards

On 5/14/2018 7:35 AM, Joao Grenhas wrote:
> Hello,
> In a PC where windows was updated to version 1803, any application 
> stopped working with 5381 ADS error.
> 
> Does anyone else experienced this?
> Any solution?
> Best Regards

Hi Joao,

When I saw your posting I took a spare workstation, did an in-place 
upgrade to Windows April 2018 version 1803 and ran my application 
without any apparent issues.  Granted I just open up a few screens, 
browsed some file records, did some quick data entry saving the updated 
information and ran a larger report.  Further testing is warranted but 
so far it seems OK.

Xbase++ version 2.00.906
Advantage version 11.10.0.1

Using:

DbeSetDefault( "ADSDBE" )
DbeInfo( COMPONENT_DATA, ADSDBE_TBL_MODE, ADSDBE_CDX)
DbeInfo( COMPONENT_ORDER, ADSDBE_INDEX_EXT, "CDX")
DbeInfo( COMPONENT_DATA, ADSDBE_LOCK_MODE, ADSDBE_COMPATIBLE_LOCKING  )
DbeInfo( COMPONENT_DATA, ADSDBE_DICTIONARY_DATA, .F. )

You did not say which version of ADS you are using or if you are using 
the Advantage Data Dictionary or even which version of Xbase++ you are 
using.

Dumb question but was the Xbase++ / ADS application running on this 
workstation prior to the 1803 update?

Is it possible that you had some ADS support files like ADS.ini located 
in the C:\Windows folder prior to the upgrade as it looks like this 
folder is moved to C:\Windows.old\WINDOWS with a new c:\windows created.

Regards.... Jonathan

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

Às 23:57 de 14/05/2018, Jonathan Leeming escreveu:
> On 5/14/2018 7:35 AM, Joao Grenhas wrote:
>> Hello,
>> In a PC where windows was updated to version 1803, any application 
>> stopped working with 5381 ADS error.
>>
>> Does anyone else experienced this?
>> Any solution?
>> Best Regards
> 
> Hi Joao,
> 
> When I saw your posting I took a spare workstation, did an in-place 
> upgrade to Windows April 2018 version 1803 and ran my application 
> without any apparent issues.  Granted I just open up a few screens, 
> browsed some file records, did some quick data entry saving the updated 
> information and ran a larger report.  Further testing is warranted but 
> so far it seems OK.
> 
> Xbase++ version 2.00.906
> Advantage version 11.10.0.1
> 
> Using:
> 
> DbeSetDefault( "ADSDBE" )
> DbeInfo( COMPONENT_DATA, ADSDBE_TBL_MODE, ADSDBE_CDX)
> DbeInfo( COMPONENT_ORDER, ADSDBE_INDEX_EXT, "CDX")
> DbeInfo( COMPONENT_DATA, ADSDBE_LOCK_MODE, ADSDBE_COMPATIBLE_LOCKING  )
> DbeInfo( COMPONENT_DATA, ADSDBE_DICTIONARY_DATA, .F. )
> 
> You did not say which version of ADS you are using or if you are using 
> the Advantage Data Dictionary or even which version of Xbase++ you are 
> using.
> 
> Dumb question but was the Xbase++ / ADS application running on this 
> workstation prior to the 1803 update?
> 
> Is it possible that you had some ADS support files like ADS.ini located 
> in the C:\Windows folder prior to the upgrade as it looks like this 
> folder is moved to C:\Windows.old\WINDOWS with a new c:\windows created.
> 
> Regards.... Jonathan
> 

Jonathan, thank you for your answer and test.
My problem is the connection it self:
   oSession := dacSession():new( "ADSDBE", cServerDrive )
fails with error 5381.

Apparently this problem has something to do with SMBv1 and the fact that 
Windows 10 version 1803 is blocking Network connections from executables 
that use a ADS server in a network share using SMBv1.

I tried several combinations that workd and didn't.

These didn't work:
   W10 1803, 32 bits -> Server 2003 Small Business Server Service Pack 2
                        ADS 8.0 32 bits
                        SMB share connects with 1.5

   W10 1803, 64 bits -> Server 2003 Small Business Server Service Pack 2
                        ADS 8.0 32 bits
                        SMB share connects with 1.5

This works:
   W10 1803, 64 bits -> Server 2012 R2 Standard x64
                        ADS 12.0 64 bits
                        SMB share connects with 3.0

And this one didn't work, but it's confusing because the SMB version is 
3.0.2. So there may be some more problems theres...
   W10 1803, 32 bits -> Server 2012 R2 Foundation x64
                        ADS 8.10 32 bits
                        SMB share connects with 3.0.2

Note: To find out which SMB Version each network share use, fire up a 
PowerShell in Admin and run "Get-SmbConnection".

Best Regards,

On 5/15/2018 8:43 AM, Joao Grenhas wrote:
> Às 23:57 de 14/05/2018, Jonathan Leeming escreveu:
>> On 5/14/2018 7:35 AM, Joao Grenhas wrote:
>>> Hello,
>>> In a PC where windows was updated to version 1803, any application 
>>> stopped working with 5381 ADS error.
>>>
>>> Does anyone else experienced this?
>>> Any solution?
>>> Best Regards
>>
>> Hi Joao,
>>
>> When I saw your posting I took a spare workstation, did an in-place 
>> upgrade to Windows April 2018 version 1803 and ran my application 
>> without any apparent issues.  Granted I just open up a few screens, 
>> browsed some file records, did some quick data entry saving the 
>> updated information and ran a larger report.  Further testing is 
>> warranted but so far it seems OK.
>>
>> Xbase++ version 2.00.906
>> Advantage version 11.10.0.1
>>
>> Using:
>>
>> DbeSetDefault( "ADSDBE" )
>> DbeInfo( COMPONENT_DATA, ADSDBE_TBL_MODE, ADSDBE_CDX)
>> DbeInfo( COMPONENT_ORDER, ADSDBE_INDEX_EXT, "CDX")
>> DbeInfo( COMPONENT_DATA, ADSDBE_LOCK_MODE, ADSDBE_COMPATIBLE_LOCKING  )
>> DbeInfo( COMPONENT_DATA, ADSDBE_DICTIONARY_DATA, .F. )
>>
>> You did not say which version of ADS you are using or if you are using 
>> the Advantage Data Dictionary or even which version of Xbase++ you are 
>> using.
>>
>> Dumb question but was the Xbase++ / ADS application running on this 
>> workstation prior to the 1803 update?
>>
>> Is it possible that you had some ADS support files like ADS.ini 
>> located in the C:\Windows folder prior to the upgrade as it looks like 
>> this folder is moved to C:\Windows.old\WINDOWS with a new c:\windows 
>> created.
>>
>> Regards.... Jonathan
>>
> 
> Jonathan, thank you for your answer and test.
> My problem is the connection it self:
>    oSession := dacSession():new( "ADSDBE", cServerDrive )
> fails with error 5381.
> 
> Apparently this problem has something to do with SMBv1 and the fact that 
> Windows 10 version 1803 is blocking Network connections from executables 
> that use a ADS server in a network share using SMBv1.
> 
> I tried several combinations that workd and didn't.
> 
> These didn't work:
>    W10 1803, 32 bits -> Server 2003 Small Business Server Service Pack 2
>                         ADS 8.0 32 bits
>                         SMB share connects with 1.5
> 
>    W10 1803, 64 bits -> Server 2003 Small Business Server Service Pack 2
>                         ADS 8.0 32 bits
>                         SMB share connects with 1.5
> 
> This works:
>    W10 1803, 64 bits -> Server 2012 R2 Standard x64
>                         ADS 12.0 64 bits
>                         SMB share connects with 3.0
> 
> And this one didn't work, but it's confusing because the SMB version is 
> 3.0.2. So there may be some more problems theres...
>    W10 1803, 32 bits -> Server 2012 R2 Foundation x64
>                         ADS 8.10 32 bits
>                         SMB share connects with 3.0.2
> 
> Note: To find out which SMB Version each network share use, fire up a 
> PowerShell in Admin and run "Get-SmbConnection".
> 
> Best Regards,

Hi,

My settings are closest to the configuration that you found to work...

W10 1803, 64 bits -> Server 2012 Standard x64
 >                         ADS 11.0 64 bits
 >                         SMB share connects with 3.0

So little help from me... Sorry... Regards... Jonathan

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

Hi Joao,

I have other problems accessing a windows xp from a windows 10 machine, your server 2003 is equivalent to xp, and microsoft has disabled smb1 on 
windows 10, windows 10 only has smb2 now, so your server must be upgraded to a smb2 level....

regards,
Edgar



Em 15/05/2018 11:43, Joao Grenhas escreveu:
> Às 23:57 de 14/05/2018, Jonathan Leeming escreveu:
>> On 5/14/2018 7:35 AM, Joao Grenhas wrote:
>>> Hello,
>>> In a PC where windows was updated to version 1803, any application stopped working with 5381 ADS error.
>>>
>>> Does anyone else experienced this?
>>> Any solution?
>>> Best Regards
>>
>> Hi Joao,
>>
>> When I saw your posting I took a spare workstation, did an in-place upgrade to Windows April 2018 version 1803 and ran my application without any 
>> apparent issues.  Granted I just open up a few screens, browsed some file records, did some quick data entry saving the updated information and ran 
>> a larger report.  Further testing is warranted but so far it seems OK.
>>
>> Xbase++ version 2.00.906
>> Advantage version 11.10.0.1
>>
>> Using:
>>
>> DbeSetDefault( "ADSDBE" )
>> DbeInfo( COMPONENT_DATA, ADSDBE_TBL_MODE, ADSDBE_CDX)
>> DbeInfo( COMPONENT_ORDER, ADSDBE_INDEX_EXT, "CDX")
>> DbeInfo( COMPONENT_DATA, ADSDBE_LOCK_MODE, ADSDBE_COMPATIBLE_LOCKING  )
>> DbeInfo( COMPONENT_DATA, ADSDBE_DICTIONARY_DATA, .F. )
>>
>> You did not say which version of ADS you are using or if you are using the Advantage Data Dictionary or even which version of Xbase++ you are using.
>>
>> Dumb question but was the Xbase++ / ADS application running on this workstation prior to the 1803 update?
>>
>> Is it possible that you had some ADS support files like ADS.ini located in the C:\Windows folder prior to the upgrade as it looks like this folder 
>> is moved to C:\Windows.old\WINDOWS with a new c:\windows created.
>>
>> Regards.... Jonathan
>>
> 
> Jonathan, thank you for your answer and test.
> My problem is the connection it self:
>    oSession := dacSession():new( "ADSDBE", cServerDrive )
> fails with error 5381.
> 
> Apparently this problem has something to do with SMBv1 and the fact that Windows 10 version 1803 is blocking Network connections from executables that 
> use a ADS server in a network share using SMBv1.
> 
> I tried several combinations that workd and didn't.
> 
> These didn't work:
>    W10 1803, 32 bits -> Server 2003 Small Business Server Service Pack 2
>                         ADS 8.0 32 bits
>                         SMB share connects with 1.5
> 
>    W10 1803, 64 bits -> Server 2003 Small Business Server Service Pack 2
>                         ADS 8.0 32 bits
>                         SMB share connects with 1.5
> 
> This works:
>    W10 1803, 64 bits -> Server 2012 R2 Standard x64
>                         ADS 12.0 64 bits
>                         SMB share connects with 3.0
> 
> And this one didn't work, but it's confusing because the SMB version is 3.0.2. So there may be some more problems theres...
>    W10 1803, 32 bits -> Server 2012 R2 Foundation x64
>                         ADS 8.10 32 bits
>                         SMB share connects with 3.0.2
> 
> Note: To find out which SMB Version each network share use, fire up a PowerShell in Admin and run "Get-SmbConnection".
> 
> Best Regards,

Edgar Borger
Softsupply Informatica Ltda.
Rua Alagoas, 48
Sao Paulo, SP
01242-000
Tel   : (5511) 3159-1997
Email : softsupply@terra.com.br

Hi,

Yes, it seems your error is caused by the restriction introduced in 
Win10 1803: a process is not allowed to create a socket under this 
version of Win10 if it launched from a share (file server) that is only 
SMB1 capable. (Win 2003 Small Business, Win XP, Samba 3.2 are examples 
of such file servers). At least SMB2 should be the protocol used between 
Win10 1803 client and the file server.

Best Regards,
Otto

>   oSession := dacSession():new( "ADSDBE", cServerDrive )
> fails with error 5381.

PDR 6959

so how does cServerDrive look like ?
i guess you use a Drive Letter ... (Lanmanager -> SMB1 -> UDP Port)

since Vista it is recommend to use UNC Path, also without ADS, with SMB2
as i know you also have to include Port Number in UNC Connection String

remember Firewall must also exclude your ADS Port Number

I added the port to the IP in the connection string. That made it 
running again. So it's like "DBE=ADSDBE; SERVER=\\192.168.2.206:6262\...".

And error 5381 ist wrong. PDR 6959 says that it should be 6420 instead.

Jan

Am 14.05.2018 um 15:35 schrieb Joao Grenhas:
> Hello,
> In a PC where windows was updated to version 1803, any application 
> stopped working with 5381 ADS error.
> 
> Does anyone else experienced this?
> Any solution?
> Best Regards