Enterprise Manager problem

Using SQL2000 with Enterprise Manager - sometimes, when we try to expand any
tab, such as databases or management, it comes back as empty!! Only
rebooting the server will make it come back but then at some point it stops
working again!
Any ideas much appreciated...
Best regards
Mark
Hello Mark,
Have you tried to reinstall the Enterprise Manager?
Have you applied the latest services pack of the SQL Server?
Did this issue only occur on the local server or remote server?
Please try to reinstall the Enterprise Manager and let me know the result.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi Wei Lu,
The problem happens on every client on which Enterprise Manager is
installed. It also happens if I make a remote connection. If we reboot the
server then the problem goes away on all clients but then just comes back
after a few days.
Interestingly, while the server is in this "broken" state, using SQL 2005
Management Studio seems to work with no problems.
Best regards
Mark
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:NdFWZcMSHHA.2268@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mark,
> Have you tried to reinstall the Enterprise Manager?
> Have you applied the latest services pack of the SQL Server?
> Did this issue only occur on the local server or remote server?
> Please try to reinstall the Enterprise Manager and let me know the result.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
|||On Feb 6, 6:54 am, "Mark Baldwin" <sWoz...@.community.nospam> wrote:
> Hi Wei Lu,
> The problem happens on every client on which Enterprise Manager is
> installed. It also happens if I make a remote connection. If we reboot the
> server then the problem goes away on all clients but then just comes back
> after a few days.
> Interestingly, while the server is in this "broken" state, using SQL 2005
> Management Studio seems to work with no problems.
>
Wei Lu asked about service packs, you didn't answer. Are the CLIENTS
at the same service pack level as the SERVER? If not, you can see
strange things like this occur.
|||Hello Mark,
Have you applied the same service pack on all the clients?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Enterprise Manager problem

Using SQL2000 with Enterprise Manager - sometimes, when we try to expand any
tab, such as databases or management, it comes back as empty!! Only
rebooting the server will make it come back but then at some point it stops
working again!
Any ideas much appreciated...
Best regards
MarkHello Mark,
Have you tried to reinstall the Enterprise Manager?
Have you applied the latest services pack of the SQL Server?
Did this issue only occur on the local server or remote server?
Please try to reinstall the Enterprise Manager and let me know the result.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Wei Lu,
The problem happens on every client on which Enterprise Manager is
installed. It also happens if I make a remote connection. If we reboot the
server then the problem goes away on all clients but then just comes back
after a few days.
Interestingly, while the server is in this "broken" state, using SQL 2005
Management Studio seems to work with no problems.
Best regards
Mark
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:NdFWZcMSHHA.2268@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mark,
> Have you tried to reinstall the Enterprise Manager?
> Have you applied the latest services pack of the SQL Server?
> Did this issue only occur on the local server or remote server?
> Please try to reinstall the Enterprise Manager and let me know the result.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> Get notification to my posts through email? Please refer to
> l]
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> [url]http://msdn.microsoft.com/subscriptions/support/default.aspx." target="_blank">http://msdn.microsoft.com/subscript...t/default.aspx.
> ========================================
==========
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||On Feb 6, 6:54 am, "Mark Baldwin" <sWoz...@.community.nospam> wrote:
> Hi Wei Lu,
> The problem happens on every client on which Enterprise Manager is
> installed. It also happens if I make a remote connection. If we reboot the
> server then the problem goes away on all clients but then just comes back
> after a few days.
> Interestingly, while the server is in this "broken" state, using SQL 2005
> Management Studio seems to work with no problems.
>
Wei Lu asked about service packs, you didn't answer. Are the CLIENTS
at the same service pack level as the SERVER? If not, you can see
strange things like this occur.|||Hello Mark,
Have you applied the same service pack on all the clients?
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.

Enterprise Manager problem

Using SQL2000 with Enterprise Manager - sometimes, when we try to expand any
tab, such as databases or management, it comes back as empty!! Only
rebooting the server will make it come back but then at some point it stops
working again!
Any ideas much appreciated...
--
Best regards
MarkHello Mark,
Have you tried to reinstall the Enterprise Manager?
Have you applied the latest services pack of the SQL Server?
Did this issue only occur on the local server or remote server?
Please try to reinstall the Enterprise Manager and let me know the result.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Wei Lu,
The problem happens on every client on which Enterprise Manager is
installed. It also happens if I make a remote connection. If we reboot the
server then the problem goes away on all clients but then just comes back
after a few days.
Interestingly, while the server is in this "broken" state, using SQL 2005
Management Studio seems to work with no problems.
--
Best regards
Mark
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:NdFWZcMSHHA.2268@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mark,
> Have you tried to reinstall the Enterprise Manager?
> Have you applied the latest services pack of the SQL Server?
> Did this issue only occur on the local server or remote server?
> Please try to reinstall the Enterprise Manager and let me know the result.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||On Feb 6, 6:54 am, "Mark Baldwin" <sWoz...@.community.nospam> wrote:
> Hi Wei Lu,
> The problem happens on every client on which Enterprise Manager is
> installed. It also happens if I make a remote connection. If we reboot the
> server then the problem goes away on all clients but then just comes back
> after a few days.
> Interestingly, while the server is in this "broken" state, using SQL 2005
> Management Studio seems to work with no problems.
>
Wei Lu asked about service packs, you didn't answer. Are the CLIENTS
at the same service pack level as the SERVER? If not, you can see
strange things like this occur.|||Hello Mark,
Have you applied the same service pack on all the clients?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Enterprise Manager Corrupted?

We create a simple maintenance plan with no error. When we go back to edit the settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (although we can manually enter a number), and the drop-down that should show "hours", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?
Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>
|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>
|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter

Enterprise Manager Corrupted?

We create a simple maintenance plan with no error. When we go back to edit t
he settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup
files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (althoug
h we can manually enter a number), and the drop-down that should show "hours
", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter|||The SQL Server 2000 instance was originally installed (by another
consultant) last summer. I doubt that any hot fixes were applied before we
came onto the scene in December, since, as you saw, they never got around to
applying SP3.
The master/msdb were installed fresh, I'm sure (the other vendor wasn't
sophisticated enough to know how to do any of that.
Any other thoughts? I'm sort of getting the idea that we probably have no
choice but to rip it out and reinstall?
J
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OHyiE7oGEHA.2052@.TK2MSFTNGP11.phx.gbl...
> What is the database compatibility? What hotfixes have been applied?
Have
> you restored master or msdb from another place or another version?
> I'm just trying to think of things which would make a system-used datatype
> change, and usually these are restricted to service pack/version releases.
> A
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
>

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
RonYou can try to reinstall the SQL Server service pack to start with...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>

Enterprise Manager broken on SQL 2000, how to put back

I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
SQL appears to be running fine and my SQL applications are working fine too.
How can I put back my SQL Enterprise Manager and SQL Query Analyser?
If I reinstall SQL 2000 will that mess up my installed SQL applications?
Will SQL installer attempt to "repair" things with messing up my installed
databases?
My SQL applications/databases are a bear to reinstall and I don't want to if
I don't have to. Like I said, they are running fine.
Greatful for any help.
Ron
You can try to reinstall the SQL Server service pack to start with...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A7A214E5-B073-4988-8E18-8464F2407483@.microsoft.com...
> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>
|||Thank you for your response. I tried first to restart the SQL server. Boy,
that was a mistake (of sorts). When the server came back up, none of the SQL
applications were working (although the SQL service had started).
Tried to reinstall SP3 as suggested (thank you) but niether windows
authentication nor the sa account would work.
So, out of desperation I reinstalled Veritas Backupexec 91 for servers. I
rebooted the machine and bingo, the SQL apps could access the SQL databases
again!
But SQL is still broken, in that Enterprise Manager and SQL query will not
run.
I am almost to the point where I am going to try reinstalling SQL.
Will it recognize my existing SQL databases or will I have to reinstall
everything?
The Win 2003 server itself is fine, it's just that SQL is "not all there" it
seems.
Ron
"Ron" wrote:

> I uninstalled Veritas Backup Exec 90 from my SQL 2000 server.
> Now, none of my SQL "Snap Ins" (SQL Query, Enterprise Manager) work.
> SQL appears to be running fine and my SQL applications are working fine too.
> How can I put back my SQL Enterprise Manager and SQL Query Analyser?
> If I reinstall SQL 2000 will that mess up my installed SQL applications?
> Will SQL installer attempt to "repair" things with messing up my installed
> databases?
> My SQL applications/databases are a bear to reinstall and I don't want to if
> I don't have to. Like I said, they are running fine.
> Greatful for any help.
> Ron
>