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
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:
[vbcol=seagreen]
> 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:
|||Ifinally got Connection to host lost?
Is this normal?
What should I be looking for
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> 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:
Showing posts with label error. Show all posts
Showing posts with label error. Show all posts
Friday, March 30, 2012
Moderatores Please Help
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 e
xist;
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
>|||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:
[vbcol=seagreen]
> 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 witho
ut
> timing out.
> Regards
> Mike
>
> "G Q" wrote:
>|||Ifinally got Connection to host lost?
Is this normal?
What should I be looking for
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> 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 witho
ut
> timing out.
> Regards
> Mike
>
> "G Q" wrote:
>sql
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 e
xist;
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
>|||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:
[vbcol=seagreen]
> 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 witho
ut
> timing out.
> Regards
> Mike
>
> "G Q" wrote:
>|||Ifinally got Connection to host lost?
Is this normal?
What should I be looking for
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> 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 witho
ut
> timing out.
> Regards
> Mike
>
> "G Q" wrote:
>sql
Wednesday, March 28, 2012
Moderatores Please Help
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
> >
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
> >
Model DB is hung on a restore ??
Is there a way to stop a hung restore ?
Here are some error logs:
2003-12-09 12:35:20.94 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2003-12-09 12:35:20.94 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-12-09 12:35:20.94 server All rights reserved.
2003-12-09 12:35:20.94 server Server Process ID is 3984.
2003-12-09 12:35:20.94 server Logging SQL Server messages in file
'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2003-12-09 12:35:20.96 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2003-12-09 12:35:21.10 server SQL Server configured for thread mode
processing.
2003-12-09 12:35:21.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2003-12-09 12:35:21.17 server Attempting to initialize Distributed
Transaction Coordinator.
2003-12-09 12:35:23.25 spid3 Starting up database 'master'.
2003-12-09 12:35:23.32 server Using 'SSNETLIB.DLL' version '8.0.760'.
2003-12-09 12:35:23.32 spid5 Starting up database 'model'.
2003-12-09 12:35:23.32 spid3 Server name is 'W2KSVR'.
2003-12-09 12:35:23.32 spid8 Starting up database 'msdb'.
2003-12-09 12:35:23.32 spid9 Starting up database 'pubs'.
2003-12-09 12:35:23.32 spid10 Starting up database 'Northwind'.
2003-12-09 12:35:23.32 spid11 Starting up database 'StarBldr'.
2003-12-09 12:35:23.32 spid12 Starting up database 'SurfControl_WebFilter'.
2003-12-09 12:35:23.32 spid13 Starting up database 'BRCS'.
2003-12-09 12:35:23.32 spid14 Starting up database 'BEDB'.
2003-12-09 12:35:23.33 spid11 Bypassing recovery for database 'StarBldr'
because it is marked IN LOAD.
2003-12-09 12:35:23.33 spid5 Bypassing recovery for database 'model' because
it is marked IN LOAD.
2003-12-09 12:35:23.33 spid5 Database 'model' cannot be opened. It is in the
middle of a restore.
2003-12-09 12:35:23.33 spid13 Bypassing recovery for database 'BRCS' because
it is marked IN LOAD.
HERE IS THE ERRORLOG.1 file:
2003-12-09 12:33:19.02 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2003-12-09 12:33:19.02 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-12-09 12:33:19.02 server All rights reserved.
2003-12-09 12:33:19.02 server Server Process ID is 4364.
2003-12-09 12:33:19.02 server Logging SQL Server messages in file
'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2003-12-09 12:33:19.02 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2003-12-09 12:33:19.16 server SQL Server configured for thread mode
processing.
2003-12-09 12:33:19.16 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2003-12-09 12:33:19.24 server Attempting to initialize Distributed
Transaction Coordinator.
2003-12-09 12:33:21.30 spid3 Starting up database 'master'.
2003-12-09 12:33:21.35 server Using 'SSNETLIB.DLL' version '8.0.760'.
2003-12-09 12:33:21.35 spid5 Starting up database 'model'.
2003-12-09 12:33:21.36 spid3 Server name is 'W2KSVR'.
2003-12-09 12:33:21.36 spid8 Starting up database 'msdb'.
2003-12-09 12:33:21.36 spid9 Starting up database 'pubs'.
2003-12-09 12:33:21.36 spid10 Starting up database 'Northwind'.
2003-12-09 12:33:21.36 spid11 Starting up database 'StarBldr'.
2003-12-09 12:33:21.36 spid13 Starting up database 'BRCS'.
2003-12-09 12:33:21.36 spid12 Starting up database 'SurfControl_WebFilter'.
2003-12-09 12:33:21.36 spid14 Starting up database 'BEDB'.
2003-12-09 12:33:21.36 spid11 Bypassing recovery for database 'StarBldr'
because it is marked IN LOAD.
2003-12-09 12:33:21.36 spid5 Bypassing recovery for database 'model' because
it is marked IN LOAD.
2003-12-09 12:33:21.36 spid13 Bypassing recovery for database 'BRCS' because
it is marked IN LOAD.
2003-12-09 12:33:21.38 spid5 Database 'model' cannot be opened. It is in the
middle of a restore.
Any help would be grateful... Thanks
TIASee my other reply.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"_M_" <here@.gone.com> wrote in message
news:OI34LpovDHA.3116@.tk2msftngp13.phx.gbl...
> Is there a way to stop a hung restore ?
> Here are some error logs:
> 2003-12-09 12:35:20.94 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2003-12-09 12:35:20.94 server Copyright (C) 1988-2002 Microsoft
Corporation.
> 2003-12-09 12:35:20.94 server All rights reserved.
> 2003-12-09 12:35:20.94 server Server Process ID is 3984.
> 2003-12-09 12:35:20.94 server Logging SQL Server messages in file
> 'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2003-12-09 12:35:20.96 server SQL Server is starting at priority class
> 'normal'(4 CPUs detected).
> 2003-12-09 12:35:21.10 server SQL Server configured for thread mode
> processing.
> 2003-12-09 12:35:21.10 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2003-12-09 12:35:21.17 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2003-12-09 12:35:23.25 spid3 Starting up database 'master'.
> 2003-12-09 12:35:23.32 server Using 'SSNETLIB.DLL' version '8.0.760'.
> 2003-12-09 12:35:23.32 spid5 Starting up database 'model'.
> 2003-12-09 12:35:23.32 spid3 Server name is 'W2KSVR'.
> 2003-12-09 12:35:23.32 spid8 Starting up database 'msdb'.
> 2003-12-09 12:35:23.32 spid9 Starting up database 'pubs'.
> 2003-12-09 12:35:23.32 spid10 Starting up database 'Northwind'.
> 2003-12-09 12:35:23.32 spid11 Starting up database 'StarBldr'.
> 2003-12-09 12:35:23.32 spid12 Starting up database
'SurfControl_WebFilter'.
> 2003-12-09 12:35:23.32 spid13 Starting up database 'BRCS'.
> 2003-12-09 12:35:23.32 spid14 Starting up database 'BEDB'.
> 2003-12-09 12:35:23.33 spid11 Bypassing recovery for database 'StarBldr'
> because it is marked IN LOAD.
> 2003-12-09 12:35:23.33 spid5 Bypassing recovery for database 'model'
because
> it is marked IN LOAD.
> 2003-12-09 12:35:23.33 spid5 Database 'model' cannot be opened. It is in
the
> middle of a restore.
> 2003-12-09 12:35:23.33 spid13 Bypassing recovery for database 'BRCS'
because
> it is marked IN LOAD.
> HERE IS THE ERRORLOG.1 file:
> 2003-12-09 12:33:19.02 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2003-12-09 12:33:19.02 server Copyright (C) 1988-2002 Microsoft
Corporation.
> 2003-12-09 12:33:19.02 server All rights reserved.
> 2003-12-09 12:33:19.02 server Server Process ID is 4364.
> 2003-12-09 12:33:19.02 server Logging SQL Server messages in file
> 'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2003-12-09 12:33:19.02 server SQL Server is starting at priority class
> 'normal'(4 CPUs detected).
> 2003-12-09 12:33:19.16 server SQL Server configured for thread mode
> processing.
> 2003-12-09 12:33:19.16 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2003-12-09 12:33:19.24 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2003-12-09 12:33:21.30 spid3 Starting up database 'master'.
> 2003-12-09 12:33:21.35 server Using 'SSNETLIB.DLL' version '8.0.760'.
> 2003-12-09 12:33:21.35 spid5 Starting up database 'model'.
> 2003-12-09 12:33:21.36 spid3 Server name is 'W2KSVR'.
> 2003-12-09 12:33:21.36 spid8 Starting up database 'msdb'.
> 2003-12-09 12:33:21.36 spid9 Starting up database 'pubs'.
> 2003-12-09 12:33:21.36 spid10 Starting up database 'Northwind'.
> 2003-12-09 12:33:21.36 spid11 Starting up database 'StarBldr'.
> 2003-12-09 12:33:21.36 spid13 Starting up database 'BRCS'.
> 2003-12-09 12:33:21.36 spid12 Starting up database
'SurfControl_WebFilter'.
> 2003-12-09 12:33:21.36 spid14 Starting up database 'BEDB'.
> 2003-12-09 12:33:21.36 spid11 Bypassing recovery for database 'StarBldr'
> because it is marked IN LOAD.
> 2003-12-09 12:33:21.36 spid5 Bypassing recovery for database 'model'
because
> it is marked IN LOAD.
> 2003-12-09 12:33:21.36 spid13 Bypassing recovery for database 'BRCS'
because
> it is marked IN LOAD.
> 2003-12-09 12:33:21.38 spid5 Database 'model' cannot be opened. It is in
the
> middle of a restore.
> Any help would be grateful... Thanks
> TIA
>
Here are some error logs:
2003-12-09 12:35:20.94 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2003-12-09 12:35:20.94 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-12-09 12:35:20.94 server All rights reserved.
2003-12-09 12:35:20.94 server Server Process ID is 3984.
2003-12-09 12:35:20.94 server Logging SQL Server messages in file
'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2003-12-09 12:35:20.96 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2003-12-09 12:35:21.10 server SQL Server configured for thread mode
processing.
2003-12-09 12:35:21.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2003-12-09 12:35:21.17 server Attempting to initialize Distributed
Transaction Coordinator.
2003-12-09 12:35:23.25 spid3 Starting up database 'master'.
2003-12-09 12:35:23.32 server Using 'SSNETLIB.DLL' version '8.0.760'.
2003-12-09 12:35:23.32 spid5 Starting up database 'model'.
2003-12-09 12:35:23.32 spid3 Server name is 'W2KSVR'.
2003-12-09 12:35:23.32 spid8 Starting up database 'msdb'.
2003-12-09 12:35:23.32 spid9 Starting up database 'pubs'.
2003-12-09 12:35:23.32 spid10 Starting up database 'Northwind'.
2003-12-09 12:35:23.32 spid11 Starting up database 'StarBldr'.
2003-12-09 12:35:23.32 spid12 Starting up database 'SurfControl_WebFilter'.
2003-12-09 12:35:23.32 spid13 Starting up database 'BRCS'.
2003-12-09 12:35:23.32 spid14 Starting up database 'BEDB'.
2003-12-09 12:35:23.33 spid11 Bypassing recovery for database 'StarBldr'
because it is marked IN LOAD.
2003-12-09 12:35:23.33 spid5 Bypassing recovery for database 'model' because
it is marked IN LOAD.
2003-12-09 12:35:23.33 spid5 Database 'model' cannot be opened. It is in the
middle of a restore.
2003-12-09 12:35:23.33 spid13 Bypassing recovery for database 'BRCS' because
it is marked IN LOAD.
HERE IS THE ERRORLOG.1 file:
2003-12-09 12:33:19.02 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2003-12-09 12:33:19.02 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-12-09 12:33:19.02 server All rights reserved.
2003-12-09 12:33:19.02 server Server Process ID is 4364.
2003-12-09 12:33:19.02 server Logging SQL Server messages in file
'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2003-12-09 12:33:19.02 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2003-12-09 12:33:19.16 server SQL Server configured for thread mode
processing.
2003-12-09 12:33:19.16 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2003-12-09 12:33:19.24 server Attempting to initialize Distributed
Transaction Coordinator.
2003-12-09 12:33:21.30 spid3 Starting up database 'master'.
2003-12-09 12:33:21.35 server Using 'SSNETLIB.DLL' version '8.0.760'.
2003-12-09 12:33:21.35 spid5 Starting up database 'model'.
2003-12-09 12:33:21.36 spid3 Server name is 'W2KSVR'.
2003-12-09 12:33:21.36 spid8 Starting up database 'msdb'.
2003-12-09 12:33:21.36 spid9 Starting up database 'pubs'.
2003-12-09 12:33:21.36 spid10 Starting up database 'Northwind'.
2003-12-09 12:33:21.36 spid11 Starting up database 'StarBldr'.
2003-12-09 12:33:21.36 spid13 Starting up database 'BRCS'.
2003-12-09 12:33:21.36 spid12 Starting up database 'SurfControl_WebFilter'.
2003-12-09 12:33:21.36 spid14 Starting up database 'BEDB'.
2003-12-09 12:33:21.36 spid11 Bypassing recovery for database 'StarBldr'
because it is marked IN LOAD.
2003-12-09 12:33:21.36 spid5 Bypassing recovery for database 'model' because
it is marked IN LOAD.
2003-12-09 12:33:21.36 spid13 Bypassing recovery for database 'BRCS' because
it is marked IN LOAD.
2003-12-09 12:33:21.38 spid5 Database 'model' cannot be opened. It is in the
middle of a restore.
Any help would be grateful... Thanks
TIASee my other reply.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"_M_" <here@.gone.com> wrote in message
news:OI34LpovDHA.3116@.tk2msftngp13.phx.gbl...
> Is there a way to stop a hung restore ?
> Here are some error logs:
> 2003-12-09 12:35:20.94 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2003-12-09 12:35:20.94 server Copyright (C) 1988-2002 Microsoft
Corporation.
> 2003-12-09 12:35:20.94 server All rights reserved.
> 2003-12-09 12:35:20.94 server Server Process ID is 3984.
> 2003-12-09 12:35:20.94 server Logging SQL Server messages in file
> 'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2003-12-09 12:35:20.96 server SQL Server is starting at priority class
> 'normal'(4 CPUs detected).
> 2003-12-09 12:35:21.10 server SQL Server configured for thread mode
> processing.
> 2003-12-09 12:35:21.10 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2003-12-09 12:35:21.17 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2003-12-09 12:35:23.25 spid3 Starting up database 'master'.
> 2003-12-09 12:35:23.32 server Using 'SSNETLIB.DLL' version '8.0.760'.
> 2003-12-09 12:35:23.32 spid5 Starting up database 'model'.
> 2003-12-09 12:35:23.32 spid3 Server name is 'W2KSVR'.
> 2003-12-09 12:35:23.32 spid8 Starting up database 'msdb'.
> 2003-12-09 12:35:23.32 spid9 Starting up database 'pubs'.
> 2003-12-09 12:35:23.32 spid10 Starting up database 'Northwind'.
> 2003-12-09 12:35:23.32 spid11 Starting up database 'StarBldr'.
> 2003-12-09 12:35:23.32 spid12 Starting up database
'SurfControl_WebFilter'.
> 2003-12-09 12:35:23.32 spid13 Starting up database 'BRCS'.
> 2003-12-09 12:35:23.32 spid14 Starting up database 'BEDB'.
> 2003-12-09 12:35:23.33 spid11 Bypassing recovery for database 'StarBldr'
> because it is marked IN LOAD.
> 2003-12-09 12:35:23.33 spid5 Bypassing recovery for database 'model'
because
> it is marked IN LOAD.
> 2003-12-09 12:35:23.33 spid5 Database 'model' cannot be opened. It is in
the
> middle of a restore.
> 2003-12-09 12:35:23.33 spid13 Bypassing recovery for database 'BRCS'
because
> it is marked IN LOAD.
> HERE IS THE ERRORLOG.1 file:
> 2003-12-09 12:33:19.02 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2003-12-09 12:33:19.02 server Copyright (C) 1988-2002 Microsoft
Corporation.
> 2003-12-09 12:33:19.02 server All rights reserved.
> 2003-12-09 12:33:19.02 server Server Process ID is 4364.
> 2003-12-09 12:33:19.02 server Logging SQL Server messages in file
> 'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2003-12-09 12:33:19.02 server SQL Server is starting at priority class
> 'normal'(4 CPUs detected).
> 2003-12-09 12:33:19.16 server SQL Server configured for thread mode
> processing.
> 2003-12-09 12:33:19.16 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2003-12-09 12:33:19.24 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2003-12-09 12:33:21.30 spid3 Starting up database 'master'.
> 2003-12-09 12:33:21.35 server Using 'SSNETLIB.DLL' version '8.0.760'.
> 2003-12-09 12:33:21.35 spid5 Starting up database 'model'.
> 2003-12-09 12:33:21.36 spid3 Server name is 'W2KSVR'.
> 2003-12-09 12:33:21.36 spid8 Starting up database 'msdb'.
> 2003-12-09 12:33:21.36 spid9 Starting up database 'pubs'.
> 2003-12-09 12:33:21.36 spid10 Starting up database 'Northwind'.
> 2003-12-09 12:33:21.36 spid11 Starting up database 'StarBldr'.
> 2003-12-09 12:33:21.36 spid13 Starting up database 'BRCS'.
> 2003-12-09 12:33:21.36 spid12 Starting up database
'SurfControl_WebFilter'.
> 2003-12-09 12:33:21.36 spid14 Starting up database 'BEDB'.
> 2003-12-09 12:33:21.36 spid11 Bypassing recovery for database 'StarBldr'
> because it is marked IN LOAD.
> 2003-12-09 12:33:21.36 spid5 Bypassing recovery for database 'model'
because
> it is marked IN LOAD.
> 2003-12-09 12:33:21.36 spid13 Bypassing recovery for database 'BRCS'
because
> it is marked IN LOAD.
> 2003-12-09 12:33:21.38 spid5 Database 'model' cannot be opened. It is in
the
> middle of a restore.
> Any help would be grateful... Thanks
> TIA
>
Friday, March 23, 2012
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 Error - Please HELP
I had SQL Server Personal edition on my Windows XP
Professional client computer and something happened
yesterday when the network people push down Antivirus
update. Now when I try to connect other SQL Servers on the
network, it takes too long and I keep hearing raddling
disk noise.
I have the following error messages on my Event viewer:
Hanging application mmc.exe, version 5.1.2600.0, hang
module hungapp, version 0.0.0.0, hang address 0x00000000.
also
Hanging application isqlw.exe, version 2000.80.194.0, hang
module hungapp, version 0.0.0.0, hang address 0x00000000.
Is there anyone else has experienced this.
Thanks for any feedback.I'd run a ScanDisk ... peculiar noises from any disks are usually not good.
Professional client computer and something happened
yesterday when the network people push down Antivirus
update. Now when I try to connect other SQL Servers on the
network, it takes too long and I keep hearing raddling
disk noise.
I have the following error messages on my Event viewer:
Hanging application mmc.exe, version 5.1.2600.0, hang
module hungapp, version 0.0.0.0, hang address 0x00000000.
also
Hanging application isqlw.exe, version 2000.80.194.0, hang
module hungapp, version 0.0.0.0, hang address 0x00000000.
Is there anyone else has experienced this.
Thanks for any feedback.I'd run a ScanDisk ... peculiar noises from any disks are usually not good.
MMC.EXE -Application Error
--Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
I am getting an error when I try to copy the data from a table to a text fil
e using a DTS Package. I am simply creating a connection to the database (s
ource) where the table exists and then creating another connection to the te
xt file (destination). The
properties of the text file are comma for the column delimiter, double quote
s for the text qualifers and first row contains column names. So after crea
ting the two connections I then create the 'Transform Data Task' (black arro
w going from the source to
the destination). I then go to the properties of the 'Transform Data Task'.
On the 'Source' tab I select the table I want to copy. I can preview the
data with no problems. I then click on the 'Destination' tab to define the
colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This
is where the problem happens. It doesn't define the columns in the 'Destina
tion' tab. It is blank in the white space below. When I click the 'Define
Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" refe
renced memory at "0x01521e90". The memory could not be "written". Click on
OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connecti
on, I have set the OLE DB Properties 'max characters per delimited column' f
rom 255 to 8000 to set if that is the problem since I have some columns that
are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.This error occurs when you apply SP3 or SP3a to your server. Article 814113
addresses this problem and then tells you to go to article 821277 for the p
atch downloads. You have to apply a cumulative security patch which creates
a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both
hotfixes in a test environment and it fixed the error. Hopefully it doesn'
t break anything else. Also, you have to apply these hotfixes to sql server
2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file usin
g a DTS Package. I am simply creating a connection to the database (source) where t
he table exists and then creating another connection to the text file (destination).
T
he properties of the text file are comma for the column delimiter, double qu
otes for the text qualifers and first row contains column names. So after c
reating the two connections I then create the 'Transform Data Task' (black a
rrow going from the source
to the destination). I then go to the properties of the 'Transform Data Tas
k'. On the 'Source' tab I select the table I want to copy. I can preview t
he data with no problems. I then click on the 'Destination' tab to define t
he colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. Th
is is where the problem happens. It doesn't define the columns in the 'Dest
ination' tab. It is blank in the white space below. When I click the 'Defi
ne Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Erro
r
> In the main part of the window it says: The instruction at 0x4173d23a" re
ferenced memory at "0x01521e90". The memory could not be "written". Click
on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I
have set the OLE DB Properties 'max characters per delimited column' from 255 to 800
0 to set if that is the problem since I have some columns that are varchar 255. Sti
ll
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
I am getting an error when I try to copy the data from a table to a text fil
e using a DTS Package. I am simply creating a connection to the database (s
ource) where the table exists and then creating another connection to the te
xt file (destination). The
properties of the text file are comma for the column delimiter, double quote
s for the text qualifers and first row contains column names. So after crea
ting the two connections I then create the 'Transform Data Task' (black arro
w going from the source to
the destination). I then go to the properties of the 'Transform Data Task'.
On the 'Source' tab I select the table I want to copy. I can preview the
data with no problems. I then click on the 'Destination' tab to define the
colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This
is where the problem happens. It doesn't define the columns in the 'Destina
tion' tab. It is blank in the white space below. When I click the 'Define
Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" refe
renced memory at "0x01521e90". The memory could not be "written". Click on
OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connecti
on, I have set the OLE DB Properties 'max characters per delimited column' f
rom 255 to 8000 to set if that is the problem since I have some columns that
are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.This error occurs when you apply SP3 or SP3a to your server. Article 814113
addresses this problem and then tells you to go to article 821277 for the p
atch downloads. You have to apply a cumulative security patch which creates
a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both
hotfixes in a test environment and it fixed the error. Hopefully it doesn'
t break anything else. Also, you have to apply these hotfixes to sql server
2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file usin
g a DTS Package. I am simply creating a connection to the database (source) where t
he table exists and then creating another connection to the text file (destination).
T
he properties of the text file are comma for the column delimiter, double qu
otes for the text qualifers and first row contains column names. So after c
reating the two connections I then create the 'Transform Data Task' (black a
rrow going from the source
to the destination). I then go to the properties of the 'Transform Data Tas
k'. On the 'Source' tab I select the table I want to copy. I can preview t
he data with no problems. I then click on the 'Destination' tab to define t
he colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. Th
is is where the problem happens. It doesn't define the columns in the 'Dest
ination' tab. It is blank in the white space below. When I click the 'Defi
ne Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Erro
r
> In the main part of the window it says: The instruction at 0x4173d23a" re
ferenced memory at "0x01521e90". The memory could not be "written". Click
on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I
have set the OLE DB Properties 'max characters per delimited column' from 255 to 800
0 to set if that is the problem since I have some columns that are varchar 255. Sti
ll
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
MMC.EXE -Application Error
--Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). The
properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source to
the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.
This error occurs when you apply SP3 or SP3a to your server. Article 814113 addresses this problem and then tells you to go to article 821277 for the patch downloads. You have to apply a cumulative security patch which creates a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both hotfixes in a test environment and it fixed the error. Hopefully it doesn't break anything else. Also, you have to apply these hotfixes to sql server 2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). T
he properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source
to the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Error
> In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). The
properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source to
the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'populate
from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try def
ine the columns again, I receive the following error in a pop up window:
In the Title Bar of the pop up window it says: MMC.EXE - Application Error
In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
I click OK, and then it boots me out of Enterprise Manager.
In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still ge
t the same error.
I appreciate any help in advance to try resolving this problem.
This error occurs when you apply SP3 or SP3a to your server. Article 814113 addresses this problem and then tells you to go to article 821277 for the patch downloads. You have to apply a cumulative security patch which creates a problem with passwords o
n sql logins so you have to apply a small patch to fix that. I applied both hotfixes in a test environment and it fixed the error. Hopefully it doesn't break anything else. Also, you have to apply these hotfixes to sql server 2000 with SP3 or SP3a and
also to workstations who are just running the client.
"IKE" wrote:
> --Using SQL Server 2000 standard edition with SP3 on Windows 2000 Server
> I am getting an error when I try to copy the data from a table to a text file using a DTS Package. I am simply creating a connection to the database (source) where the table exists and then creating another connection to the text file (destination). T
he properties of the text file are comma for the column delimiter, double quotes for the text qualifers and first row contains column names. So after creating the two connections I then create the 'Transform Data Task' (black arrow going from the source
to the destination). I then go to the properties of the 'Transform Data Task'. On the 'Source' tab I select the table I want to copy. I can preview the data with no problems. I then click on the 'Destination' tab to define the colmns. I click 'popula
te from source' (it populates from the source) and then click 'execute'. This is where the problem happens. It doesn't define the columns in the 'Destination' tab. It is blank in the white space below. When I click the 'Define Columns' button to try d
efine the columns again, I receive the following error in a pop up window:
> In the Title Bar of the pop up window it says: MMC.EXE - Application Error
> In the main part of the window it says: The instruction at 0x4173d23a" referenced memory at "0x01521e90". The memory could not be "written". Click on OK to terminate the program
> I click OK, and then it boots me out of Enterprise Manager.
> In the 'disconnected edit' properties for the text file destination connection, I have set the OLE DB Properties 'max characters per delimited column' from 255 to 8000 to set if that is the problem since I have some columns that are varchar 255. Still
get the same error.
> I appreciate any help in advance to try resolving this problem.
>
>
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 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).
MMC DataBase Properties Error
Hello.
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
Rita
On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina
|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
Rita
On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina
|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
MMC DataBase Properties Error
Hello.
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> > Hello.
> >
> > In SQL Server 2000, when I right click on a database and then select
> > Properties,
> > I receive the following error message: "Microsoft Management Console has
> > encountered a problem and needs to close".
> >
> > I tried a couple of databases with the same results and also rebooted but
> > that didn't resolve the issue.
> >
> > Any suggestions will be greatly appreciated :-)
> >
> > Rita
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> > Hello.
> >
> > In SQL Server 2000, when I right click on a database and then select
> > Properties,
> > I receive the following error message: "Microsoft Management Console has
> > encountered a problem and needs to close".
> >
> > I tried a couple of databases with the same results and also rebooted but
> > that didn't resolve the issue.
> >
> > Any suggestions will be greatly appreciated :-)
> >
> > Rita
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
MMC DataBase Properties Error
Hello.
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>sql
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>sql
Wednesday, March 21, 2012
MMC Can't open SQL Server Enterprise Manager.msc
Hi All,
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
> > Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
because
> > the files does not exist, is not an MMC console, or was created by a
later
> > version of MMC. This may also be because you do not have sufficied
access
> > rights to the file.
> >
> > ...when trying to run Enterprise Manager. I have tried re-installing
the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
enterprise
> > manager if logged on as the local administrator. I can also run SQL
Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems to
work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan
> >
> >|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
> > *Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> > the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> > because
> > the files does not exist, is not an MMC console, or was created by a
> > later
> > version of MMC. This may also be because you do not have sufficied
> > access
> > rights to the file.
> >
> > ....when trying to run Enterprise Manager. I have tried
> > re-installing the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
> > enterprise
> > manager if logged on as the local administrator. I can also run SQL
> > Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems
> > to work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2?
> > It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan *
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>
I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
error:
MMC cannot open the file c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
the files does not exist, is not an MMC console, or was created by a later
version of MMC. This may also be because you do not have sufficied access
rights to the file.
...when trying to run Enterprise Manager. I have tried re-installing the
server and client tools, and SP3a, but still the same error.
I have administrator access to the PC, but strangely, I can run enterprise
manager if logged on as the local administrator. I can also run SQL Server
Enterprise Manager.msc if I rename it to anything else, and it seems to work
all right.
Shall I just carry on using the new SQL Server Enterprise Manager 2? It
seems like a very odd issue.
Thanks in advance.
RyanRyan,
Can you rename it to SQLEM.msc? Does that work? Then just create a
shortcut on your desktop or Start Menu, and all should be well.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Ryan Breakspear wrote:
> Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be because
> the files does not exist, is not an MMC console, or was created by a later
> version of MMC. This may also be because you do not have sufficied access
> rights to the file.
> ...when trying to run Enterprise Manager. I have tried re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run enterprise
> manager if logged on as the local administrator. I can also run SQL Server
> Enterprise Manager.msc if I rename it to anything else, and it seems to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> seems like a very odd issue.
> Thanks in advance.
> Ryan
>|||Yep, I can rename it to anything. I can run it fine renamed as something
else, I just wondered why the problem, and if there was a solution.
Thanks for your reply.
Ryan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:edplxoLcEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Ryan,
> Can you rename it to SQLEM.msc? Does that work? Then just create a
> shortcut on your desktop or Start Menu, and all should be well.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Ryan Breakspear wrote:
> > Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
because
> > the files does not exist, is not an MMC console, or was created by a
later
> > version of MMC. This may also be because you do not have sufficied
access
> > rights to the file.
> >
> > ...when trying to run Enterprise Manager. I have tried re-installing
the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
enterprise
> > manager if logged on as the local administrator. I can also run SQL
Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems to
work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2? It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan
> >
> >|||I have the exact same settings, and the exact same problem. Wish I had
found this workaround before re-installing everything... Still would
like to know what is causing this though...
Cheers - Craig
Ryan Breakspear wrote:
> *Hi All,
> I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> the
> error:
> MMC cannot open the file c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> because
> the files does not exist, is not an MMC console, or was created by a
> later
> version of MMC. This may also be because you do not have sufficied
> access
> rights to the file.
> ....when trying to run Enterprise Manager. I have tried
> re-installing the
> server and client tools, and SP3a, but still the same error.
> I have administrator access to the PC, but strangely, I can run
> enterprise
> manager if logged on as the local administrator. I can also run SQL
> Server
> Enterprise Manager.msc if I rename it to anything else, and it seems
> to work
> all right.
> Shall I just carry on using the new SQL Server Enterprise Manager 2?
> It
> seems like a very odd issue.
> Thanks in advance.
> Ryan *
cjeff
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message888314.html|||I have been trying to fix this problem for some time. The fact that it
worked for you when you renamed it tipped me off to the source of the
problem. There is a cached version of the MMC file in the C:\Documents and
Settings\<username>\Application Data\Microsoft\MMC folder.
The problem is that on my system that cached file was corrupted.
Once I deleted the cached file, I was able to open SQL EntMgr with no problem.
"cjeff" wrote:
> I have the exact same settings, and the exact same problem. Wish I had
> found this workaround before re-installing everything... Still would
> like to know what is causing this though...
> Cheers - Craig
> Ryan Breakspear wrote:
> > *Hi All,
> >
> > I'm using XP Pro, and Windows SQL Server 2000 SP3a, and I'm getting
> > the
> > error:
> >
> > MMC cannot open the file c:\Program Files\Microsoft SQL
> > Server\80\Tools\Binn\SQL Server Enterprise Manager.msc. This may be
> > because
> > the files does not exist, is not an MMC console, or was created by a
> > later
> > version of MMC. This may also be because you do not have sufficied
> > access
> > rights to the file.
> >
> > ....when trying to run Enterprise Manager. I have tried
> > re-installing the
> > server and client tools, and SP3a, but still the same error.
> >
> > I have administrator access to the PC, but strangely, I can run
> > enterprise
> > manager if logged on as the local administrator. I can also run SQL
> > Server
> > Enterprise Manager.msc if I rename it to anything else, and it seems
> > to work
> > all right.
> >
> > Shall I just carry on using the new SQL Server Enterprise Manager 2?
> > It
> > seems like a very odd issue.
> >
> > Thanks in advance.
> >
> > Ryan *
>
> --
> cjeff
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message888314.html
>
Subscribe to:
Posts (Atom)