Enterprise Manager very slow on XP Pro

Hi,
I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
same version of SQL installed on W2K / P3. The Enterprise Manager seems to
run much slower on XP than on W2K. A simple click in the left pane (e.g. on
'databases') results in 20-30 second wait (the disk led is lit solid during
that time).
Could anyone please give me any suggestions as to what I should be looking
for on the XP machine?
Thanks,
Bogdan
> I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
> same version of SQL installed on W2K / P3. The Enterprise Manager seems
to
> run much slower on XP than on W2K. A simple click in the left pane (e.g.
on
> 'databases') results in 20-30 second wait (the disk led is lit solid
during
> that time).
Do please check if your databases have the autoclose option turned on. This
is default for Personal edition, and it takes time to open all databases.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
|||Also verify that you have no ODBC tracing turned on.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in message
news:u2kKHRKRFHA.3704@.TK2MSFTNGP12.phx.gbl...
> to
> on
> during
> Do please check if your databases have the autoclose option turned on. This
> is default for Personal edition, and it takes time to open all databases.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
>
|||Neither of the databases had auto-close enabled. The ODBC tracing was not
enabled (although I'm not using ODBC to connect to any of the databases and
I hope that Enterprise Manager does not use it either).
What seemed to work was SP3a. I applied it last night and things appear to
be 'normal' now.
Dejan, Tibor: thanks for your responses.
Bogdan
"Bogdan" <someone@.domain.com> wrote in message
news:%237JkLWIRFHA.1416@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
> same version of SQL installed on W2K / P3. The Enterprise Manager seems
> to run much slower on XP than on W2K. A simple click in the left pane
> (e.g. on 'databases') results in 20-30 second wait (the disk led is lit
> solid during that time).
> Could anyone please give me any suggestions as to what I should be looking
> for on the XP machine?
> Thanks,
> Bogdan
>
|||> I hope that Enterprise Manager does not use it either).
Both EM and QA uses ODBC.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bogdan" <someone@.domain.com> wrote in message news:e3FUs4URFHA.3944@.TK2MSFTNGP10.phx.gbl...
> Neither of the databases had auto-close enabled. The ODBC tracing was not enabled (although I'm
> not using ODBC to connect to any of the databases and I hope that Enterprise Manager does not use
> it either).
> What seemed to work was SP3a. I applied it last night and things appear to be 'normal' now.
> Dejan, Tibor: thanks for your responses.
> Bogdan
>
> "Bogdan" <someone@.domain.com> wrote in message news:%237JkLWIRFHA.1416@.TK2MSFTNGP10.phx.gbl...
>
|||Dejan Sarka wrote:
> Do please check if your databases have the autoclose option turned
> on. This is default for Personal edition, and it takes time to open
> all databases.
I've had a laptop that's been slow for months with QA and SQL EM and
it's been driving me crazy. Even pressing the Cancel button from the
Database properties in SQL EM caused undue database and disk activity.
Checked the databases, and sure enough, there was one user database that
mysteriously had Auto Close turned on. Probably turned it on for testing
and forgot to turn it off.
You fixed me. Thanks.
David Gugick
Imceda Software
www.imceda.com
|||If you want fast access to your database try SQL Admin Studio from
www.simego.com as this tool is just amazingly fast at connecting and
browsing SQL Server Databases.
"Bogdan" <someone@.domain.com> wrote in message
news:%237JkLWIRFHA.1416@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have SQL 2000 Personal Edition / SP3 on XP Pro, P4/HT. I also have the
> same version of SQL installed on W2K / P3. The Enterprise Manager seems
> to run much slower on XP than on W2K. A simple click in the left pane
> (e.g. on 'databases') results in 20-30 second wait (the disk led is lit
> solid during that time).
> Could anyone please give me any suggestions as to what I should be looking
> for on the XP machine?
> Thanks,
> Bogdan
>
|||Another way that I've seen autoclose turned on is when
moving a database from MSDE to MSSQL.
MSDE, IIRC, defaults to autoclose on.
jg

Quote:

Originally posted by David Gugick
Dejan Sarka wrote:
> Do please check if your databases have the autoclose option turned
> on. This is default for Personal edition, and it takes time to open
> all databases.
I've had a laptop that's been slow for months with QA and SQL EM and
it's been driving me crazy. Even pressing the Cancel button from the
Database properties in SQL EM caused undue database and disk activity.
Checked the databases, and sure enough, there was one user database that
mysteriously had Auto Close turned on. Probably turned it on for testing
and forgot to turn it off.
You fixed me. Thanks.
David Gugick
Imceda Software
www.imceda.com

Enterprise Manager Tools SQL2000

I have a new laptop with xp pro. Where are the client tools for SQL2000?
I need Query Anzlyser and Enterprise Mgr.

Thanks,
MikeHi Mike,

The SQL Server client tools are part of the SQL Server installation and come with the SQL Server CD.

See the following KB article: (see section: To Install Client Tools Only for SQL Server 2000)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303747

This is not included as part of Windows XP Professional.

Regards,
Vikram

Enterprise Manager Server Registration General Network Error

I'm having problems Registering servers in Enterrpise Manager.
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Gene
ral network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Conn
ectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Beginkb below has some good troubleshooting steps
http://support.microsoft.com/defaul...kb;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Ge
neral
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Co
nnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Gene
ral network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Conn
ectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from th
e
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authenticatio
n
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:

> kb below has some good troubleshooting steps
> http://support.microsoft.com/defaul...kb;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>

Enterprise Manager Server Registration General Network Error

I'm having problems Registering servers in Enterrpise Manager.
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. Hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Begin
kb below has some good troubleshooting steps
http://support.microsoft.com/default...b;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. Hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>
|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from the
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authentication
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:

> kb below has some good troubleshooting steps
> http://support.microsoft.com/default...b;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>

enterprise manager on Windows XP x64

I have just installed Windows XP Pro x64 on new computer and having hard
time installing enterprise manager (SQL Server 2000) to connect to my SQL
2000 Server running on remote machine.
Is there any version of SQL Client Tools for x64 or I have to purchase SQL
Server 2005.
Thanks,
Vlado"Vlado Jasovic \(www.excelleinc.com\)" <vjasovicATexcelleincDOTcom>
wrote in news:LIydnU5LKY-WLuLenZ2dnUVZ_tidnZ2d@.giganews.com:
> I have just installed Windows XP Pro x64 on new computer and having
> hard time installing enterprise manager (SQL Server 2000) to connect
> to my SQL 2000 Server running on remote machine.
You can install and run the 32-bit version of Enterprise Manager. As far as
I know there is no 64-bit version of it.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging

enterprise manager on Windows XP x64

I have just installed Windows XP Pro x64 on new computer and having hard
time installing enterprise manager (SQL Server 2000) to connect to my SQL
2000 Server running on remote machine.
Is there any version of SQL Client Tools for x64 or I have to purchase SQL
Server 2005.
Thanks,
Vlado
"Vlado Jasovic \(www.excelleinc.com\)" <vjasovicATexcelleincDOTcom>
wrote in news:LIydnU5LKY-WLuLenZ2dnUVZ_tidnZ2d@.giganews.com:

> I have just installed Windows XP Pro x64 on new computer and having
> hard time installing enterprise manager (SQL Server 2000) to connect
> to my SQL 2000 Server running on remote machine.
You can install and run the 32-bit version of Enterprise Manager. As far as
I know there is no 64-bit version of it.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging

enterprise manager on Windows XP x64

I have just installed Windows XP Pro x64 on new computer and having hard
time installing enterprise manager (SQL Server 2000) to connect to my SQL
2000 Server running on remote machine.
Is there any version of SQL Client Tools for x64 or I have to purchase SQL
Server 2005.
Thanks,
Vlado"Vlado Jasovic \(www.excelleinc.com\)" <vjasovicATexcelleincDOTcom>
wrote in news:LIydnU5LKY-WLuLenZ2dnUVZ_tidnZ2d@.giganews.com:

> I have just installed Windows XP Pro x64 on new computer and having
> hard time installing enterprise manager (SQL Server 2000) to connect
> to my SQL 2000 Server running on remote machine.
You can install and run the 32-bit version of Enterprise Manager. As far as
I know there is no 64-bit version of it.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging

Enterprise Manager error

After installing Enterprise Manager on a new HP laptop running XP Pro sp2, I get the following error message when to trying to "Return all rows" from a table. "Provider cannot be found. It may not be properly installed."

Everything I read on the internet says to install or reinstall Jet 4.0 sp8, but this has not solved the problem. I've also installed the latest MDAC...MDAC 2.8 SP1 on Windows XP SP2, and ran the compchecker, everthing checks out ok. Any ideas?

Thanks
T.C.

I have a new Sony VAIO laptop and am running XP Pro sp2 and get the same error when trying to open a table in any database.
I just installed SQL2000 sp4 hoping the error would go away...it didn't.
Did your problem ever get resolved?
|||

Hello,

I had searched through Google and Microsoft website for the error message. I find a few matches. You could try the solution suggested in http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=44561. Another link with suggestion from alleged Microsoft online support is http://www.mcse.ms/message201860.html. It could be due to MDAC issue.

Enterprise Manager error

After installing Enterprise Manager on a new HP laptop running XP Pro sp2, I get the following error message when to trying to "Return all rows" from a table. "Provider cannot be found. It may not be properly installed."

Everything I read on the internet says to install or reinstall Jet 4.0 sp8, but this has not solved the problem. I've also installed the latest MDAC...MDAC 2.8 SP1 on Windows XP SP2, and ran the compchecker, everthing checks out ok. Any ideas?

Thanks
T.C.

I have a new Sony VAIO laptop and am running XP Pro sp2 and get the same error when trying to open a table in any database.
I just installed SQL2000 sp4 hoping the error would go away...it didn't.
Did your problem ever get resolved?
|||

Hello,

I had searched through Google and Microsoft website for the error message. I find a few matches. You could try the solution suggested in http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=44561. Another link with suggestion from alleged Microsoft online support is http://www.mcse.ms/message201860.html. It could be due to MDAC issue.

Enterprise Manager error

After installing Enterprise Manager on a new HP laptop running XP Pro sp2, I get the following error message when to trying to "Return all rows" from a table. "Provider cannot be found. It may not be properly installed."

Everything I read on the internet says to install or reinstall Jet 4.0 sp8, but this has not solved the problem. I've also installed the latest MDAC...MDAC 2.8 SP1 on Windows XP SP2, and ran the compchecker, everthing checks out ok. Any ideas?

Thanks
T.C.

I have a new Sony VAIO laptop and am running XP Pro sp2 and get the same error when trying to open a table in any database.

I just installed SQL2000 sp4 hoping the error would go away...it didn't.

Did your problem ever get resolved?|||

Hello,

I had searched through Google and Microsoft website for the error message. I find a few matches. You could try the solution suggested in http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=44561. Another link with suggestion from alleged Microsoft online support is http://www.mcse.ms/message201860.html. It could be due to MDAC issue.