469,271 Members | 1,785 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,271 developers. It's quick & easy.

Problems running Enterprise Manager and Service Manager

PF
On one of our machines, all of the SQL Server 2000
components except for the main Server component (SQL Server
core) itself were installed (Management tools, etc) a while ago
and everything was running fine. Now I go and add/install the
Server component and then Service Pack 3a.

It seems that Service Manager won't start up (I get an hourglass cursor)
and now I find that Enterprise Manager won't run as well. No error
messages appeared and I don't think I saw anything unusual in
the log file.

However, I can use Enterprise Manager on a different
machine and connect to the database (so the database
itself seems to be running).

Any suggestions as to what the problem might be and how to
fix it? I like to see if I can repair this without having
to do a reinstall.

Thanks.

PF

Jul 20 '05 #1
2 2163
PF (pf****@hotmail.com) writes:
On one of our machines, all of the SQL Server 2000
components except for the main Server component (SQL Server
core) itself were installed (Management tools, etc) a while ago
and everything was running fine. Now I go and add/install the
Server component and then Service Pack 3a.

It seems that Service Manager won't start up (I get an hourglass cursor)
and now I find that Enterprise Manager won't run as well. No error
messages appeared and I don't think I saw anything unusual in
the log file.

However, I can use Enterprise Manager on a different
machine and connect to the database (so the database
itself seems to be running).

Any suggestions as to what the problem might be and how to
fix it? I like to see if I can repair this without having
to do a reinstall.


This sounds like something I ran into on my work machine some time
back. I got the machine from our sysadmin with a cloned standard
setup, which included SQL Server tools and utilities, but not the
server. I installed the server and applied SP3, and then none of
the SQL tools would start. If I attempted to start Query Analyzer,
isqlw.exe would show up in Task Manager, but not getting any CPU
time and the GUI never showed up.

OSQL was even funnier. From the one tool that could connect - ISQL -
I could see that the OSQL created multipled connections to SQL Server
until it finally croaked with an error message.

Since ISQL, which connects through DB-Library, worked, my suspicioun was
that the problem was related to ODBC in some way, I did try to reinstall the
MDAC, but no avail. If you are really dead set on sorting this out without
reinstalling, you could pursue that track.

Myself, I uninstalled all of SQL Server and reinstalled. Since this was
a new machine, this was not of an issue.

You didn't say which OS you had. Mine was Windows XP SP1.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 20 '05 #2
[Posted and mailed]

"PF" <pf****@hotmail.com> writes:
On one of our machines, all of the SQL Server 2000
components except for the main Server component (SQL Server
core) itself were installed (Management tools, etc) a while ago
and everything was running fine. Now I go and add/install the
Server component and then Service Pack 3a.

It seems that Service Manager won't start up (I get an hourglass cursor)
and now I find that Enterprise Manager won't run as well. No error
messages appeared and I don't think I saw anything unusual in
the log file.

However, I can use Enterprise Manager on a different
machine and connect to the database (so the database
itself seems to be running).

Any suggestions as to what the problem might be and how to
fix it? I like to see if I can repair this without having
to do a reinstall.

OK, so I brought this up with my contacts with Microsoft, who gave me
two suggestions:

1) Reapply MDAC 2.8. (Which was what I tried myself without success)

2) look at dasetup.log in the winnt directory, the setup log for MDAC.

Whatever, the reason is likely to be a case of mismatched dlls. I was
suggested that you run the Component Checker to find this out as well.

If you still have problems after reapplying the MDAC, post the dasetup.log
file, or mail it to me.
The MDAC and Component Checker are available for download from
www.microsoft.com. Unfortunately, I don't have direct links, but
I seem to recall that they easy to find if you search downloads.
--
Erland Sommarskog, Stockholm, es****@sommarskog.se

Jul 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Rafal Zurkowski | last post: by
2 posts views Thread by si.downes | last post: by
4 posts views Thread by Fred Nelson | last post: by
reply views Thread by zhoujie | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.