Problems with SQL Server/Enterprise mgr

  • Thread starter Thread starter Joel Zinn
  • Start date Start date
J

Joel Zinn

I have had problems getting SQL Server Enterprise manager since the
signature update prior to the last update.

Ent mgr will not start and I get the error message asking to send info to
MS, which I have done many times.

Not sure if MSAS has done this, but I had no problems prior to the signature
update late last week. I have even tried uninstalling and re-installing
Ent Mgr, but no help.

Anyone else having this problem?
 
-----Original Message-----
I have had problems getting SQL Server Enterprise
manager since the signature update prior to the last
update.
Ent mgr will not start and I get the error message asking to send info to
MS, which I have done many times.
Not sure if MSAS has done this, but I had no problems prior to the signature
update late last week. I have even tried uninstalling and re-installing
Ent Mgr, but no help.

Anyone else having this problem?

Hi

This is a Beta and to use betas within sensitive
corporate networks might not be a good idea, in this
case also within server environment.

I would directly uninstall MSAS and wait for a
enterprise version. You can maybe contact a MS
solution partner/provider for this request.

When I also see with all respect Electric Power involved,
hopefully not distribution/operation? I thinks about this
which also ruined SCADA systems.

http://ses.symantec.com/industry/power/article.cfm?
articleid=3186
 
I appreciate your concerns. This is a development box, not even a server.
I use Ent Mgr to access some test db's on my development servers.
 
Joel said:
I appreciate your concerns. This is a development box, not even a server.
I use Ent Mgr to access some test db's on my development servers.

Hi

Great !

Electric power and Slammer woke me up some years ago
when one nuclear plant used a SQL database for SCADA
and one hired software programmer opened up for
Slammer from a portable PC..........


I think anyone else maybe can give you a clue about MSAS
and SQL issues.
 
Someone on the SQL Server newsgroup suggested that I might have a corupt MMC
Snap in and recommended that I replace it. I will try that. It is just
strange that it only started after last week's pattern update.
 
Let us know. I haven't seen this posted before, and don't have a way to
test it myself. Also consider other scanners on your machine which may be
regularly updated. Microsoft Antispyware has been blamed in several threads
here for issues which in the end were solved by patches to McAfee antivirus
apps which were also running on the affected systems.
 
Back
Top