| Author |
|
Boneoh
New User
Joined: December/08/2007
Online Status: Offline
Info: 3
|
| Added: December/08/2007 at 3:14pm | IP Logged
|
|
|
Hi!
I am getting the following error message:
Database connection error
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
Running version 8.1, here is my environment:
Windows Server 2003 - Standard x64 Edition - Service Pack 2
SQL Server Express Edition
Here is my connection string:
Driver={SQL
Server};UID=aspbanneruser;password=temp;DATABASE=AspBanner;S ERV
ER=127.0.0.1
I believe that the folder permissions have been set properly. The settings
are being stored in the aspbanner_unlimited_config.asp file.
I am not seeing any errors in the event viewer under system, security, or
application logs.
I have searched the forums, but have not seen this error or anything
similar to it.
I was able to install and test this on my laptop without any major issues. I
am now installing this on our production server. It is a dedicated server,
so I have complete access to this machine.
Any pointers will be appreciated.
Regards,
Pete
|
| Back to Top |
|
| |
Boneoh
New User
Joined: December/08/2007
Online Status: Offline
Info: 3
|
| Added: December/08/2007 at 3:15pm | IP Logged
|
|
|
Not sure why the connection string is displayed funny in my first post, but it
is correctly formatted in the asp page. Something strange about my cut and
paste there...
Pete
|
| Back to Top |
|
| |
cwilliams
Admin Group
CJWSoft Web Software Developer
Joined: April/06/2004
Online Status: Offline
Info: 1769
|
| Added: December/08/2007 at 3:25pm | IP Logged
|
|
|
humm, that is a low level error saying there is a problem with he connection string.. really before any sugnificant asp even gets to run..
I understand what your saying about the forum messing up what you pasted too.
But something must be wrong with the connection string info your using..
I'd start with the 127.0.0.1 part... try other things like the true named instance of the SQL Server or an IP... 127.0.0.1 won't always work on a real server like it will locally... all depends on the setup really..
On my SQL Server I connect to the Data Source something like this..
Data Source=CJWXXX,53XX
Of course I specify the port number because I changed it from the default for security reasons..
The named instance thing is somewhat mentioned here..
http://www.derkeiler.com/Newsgroups/microsoft.public.sqlserv er.security/2002-06/0843.html
Also try a connection string more like this...
Provider=sqloledb;Data Source=poseidon;Initial Catalog=aspbanner;User Id=asppbanneruser;Password=temp;
I am not sure if the 64 bit thing is a factor or not.. I do know you cant connect to access databases on 64 bit IIS because of there being no drivers... there is some command you run to put iis into 32bit mode which solves that particular issue
Personally I have had a ton of problems with my own servers that I ran 64bit 2003 on.. I eventually went to back to 32 bit versions of the OS as I got sick of the problems..
Regardless, that is another story... you should be able to connect to a sql database ok.. but you have something wrong there .. not sure what..
You might want to try getting your connection string working with very simple code like this before you try to sort it out in ASPBanner..
http://www.codetoad.com/asp_query_displayer.asp
__________________
Best Regards,
Christopher Williams
www.CJWSoft.com
|
| Back to Top |
|
| |
Boneoh
New User
Joined: December/08/2007
Online Status: Offline
Info: 3
|
| Added: December/08/2007 at 5:29pm | IP Logged
|
|
|
I found the solution.
I changed 127.0.0.1 to 127.0.0.1\U15243104
It appears that the connection thinks there is a named instance of SQL.
Interesting that none of my other applications on this server needed this.
They are all asp.net, I am sure that there are many other differences.
Thanks!
Pete
|
| Back to Top |
|
| |
Active Info
Memberlist
Search
Help
Register
Login
Info: Invalid connection
