tracker issue : CF-3492580

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: ODBC DSN creation fails in non-cfusion instances

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 01/29/2013

Components: Database

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final / 285327

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win All

Vote Count: 1

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on August 07, 2017 using build 2016.0.01.298513 
First, two important notes:
1) cfusion instances have this directory: C:\ColdFusion10\cfusion\db
2) additional instances do not have this directory: C:\ColdFusion10\myInstance\db

Problem: ODBC DSN creation fails in non-cfusion instances

Steps to Reproduce:

1) Create an instance named myInstance w/ directory C:\ColdFusion10\myInstance
2) In the myInstance's CF Admin, create an ODBC data source

Actual Result: A file not found error is thrown, and data source config is not added to C:\ColdFusion10\cfusion\db\slserver54\cfg\swandm.ini

Expected Result: Data source config should be added to C:\ColdFusion10\cfusion\db\slserver54\cfg\swandm.ini

Please see attached image.

Also, the following error is logged to application.log and coldfusion-out.log:
"Warning","ajp-bio-8013-exec-2","01/29/13","22:19:28",,"GetProfileString: coldfusion.util.IniUtils$InvalidIniPathException: The system cannot find the path specified: C:\ColdFusion10\myInstance\db\slserver54\cfg\swandm.ini"

See? The non-cfusion instance's ODBC creation is looking for swandm.ini at the wrong location.

This is an example of the entry that should've been added to swandm.ini:

[DataSource_4]
Type=6
DataSourceLogonMethod=OSIntegrated
DataSourceProviderTypesFile=C:\ColdFusion10\cfusion\db\slserver54\bin\swsoc.ini
ServiceName=ColdFusion 10 ODBC Server
DataSourceName=MyAccessDSN
DataSourceSOCODBCConnStr=dsn=MyAccessDSN
DataSourceFetchTimeStampAsString=0
;

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3492580

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

  1. January 30, 2013 00:00:00: 1_20130129_Bug_ODBCDSNCreationFailsInMultiInstances.jpg

Comments:

Temporary Workaround: First create the ODBC data source via the cfusion instance's CF Admin. Then create the ODBC data source via the other instance's CF Admin.
Comment by External U.
16454 | January 29, 2013 10:58:12 PM GMT
Related thread: http://forums.adobe.com/message/5032810
Comment by External U.
16455 | January 29, 2013 10:59:43 PM GMT
Btw, the "myInstance" instance in the description above essentially is the "Internet" instance in the attached image. I just changed the name of the instance to a more generic one, in the description above.
Comment by External U.
16456 | January 29, 2013 11:00:59 PM GMT
I have the exact same problem. The workaround provided did the job. I think this was a problem back in CF9 also.
Vote by External U.
16460 | July 16, 2013 02:20:49 PM GMT
This issue is fixed and this fix will be available as part of next major release of ColdFusion.
Comment by Nimit S.
16457 | September 23, 2015 11:13:56 PM GMT
Hi Nimit, Thanks very much! -Aaron
Comment by External U.
16458 | September 23, 2015 11:17:55 PM GMT
Verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). The file not found error, mentioned in this ticket's description (and shown in the screenshot), is no longer thrown. However, ODBC DSN creation still isn't successful b/c CF-3492620 is still not fixed. Thanks!, -Aaron
Comment by Aaron N.
16459 | August 07, 2017 06:15:41 AM GMT