Showing posts with label classic. Show all posts
Showing posts with label classic. Show all posts

Thursday, March 8, 2012

Can connect to sqlexpress via asp.net but not via asp

I can connect to a sqlexpress database using aspx (asp.net 2.0) pages
but not via classic asp pages. Both the asp and aspx pages are within
the same website. The sqlexpress database is also on the same server.
I have tried using a variety of connection strings within my asp pages,
including dsn, dsn-less, windows authentication, sql authentication
etc. (The sql express database by the way has mixed authenatication and
both work fine)
The errors I am getting are the following:
1. When I put a windows authentication string in my asp
page I get this error:
************
Provider error '80040e21'
Multiple-step OLE DB operation generated errors. Check
each OLE DB status value, if available. No work was done.
?, line 0
***************
2. When I use a sql authenticaion string, I get this
error:
********************
Microsoft OLE DB Provider for ODBC Drivers
error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not
found and no default driver specified
?, line 0
**********************
3. When I use a DSN connection string (with the DSN
connecting successfully within the ODBC utility) I get
this error:
******************
Microsoft OLE DB Provider for ODBC Drivers
error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot
open database "xxxx" requested by the login. The login
failed.
?, line 0
***********************
As mentioned before I have no problems in connecting to
the database via aspx pages within the same website. I can also
successfully connect to the database via visual web developer or sql
express manager on the same machine.
Any ideas?
Sorry, solved this!
|||You took the time to post that you found an answer, could you possibly post the solution?
~Another Steve

Quote:

Originally posted by Steve
Sorry, solved this!

Can connect to sqlexpress via asp.net but not via asp

I can connect to a sqlexpress database using aspx (asp.net 2.0) pages
but not via classic asp pages. Both the asp and aspx pages are within
the same website. The sqlexpress database is also on the same server.
I have tried using a variety of connection strings within my asp pages,
including dsn, dsn-less, windows authentication, sql authentication
etc. (The sql express database by the way has mixed authenatication and
both work fine)
The errors I am getting are the following:
1. When I put a windows authentication string in my asp
page I get this error:
************
Provider error '80040e21'
Multiple-step OLE DB operation generated errors. Check
each OLE DB status value, if available. No work was done.
?, line 0
***************
2. When I use a sql authenticaion string, I get this
error:
********************
Microsoft OLE DB Provider for ODBC Drivers
error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not
found and no default driver specified
?, line 0
**********************
3. When I use a DSN connection string (with the DSN
connecting successfully within the ODBC utility) I get
this error:
******************
Microsoft OLE DB Provider for ODBC Drivers
error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot
open database "xxxx" requested by the login. The login
failed.
?, line 0
***********************
As mentioned before I have no problems in connecting to
the database via aspx pages within the same website. I can also
successfully connect to the database via visual web developer or sql
express manager on the same machine.
Any ideas?Sorry, solved this!|||You took the time to post that you found an answer, could you possibly
post the solution?
~Another Steve
Steve wrote:
> *Sorry, solved this! *
larmores
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1889178.html

Wednesday, March 7, 2012

Can Classic ASP Interact with SQL Server 2005?

Forgive me if this is not the most appropriate group to pose this question.
I have a classic ASP app that is currently connecting to a SQL Server 2000
database using MDAC 2.8. Can a classic ASP application using MDAC 2.8
connect to and interact with SQL Server 2005? What issues might I encounter?
What known requirements are there to do this?
Thank you very much for any insight you can offer.
Ken Sturgeon
Most probably you dont need to change anything in your code to make this
work. At least I didn't have to change anything
Milan
P.S. Most probably you use ADO objects.
"Ken Sturgeon" <aksturgeon@.charter.net> wrote in message
news:O8Wn0j4FGHA.1028@.TK2MSFTNGP11.phx.gbl...
> Forgive me if this is not the most appropriate group to pose this
> question.
> I have a classic ASP app that is currently connecting to a SQL Server 2000
> database using MDAC 2.8. Can a classic ASP application using MDAC 2.8
> connect to and interact with SQL Server 2005? What issues might I
> encounter? What known requirements are there to do this?
> Thank you very much for any insight you can offer.
> Ken Sturgeon
>

Can Classic ASP Interact with SQL Server 2005?

Forgive me if this is not the most appropriate group to pose this question.
I have a classic ASP app that is currently connecting to a SQL Server 2000
database using MDAC 2.8. Can a classic ASP application using MDAC 2.8
connect to and interact with SQL Server 2005? What issues might I encounter?
What known requirements are there to do this?
Thank you very much for any insight you can offer.
Ken SturgeonMost probably you dont need to change anything in your code to make this
work. At least I didn't have to change anything
Milan
P.S. Most probably you use ADO objects.
"Ken Sturgeon" <aksturgeon@.charter.net> wrote in message
news:O8Wn0j4FGHA.1028@.TK2MSFTNGP11.phx.gbl...
> Forgive me if this is not the most appropriate group to pose this
> question.
> I have a classic ASP app that is currently connecting to a SQL Server 2000
> database using MDAC 2.8. Can a classic ASP application using MDAC 2.8
> connect to and interact with SQL Server 2005? What issues might I
> encounter? What known requirements are there to do this?
> Thank you very much for any insight you can offer.
> Ken Sturgeon
>