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

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

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

MDAC 2.71 Memory Leak

Hi everyone,
I understand SQL Server 2000 SP3 contains an MDAC 2.71
version that causes Memory Leak. However, If I install
MDAC 2.71 through Windows Update, would the server suffer
from Memory Leak also?
I have an SQL 2000 server running on Win 2K. My server
was never installed SP3. But, I did update MDAC 2.7
version via Windows Update. Few months later, my server
now is experiencing Memory Leak. When I run MDAC component
checker, there does have mismatches of MDAC 2.7 SP1 or 2.7
XP SP1. I wonder how do I fix that? I don't really want
to install SP3a. Would install the latest version of MDAC
(2.71a) fix the problem?
Thank you very very very much!!
AnnieHave you looked at the date and time stamp related to the
MDAC installation ? Is this on a dual or higher processor
server ? I am researching the same but on multiple
processor problem with the MDAC.
Bruce
>--Original Message--
>Hi everyone,
> I understand SQL Server 2000 SP3 contains an MDAC 2.71
>version that causes Memory Leak. However, If I install
>MDAC 2.71 through Windows Update, would the server suffer
>from Memory Leak also?
> I have an SQL 2000 server running on Win 2K. My server
>was never installed SP3. But, I did update MDAC 2.7
>version via Windows Update. Few months later, my server
>now is experiencing Memory Leak. When I run MDAC
component
>checker, there does have mismatches of MDAC 2.7 SP1 or
2.7
>XP SP1. I wonder how do I fix that? I don't really want
>to install SP3a. Would install the latest version of MDAC
>(2.71a) fix the problem?
>Thank you very very very much!!
>Annie
>.
>|||Mine is Dual processor.
I run MDAC Component Check on my SQL Server 2000. None
of the versions of MDAC passed the tests. The closest one
is 2.7 SP1 (2.71.9030.9) with only One error on
msjtes40.dll file:
msjtes40.dll,Error,Field 'FileVersion' mismatch:
Expect '4.00.2927.8' Got '4.00.5914.0',Microsoft Jet
Expression
There is another MDAC version came out call MDAC 2.71
Refresh. The difference between MDAC 2.71 and 2.71
Refresh is mdac_typ.exe file posted on MS website.
But, I don't know what files does this mdac_typ.exe
alter.
What's your problem?
Annie
>--Original Message--
>Have you looked at the date and time stamp related to the
>MDAC installation ? Is this on a dual or higher processor
>server ? I am researching the same but on multiple
>processor problem with the MDAC.
>Bruce
>>--Original Message--
>>Hi everyone,
>> I understand SQL Server 2000 SP3 contains an MDAC 2.71
>>version that causes Memory Leak. However, If I install
>>MDAC 2.71 through Windows Update, would the server
suffer
>>from Memory Leak also?
>> I have an SQL 2000 server running on Win 2K. My
server
>>was never installed SP3. But, I did update MDAC 2.7
>>version via Windows Update. Few months later, my server
>>now is experiencing Memory Leak. When I run MDAC
>component
>>checker, there does have mismatches of MDAC 2.7 SP1 or
>2.7
>>XP SP1. I wonder how do I fix that? I don't really
want
>>to install SP3a. Would install the latest version of
MDAC
>>(2.71a) fix the problem?
>>Thank you very very very much!!
>>Annie
>>.
>.
>