Re: 64bit CF Server and System DSNs - Solved
There actually IS a 64bit version of the MSDASQL provider. After
installing that and adding 'Provider=MSDASQL;' to all connection
strings, everything started working fine.
Bobby Hartsfiled wrote:
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
MicrosoftInternetExplorer4
We
are in the process of setting up a 64bit, multiserver configuration ColdFusion
server. We have setup and tested multiserver configuration in the past but
that
was on 32bit. This is our first attempt at 64bit.
- Windows 64bit Server 2003 R2
- CF 8 Enterprise 64 bit
Some
parts of our application still contain legacy ASP code and we use System DSNs
to allow that legacy code to talk to our databases. With 64bit, we are
receiving the following error anytime ASP attempts to talk to a system DSN.
ADODB.Connection error '800a0ea9'
Provider is not specified and there is no
designated default provider.
/openadmin/_scripts/conn.inc, line 11
I
found a couple of different reasons and alleged solutions to this but have
still had no luck solving it. The first, and most common, explanation that
I've
found is that the MSDASQL.dll (provider for ODBC drivers) has no 64 bit
version
and that SQLOLEDB should be used instead. To use SQLOLEDB, the suggestion was
to add the provider argument to your connection strings:
DSN=systemDSNName;UID=username;PWD=password;
Prodvider=SQLOLEDB;
When
I try that, I receive a different error:
Microsoft OLE DB Provider for SQL Server
error '80004005'
Invalid connection string attribute
/openadmin/_scripts/conn.inc, line 11
Another
solution was to use the connection string argument Driver={SQL Server}
instead of the provider. But when I try that, I get a completely different
error message:
Microsoft OLE DB Provider for SQL Server
error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL
Server does not exist or access denied.
/openadmin/_scripts/conn.inc, line 11
Another
solution, yet again, was to use the 32bit version of the ODBC Manager to
create
your system DSNs. I tried that as well with all of the same results. I also
tried setting IIS to run as a 32 bit application by setting
Enable32BitAppOnWin64 to true but that resulted in a different error as
well:
%1
is not a valid Win32 application.
I
also tried all of the same connection string changes from above while running
at 32bit but there was no change in this error messages.
As
you can see, I'm not having much luck. Has anyone else had this issue before
that might be able to offer some suggestions?
Thanks
for any help you can offer.
~|
Want to reach the ColdFusion community with something they want? Let them know
on the House of Fusion mailing lists
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329874
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: 64bit CF Server and System DSNs - Solved
That is an outstanding tip...
Mark A. Kruger, CFG, MCSE
(402) 408-3733 ext 105
www.cfwebtools.com
www.coldfusionmuse.com
www.necfug.com
-Original Message-
From: Bobby [mailto:bo...@acoderslife.com]
Sent: Wednesday, January 20, 2010 8:14 PM
To: cf-talk
Subject: Re: 64bit CF Server and System DSNs - Solved
There actually IS a 64bit version of the MSDASQL provider. After installing
that and adding 'Provider=MSDASQL;' to all connection strings, everything
started working fine.
Bobby Hartsfiled wrote:
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
MicrosoftInternetExplorer4
We
are in the process of setting up a 64bit, multiserver configuration
ColdFusion server. We have setup and tested multiserver configuration
in the past but that was on 32bit. This is our first attempt at 64bit.
- Windows 64bit Server 2003 R2
- CF 8 Enterprise 64 bit
Some
parts of our application still contain legacy ASP code and we use
System DSNs to allow that legacy code to talk to our databases. With
64bit, we are receiving the following error anytime ASP attempts to talk
to a system DSN.
ADODB.Connection error '800a0ea9'
Provider is not specified and there is no designated default provider.
/openadmin/_scripts/conn.inc, line 11
I
found a couple of different reasons and alleged solutions to this but
have still had no luck solving it. The first, and most common,
explanation that I've found is that the MSDASQL.dll (provider for ODBC
drivers) has no 64 bit version and that SQLOLEDB should be used
instead. To use SQLOLEDB, the suggestion was to add the provider
argument to your connection strings:
DSN=systemDSNName;UID=username;PWD=password;
Prodvider=SQLOLEDB;
When
I try that, I receive a different error:
Microsoft OLE DB Provider for SQL Server error '80004005'
Invalid connection string attribute
/openadmin/_scripts/conn.inc, line 11
Another
solution was to use the connection string argument Driver={SQL Server}
instead of the provider. But when I try that, I get a completely
different error message:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.
/openadmin/_scripts/conn.inc, line 11
Another
solution, yet again, was to use the 32bit version of the ODBC Manager
to create your system DSNs. I tried that as well with all of the same
results. I also tried setting IIS to run as a 32 bit application by
setting Enable32BitAppOnWin64 to true but that resulted in a different
error as well:
%1
is not a valid Win32 application.
I
also tried all of the same connection string changes from above while
running at 32bit but there was no change in this error messages.
As
you can see, I'm not having much luck. Has anyone else had this issue
before
that might be able to offer some suggestions?
Thanks
for any help you can offer.
~|
Want to reach the ColdFusion community with something they want? Let them know
on the House of Fusion mailing lists
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329877
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
