We have an old server 6.5
Try to login to sql 6.5 Enterprise manager
and try to connect get the following Error: SQL Server Error
[DB Libraray] Unable to connect: SQL server is unavailable or does not exist;
Severity level 9 MsgNo 10004 OS Error 53
ConnectionOpen(CreateFile())
The Users are able to use the Db thru the VB application...
How do I resolve this. How do I get to Open Enterprise manager and manage my
tasks and backups
Please helpHi
Are you trying to do this from the Server? If not, try it from there.
Check how the VB application is connecting. Is it using the name or an IP.
Try "TELNET servername 1433)" and see if it gives you a blank screen without
timing out.
Regards
Mike
"G Q" wrote:
> We have an old server 6.5
> Try to login to sql 6.5 Enterprise manager
> and try to connect get the following Error: SQL Server Error
> [DB Libraray] Unable to connect: SQL server is unavailable or does not exist;
> Severity level 9 MsgNo 10004 OS Error 53
> ConnectionOpen(CreateFile())
> The Users are able to use the Db thru the VB application...
> How do I resolve this. How do I get to Open Enterprise manager and manage my
> tasks and backups
> Please help
>|||Ifinally got Connection to host lost?
Is this normal?
What should I be looking for
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Are you trying to do this from the Server? If not, try it from there.
> Check how the VB application is connecting. Is it using the name or an IP.
> Try "TELNET servername 1433)" and see if it gives you a blank screen without
> timing out.
> Regards
> Mike
>
> "G Q" wrote:
> > We have an old server 6.5
> > Try to login to sql 6.5 Enterprise manager
> > and try to connect get the following Error: SQL Server Error
> > [DB Libraray] Unable to connect: SQL server is unavailable or does not exist;
> > Severity level 9 MsgNo 10004 OS Error 53
> >
> > ConnectionOpen(CreateFile())
> >
> > The Users are able to use the Db thru the VB application...
> >
> > How do I resolve this. How do I get to Open Enterprise manager and manage my
> > tasks and backups
> >
> > Please help
> >|||Thank You for Your Response.
It did give a balnk screen no time out. I tried the Enterprise manager from
both the server and my machine, I could not connect.
I need to finish my tasks and projects.
Thank You in adavance
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Are you trying to do this from the Server? If not, try it from there.
> Check how the VB application is connecting. Is it using the name or an IP.
> Try "TELNET servername 1433)" and see if it gives you a blank screen without
> timing out.
> Regards
> Mike
>
> "G Q" wrote:
> > We have an old server 6.5
> > Try to login to sql 6.5 Enterprise manager
> > and try to connect get the following Error: SQL Server Error
> > [DB Libraray] Unable to connect: SQL server is unavailable or does not exist;
> > Severity level 9 MsgNo 10004 OS Error 53
> >
> > ConnectionOpen(CreateFile())
> >
> > The Users are able to use the Db thru the VB application...
> >
> > How do I resolve this. How do I get to Open Enterprise manager and manage my
> > tasks and backups
> >
> > Please help
> >
Showing posts with label manager. Show all posts
Showing posts with label manager. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
mmx.exe as encountered a problem and as to close
Hi,
since yesterday I have this message everytime I try to open Sql Server
"Enterprise manager"; I reinstalled the outfit completely without success
since yesterday I have this message everytime I try to open Sql Server
"Enterprise manager"; I reinstalled the outfit completely without success
any solution
thanks
FernandFernand St-Georges wrote:
> Hi,
> since yesterday I have this message everytime I try to open Sql Server
> "Enterprise manager"; I reinstalled the outfit completely without success
> any solution
> thanks
> Fernand
If it's MMC.exe (not MMX.exe) then there's a couple of things to look
at:
1) Can you start MMC.exe separately (through Start -> Run)? If not,
then MMC itself is foobar - it's a built-in part of windows (Microsoft
Management Console), so you'll need to look at repairing windows in
some manner - possible reapplying your last service pack (or deleting
MMC.exe then reapplying the SP)
2) If you can start MMC.exe then it's probably the SQL Server (tools)
install. How thoroughly did you do your reinstall? We're all
directories completely cleared?|||Hi,
I did as you said...the MMC console opens by itself.
To answer your second question, this morning I reinstalled completely SQL
Server, but without deleting the files
do you think I better delete everything?
thanks
"Damien" <Damien_The_Unbeliever@.hotmail.com> a crit dans le message de
news: 1121949111.547383.267750@.g43g2000cwa.googlegroups. com...
> Fernand St-Georges wrote:
>> Hi,
>> since yesterday I have this message everytime I try to open Sql Server
>> "Enterprise manager"; I reinstalled the outfit completely without
>> success
>>
>> any solution
>>
>> thanks
>>
>> Fernand
> If it's MMC.exe (not MMX.exe) then there's a couple of things to look
> at:
> 1) Can you start MMC.exe separately (through Start -> Run)? If not,
> then MMC itself is foobar - it's a built-in part of windows (Microsoft
> Management Console), so you'll need to look at repairing windows in
> some manner - possible reapplying your last service pack (or deleting
> MMC.exe then reapplying the SP)
> 2) If you can start MMC.exe then it's probably the SQL Server (tools)
> install. How thoroughly did you do your reinstall? We're all
> directories completely cleared?|||
thanks for the info...in fact MMC open but not the file related to Sql
Server Enterprise Manager.msc
I did reinstall SQL Server but without clearing the directories at all.
You think I should?
thanks
*** Sent via Developersdex http://www.developersdex.com ***|||Fernand St-Georges wrote:
> thanks for the info...in fact MMC open but not the file related to Sql
> Server Enterprise Manager.msc
> I did reinstall SQL Server but without clearing the directories at all.
> You think I should?
> thanks
> *** Sent via Developersdex http://www.developersdex.com ***
It's worth a try and doesn't cost much time to do - I have a feeling,
since the console is a "management tool", that it may be left behind.
On the other hand, if you deinstall, delete everything, reinstall, and
the problem still recurs, then it is likely to be the settings related
to the console.
I've had a bit of a search, and cannot seem to find any likely settings
- does anyone else here know where EM stores such things as the
registrations, etc? I'm fairly sure that they're stored on a per-user
basis, but I cannot find anything likely in either the registry (HKCU),
nor in the profile directories.
Damien|||Damien wrote:
> does anyone else here know where EM stores such things as the
> registrations, etc? I'm fairly sure that they're stored on a per-user
> basis, but I cannot find anything likely in either the registry (HKCU),
> nor in the profile directories.
The server registration information may be stored in different places,
depending on the configurations from Tools / Options / Server
Registration Information. With the default option (Read/Store locally,
user independent), the location is:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL
Server\80\Tools\SQLEW\Registered Servers X
Razvan
mmc.exe-Entry point not found in Enterprise Manager
I recently installed SQL 2000 on my machine and it was running fine till I i
nstalled SQL7 on the same machine. Now the SQL7 is running okay but I can't
use SQL2000 anymore. I received the following while try to open Enterprise
Manager:
mmc-entry point not found
The procedure entry point ? loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PB
G@.Z could
not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ? loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PB
G@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.|||Thank you guys. I will give it a try.
nstalled SQL7 on the same machine. Now the SQL7 is running okay but I can't
use SQL2000 anymore. I received the following while try to open Enterprise
Manager:
mmc-entry point not found
The procedure entry point ? loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PB
G@.Z could
not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ? loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PB
G@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.|||Thank you guys. I will give it a try.
mmc.exe-Entry point not found in Enterprise Manager
I recently installed SQL 2000 on my machine and it was running fine till I installed SQL7 on the same machine. Now the SQL7 is running okay but I can't use SQL2000 anymore. I received the following while try to open Enterprise Manager:
mmc-entry point not found
The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.
Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.
|||Thank you guys. I will give it a try.
mmc-entry point not found
The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.
Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.
|||Thank you guys. I will give it a try.
mmc.exe-Entry point not found in Enterprise Manager
I recently installed SQL 2000 on my machine and it was running fine till I installed SQL7 on the same machine. Now the SQL7 is running okay but I can't use SQL2000 anymore. I received the following while try to open Enterprise Manager
mmc-entry point not foun
The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.Uninstall SQL Server 7.0 and 2000. If you still have to
use SQL Server 7.0 First, Install SQL Server 7.0 as the
default then, Install SQL Server 2000 as the named
instance.
>--Original Message--
>I recently installed SQL 2000 on my machine and it was
running fine till I installed SQL7 on the same machine.
Now the SQL7 is running okay but I can't use SQL2000
anymore. I received the following while try to open
Enterprise Manager:
>mmc-entry point not found
>The procedure entry point ?
loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be
located in the dynamic link library SEMCOMN.dll
>Can anyone provide me with some advise? Thanks in
advance.
>.
>|||Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.|||Thank you guys. I will give it a try.sql
mmc-entry point not foun
The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.Uninstall SQL Server 7.0 and 2000. If you still have to
use SQL Server 7.0 First, Install SQL Server 7.0 as the
default then, Install SQL Server 2000 as the named
instance.
>--Original Message--
>I recently installed SQL 2000 on my machine and it was
running fine till I installed SQL7 on the same machine.
Now the SQL7 is running okay but I can't use SQL2000
anymore. I received the following while try to open
Enterprise Manager:
>mmc-entry point not found
>The procedure entry point ?
loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be
located in the dynamic link library SEMCOMN.dll
>Can anyone provide me with some advise? Thanks in
advance.
>.
>|||Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.|||Thank you guys. I will give it a try.sql
mmc.exe-Entry Point Not Found
WHEN I start enterprise manager on SQL 2000, ERROR message
occurred as folows:
mmc.exe-Entry Point Not Found
The procedure entry point wNetCachePassword could not be
located in the dynamic link library MPR.DLL.
Please tell me if you experienced !
thanksCan you find the dll mpr.dll on that server? If not, copy it from another
server.
Once you have located it, go to
http://www.microsoft.com/windows2000/downloads/servicepacks/SP4/supporttools.asp
There is a great tool that is part of the package you can download at that
site -- dependency walker (also you can use the dependency tool from Visual
Studio). Open the dll with the dependency walker and it will tell you what
is missing from your server. Then you can get the appropriate files. Good
luck.
Another thing to is to go to http://www.microsoft.com/mmc, and try
reinstalling the management console.
--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
*******************************************************************
"Matthew Jin" <jinmz@.yahoo.com> wrote in message
news:2a4401c3fc92$e82ec5b0$a101280a@.phx.gbl...
> WHEN I start enterprise manager on SQL 2000, ERROR message
> occurred as folows:
> mmc.exe-Entry Point Not Found
> The procedure entry point wNetCachePassword could not be
> located in the dynamic link library MPR.DLL.
> Please tell me if you experienced !
> thanks
>
occurred as folows:
mmc.exe-Entry Point Not Found
The procedure entry point wNetCachePassword could not be
located in the dynamic link library MPR.DLL.
Please tell me if you experienced !
thanksCan you find the dll mpr.dll on that server? If not, copy it from another
server.
Once you have located it, go to
http://www.microsoft.com/windows2000/downloads/servicepacks/SP4/supporttools.asp
There is a great tool that is part of the package you can download at that
site -- dependency walker (also you can use the dependency tool from Visual
Studio). Open the dll with the dependency walker and it will tell you what
is missing from your server. Then you can get the appropriate files. Good
luck.
Another thing to is to go to http://www.microsoft.com/mmc, and try
reinstalling the management console.
--
*******************************************************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
*******************************************************************
"Matthew Jin" <jinmz@.yahoo.com> wrote in message
news:2a4401c3fc92$e82ec5b0$a101280a@.phx.gbl...
> WHEN I start enterprise manager on SQL 2000, ERROR message
> occurred as folows:
> mmc.exe-Entry Point Not Found
> The procedure entry point wNetCachePassword could not be
> located in the dynamic link library MPR.DLL.
> Please tell me if you experienced !
> thanks
>
mmc.exe-Entry Point Not Found
WHEN I start enterprise manager on SQL 2000, ERROR message
occurred as folows:
mmc.exe-Entry Point Not Found
The procedure entry point wNetCachePassword could not be
located in the dynamic link library MPR.DLL.
Please tell me if you experienced !
thanksCan you find the dll mpr.dll on that server? If not, copy it from another
server.
Once you have located it, go to
http://www.microsoft.com/windows200...rosoft.com/mmc, and try
reinstalling the management console.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Matthew Jin" <jinmz@.yahoo.com> wrote in message
news:2a4401c3fc92$e82ec5b0$a101280a@.phx.gbl...
> WHEN I start enterprise manager on SQL 2000, ERROR message
> occurred as folows:
> mmc.exe-Entry Point Not Found
> The procedure entry point wNetCachePassword could not be
> located in the dynamic link library MPR.DLL.
> Please tell me if you experienced !
> thanks
>
occurred as folows:
mmc.exe-Entry Point Not Found
The procedure entry point wNetCachePassword could not be
located in the dynamic link library MPR.DLL.
Please tell me if you experienced !
thanksCan you find the dll mpr.dll on that server? If not, copy it from another
server.
Once you have located it, go to
http://www.microsoft.com/windows200...rosoft.com/mmc, and try
reinstalling the management console.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Matthew Jin" <jinmz@.yahoo.com> wrote in message
news:2a4401c3fc92$e82ec5b0$a101280a@.phx.gbl...
> WHEN I start enterprise manager on SQL 2000, ERROR message
> occurred as folows:
> mmc.exe-Entry Point Not Found
> The procedure entry point wNetCachePassword could not be
> located in the dynamic link library MPR.DLL.
> Please tell me if you experienced !
> thanks
>
mmc.exe writes a lot to SQL.LOG when working with Enterprise Manag
I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
generated by mmc.exe, when I was working with Enterprise Manager. For
instance, a double-click a database name or the server name would write abou
t
330K to the file. Thus, I had to wait for about 40 seconds per click. It
happended only on my Windows 2000 Server (SP4). Other servers do not even
generate the file. The following is sample of information written to the fil
e:
sqlstp 17c-840 ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794460
Any idea about it? How to turn off it? Thanks.I found a solution: Turning off ODBC tracing. It's the ODBC tracing that
writes trace to the file.
"Kathy" wrote:
> I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which w
as
> generated by mmc.exe, when I was working with Enterprise Manager. For
> instance, a double-click a database name or the server name would write ab
out
> 330K to the file. Thus, I had to wait for about 40 seconds per click. It
> happended only on my Windows 2000 Server (SP4). Other servers do not even
> generate the file. The following is sample of information written to the f
ile:
> sqlstp 17c-840 ENTER SQLAllocHandle
> SQLSMALLINT 1 <SQL_HANDLE_ENV>
> SQLHANDLE 00000000
> SQLHANDLE * 00794460
> Any idea about it? How to turn off it? Thanks.
>
generated by mmc.exe, when I was working with Enterprise Manager. For
instance, a double-click a database name or the server name would write abou
t
330K to the file. Thus, I had to wait for about 40 seconds per click. It
happended only on my Windows 2000 Server (SP4). Other servers do not even
generate the file. The following is sample of information written to the fil
e:
sqlstp 17c-840 ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794460
Any idea about it? How to turn off it? Thanks.I found a solution: Turning off ODBC tracing. It's the ODBC tracing that
writes trace to the file.
"Kathy" wrote:
> I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which w
as
> generated by mmc.exe, when I was working with Enterprise Manager. For
> instance, a double-click a database name or the server name would write ab
out
> 330K to the file. Thus, I had to wait for about 40 seconds per click. It
> happended only on my Windows 2000 Server (SP4). Other servers do not even
> generate the file. The following is sample of information written to the f
ile:
> sqlstp 17c-840 ENTER SQLAllocHandle
> SQLSMALLINT 1 <SQL_HANDLE_ENV>
> SQLHANDLE 00000000
> SQLHANDLE * 00794460
> Any idea about it? How to turn off it? Thanks.
>
mmc.exe writes a lot to SQL.LOG when working with Enterprise Manag
I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
generated by mmc.exe, when I was working with Enterprise Manager. For
instance, a double-click a database name or the server name would write about
330K to the file. Thus, I had to wait for about 40 seconds per click. It
happended only on my Windows 2000 Server (SP4). Other servers do not even
generate the file. The following is sample of information written to the file:
sqlstp 17c-840ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794460
Any idea about it? How to turn off it? Thanks.
I found a solution: Turning off ODBC tracing. It's the ODBC tracing that
writes trace to the file.
"Kathy" wrote:
> I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
> generated by mmc.exe, when I was working with Enterprise Manager. For
> instance, a double-click a database name or the server name would write about
> 330K to the file. Thus, I had to wait for about 40 seconds per click. It
> happended only on my Windows 2000 Server (SP4). Other servers do not even
> generate the file. The following is sample of information written to the file:
> sqlstp 17c-840ENTER SQLAllocHandle
> SQLSMALLINT 1 <SQL_HANDLE_ENV>
> SQLHANDLE 00000000
> SQLHANDLE * 00794460
> Any idea about it? How to turn off it? Thanks.
>
generated by mmc.exe, when I was working with Enterprise Manager. For
instance, a double-click a database name or the server name would write about
330K to the file. Thus, I had to wait for about 40 seconds per click. It
happended only on my Windows 2000 Server (SP4). Other servers do not even
generate the file. The following is sample of information written to the file:
sqlstp 17c-840ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794460
Any idea about it? How to turn off it? Thanks.
I found a solution: Turning off ODBC tracing. It's the ODBC tracing that
writes trace to the file.
"Kathy" wrote:
> I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
> generated by mmc.exe, when I was working with Enterprise Manager. For
> instance, a double-click a database name or the server name would write about
> 330K to the file. Thus, I had to wait for about 40 seconds per click. It
> happended only on my Windows 2000 Server (SP4). Other servers do not even
> generate the file. The following is sample of information written to the file:
> sqlstp 17c-840ENTER SQLAllocHandle
> SQLSMALLINT 1 <SQL_HANDLE_ENV>
> SQLHANDLE 00000000
> SQLHANDLE * 00794460
> Any idea about it? How to turn off it? Thanks.
>
mmc.exe writes a lot to SQL.LOG when working with Enterprise Manag
I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
generated by mmc.exe, when I was working with Enterprise Manager. For
instance, a double-click a database name or the server name would write about
330K to the file. Thus, I had to wait for about 40 seconds per click. It
happended only on my Windows 2000 Server (SP4). Other servers do not even
generate the file. The following is sample of information written to the file:
sqlstp 17c-840 ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794460
Any idea about it? How to turn off it? Thanks.I found a solution: Turning off ODBC tracing. It's the ODBC tracing that
writes trace to the file.
"Kathy" wrote:
> I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
> generated by mmc.exe, when I was working with Enterprise Manager. For
> instance, a double-click a database name or the server name would write about
> 330K to the file. Thus, I had to wait for about 40 seconds per click. It
> happended only on my Windows 2000 Server (SP4). Other servers do not even
> generate the file. The following is sample of information written to the file:
> sqlstp 17c-840 ENTER SQLAllocHandle
> SQLSMALLINT 1 <SQL_HANDLE_ENV>
> SQLHANDLE 00000000
> SQLHANDLE * 00794460
> Any idea about it? How to turn off it? Thanks.
>sql
generated by mmc.exe, when I was working with Enterprise Manager. For
instance, a double-click a database name or the server name would write about
330K to the file. Thus, I had to wait for about 40 seconds per click. It
happended only on my Windows 2000 Server (SP4). Other servers do not even
generate the file. The following is sample of information written to the file:
sqlstp 17c-840 ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794460
Any idea about it? How to turn off it? Thanks.I found a solution: Turning off ODBC tracing. It's the ODBC tracing that
writes trace to the file.
"Kathy" wrote:
> I noticed that mmc.exe wrote a lot of information to SQL.LOG file, which was
> generated by mmc.exe, when I was working with Enterprise Manager. For
> instance, a double-click a database name or the server name would write about
> 330K to the file. Thus, I had to wait for about 40 seconds per click. It
> happended only on my Windows 2000 Server (SP4). Other servers do not even
> generate the file. The following is sample of information written to the file:
> sqlstp 17c-840 ENTER SQLAllocHandle
> SQLSMALLINT 1 <SQL_HANDLE_ENV>
> SQLHANDLE 00000000
> SQLHANDLE * 00794460
> Any idea about it? How to turn off it? Thanks.
>sql
mmc.exe - .dll files are corrupted
Windows NT 4.0 operating system SQL 7.0 is loaded. Sql enterprise manager is opend mmc.exe - .dll files are corrupted. Please giveme advice
ThankyouHi there,
welcome to thescipts, take care my fren.. :)
MMC Problem
Hi Guys,
Can anybody help me out plz?
When I tried to open Enterprise Manager of SQL server I'm
recieving this error message.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
While IIS MMC and other MMC are working fine. Getting problem only with SQL
Server Enterprise Manager.
Thanx in advance.
Probably the easiest thing to do would be reinstall the SQL Client tools.
Rerun setup and just choose to install the client tools.
Donna Lambert
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>
|||Hi Donna,
Thanx for your interest.
I uninstalled first then installed again both Server and Client tools,
unfortunately still the problem exists.
Sorry I didn't write complete error message. which read as
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>
Can anybody help me out plz?
When I tried to open Enterprise Manager of SQL server I'm
recieving this error message.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
While IIS MMC and other MMC are working fine. Getting problem only with SQL
Server Enterprise Manager.
Thanx in advance.
Probably the easiest thing to do would be reinstall the SQL Client tools.
Rerun setup and just choose to install the client tools.
Donna Lambert
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>
|||Hi Donna,
Thanx for your interest.
I uninstalled first then installed again both Server and Client tools,
unfortunately still the problem exists.
Sorry I didn't write complete error message. which read as
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>
MMC Problem
Hi Guys,
Can anybody help me out plz?
When I tried to open Enterprise Manager of SQL server I'm
recieving this error message.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
While IIS MMC and other MMC are working fine. Getting problem only with SQL
Server Enterprise Manager.
Thanx in advance.Probably the easiest thing to do would be reinstall the SQL Client tools.
Rerun setup and just choose to install the client tools.
Donna Lambert
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>|||Hi Donna,
Thanx for your interest.
I uninstalled first then installed again both Server and Client tools,
unfortunately still the problem exists.
Sorry I didn't write complete error message. which read as
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>sql
Can anybody help me out plz?
When I tried to open Enterprise Manager of SQL server I'm
recieving this error message.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
While IIS MMC and other MMC are working fine. Getting problem only with SQL
Server Enterprise Manager.
Thanx in advance.Probably the easiest thing to do would be reinstall the SQL Client tools.
Rerun setup and just choose to install the client tools.
Donna Lambert
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>|||Hi Donna,
Thanx for your interest.
I uninstalled first then installed again both Server and Client tools,
unfortunately still the problem exists.
Sorry I didn't write complete error message. which read as
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQL
> Server Enterprise Manager.
> Thanx in advance.
>sql
MMC Problem
Hi Guys,
Can anybody help me out plz?
When I tried to open Enterprise Manager of SQL server I'm
recieving this error message.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
While IIS MMC and other MMC are working fine. Getting problem only with SQL
Server Enterprise Manager.
Thanx in advance.Probably the easiest thing to do would be reinstall the SQL Client tools.
Rerun setup and just choose to install the client tools.
Donna Lambert
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQ
L
> Server Enterprise Manager.
> Thanx in advance.
>|||Hi Donna,
Thanx for your interest.
I uninstalled first then installed again both Server and Client tools,
unfortunately still the problem exists.
Sorry I didn't write complete error message. which read as
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQ
L
> Server Enterprise Manager.
> Thanx in advance.
>
Can anybody help me out plz?
When I tried to open Enterprise Manager of SQL server I'm
recieving this error message.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
While IIS MMC and other MMC are working fine. Getting problem only with SQL
Server Enterprise Manager.
Thanx in advance.Probably the easiest thing to do would be reinstall the SQL Client tools.
Rerun setup and just choose to install the client tools.
Donna Lambert
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQ
L
> Server Enterprise Manager.
> Thanx in advance.
>|||Hi Donna,
Thanx for your interest.
I uninstalled first then installed again both Server and Client tools,
unfortunately still the problem exists.
Sorry I didn't write complete error message. which read as
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
created by alater version of MMC. This may also be because you do not have
sufficient access rights to the file.
"uzair" wrote:
> Hi Guys,
> Can anybody help me out plz?
> When I tried to open Enterprise Manager of SQL server I'm
> recieving this error message.
> This may be because the file does not exist, is not an MMC console, or was
> created by alater version of MMC. This may also be because you do not have
> sufficient access rights to the file.
> While IIS MMC and other MMC are working fine. Getting problem only with SQ
L
> Server Enterprise Manager.
> Thanx in advance.
>
MMC initialize error
I have SQL server 2000. when I try to open Enterprise Manager, I am geting
this error message.
"snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
CLSID: {00100100-1816-8EF5-00AA0062C58F}"
Please help me how to reslove this problem. Thanks.
"Error Messages When You Install Office Server Extensions on Computer with
SQL Server 2000"
http://support.microsoft.com/default...&Product=sql2k
"Why does SQL Server 2005 break SQL Server 2000 tools?"
http://www.aspfaq.com/sql2005/show.asp?id=4 (maybe the solution of
re-register sqldmo.dll for SQL Server 2000 works in your situation)
Cristian Lefter, SQL Server MVP
"Kumar" <ravik_v@.hotmail.com> wrote in message
news:BDA694A0-E055-49CA-A1F8-C32BD6282966@.microsoft.com...
>I have SQL server 2000. when I try to open Enterprise Manager, I am geting
> this error message.
> "snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
> CLSID: {00100100-1816-8EF5-00AA0062C58F}"
> Please help me how to reslove this problem. Thanks.
this error message.
"snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
CLSID: {00100100-1816-8EF5-00AA0062C58F}"
Please help me how to reslove this problem. Thanks.
"Error Messages When You Install Office Server Extensions on Computer with
SQL Server 2000"
http://support.microsoft.com/default...&Product=sql2k
"Why does SQL Server 2005 break SQL Server 2000 tools?"
http://www.aspfaq.com/sql2005/show.asp?id=4 (maybe the solution of
re-register sqldmo.dll for SQL Server 2000 works in your situation)
Cristian Lefter, SQL Server MVP
"Kumar" <ravik_v@.hotmail.com> wrote in message
news:BDA694A0-E055-49CA-A1F8-C32BD6282966@.microsoft.com...
>I have SQL server 2000. when I try to open Enterprise Manager, I am geting
> this error message.
> "snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
> CLSID: {00100100-1816-8EF5-00AA0062C58F}"
> Please help me how to reslove this problem. Thanks.
MMC initialize error
I have SQL server 2000. when I try to open Enterprise Manager, I am geting
this error message.
"snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
CLSID: {00100100-1816-8EF5-00AA0062C58F}"
Please help me how to reslove this problem. Thanks."Error Messages When You Install Office Server Extensions on Computer with
SQL Server 2000"
http://support.microsoft.com/default.aspx?scid=kb;en-us;281460&Product=sql2k
"Why does SQL Server 2005 break SQL Server 2000 tools?"
http://www.aspfaq.com/sql2005/show.asp?id=4 (maybe the solution of
re-register sqldmo.dll for SQL Server 2000 works in your situation)
Cristian Lefter, SQL Server MVP
"Kumar" <ravik_v@.hotmail.com> wrote in message
news:BDA694A0-E055-49CA-A1F8-C32BD6282966@.microsoft.com...
>I have SQL server 2000. when I try to open Enterprise Manager, I am geting
> this error message.
> "snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
> CLSID: {00100100-1816-8EF5-00AA0062C58F}"
> Please help me how to reslove this problem. Thanks.
this error message.
"snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
CLSID: {00100100-1816-8EF5-00AA0062C58F}"
Please help me how to reslove this problem. Thanks."Error Messages When You Install Office Server Extensions on Computer with
SQL Server 2000"
http://support.microsoft.com/default.aspx?scid=kb;en-us;281460&Product=sql2k
"Why does SQL Server 2005 break SQL Server 2000 tools?"
http://www.aspfaq.com/sql2005/show.asp?id=4 (maybe the solution of
re-register sqldmo.dll for SQL Server 2000 works in your situation)
Cristian Lefter, SQL Server MVP
"Kumar" <ravik_v@.hotmail.com> wrote in message
news:BDA694A0-E055-49CA-A1F8-C32BD6282966@.microsoft.com...
>I have SQL server 2000. when I try to open Enterprise Manager, I am geting
> this error message.
> "snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
> CLSID: {00100100-1816-8EF5-00AA0062C58F}"
> Please help me how to reslove this problem. Thanks.
MMC initialize error
I have SQL server 2000. when I try to open Enterprise Manager, I am geting
this error message.
"snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
CLSID: {00100100-1816-8EF5-00AA0062C58F}"
Please help me how to reslove this problem. Thanks."Error Messages When You Install Office Server Extensions on Computer with
SQL Server 2000"
http://support.microsoft.com/defaul...0&Product=sql2k
"Why does SQL Server 2005 break SQL Server 2000 tools?"
http://www.aspfaq.com/sql2005/show.asp?id=4 (maybe the solution of
re-register sqldmo.dll for SQL Server 2000 works in your situation)
Cristian Lefter, SQL Server MVP
"Kumar" <ravik_v@.hotmail.com> wrote in message
news:BDA694A0-E055-49CA-A1F8-C32BD6282966@.microsoft.com...
>I have SQL server 2000. when I try to open Enterprise Manager, I am geting
> this error message.
> "snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
> CLSID: {00100100-1816-8EF5-00AA0062C58F}"
> Please help me how to reslove this problem. Thanks.
this error message.
"snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
CLSID: {00100100-1816-8EF5-00AA0062C58F}"
Please help me how to reslove this problem. Thanks."Error Messages When You Install Office Server Extensions on Computer with
SQL Server 2000"
http://support.microsoft.com/defaul...0&Product=sql2k
"Why does SQL Server 2005 break SQL Server 2000 tools?"
http://www.aspfaq.com/sql2005/show.asp?id=4 (maybe the solution of
re-register sqldmo.dll for SQL Server 2000 works in your situation)
Cristian Lefter, SQL Server MVP
"Kumar" <ravik_v@.hotmail.com> wrote in message
news:BDA694A0-E055-49CA-A1F8-C32BD6282966@.microsoft.com...
>I have SQL server 2000. when I try to open Enterprise Manager, I am geting
> this error message.
> "snap-in failed to Initialize Name: Microsoft SQL Enterprise Manager
> CLSID: {00100100-1816-8EF5-00AA0062C58F}"
> Please help me how to reslove this problem. Thanks.
MMC for SQL Server 2005?
I would like to add SQL Server 2005 management console to my custom built MM
C
– but the only snap in I can find is SQL Server Configuration Manager. Is
there a snap-in for SQL Server 2005 available or do I have to use SQL Server
Management Studio?
Cheers,
NinaHi Nina
AFAIK there is no MMC other than Configuration Manager, in general MMCs have
been replaced by more reliable managed code, therefore you would need to
write your own that uses SMO.
John
"Nina" wrote:
> I would like to add SQL Server 2005 management console to my custom built
MMC
> – but the only snap in I can find is SQL Server Configuration Manager. I
s
> there a snap-in for SQL Server 2005 available or do I have to use SQL Serv
er
> Management Studio?
> Cheers,
> Nina|||Thanks for confirming that John.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Nina
> AFAIK there is no MMC other than Configuration Manager, in general MMCs ha
ve
> been replaced by more reliable managed code, therefore you would need to
> write your own that uses SMO.
> John
> "Nina" wrote:
>sql
C
– but the only snap in I can find is SQL Server Configuration Manager. Is
there a snap-in for SQL Server 2005 available or do I have to use SQL Server
Management Studio?
Cheers,
NinaHi Nina
AFAIK there is no MMC other than Configuration Manager, in general MMCs have
been replaced by more reliable managed code, therefore you would need to
write your own that uses SMO.
John
"Nina" wrote:
> I would like to add SQL Server 2005 management console to my custom built
MMC
> – but the only snap in I can find is SQL Server Configuration Manager. I
s
> there a snap-in for SQL Server 2005 available or do I have to use SQL Serv
er
> Management Studio?
> Cheers,
> Nina|||Thanks for confirming that John.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Nina
> AFAIK there is no MMC other than Configuration Manager, in general MMCs ha
ve
> been replaced by more reliable managed code, therefore you would need to
> write your own that uses SMO.
> John
> "Nina" wrote:
>sql
MMC error with Enterprise Manager
When attempting to display a database's property window in Enterprise Manager
an error happens with MMC. On a machine that also has SQL Server 2005 client
tools installed Enterprise manager crashes. On other machines that do not
have SQL Server 2005 client tools installed, MMC throws an error similar to
the one below before Enterprise Manager crashes:
mmc.exe Application error The instruction at "0x7801094 referenced
memory.....
The exact memory address in the above error message is not correct. I copied
it from another reference (on Google) dealing with DTS / MMC errors. I do not
have the exact message because I was forced to reinstall SQL Server 2000 in
order to use the RTM version to get around this error. The bug does not
happen in the RTM version but does with both SP3 and SP4.
The problem started fairly recently and I suspect it has to do with a
Microsoft update. It is happening to every computer computer in our facility
that has service packs applied to SQL Server and affects more than the
ability to display a databases property page.
Does anyone have any knowledge as to what might be causing these errors with
MMC and whether or not there is a work around?
I have now applied SP4 again and can replicate the error again.
When I right click on a Database in Enterprise Manager and select properties
I receive the following message:
mmc.exe - Application Error
The instruction at "0x4247b98b" referenced memory at "0x0000001c". The
memory could not be read.
Click OK to terminate....
I am running SQL Server 2000 on Windows 2000 (SP4).
an error happens with MMC. On a machine that also has SQL Server 2005 client
tools installed Enterprise manager crashes. On other machines that do not
have SQL Server 2005 client tools installed, MMC throws an error similar to
the one below before Enterprise Manager crashes:
mmc.exe Application error The instruction at "0x7801094 referenced
memory.....
The exact memory address in the above error message is not correct. I copied
it from another reference (on Google) dealing with DTS / MMC errors. I do not
have the exact message because I was forced to reinstall SQL Server 2000 in
order to use the RTM version to get around this error. The bug does not
happen in the RTM version but does with both SP3 and SP4.
The problem started fairly recently and I suspect it has to do with a
Microsoft update. It is happening to every computer computer in our facility
that has service packs applied to SQL Server and affects more than the
ability to display a databases property page.
Does anyone have any knowledge as to what might be causing these errors with
MMC and whether or not there is a work around?
I have now applied SP4 again and can replicate the error again.
When I right click on a Database in Enterprise Manager and select properties
I receive the following message:
mmc.exe - Application Error
The instruction at "0x4247b98b" referenced memory at "0x0000001c". The
memory could not be read.
Click OK to terminate....
I am running SQL Server 2000 on Windows 2000 (SP4).
Wednesday, March 21, 2012
MMC Cannot open
who knows how to fix this:
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
This may be because the file doesnt exist, is not an MMC console, or
was created by a later version of MMC. This may also be because
you do not have sufficient access rights to the file.
I have rebooted the server, and restarted my machine, uninstalled and reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manager. Can anyone help?
Thanks in advance
Jane
Jane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>
|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The problem is very strange. I suppose I am locked by the server. Don't know what to do now.
As I said, I am new to SQL Server, I am trying to explore it. But there isn't a senior member in our team, so your help turns to be very important for me. I am looking forward to any ideas.
Cheers
Jane
|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Thanks for your help, but it doesn't work. Any ideas?
Jane
-- Dinesh T.K wrote: --
Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>
|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
This may be because the file doesnt exist, is not an MMC console, or
was created by a later version of MMC. This may also be because
you do not have sufficient access rights to the file.
I have rebooted the server, and restarted my machine, uninstalled and reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manager. Can anyone help?
Thanks in advance
Jane
Jane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>
|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The problem is very strange. I suppose I am locked by the server. Don't know what to do now.
As I said, I am new to SQL Server, I am trying to explore it. But there isn't a senior member in our team, so your help turns to be very important for me. I am looking forward to any ideas.
Cheers
Jane
|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Thanks for your help, but it doesn't work. Any ideas?
Jane
-- Dinesh T.K wrote: --
Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>
|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>
Subscribe to:
Posts (Atom)