Error: Cannot display activity

TITLE: Microsoft SQL Server Management Studio Express (CTP Nov)

OS: Both XP SP2 and Win2003 SP1

Cannot display activity for database 'SomeDBName'.

ADDITIONAL INFORMATION:

Could not load file or assembly 'ActivityMonitor, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (mscorlib)

To reproduce:

Try to detach a database which has at least one active connection. On the Detach Database dialog click on: 1 Active connection.

Hi, this issue has already been found and resolved. You should not see this on the RTM version.|||

Hi

This is the only place in the entire world I have found reference to this problem. I have the same problem and I'm running MS SQL Server 2005 Express SP1 running on XP SP2.

Help > About on SSMSE shows:

Microsoft SQL Server Management Studio Express 9.00.2047.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

I found a KB article a while back about changing the registry key HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\TlbAutoRepair\mscorlib.tlb TlbPath value of %CLRVERSION% to v2.0.50727 but that didn't fix it. I've since tried repairing .Net Framework 2.0 and SSMSE but still have the problem.

Any ideas where to go next?

Mick

Error: Cannot display activity

TITLE: Microsoft SQL Server Management Studio Express (CTP Nov)

OS: Both XP SP2 and Win2003 SP1

Cannot display activity for database 'SomeDBName'.

ADDITIONAL INFORMATION:

Could not load file or assembly 'ActivityMonitor, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (mscorlib)

To reproduce:

Try to detach a database which has at least one active connection. On the Detach Database dialog click on: 1 Active connection.

Hi, this issue has already been found and resolved. You should not see this on the RTM version.|||

Hi

This is the only place in the entire world I have found reference to this problem. I have the same problem and I'm running MS SQL Server 2005 Express SP1 running on XP SP2.

Help > About on SSMSE shows:

Microsoft SQL Server Management Studio Express 9.00.2047.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

I found a KB article a while back about changing the registry key HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\TlbAutoRepair\mscorlib.tlb TlbPath value of %CLRVERSION% to v2.0.50727 but that didn't fix it. I've since tried repairing .Net Framework 2.0 and SSMSE but still have the problem.

Any ideas where to go next?

Mick

Error, when alter table

Hi,
on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in a
ny Databse when trying to 'alter table'
The error says something like 'Cursor not vaild' or in German 'Ungueltiger C
ursorstatus'
Any ideas?
Thanks in advanceDid you try running an explicit ALTER TABLE statement in Query Analyzer,
instead of making changes using Enterprise Manager?
http://www.aspfaq.com/2515
http://www.aspfaq.com/
(Reverse address to reply.)
"DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com>
wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com...
> Hi,
> on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in
any Databse when trying to 'alter table'
> The error says something like 'Cursor not vaild' or in German 'Ungueltiger
Cursorstatus'
> Any ideas?
> Thanks in advance|||Hi again,
your suggestions work fine with the QueryAnalyzer. But beside that, we are f
acing the problem, that some asp-Scripts do not work when performing a 'rs.U
pdate'
They show error: (80040e23) 'Cursor operation conflict'
The Scripts worked fine before.
"Aaron [SQL Server MVP]" wrote:

> Did you try running an explicit ALTER TABLE statement in Query Analyzer,
> instead of making changes using Enterprise Manager?
> http://www.aspfaq.com/2515
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com
> wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com..
.
> any Databse when trying to 'alter table'
> Cursorstatus'
>
>|||> some asp-Scripts do not work when performing a 'rs.Update'
Call a stored procedure or use an UPDATE statement to perform an update.
Don't use a heavy, lock-intensive recordset object...
http://www.aspfaq.com/2191
http://www.aspfaq.com/
(Reverse address to reply.)|||That might be true, but the Scripts workes on our 'old' Server.
The only thing we want is the scripts running in the 'new' environment.
We will not change everything because of some bad SQL-Patches.
If it is the only chance I'd prefer installing a new instance of the SQL-Ser
ver without the above mentioned Patch.
"Aaron [SQL Server MVP]" wrote:

> Call a stored procedure or use an UPDATE statement to perform an update.
> Don't use a heavy, lock-intensive recordset object...
> http://www.aspfaq.com/2191
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||That might be true, but the Scripts workes on our 'old' Server.
The only thing we want is the scripts running in the 'new' environment.
We will not change everything because of some bad SQL-Patches.
If it is the only chance I'd prefer installing a new instance of the SQL-Ser
ver without the above mentioned Patch.
"Aaron [SQL Server MVP]" wrote:

> Call a stored procedure or use an UPDATE statement to perform an update.
> Don't use a heavy, lock-intensive recordset object...
> http://www.aspfaq.com/2191
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||> If it is the only chance I'd prefer installing a new instance of the
SQL-Server without the above mentioned Patch.
Did you actually read the whole article I referenced? Here it is again,
just in case:
http://www.aspfaq.com/2515
http://www.aspfaq.com/
(Reverse address to reply.)

Error, when alter table

Hi,
on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in any Databse when trying to 'alter table'
The error says something like 'Cursor not vaild' or in German 'Ungueltiger Cursorstatus'
Any ideas?
Thanks in advanceDid you try running an explicit ALTER TABLE statement in Query Analyzer,
instead of making changes using Enterprise Manager?
http://www.aspfaq.com/2515
--
http://www.aspfaq.com/
(Reverse address to reply.)
"DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com>
wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com...
> Hi,
> on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in
any Databse when trying to 'alter table'
> The error says something like 'Cursor not vaild' or in German 'Ungueltiger
Cursorstatus'
> Any ideas?
> Thanks in advance|||> some asp-Scripts do not work when performing a 'rs.Update'
Call a stored procedure or use an UPDATE statement to perform an update.
Don't use a heavy, lock-intensive recordset object...
http://www.aspfaq.com/2191
--
http://www.aspfaq.com/
(Reverse address to reply.)|||> If it is the only chance I'd prefer installing a new instance of the
SQL-Server without the above mentioned Patch.
Did you actually read the whole article I referenced? Here it is again,
just in case:
http://www.aspfaq.com/2515
--
http://www.aspfaq.com/
(Reverse address to reply.)

Error, when alter table

Hi,
on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in any Databse when trying to 'alter table'
The error says something like 'Cursor not vaild' or in German 'Ungueltiger Cursorstatus'
Any ideas?
Thanks in advance
Did you try running an explicit ALTER TABLE statement in Query Analyzer,
instead of making changes using Enterprise Manager?
http://www.aspfaq.com/2515
http://www.aspfaq.com/
(Reverse address to reply.)
"DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com>
wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com...
> Hi,
> on a SQL Server 200 installed on a Win2003 Std. Server, we get an error in
any Databse when trying to 'alter table'
> The error says something like 'Cursor not vaild' or in German 'Ungueltiger
Cursorstatus'
> Any ideas?
> Thanks in advance
|||Hi again,
your suggestions work fine with the QueryAnalyzer. But beside that, we are facing the problem, that some asp-Scripts do not work when performing a 'rs.Update'
They show error: (80040e23) 'Cursor operation conflict'
The Scripts worked fine before.
"Aaron [SQL Server MVP]" wrote:

> Did you try running an explicit ALTER TABLE statement in Query Analyzer,
> instead of making changes using Enterprise Manager?
> http://www.aspfaq.com/2515
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "DOKOM@.community.nospam" <DOKOM@.community.nospam@.discussions.microsoft.com>
> wrote in message news:A51F71F0-A5DD-43B9-B849-B3B26759C929@.microsoft.com...
> any Databse when trying to 'alter table'
> Cursorstatus'
>
>
|||> some asp-Scripts do not work when performing a 'rs.Update'
Call a stored procedure or use an UPDATE statement to perform an update.
Don't use a heavy, lock-intensive recordset object...
http://www.aspfaq.com/2191
http://www.aspfaq.com/
(Reverse address to reply.)
|||That might be true, but the Scripts workes on our 'old' Server.
The only thing we want is the scripts running in the 'new' environment.
We will not change everything because of some bad SQL-Patches.
If it is the only chance I'd prefer installing a new instance of the SQL-Server without the above mentioned Patch.
"Aaron [SQL Server MVP]" wrote:

> Call a stored procedure or use an UPDATE statement to perform an update.
> Don't use a heavy, lock-intensive recordset object...
> http://www.aspfaq.com/2191
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
|||That might be true, but the Scripts workes on our 'old' Server.
The only thing we want is the scripts running in the 'new' environment.
We will not change everything because of some bad SQL-Patches.
If it is the only chance I'd prefer installing a new instance of the SQL-Server without the above mentioned Patch.
"Aaron [SQL Server MVP]" wrote:

> Call a stored procedure or use an UPDATE statement to perform an update.
> Don't use a heavy, lock-intensive recordset object...
> http://www.aspfaq.com/2191
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
|||> If it is the only chance I'd prefer installing a new instance of the
SQL-Server without the above mentioned Patch.
Did you actually read the whole article I referenced? Here it is again,
just in case:
http://www.aspfaq.com/2515
http://www.aspfaq.com/
(Reverse address to reply.)