Issue with Windows 10 1803, build 17134

[nattivillin]

Users whose workstation have updated cant access commit.

Procedure halted due to access error.

How do we fix?

[Support Team]

Re: Issue with Windows 10 1803, build 17134

Thank you. We've received a few others report about this and we're not sure what Windows has changed that cause this. In any case - what helped in their case is to either rename (just like delete but keep the files) files
\RangerMSP\Client\ADS.ini
AND -
\RangerMSP\LastVer\ADS.ini

To ADS.ini-BK

And when this did not help - adding ADS.exe to the firewall resolved this issue.

Hope this helps.

[nattivillin]

Re: Issue with Windows 10 1803, build 17134

where is ads.exe?

[Support Team]

Re: Issue with Windows 10 1803, build 17134

That's the SQL back end on your server. Look for it as the installation path may vary.

[nattivillin]

Re: Issue with Windows 10 1803, build 17134

Its already allowed in the firewall.

Do we need to restart any services after the file rename?

[Support Team]

Re: Issue with Windows 10 1803, build 17134

Try to add it again and verify it is fully allowed to all users, including the port it is using - that you can find out by running Advantage Configuration Utility on your server, default is 6262. BTW, did you try renaming the ADS.ini file?

[nattivillin]

Re: Issue with Windows 10 1803, build 17134

Looks like the name change worked, thanks!