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 and SQL ODBC connection

Hi everyone, I need your expert advice. I have a w2k AD service with mssql on
it. and I setup another w2k server with IIS on it as webserver. my website
works on NT servers, but when I moved the website to the w2k server, it
doesn't work. It saids:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
/media/IIS_Gen_3.0_Recordset.js, line 366
My problem not stops here, as my website created by a program, therefore, I
don't know how to change the open connection statement. so therefore, I can
only find a way to overcome this user account login problem.
=?Utf-8?B?UGF0cmljayBUYW5n?= <PatrickTang@.discussions.microsoft.com>
wrote in news:E04EF7D8-542E-455B-A5C3-D134A92653F2@.microsoft.com:
I'm up against a similar problem, but having checked out KB 247931 I'm
still baffled.
AFAICS, the browser takes the authentication happily, but sql 2k gives me
either a '\' as the failed login or the same as below.
Yet the users are all members of a domain group that has access set
up....

> Hi everyone, I need your expert advice. I have a w2k AD service with
> mssql on it. and I setup another w2k server with IIS on it as
> webserver. my website works on NT servers, but when I moved the
> website to the w2k server, it doesn't work. It saids:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'NT AUTHORITY\ANONYMOUS LOGON'.
> /media/IIS_Gen_3.0_Recordset.js, line 366
> My problem not stops here, as my website created by a program,
> therefore, I don't know how to change the open connection statement.
> so therefore, I can only find a way to overcome this user account
> login problem.
>
sql

Problem with ASP & SQL ODBC connection

Hi everyone, I need your expert advice. I have a w2k AD service with mssql on
it. and I setup another w2k server with IIS on it as webserver. my website
works on NT servers, but when I moved the website to the w2k server, it
doesn't work. It saids:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
/media/IIS_Gen_3.0_Recordset.js, line 366
My problem not stops here, as my website created by a program, therefore, I
don't know how to change the open connection statement. so therefore, I can
only find a way to overcome this user account login problem.
Hi
Since it is and IIS site, the local NT IIS account, IUSR_<machinename>, will
be the user coming through on the connection. You need to give it rights in
you DB.
The best way to do this is to create a domain account for IIS, give it
rights in your DB and then re-configure IIS to use that for anonymous access.
There are security implications, so make sure that you give the user the
least rights at domain and DB level.
Regards
Mike
"Patrick Tang" wrote:

> Hi everyone, I need your expert advice. I have a w2k AD service with mssql on
> it. and I setup another w2k server with IIS on it as webserver. my website
> works on NT servers, but when I moved the website to the w2k server, it
> doesn't work. It saids:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> /media/IIS_Gen_3.0_Recordset.js, line 366
> My problem not stops here, as my website created by a program, therefore, I
> don't know how to change the open connection statement. so therefore, I can
> only find a way to overcome this user account login problem.
>

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 64-bit ODBC code and SQLConnect and SQLWCHAR

Hi all,
I'm trying to test some 64-bit ODBC stuff and I'm running into a slight
problem. First, my configuration.
Windows XP x64
VS.Net 2005 Beta 2
SQL Server 2005 CTP
So, I have built and tested other 64 bit apps so I know that things are all
working, but now I'm trying to test ODBC and I'm running into a problem. I
have the following code :
SQLCHAR Database[MAXBUFLEN]; // = "Cloud";
SQLCHAR User[MAXBUFLEN]; // = "fred";
SQLCHAR Pass[MAXBUFLEN]; // = "me";
sprintf ((char *)Database, "%s", "Cloud");
sprintf ((char *)User, "%s", "fred");
sprintf ((char *)Pass, "%s", "me");
retcode = SQLConnect(hdbc1, Database, SQL_NTS,
User, SQL_NTS, Pass, SQL_NTS);
If I execute this code as part of a little test program on my 32 bit box, it
connects just fine. Now, to get this code to compile on the 64-bit box, I
have to cast the string variable with (SQLWCHAR *) like this.
retcode = SQLConnect(hdbc1, (SQLWCHAR *)Database, SQL_NTS,
(SQLWCHAR *)User, SQL_NTS, (SQLWCHAR *)Pass, SQL_NTS);
So it compiles, but when I run it, I get an error back. If I take a look
at what (SQLWCHAR *)Database produces, its some unreadable junk. If I turn
on ODBC logging and then after the SQLConnect call take a look at the log,
where I should see the database for instance, I see just random characters.
So, what gives ? Do I have to do something special when working with
SQLWCHAR ?
Thanks for any help anyone can give me.
Nick
Hi
SQL Server 2005 CTP questions to the community newsgroups:
http://communities.microsoft.com/new...r2005&slcid=us
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nick Palmer" <nick@.kcicorp.com> wrote in message
news:11i480ff7qiikf9@.corp.supernews.com...
> Hi all,
> I'm trying to test some 64-bit ODBC stuff and I'm running into a slight
> problem. First, my configuration.
> Windows XP x64
> VS.Net 2005 Beta 2
> SQL Server 2005 CTP
> So, I have built and tested other 64 bit apps so I know that things are
> all
> working, but now I'm trying to test ODBC and I'm running into a problem.
> I
> have the following code :
> SQLCHAR Database[MAXBUFLEN]; // = "Cloud";
> SQLCHAR User[MAXBUFLEN]; // = "fred";
> SQLCHAR Pass[MAXBUFLEN]; // = "me";
> sprintf ((char *)Database, "%s", "Cloud");
> sprintf ((char *)User, "%s", "fred");
> sprintf ((char *)Pass, "%s", "me");
> retcode = SQLConnect(hdbc1, Database, SQL_NTS,
> User, SQL_NTS, Pass, SQL_NTS);
> If I execute this code as part of a little test program on my 32 bit box,
> it
> connects just fine. Now, to get this code to compile on the 64-bit box, I
> have to cast the string variable with (SQLWCHAR *) like this.
> retcode = SQLConnect(hdbc1, (SQLWCHAR *)Database, SQL_NTS,
> (SQLWCHAR *)User, SQL_NTS, (SQLWCHAR *)Pass, SQL_NTS);
> So it compiles, but when I run it, I get an error back. If I take a look
> at what (SQLWCHAR *)Database produces, its some unreadable junk. If I
> turn
> on ODBC logging and then after the SQLConnect call take a look at the log,
> where I should see the database for instance, I see just random
> characters.
> So, what gives ? Do I have to do something special when working with
> SQLWCHAR ?
> Thanks for any help anyone can give me.
> Nick
>

Problem with 64-bit ODBC code and SQLConnect and SQLWCHAR

Hi all,
I'm trying to test some 64-bit ODBC stuff and I'm running into a slight
problem. First, my configuration.
Windows XP x64
VS.Net 2005 Beta 2
SQL Server 2005 CTP
So, I have built and tested other 64 bit apps so I know that things are all
working, but now I'm trying to test ODBC and I'm running into a problem. I
have the following code :
SQLCHAR Database[MAXBUFLEN]; // = "Cloud";
SQLCHAR User[MAXBUFLEN]; // = "fred";
SQLCHAR Pass[MAXBUFLEN]; // = "me";
sprintf ((char *)Database, "%s", "Cloud");
sprintf ((char *)User, "%s", "fred");
sprintf ((char *)Pass, "%s", "me");
retcode = SQLConnect(hdbc1, Database, SQL_NTS,
User, SQL_NTS, Pass, SQL_NTS);
If I execute this code as part of a little test program on my 32 bit box, it
connects just fine. Now, to get this code to compile on the 64-bit box, I
have to cast the string variable with (SQLWCHAR *) like this.
retcode = SQLConnect(hdbc1, (SQLWCHAR *)Database, SQL_NTS,
(SQLWCHAR *)User, SQL_NTS, (SQLWCHAR *)Pass, SQL_NTS);
So it compiles, but when I run it, I get an error back. If I take a look
at what (SQLWCHAR *)Database produces, its some unreadable junk. If I turn
on ODBC logging and then after the SQLConnect call take a look at the log,
where I should see the database for instance, I see just random characters.
So, what gives ? Do I have to do something special when working with
SQLWCHAR ?
Thanks for any help anyone can give me.
NickHi
SQL Server 2005 CTP questions to the community newsgroups:
http://communities.microsoft.com/ne...lcid=us

--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nick Palmer" <nick@.kcicorp.com> wrote in message
news:11i480ff7qiikf9@.corp.supernews.com...
> Hi all,
> I'm trying to test some 64-bit ODBC stuff and I'm running into a slight
> problem. First, my configuration.
> Windows XP x64
> VS.Net 2005 Beta 2
> SQL Server 2005 CTP
> So, I have built and tested other 64 bit apps so I know that things are
> all
> working, but now I'm trying to test ODBC and I'm running into a problem.
> I
> have the following code :
> SQLCHAR Database[MAXBUFLEN]; // = "Cloud";
> SQLCHAR User[MAXBUFLEN]; // = "fred";
> SQLCHAR Pass[MAXBUFLEN]; // = "me";
> sprintf ((char *)Database, "%s", "Cloud");
> sprintf ((char *)User, "%s", "fred");
> sprintf ((char *)Pass, "%s", "me");
> retcode = SQLConnect(hdbc1, Database, SQL_NTS,
> User, SQL_NTS, Pass, SQL_NTS);
> If I execute this code as part of a little test program on my 32 bit box,
> it
> connects just fine. Now, to get this code to compile on the 64-bit box, I
> have to cast the string variable with (SQLWCHAR *) like this.
> retcode = SQLConnect(hdbc1, (SQLWCHAR *)Database, SQL_NTS,
> (SQLWCHAR *)User, SQL_NTS, (SQLWCHAR *)Pass, SQL_NTS);
> So it compiles, but when I run it, I get an error back. If I take a look
> at what (SQLWCHAR *)Database produces, its some unreadable junk. If I
> turn
> on ODBC logging and then after the SQLConnect call take a look at the log,
> where I should see the database for instance, I see just random
> characters.
> So, what gives ? Do I have to do something special when working with
> SQLWCHAR ?
> Thanks for any help anyone can give me.
> Nick
>

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.