I just updated MDAC on one of my machines and I'm now having trouble accessing my SQL server. It's a local connection using SQLOLEDB in a VB dll. It was working fine before the update and now I get:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/cms25/CMS.asp, line 33
Most of the information I can find on this refers to TCP/IP connections but the SQL server is local. My connect function looks like this:
Public Sub ADOConnect()
With m_ADOConnection
.Provider = "SQLOLEDB"
.CursorLocation = adOpenStatic
.CommandTimeout = 20
.Mode = adModeReadWrite
.ConnectionString = "Data Source=" & m_strServer & ";Database=" & m_strName & ";" & m_strUsernamePassword
.open
End With
End Sub
On this server, m_strServer = "(local)". What am I missing? Thanks for any help in advance!
a.From which version of MDAC to which version?
On what platform?
Biggest headache I had was that 2.5 default connection library was Named pipes while 2.7 and later, the default was TCP. If you didn't have TCP and DNS configured properly, then the upgrade would result in errors that you may not have noticed previously.
Regards,
hmscott|||I believe I went from something like 2.5 to 2.8 so you might be right. How do I make sure the server is configured properly? Where do I set up named pipes?
UPDATE:
As soon as I enabled the TCP/IP access, it worked so I guess I'm not using named pipes... I'll have to look into this some more because I'd like to avoid using TCP/IP entirely. I'm assuming named pipes is faster?|||Check this KBA http://support.microsoft.com/kb/328306/en-us for the relevant reasons.sql
Showing posts with label accessing. Show all posts
Showing posts with label accessing. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MDAC 2.8 Update Causes Problems
Hello,
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,
Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
David Gugick
Imceda Software
www.imceda.com
|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Would
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com
|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com
|||Oops I was kind of wondering about that . It doesn't work anyway, but when I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
David Gugick
Imceda Software
www.imceda.com
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,
Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
David Gugick
Imceda Software
www.imceda.com
|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Would
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com
|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com
|||Oops I was kind of wondering about that . It doesn't work anyway, but when I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
David Gugick
Imceda Software
www.imceda.com
MDAC 2.8 Update Causes Problems
Hello,
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
--
David Gugick
Imceda Software
www.imceda.com|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Would
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> > Hello,
> > I have a 2000 server hosting a site using SQL Server 7. I have been
> > having problems accessing the database and I kept getting an error
> > 80004005 Data source name not found and no default driver specified.
> > I went to the Microsoft site and found the white paper and followed a
> > link to download an MDAC 2.8 update that was compatible with Windows
> > 2000. However now my site doesn't work at all and I get:
> >
> > Error Type:
> > Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> > 'sa'. Reason: Not associated with a trusted SQL Server connection.
> > /includes/i_shop.asp, line 87
> >
> > I've been searching, but I still can't find exactly what I need and
> > suggestions would be greatly appreciated.
> >
> > Thanks for any help,
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> > I went through and used the component checker and there is one
> > unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> > Microsoft site the file that is supposed to be included is
> > sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> > download the right file and replace it? The connection string and
> > everything else hasn't changed and it all worked for years. The only
> > change was the 2.8 update. Should I look at the i_shop.asp page for
> > clues? Why is it listed.
> > Thanks for any help,
> > Mike
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com|||Oops I was kind of wondering about that . It doesn't work anyway, but when I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> > I didn't create this site and the only connection string I could find
> > was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> > this the one I need to worry about?
> > Thnaks again,
> > Mike
> >
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
--
David Gugick
Imceda Software
www.imceda.com
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
--
David Gugick
Imceda Software
www.imceda.com|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Would
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> > Hello,
> > I have a 2000 server hosting a site using SQL Server 7. I have been
> > having problems accessing the database and I kept getting an error
> > 80004005 Data source name not found and no default driver specified.
> > I went to the Microsoft site and found the white paper and followed a
> > link to download an MDAC 2.8 update that was compatible with Windows
> > 2000. However now my site doesn't work at all and I get:
> >
> > Error Type:
> > Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> > 'sa'. Reason: Not associated with a trusted SQL Server connection.
> > /includes/i_shop.asp, line 87
> >
> > I've been searching, but I still can't find exactly what I need and
> > suggestions would be greatly appreciated.
> >
> > Thanks for any help,
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> > I went through and used the component checker and there is one
> > unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> > Microsoft site the file that is supposed to be included is
> > sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> > download the right file and replace it? The connection string and
> > everything else hasn't changed and it all worked for years. The only
> > change was the 2.8 update. Should I look at the i_shop.asp page for
> > clues? Why is it listed.
> > Thanks for any help,
> > Mike
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com|||Oops I was kind of wondering about that . It doesn't work anyway, but when I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> > I didn't create this site and the only connection string I could find
> > was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> > this the one I need to worry about?
> > Thnaks again,
> > Mike
> >
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
--
David Gugick
Imceda Software
www.imceda.com
MDAC 2.8 Update Causes Problems
Hello,
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
David Gugick
Imceda Software
www.imceda.com|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Woul
d
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com|||Oops I was kind of wondering about that . It doesn't work anyway, but when
I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
David Gugick
Imceda Software
www.imceda.com
I have a 2000 server hosting a site using SQL Server 7. I have been having
problems accessing the database and I kept getting an error 80004005 Data
source name not found and no default driver specified. I went to the
Microsoft site and found the white paper and followed a link to download an
MDAC 2.8 update that was compatible with Windows 2000. However now my site
doesn't work at all and I get:
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'sa'.
Reason: Not associated with a trusted SQL Server connection.
/includes/i_shop.asp, line 87
I've been searching, but I still can't find exactly what I need and
suggestions would be greatly appreciated.
Thanks for any help,Med103 wrote:
> Hello,
> I have a 2000 server hosting a site using SQL Server 7. I have been
> having problems accessing the database and I kept getting an error
> 80004005 Data source name not found and no default driver specified.
> I went to the Microsoft site and found the white paper and followed a
> link to download an MDAC 2.8 update that was compatible with Windows
> 2000. However now my site doesn't work at all and I get:
> Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'sa'. Reason: Not associated with a trusted SQL Server connection.
> /includes/i_shop.asp, line 87
> I've been searching, but I still can't find exactly what I need and
> suggestions would be greatly appreciated.
> Thanks for any help,
It looks like you are telling ADO to connect using a trusted connection,
but it's picking up "sa" as the user name (or are you passing that in?)
Do you want to be using ODBC with ADO? You're not using the ADO drivers
according to that error. Post your connection string and also try
connecting using SQL Server security from your app if you have it
enabled.
David Gugick
Imceda Software
www.imceda.com|||I went through and used the component checker and there is one unknown file
sqlsrv32.dll version 2000.85.1025.0 according to the Microsoft site the file
that is supposed to be included is sqlsrv32.dll version 2000.85.1022.0. Woul
d
it be advisable to download the right file and replace it? The connection
string and everything else hasn't changed and it all worked for years. The
only change was the 2.8 update. Should I look at the i_shop.asp page for
clues? Why is it listed.
Thanks for any help,
Mike
"David Gugick" wrote:
> Med103 wrote:
> It looks like you are telling ADO to connect using a trusted connection,
> but it's picking up "sa" as the user name (or are you passing that in?)
> Do you want to be using ODBC with ADO? You're not using the ADO drivers
> according to that error. Post your connection string and also try
> connecting using SQL Server security from your app if you have it
> enabled.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I went through and used the component checker and there is one
> unknown file sqlsrv32.dll version 2000.85.1025.0 according to the
> Microsoft site the file that is supposed to be included is
> sqlsrv32.dll version 2000.85.1022.0. Would it be advisable to
> download the right file and replace it? The connection string and
> everything else hasn't changed and it all worked for years. The only
> change was the 2.8 update. Should I look at the i_shop.asp page for
> clues? Why is it listed.
> Thanks for any help,
> Mike
You should post the connection string anyway. Just because MDAC < 2.8
allowed a malformed connection string to pass through doesn't mean 2.8
will. You want to use ODBC in this case, i assume. No?
I wouldn't worry about the file version issue right now.
David Gugick
Imceda Software
www.imceda.com|||I didn't create this site and the only connection string I could find was in
the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is this the one I
need to worry about?
Thnaks again,
Mike
"David Gugick" wrote:
> Med103 wrote:
> You should post the connection string anyway. Just because MDAC < 2.8
> allowed a malformed connection string to pass through doesn't mean 2.8
> will. You want to use ODBC in this case, i assume. No?
> I wouldn't worry about the file version issue right now.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> I didn't create this site and the only connection string I could find
> was in the siteserver console DSN=pl_commerce;UID=sa;PWD=dbsa;. Is
> this the one I need to worry about?
> Thnaks again,
> Mike
>
Well, the first thing you need to do is change the password on the "sa"
account (because you posted it to the group).
Then, you should change the connection to use some other user that has
limited, but sufficient, rights to the underlying database. Better to
use integrated security in this case instead of SQL Security.
You are using a DSN, which means you are connecting using ODBC (not the
fastest). It's better to use the native ADO driver for SQL Server.
Go to the server in question and test the ODBC connection from the ODBC
Control Panel Applet and make sure it works. maybe someone already
changed the password or the server name changed.
David Gugick
Imceda Software
www.imceda.com|||Oops I was kind of wondering about that . It doesn't work anyway, but when
I
try to use the ODBC Control Panel I get the same error posted above. I also
tried changing users, but it kept giving me an error message Invalid
connection string; connection failed.. Can I just create a new database user
in the enterprise manager and see if I can change it in the connection
string?
Thanks,
"David Gugick" wrote:
> Med103 wrote:
> Well, the first thing you need to do is change the password on the "sa"
> account (because you posted it to the group).
> Then, you should change the connection to use some other user that has
> limited, but sufficient, rights to the underlying database. Better to
> use integrated security in this case instead of SQL Security.
> You are using a DSN, which means you are connecting using ODBC (not the
> fastest). It's better to use the native ADO driver for SQL Server.
> Go to the server in question and test the ODBC connection from the ODBC
> Control Panel Applet and make sure it works. maybe someone already
> changed the password or the server name changed.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Med103 wrote:
> Oops I was kind of wondering about that . It doesn't work anyway,
> but when I try to use the ODBC Control Panel I get the same error
> posted above. I also tried changing users, but it kept giving me an
> error message Invalid connection string; connection failed.. Can I
> just create a new database user in the enterprise manager and see if
> I can change it in the connection string?
Sure can. Give that a shot. Once you get it working in the ODBC control
panel applet, you should be good to go.
David Gugick
Imceda Software
www.imceda.com
Monday, March 12, 2012
maximum of DBprocess already allocated
Hi all,
Sql server 7.0
our client is getting the below error while accessing the web application
Maximum number of DBPROCESSes already allocated
when we check the server from our side its working fine.
please let us know is the solution for this.
TIATHis should help . . . (watch wraparound)
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q164/1/71.asp&NoWebContent=1&NoWebContent=1|||hi thanks for the reply
the error we are getting is given more detailed below
DBPool - Failed to initialize RWDBConnection
Unknown Exception caught in DBConnPool::createConnection() -- RWDatabase::connection() or validation of the connection returned failed
Database middleware messages:
ErrorCode: vendorLib Msg VENDORLIB] Vendor Library Error: Maximum number of DBPROCESSes already allocated
Pls help!!!!
Sql server 7.0
our client is getting the below error while accessing the web application
Maximum number of DBPROCESSes already allocated
when we check the server from our side its working fine.
please let us know is the solution for this.
TIATHis should help . . . (watch wraparound)
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q164/1/71.asp&NoWebContent=1&NoWebContent=1|||hi thanks for the reply
the error we are getting is given more detailed below
DBPool - Failed to initialize RWDBConnection
Unknown Exception caught in DBConnPool::createConnection() -- RWDatabase::connection() or validation of the connection returned failed
Database middleware messages:
ErrorCode: vendorLib Msg VENDORLIB] Vendor Library Error: Maximum number of DBPROCESSes already allocated
Pls help!!!!
maximum number of processes already allocated
Hi all,
Sql server 7.0
our client is getting the below error while accessing the
web application
Maximum number of DBPROCESSes already allocated
when we check the server from our side its working fine.
please let us know is the solution for this.
TIAHi,
Can you please check the "No of user connections" configured in Client's SQL
server.
How to check
From query Analyzer execute the below statement
sp_configure 'user connections'
If the run value is '0' then the allocation is dynamic and problem should be
because of some other issue. Incase if the run value is very low then
increase the value to a higher amount using. Eg to increase it to 100
connections.
sp_configure 'user connections',100
go
reconfigure with override
After this restart the MSSQL server service. If they still have issues
please attach the SQL server error log created during problem situation.
Thanks
Hari
MCDBA
"haseeb" <anonymous@.discussions.microsoft.com> wrote in message
news:a62d01c406e5$0c0e07a0$a301280a@.phx.gbl...
> Hi all,
> Sql server 7.0
> our client is getting the below error while accessing the
> web application
> Maximum number of DBPROCESSes already allocated
> when we check the server from our side its working fine.
> please let us know is the solution for this.
> TIA
>
Sql server 7.0
our client is getting the below error while accessing the
web application
Maximum number of DBPROCESSes already allocated
when we check the server from our side its working fine.
please let us know is the solution for this.
TIAHi,
Can you please check the "No of user connections" configured in Client's SQL
server.
How to check
From query Analyzer execute the below statement
sp_configure 'user connections'
If the run value is '0' then the allocation is dynamic and problem should be
because of some other issue. Incase if the run value is very low then
increase the value to a higher amount using. Eg to increase it to 100
connections.
sp_configure 'user connections',100
go
reconfigure with override
After this restart the MSSQL server service. If they still have issues
please attach the SQL server error log created during problem situation.
Thanks
Hari
MCDBA
"haseeb" <anonymous@.discussions.microsoft.com> wrote in message
news:a62d01c406e5$0c0e07a0$a301280a@.phx.gbl...
> Hi all,
> Sql server 7.0
> our client is getting the below error while accessing the
> web application
> Maximum number of DBPROCESSes already allocated
> when we check the server from our side its working fine.
> please let us know is the solution for this.
> TIA
>
Subscribe to:
Posts (Atom)