Problem with asp page and ODBC on Windows 2003 SR 64 Bits

I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:

Microsoft OLE DB Provider for ODBC Driverserror '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/ConnectToDatabase.asp, line 17

I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.

Thanks you.

Ahmed

Hi,

could you please post your connection string right in here ? We can′t see if you use a DSN or a DSNless connection.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

You are likely using an ODBC driver that is not available for 64bits. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=20574&SiteID=1 for the relevnat discusion.

Can you connect to the odbc driver in question using ODBC driver manager. Start->Run->ODBCAD32.exe. Using odbc driver manager create a new dsn and test the connection.

Problem with asp page and ODBC on Windows 2003 SR 64 Bits

I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/ConnectToDatabase.asp, line 17

I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.

Thanks you.

Ahmed

Hi,

could you please post your connection string right in here ? We can′t see if you use a DSN or a DSNless connection.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

You are likely using an ODBC driver that is not available for 64bits. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=20574&SiteID=1 for the relevnat discusion.

Can you connect to the odbc driver in question using ODBC driver manager. Start->Run->ODBCAD32.exe. Using odbc driver manager create a new dsn and test the connection.

Problem with ASP - ODBC - SQL Server after moving to Windows 2003 Server

Hello,
We are setting up a backup server for one of our Web sites, and the current
machine is running Win 2K Server, the new one Win 2003 Server. Otherwise
everything else is the same.
Most everthing works fine, except for one ASP template, which is opening a
recordset with this line:
set RS = Server.CreateObject("ADODB.Recordset") rs.Open "DealerInfo",
Conn,adOpenKeyset,adLockOptimistic,adcmdtable
On the 2003 server it gives an error:
Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
[Microsoft][ODBC SQL Server Driver]Cursor type changed
I have searched for information about thids error, but not found any so far.
Any help would be appreciated.
Ragnar
I have determined that this is not really an error message, but an
informational message. It seems pretty clear that the real error lies
somewhere else, so I will have to come up with a way to add some debug
statements without stopping the code.
Ragnar
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23THcMdmpEHA.2032@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We are setting up a backup server for one of our Web sites, and the
> current machine is running Win 2K Server, the new one Win 2003 Server.
> Otherwise everything else is the same.
> Most everthing works fine, except for one ASP template, which is opening a
> recordset with this line:
> set RS = Server.CreateObject("ADODB.Recordset") rs.Open "DealerInfo",
> Conn,adOpenKeyset,adLockOptimistic,adcmdtable
> On the 2003 server it gives an error:
> Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
> [Microsoft][ODBC SQL Server Driver]Cursor type changed
> I have searched for information about thids error, but not found any so
> far.
> Any help would be appreciated.
> Ragnar
>

problem With 2000 client

One Winn 2000 workstatiom has problem with ACCESS 2003 ODBC conection to SQL
server on WIN 2003 server. Other clients are all WINXP. This cient is on the
different domain too. Some reports works, and some have error, ask for
password again but not accept it even if it is supplied again. Application
on other clients works well.
What can be reason for this error.
Thanks in advanced.
Hi Zeljko,
From your description, I know that when you are connecting SQL Server 2000
on Windows 2003 with your Access 2003 installed on Windows 2000
Workstation, some reports will not work proper. Have I fully understand the
issue?
Would you please give me more information for that?
1. For those cannot be opened report, do they have some common controls,
such as Combo box or Subform?
2. Will it be OK when under the same domian? (still using Access 2003 on
Windows 2000)
3. You are using ADP, isn't it? Would please please give the error message
when it ask you Login information again? or please give me more description
about asking for password
4. Have you have the latest upgrade of Windows 2000, which should be
Windows 2000 Service Pack 4
Please apply my suggestions above and let me know if this helps resolve
your problem. If there is anything more I can do to assist you, please feel
free to post it in the group
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
|||Hi Zeljko,
I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions I've posted, please don't hesitate to let me know
directly. It's my pleasure to be of assistance
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
sql

problem With 2000 client

One Winn 2000 workstatiom has problem with ACCESS 2003 ODBC conection to SQL
server on WIN 2003 server. Other clients are all WINXP. This cient is on the
different domain too. Some reports works, and some have error, ask for
password again but not accept it even if it is supplied again. Application
on other clients works well.
What can be reason for this error.
Thanks in advanced.Hi Zeljko,
From your description, I know that when you are connecting SQL Server 2000
on Windows 2003 with your Access 2003 installed on Windows 2000
Workstation, some reports will not work proper. Have I fully understand the
issue?
Would you please give me more information for that?
1. For those cannot be opened report, do they have some common controls,
such as Combo box or Subform?
2. Will it be OK when under the same domian? (still using Access 2003 on
Windows 2000)
3. You are using ADP, isn't it? Would please please give the error message
when it ask you Login information again? or please give me more description
about asking for password
4. Have you have the latest upgrade of Windows 2000, which should be
Windows 2000 Service Pack 4
Please apply my suggestions above and let me know if this helps resolve
your problem. If there is anything more I can do to assist you, please feel
free to post it in the group
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.|||Hi Zeljko,
I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions I've posted, please don't hesitate to let me know
directly. It's my pleasure to be of assistance
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.