BMCPatrol/BackupExec with MSDE and SQL Server Enterprise Edition

I have a odd situation and am unsure of my best option.
We use BMC Patrol to monitor an Enterprise Edition database. A server guy
came along and installed Backup Exec to make some one-off tape backups for a
vendor. He installed and decided to use MSDE. MSDE is now installed on my
server as well. I would never had known this except that BMC Patrol now has
no idea where my Enterprise Edition instance has gone to nor does it
recognize its existance.
BMC Patrol support bounced back the request for help by saying that MSDE has
"corrupted" registry settings and promoted itself somehow as the primary
instance in the registry.
Questions: Uninstalling MSDE did not resolve the situation.
- Is there such a registry setting?
- Is there a known, supported way to reverse this situation?
- Is my only alternative to re-install the SQL Server Enterprise Edition?
Thanks
hi Andy,
Andy Sprecher wrote:
> I have a odd situation and am unsure of my best option.
> We use BMC Patrol to monitor an Enterprise Edition database. A
> server guy came along and installed Backup Exec to make some one-off
> tape backups for a vendor. He installed and decided to use MSDE.
> MSDE is now installed on my server as well. I would never had known
> this except that BMC Patrol now has no idea where my Enterprise
> Edition instance has gone to nor does it recognize its existance.
> BMC Patrol support bounced back the request for help by saying that
> MSDE has "corrupted" registry settings and promoted itself somehow as
> the primary instance in the registry.
> Questions: Uninstalling MSDE did not resolve the situation.
> - Is there such a registry setting?
> - Is there a known, supported way to reverse this situation?
> - Is my only alternative to re-install the SQL Server Enterprise
> Edition?
I knew that installing MSDE sp3a on servers running SQL Server 2000 sp4 will
corrupt the registry in the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
SQLPath key
that's to say that breaks accessing Query Analyzer and SQL Profiler from
Enterprise manager, but this is the only problem I'm aware of.. BTW there's
no concept of "primary instance", just default and named instance, but
installing MSDE on a previously installed SQL Server (default or named
instance) server does not involve the reported scenario... this has been
tested for sure :D
I do not know which registry key is BMC Patrol tool querying on, and this
can be related to the reported corruption, but I really have no further
hints... I think you have to open a case with Microsoft PSS..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea Montanari wrote:
> I do not know which registry key is BMC Patrol tool querying on, and
> this can be related to the reported corruption, but I really have no
> further hints... I think you have to open a case with Microsoft PSS..
just an additional note... before calling Microsoft PSS, I'd check that your
Enterprise instance runs smoothly and as expected, that no errors are raised
(scan your log and event viewer) and I'd contact again BMC for the registry
key they thin are messed up...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Blackberry Server MSDE and active directory authentication

To all, thanks in advance,
I have blackberry server running sql msde 2000 (sp4), which is
authenticated via windows integrated with an active directory user
account. When I changed the password on said user account, restart the
mssqlserver service, it fails to start with a 560 error. I had to
changed said user account back to the old password in order for the
mssqlserver service to start. I wanted know where in ms sql msde 2000,
I needed to make the change in order for this service to start. I also
tried starting the service using local system account and it would not
start either. All help with this is greatly appreciated.
JB
Hi
Control Panel > Services. The Service can be stopped and started from there,
and the account password can be changed there for the service.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<jon.jefferson@.gmail.com> wrote in message
news:1131849352.800496.311170@.g47g2000cwa.googlegr oups.com...
> To all, thanks in advance,
> I have blackberry server running sql msde 2000 (sp4), which is
> authenticated via windows integrated with an active directory user
> account. When I changed the password on said user account, restart the
> mssqlserver service, it fails to start with a 560 error. I had to
> changed said user account back to the old password in order for the
> mssqlserver service to start. I wanted know where in ms sql msde 2000,
> I needed to make the change in order for this service to start. I also
> tried starting the service using local system account and it would not
> start either. All help with this is greatly appreciated.
> JB
>
|||Mike
Thanks for your response, but I did that and the service would not
start under with the new password. The only idea I did not try was to
restart the Server.
Thanks,
JB
|||Mike,
Also, there are other services that start with this same service
account (i.e. all the blackberry services,) and those start fine,
except for errors in the Apps event log because the msssqlserver
service would not start with the same user account change for some
strange reason. I am changing passwords to in AD because I am taking
over duties after someone has left and need to change passwords for
security purposes. This is my only hold up.
JB

Bizarre data loss running maintenance plan

I'm running MSDE 2000 SP4 on Win2KAS SP4 (fully patched). I have a
maintenance plan that backs up the database at 18:30 and backs up the
transaction log at midnight. Apparently the transaction log backups have
been failing because the database is set to the Simple recovery model. More
importantly, I'm losing updates to records that were updated prior to the
database backup! The inserted records are still there, but the updates
appear to have been rolled back (at least in one table where I've verifiied
the problem.) I'm running some more checks now and I've set the recovery
model to Full, but I'm interested in knowing if anyone else has seen anything
like this before.
hi,
Donald Welker wrote:
> I'm running MSDE 2000 SP4 on Win2KAS SP4 (fully patched). I have a
> maintenance plan that backs up the database at 18:30 and backs up the
> transaction log at midnight. Apparently the transaction log backups
> have been failing because the database is set to the Simple recovery
> model.
and this is a standard behavior :D

>More importantly, I'm losing updates to records that were
> updated prior to the database backup! The inserted records are still
> there, but the updates appear to have been rolled back (at least in
> one table where I've verifiied the problem.) I'm running some more
> checks now and I've set the recovery model to Full, but I'm
> interested in knowing if anyone else has seen anything like this
> before.
I do not think this has something to do with backup operation, even if
performed via Maintenance Plan (unfortunately a little buggy tool)... it's
actually not possible (and the simple recovery model is no guilty at all)
for a backup task to rollback update statements while committing insert...
the problem must be else where...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Overnight testing has isolated the occurence of the change to running the
transaction log backup at midnight. The data is fine at 23:55:01 and bad at
00:00:01. However it seems that I cannot reproduce this result even by
rescheduling the maintenance plan job steps to run in sequence during the
day. I've just dropped and replaced the maintenance plan (with a better
schedule) to see if that has any effect. Also, the new plan only backs up
this database rather than "All User Databases" (might also be related.)
"Andrea Montanari" wrote:

> hi,
> Donald Welker wrote:
> and this is a standard behavior :D
I've noticed.

> I do not think this has something to do with backup operation, even if
> performed via Maintenance Plan (unfortunately a little buggy tool)... it's
> actually not possible (and the simple recovery model is no guilty at all)
> for a backup task to rollback update statements while committing insert...
> the problem must be else where...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
It's happened three nights in a row so far, so it's certainly possible. It
still happened last night with Full recovery model, it just didn't record an
error anymore.