[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

Enterprise manager not working

I click on the Enterprise Manager on the start menu >> programs >>MS SQL >> Enterprise Manager and I receive this message "MMC cannot open the selected file"  Any ideas on how to fix this, I reinstalled the tool and I receive the same message.

0
mystikal1000
Asked:
mystikal1000
1 Solution
 
leonstrykerCommented:
Are you able to connect to the server in any other way?
0
 
mastooCommented:
Right click the menu item and get properties.  Post what is in the Shortcut tab's "target" field.
0
 
bruintjeCommented:
what changed when this started?

did you uninstall sql server 2000? then this may apply
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q272453

or the file is just corrupt, you installed again but what if you try

to replace your existing file > SQL Server Enterprise Manager.MSC
should be located at  > YourSQLInstallPath\Microsoft SQL Server\80\Tools\Binn
with the original  SQL Server Enterprise Manager.MSC file from the installation CD
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
mystikal1000Author Commented:
"C:\Program Files\Microsoft SQL Server\80\Tools\BINN" but its missing and reinstalling doesn't help...
0
 
mystikal1000Author Commented:
Here is the installation log file...


Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=7V20231;UID=sa;PWD=;database=master

[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

driver={sql server};server=7V20231;UID=sa;PWD=;database=master

[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

driver={sql server};server=7V20231;UID=sa;PWD=;database=master

[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

SQL Server configuration failed.

###############################################################################

10:11:45 Process Exit Code: (-1)
10:13:11 Setup failed to configure the server.   Refer to the server error logs and C:\WINNT\sqlstp.log for more information.
10:13:11 Action CleanUpInstall:
10:13:11 C:\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -Action 4 -Service SQLSERVERAGENT
10:13:11 Process Exit Code: (1060) The specified service does not exist as an installed service.

10:13:11 C:\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -Action 4 -Service MSSQLSERVER
10:13:12 Process Exit Code: (0)
10:13:12 StatsGenerate returned: 2
10:13:12 StatsGenerate (0x0,0x1,0xf000000,0x300,1033,303,0x0,0x1,0,0,0
10:13:12 StatsGenerate -1,dp98236)
10:13:12 Installation Failed.
0
 
bruintjeCommented:
source : http://groups.google.com/groups?selm=%23GL56wc2CHA.2332%40TK2MSFTNGP10.phx.gbl&output=gplain

relevant part
-------------
This is usually due to a problem with the SQL ODBC driver (C:\WINNT\sqlsrv32.dll).
Try installing MDAC first, reboot and then installing SQL Server.
You can download the latest version of MDAC from
www.microsoft.com/data 
or you can run sqlerdis.exe which is found on your install CD in \X86\OTHER
-------------
0
 
mystikal1000Author Commented:
Should I uninstall sql server before installing MDAC?
0
 
bruintjeCommented:
if that's possible
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Tackle projects and never again get stuck behind a technical roadblock.
Join Now