tracker issue : CF-3831838

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

ODBC Connections Fail after Installation of Update 1

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce


Created: 09/25/2014

Components: Database, ODBC

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win 2008 Server R2

Vote Count: 0

After installing update 1 all ODBC connections fail.

Steps to Reproduce: Install update 1

Actual Result: All ODBC connections fail

Expected Result: All ODBC connections should work as they did prior to the update

Any Workarounds: Restart the ColdFusion service a second time and the errors go away.

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

Watson Bug ID:	3831838

External Customer Info:
External Company:  
External Customer Name: Stephen.M.Walker
External Customer Email:  
External Test Config: Windows 2008R (64 bit) VM

IIS 7.5

ColdFusion service uses AD account for startup.



I am adding this in case others run into this issue. This happened on both the development and production servers. Not sure if it is related to the use of the AD account. Personal device running Win 8.1 and IIS 8.5 and OSX Yosemite, experience no issues using the default accounts.
Comment by External U.
10825 | September 25, 2014 12:02:09 PM GMT
Stephen, Have you tried verifying the datasource after applying the update? Is this issue reproducible? Please tell me OS name where you are facing this issue. I will try to reproduce this issue to understand it. Regards, Nimit
Comment by Nimit S.
10826 | October 07, 2014 04:02:54 AM GMT
Nimit, Stopping and restarting the service resolved the issue. This was on Windows 2008 R2. This happened on two different systems.
Comment by External U.
10827 | October 07, 2014 02:31:14 PM GMT
As you confirmed you are not facing this issue anymore after restarting the service. We are closing this bug. If you face this issue again please let us know so that we can re-open this bug.
Comment by Nimit S.
10828 | December 03, 2014 02:15:48 AM GMT