Title:
[ANeff] Bug for: GM (CF8 thru Aether) builds never have correct ODBC port in CF Admin or CAR creation
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/Fixed
Reporter/Name(from Bugbase): Aaron Neff / ()
Created: 04/30/2018
Components: Database, MSAccess
Versions: 2018
Failure Type: Non Functioning
Found In Build/Fixed In Build: 2018.0.01.308605 (PreRelease) / 2018.0.0.309022
Priority/Frequency: Normal / Some users will encounter
Locale/System: / Windows 10 64 bit
Vote Count: 0
Issue1: Aether ODBC creation/migration is using CF2016's ports 20005/20006 instead of 20007/20008
Issue2: Since at least CF8, GM builds never had correct ODBC port for ODBC DSN creation or CAR creation/deploy (i.e. this issue needs a future-proof fix)
History: In each CF release (at least since CF8), swandm.ini is updated w/ new ODBC ports but CF Admin and CAR creation/deploy use old ports. Thus ODBC DSN creation/migration fails.
- CF8: 19997 and 19998
- CF9: 19999 and 20000
- CF10: 20001 and 20002
- CF11: 20003 and 20004
- CF2016: 20005 and 20006
- CF2018: 20007 and 20008
See many tickets where users run into this in every release. Also see my CF-3492574 where I'd requested a future-proof fix, yet issue recurs.
Repro:
1) In Aether's swandm.ini see ODBC ports are 20007 and 20008 (good).
2) In Aether CF Admin, create an ODBC DSN and see red error text.
-----------
Unable to update the NT registry.
Variable DRIVERPATH is undefined.
-----------
Actual Result: ODBC DSN ports in Aether's neo-datasource.xml are 20006
Expected Result: ODBC DSN ports in Aether's neo-datasource.xml are 20008
Suggestion: Have DSN and CAR creation read the SequeLink ports directly from swandm.ini.
Request: Please let us know when Aether is fixed (DSN creation -and- CAR creation). But please do not close this ticket until a future-proof fix has been implemented. Or we'll be right back here again in CF2020 ;)Attachments:
Comments: