By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,842 Members | 2,440 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,842 IT Pros & Developers. It's quick & easy.

SQL fails after SP3a has been applied. Slammer?

P: n/a
A Win2k, SQL2k machine with SP2 that only just now has been updated to SP3a
fails in different ways. Among other things, when I now start Enterprise
Manager, I get a message saying "rebbrui.rll" is missing and the snap-in
fails to initiate. But then the Manager starts anyway.

But the SQL application does not work. I searched around the net, and I
found that it looks as if SQL Slammer has been on the server. I can tell by
the similar symptoms other users have had, allthough I am not sure. Anyway,
when I run some online virusscans and the Symantec SQLexp-tool to remove
Slammer, I am told that the system is virusfree. Is that because SP3a to
SQL2000 automatically got rid of the virus (if any)?

But how do I get the SQL to run without any errors again?

The server also runs in Terminal Application Mode.

Regards, Lars.
Jul 23 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a

"Lars Bonnesen" <no***@none.invalid> wrote in message
news:41*********************@dtext01.news.tele.dk. ..
A Win2k, SQL2k machine with SP2 that only just now has been updated to SP3a
fails in different ways. Among other things, when I now start Enterprise
Manager, I get a message saying "rebbrui.rll" is missing and the snap-in
fails to initiate. But then the Manager starts anyway.

But the SQL application does not work. I searched around the net, and I
found that it looks as if SQL Slammer has been on the server. I can tell
by
the similar symptoms other users have had, allthough I am not sure.
Anyway,
when I run some online virusscans and the Symantec SQLexp-tool to remove
Slammer, I am told that the system is virusfree. Is that because SP3a to
SQL2000 automatically got rid of the virus (if any)?

But how do I get the SQL to run without any errors again?

The server also runs in Terminal Application Mode.

Regards, Lars.


Based on this post (not many details, unfortunately), Terminal Application
Mode may be a problem:

http://tek-tips.com/viewthread.cfm?qid=732941

The SP3a readme does mention a problem with installing MSDE in Terminal
Services, but not with installing the full MSSQL product. You don't mention
your edition, but since you're using Enterprise Manager, I guess you
probably have Standard or Enterprise.

http://support.microsoft.com/default..._2000_sp3_d3jb

To fix the missing file error, you'll probably need to reinstall the client
tools, and if you cannot connect to MSSQL at all (what exactly does "the SQL
application does not work" mean?), or the service won't start, then it might
be worth simply uninstalling and reinstalling the whole thing anyway.

Then you can install SP3a, and finally restore or reattach your databases.
If that isn't a good solution for some reason (time, data loss etc.), then
it would probably be a good idea to call MS - support for problems caused by
bugs is free.

Simon
Jul 23 '05 #2

P: n/a

"Simon Hayes" <sq*@hayes.ch> wrote in message
news:41**********@news.bluewin.ch...
Based on this post (not many details, unfortunately), Terminal Application
Mode may be a problem:

http://tek-tips.com/viewthread.cfm?qid=732941
Did in fact find that URL during my netsearch for a solution. The problem
with that is that "Add/remove programms" assumes you are installing from a
CD - and I have the SP3a patch downloaded on disk. What he thinks about when
saying "change user", I do not understand.
The SP3a readme does mention a problem with installing MSDE in Terminal
Services, but not with installing the full MSSQL product. You don't
mention your edition, but since you're using Enterprise Manager, I guess
you probably have Standard or Enterprise.
Well, it is not "my" installation, but I am pretty sure they run Standard
Edition.
http://support.microsoft.com/default..._2000_sp3_d3jb

To fix the missing file error, you'll probably need to reinstall the
client tools, and if you cannot connect to MSSQL at all (what exactly does
"the SQL application does not work" mean?),
That is a third party program, that uses the SQL-thing. It will not work.

Did I BTW mention, that I am able to view the databases through Enterprise
Manager - after getting passed that missing .rll file error?
or the service won't start,
The SQL service does start.
then it might be worth simply uninstalling and reinstalling the whole
thing anyway.
Yes, perhaps. But I wouldn't rather...
Then you can install SP3a, and finally restore or reattach your databases.
If that isn't a good solution for some reason (time, data loss etc.), then
it would probably be a good idea to call MS - support for problems caused
by bugs is free.


Sure, if it is a bug. The problem is that I am afraid it is because of the
Slammer. (Well which also is a result of a security bug).

Regards, Lars.
Jul 23 '05 #3

P: n/a

"Simon Hayes" <sq*@hayes.ch> wrote in message
news:41**********@news.bluewin.ch...

"Lars Bonnesen" <no***@none.invalid> wrote in message
news:41*********************@dtext01.news.tele.dk. .. http://tek-tips.com/viewthread.cfm?qid=732941

The SP3a readme does mention a problem with installing MSDE in Terminal
Services, but not with installing the full MSSQL product. You don't
mention your edition, but since you're using Enterprise Manager, I guess
you probably have Standard or Enterprise.
It definatly was because of the above. Apparently SP3a has to be installed
from add/remove when running Terminal Services in app. mode. I wasn't fully
aware of the way to run a program for other than a CD/disc in here, but that
seemed to be no problem at all.

Now the enterprise manager starts without any problems.

Then again, I still have some problems with a web app. that is running on
the server, but this is another story.
http://support.microsoft.com/default..._2000_sp3_d3jb

To fix the missing file error, you'll probably need to reinstall the
client tools, and if you cannot connect to MSSQL at all (what exactly does
"the SQL application does not work" mean?), or the service won't start,
then it might be worth simply uninstalling and reinstalling the whole
thing anyway.


Perhaps I have to do this if it is the SQL that is causing the problem with
the web app.

Regards, Lars.
Jul 23 '05 #4

P: n/a

"Lars Bonnesen" <no***@none.invalid> wrote in message
news:41*********************@dtext01.news.tele.dk. ..
Now the enterprise manager starts without any problems.

Then again, I still have some problems with a web app. that is running on
the server, but this is another story.


Well... a strange thing:

The application that is using the SQL works when I connect via Termina
Service.

But when another user connects to the SQL via Terminal Service with the same
credential, it does not.

The SQLagent seems to be not running. I get "An error 1060 - (The specified
service does not exist as an installed service) occoured ehile performing
this service operation on the SQLServerAgent service".

Now it looks to me as being a Terminal Service error. Am I correct?

Regards, Lars.
Jul 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.