Wrox Programmer Forums
|
Classic ASP Databases Discuss using ASP 3 to work with data in databases, including ASP Database Setup issues from the old P2P forum on this specific subtopic. See also the book forum Beginning ASP.NET Databases for questions specific to that book. NOT for ASP.NET 1.0, 1.1, or 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP Databases section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 18th, 2003, 12:04 PM
Registered User
 
Join Date: Jul 2003
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default ADODB.Recordset error '800a0e7d'

I apologize in advance, as I am a newbie of newbies to ASP. I designed a website and was given an ASP/SQL2K app to integrate into the website. I was told all I had to do was upload the files and edit one line of code and I would be ready to go. Well...it hasn;t been so easy. When I try to login to the app, I get this message:

Sorry, there is a data connection problem. Please try again later.[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.-2147467259
ADODB.Recordset error '800a0e7d'

The connection cannot be used to perform this operation. It is either closed or invalid in this context.

/directory/app_routines.asp, line 1884


Here is the chuck of code I edited....maybe it will help show what's going on?:


Sub LiveryDataConnectionOpen
    on Error resume next
    Set oConn = Server.CreateObject("ADODB.Connection")
    Err.Clear
    oConn.Open "driver={SQL Server};SERVER=66.132.211.151;DATABASE=main;UID=sa ;PWD="
    if Err.number<>0 then
        Response.Write "Sorry, there is a data connection problem. Please try again later."
        Response.write Err.Description
        Response.Write Err.number
        Err.Clear
    else
        LiveryConnectionOpen=True
    end if
    on Error goto 0
End Sub


Where do I start to look? is this a database or a code problem?? Thanks for your time.

-Paul


 
Old July 18th, 2003, 12:27 PM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Hi there,

I think the place to look is the SQL Server. First of all, does the SQL Server instance run? What happens when you try to log in locally to the SQL Server, using the Enterprise manager for example. Does that work?

If that is OK, can 66.132.211.151 be reached from your web application server? If there are firewalls in between, you need to open up port 1433 (the default port for SQL Server, yours may be different).

If that is alright, check that the database you are connecting to has a valid SA account with a blank password (note: it is very very very not recommended to have s SQL server with a blank password. Especially if you are posting your IP address, user name and password to a public forum. That would be the first change I'd make!!!!!! Create a new account with a strong password that you use to connect to SQL server. Give the SA account an impossible password, like O*&TOU&Y, write that down, put it in a safe and forget about the SA account ;) )

If that doesn't help, provide some more info. Where is the SQL server located, where is IIS, etc. etc.

Hope this Helps,

Imar



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
 
Old July 18th, 2003, 12:44 PM
Registered User
 
Join Date: Jul 2003
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Imar,

Part of the problem is I have only been in front of the web server. I'm told by the network people that everything should be all set. The web server and SQL2K are two seperate boxes on the same network, and a firewall is involved. I told them I would be using a webform to login to the app and connect to the SQL2K db. They said the proper ports were opened so that this could happen.

How would I try to reach the IP address from my web app for testing?

P.S. That IP address is not the right address. I modified it before posting :)

Thanks for your help,
Paul

Quote:
quote:Originally posted by Imar
 Hi there,

I think the place to look is the SQL Server. First of all, does the SQL Server instance run? What happens when you try to log in locally to the SQL Server, using the Enterprise manager for example. Does that work?

If that is OK, can 66.132.211.151 be reached from your web application server? If there are firewalls in between, you need to open up port 1433 (the default port for SQL Server, yours may be different).

If that is alright, check that the database you are connecting to has a valid SA account with a blank password (note: it is very very very not recommended to have s SQL server with a blank password. Especially if you are posting your IP address, user name and password to a public forum. That would be the first change I'd make!!!!!! Create a new account with a strong password that you use to connect to SQL server. Give the SA account an impossible password, like O*&TOU&Y, write that down, put it in a safe and forget about the SA account ;) )

If that doesn't help, provide some more info. Where is the SQL server located, where is IIS, etc. etc.

Hope this Helps,

Imar



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
 
Old July 18th, 2003, 12:50 PM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

OK, good. Posting public IP address is not a wise thing to do ;)

Anyway, your DBA should still fix the SA password, as it is a major security hole.

If both computers are on the same network, you may try to use the local IP address instead (if they have one).

If you have the luxury of having SQL Server Enterprise manager on your webserver, you can use that and see if you can connect to your SQL Server. (You could install these tools on your server and find out, though). Otherwise, you can try to ping it, although that wouldn't tell you that you can correctly access SQL Server.

If that doesn't help, I am not sure what to do. There may be tools around to check the server and the open ports, although I can't come up with a name right now.

Regards,

Imar



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
 
Old August 28th, 2003, 09:47 PM
Registered User
 
Join Date: Aug 2003
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi hurler,

I have exactly the same problem. Were you able to fix it finally? If so, what is your approach?

Thankx!

Chris






Similar Threads
Thread Thread Starter Forum Replies Last Post
Help: ADODB.Recordset error '800a0e7d' comets Classic ASP Databases 5 October 15th, 2011 11:27 AM
ADODB.Recordset error lance Wrox Book Feedback 2 February 23rd, 2007 02:37 PM
ADODB.RecordSet -- Error nabeeljohn Classic ASP Professional 10 November 9th, 2006 05:23 AM
Get the error "ADODB.Recordset error '800a0e7d' " Raymond Classic ASP Databases 2 August 5th, 2006 03:53 PM
ADODB.Recordset error '800a0cb3' klittlejohn SQL Server ASP 2 January 19th, 2004 10:17 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.