SQL Server 2005 Express Beta messes up your SQL Server 2000, BEWARE

ERROR after uninstalling SQL Server 2005 Express

I get this message,

SQLDMO has not been registered. Please re-run your setupand contact your
system administrator.

GREAT!!! ReInstalled SQL SERVER 2000 after playing around with SQL Server
2005...

Snap In Failed to Initialize,
Name: Sql SErver Enterprise Manager
CSLID: (00100100-1816-11D0-8EF5-00AA0062C58F)



THIS IS NOT BETA, this ALPHA!!!


Year 2006 here we come.....

I'm running SQL2000 as well as SQL2005beta, and I have had no problems 
installing.  Although I haven't used SQL2005b in any projects yet...

John

Hi Ik,

From the last messages I saw from you that it is not serious what you are
writing, however in Microsoft groups people are often looking what nicks and
what email addresses are used. Names as Ikll@hotmail and even showing that
you do not attended cross posting shows mostly people who cannot be taken
serious.

Therefore, when you want to have your fun, hide your goal better, now you
get probably only answers from newbie's in newsgroups. (You reached probably
a part of your goal getting an answer from me).

Some advices to prevent this:
-    Do not show so obvious that you are hiding your identity.
-    do not cross post to newsgroups that do not have to do with the
subject.

 Do not expect an answer from me on a reaction from you, it will not be.
 Just my thought,

Cor

This is a beta after all, and I trust you do not install beta software on a production machine?

There's at least one thread with your scenario at the proper beta newsgroup for SQL Express. You find
information about that group at the same place where you downloaded SQL Express.

-- 
Tibor Karaszi, SQL Server MVP
 http://www.**--****.com/ 
 http://www.**--****.com/ 

I don't have a handy test machine to try to reproduce this, but first 
try this, if the only thing that's broken is Enterprise Manager:

1.  Open a command window.
2.  Navigate to the SQL Server 2000 tools\binn directory, usually 
c:\program files\microsoft sql server\80\tools\binn
3. Run REGSVR32 /U SQLMMC.DLL to reregister the snapin.

If that doesn't work, I'll be happy to report the problem to Microsoft 
if you post back with some more detail:

Steps to reproduce sound like this, with a few questions:.
1.  Install SQL Server 2000
1.5 ???Did you install .NET Framework 2.0 here or before step 1?
1.7 ???Do you know if Enterprise Manager worked at this point?
2.  Install SQL Server 2005 Express Edition
2.5 ???Do you know if Enterprise Manager worked at this point?
3.  Uninstall SQL Server 2005 Express Edition
3.5 ???Did you uninstall .NET Framework 2.0 also?
4.  Enterprise Manager doesn't work.

What operating system are you using?
What version/service pack of SQL Server 2000 do you have?

Steve Kass
Drew University

> THIS IS NOT BETA, this ALPHA!!!

Oh brother, I'll echo Tibor's sentiment.  If you install beta software on 
production machines, don't cry to the vendor.

Please post to the SQL Server Express newsgroup.  What does this have to do 
with the .net framework, vb.net, c#, and programming in SQL Server? 

 http://www.**--****.com/ 

hth
andrew

 http://www.**--****.com/ 

You seem to have a problem with playing around with beta software on
machines that you cannot afford to have problems with, as this is the second
set of threads where you have LOUDLY complained about how dumb Microsoft is.
IMO, installing betaware (from anyone) on a production machine is a very
ignorant and/or stupid maneuver.

As we are a group that is horrible at reading readme files, where it tells
you not to install betas on production machines, the first time is
understandable. We pull out our media and get going. IN all fairness to the
manufacturer, we realize it was our mistake and move on. You seem to have a
problem with the idea that you could be at fault one iota.

It is a great service, for me, to have access to products before release. It
helps me stay ahead of the crowd when the final release is out. But, if I
were Microsoft, I would consider stopping the public betas, largely because
of people who complain when a public beta is released.

-- 
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************

Cowboy,

Well said.  My sentiments exactly.

-Sam Matzen


"Cowboy (Gregory A. Beamer) [MVP]" < XXXX@XXXXX.COM > wrote


second
is.
the
a
It
because



Server

First off, MICROSOFT, doesn't listen you and there is definite proof of that
over and over again.

To even think that a README and a BETA disclaimer allows you to put
something out that they should have already tested on their owe in house
server shows how out of touch your are with the real world.

When you put out a BETA, why not test it on lots and lots other microsoft
computers first.  I got these bugs immediately...there are so many bugs, but
to{*filter*}up SQL Server 2000 on the same machine, COME ON?

Of course it's on the development machine!!  I am not going to dedicate an
entire computer to testing a beta, NITWIT!!!

I am also smart enough to NOT put it on production, BUT OF COURSE, you, MR.
MVP, know all about production, RIGHT?  WRONG, YOU DON'T know anything about
production because if your are an MVP because you can't be in two places at
the same time and since you spend all you time answering the same questions
over and over again, you can't actually be doing REAL WORK, nitwit.....






"Cowboy (Gregory A. Beamer) [MVP]" < XXXX@XXXXX.COM > wrote


second
is.
the
a
It
because



Server

> Of course it's on the development machine!!  I am not going to dedicate an

What are you whining about?  Did someone hold a gun to your head and force 
you to install the software?  GROW UP! 

Wow, I guess Beta means nothing to some people. I can certainly remember
back to when there weren't such wide open Beta's and it was difficult even
to get a Beta copy of anything much less something like SQL server.

I can even remember some beta licenses that required a full disk format
before installation.

It's BETA it can and may wipe out your whole system. If you can't risk the
system you are putting it on, then don't put it on, and wait for a release
version.

It is just like {*filter*}, if you can't afford to lose the $100 in your
pocket, then keep it there and don't bet it on roulette.

Even if you can afford to lose it, don't bet it on roulette. Horrible vig.
Find yourself a 10 times odds craps table during off hours. Closest thing to
a fair shake you're likely to find in a {*filter*}. But that's neither here nor
there. Your point is well taken.