Error from sys.dm_db_index_physical_stats "No exceptions should be raised by this code"

I'm setting up a routine to do some reindexing. To get the info I need I'm trying to use the new function. The DB I think is causing the problem does pass DBCC CHECKDB. I'm not sure why I'm getting this but can not find anyone else that is getting this same error.

When I run this....

SELECT *

FROM sys.dm_db_index_physical_stats (NULL, NULL, NULL, NULL, 'detailed')

I get this....

Location: qxcntxt.cpp:954

Expression: !"No exceptions should be raised by this code"

SPID: 236

Process ID: 1060

Msg 0, Level 11, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

Msg 0, Level 20, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

If I run only for the DB I think is causing the problem I get this...

Msg 0, Level 11, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

Msg 0, Level 20, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

Well, since this created a dump I guess I'll be contacting product support services. Just thought I'd check online first.|||

I think when system code claims: Expression: !"No exceptions should be raised by this code" that would be the best thing...

Can you post here and tell us what the issue was?

|||Unfortunately, this is an internal server error due to unknown cause, and unlikely to get resolved with standard mini dump only.|||

This is was found to be a bug in SP1 of SQL 2005. The work around is to use limited instead of detailed. I don't get all the data I was wanting to collect but this will work ok until SP2 is released with the fix. We had three DBs on our 2005 server that would generate this error.

|||Thanks for letting us know. It is always interesting when someone else is having a similar problem if a resolution (or lack thereof :) is noted!

Error from sys.dm_db_index_physical_stats "No exceptions should be raised by this code&

I'm setting up a routine to do some reindexing. To get the info I need I'm trying to use the new function. The DB I think is causing the problem does pass DBCC CHECKDB. I'm not sure why I'm getting this but can not find anyone else that is getting this same error.

When I run this....

SELECT *

FROM sys.dm_db_index_physical_stats (NULL, NULL, NULL, NULL, 'detailed')

I get this....

Location: qxcntxt.cpp:954

Expression: !"No exceptions should be raised by this code"

SPID: 236

Process ID: 1060

Msg 0, Level 11, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

Msg 0, Level 20, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

If I run only for the DB I think is causing the problem I get this...

Msg 0, Level 11, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

Msg 0, Level 20, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.

Well, since this created a dump I guess I'll be contacting product support services. Just thought I'd check online first.|||

I think when system code claims: Expression: !"No exceptions should be raised by this code" that would be the best thing...

Can you post here and tell us what the issue was?

|||Unfortunately, this is an internal server error due to unknown cause, and unlikely to get resolved with standard mini dump only.|||

This is was found to be a bug in SP1 of SQL 2005. The work around is to use limited instead of detailed. I don't get all the data I was wanting to collect but this will work ok until SP2 is released with the fix. We had three DBs on our 2005 server that would generate this error.

|||Thanks for letting us know. It is always interesting when someone else is having a similar problem if a resolution (or lack thereof :) is noted!

Error during set partner statement (SP1)

Hi!

I have the following error during setting partner on mirror server
Msg 1431, Level 16, State 4, Line 1
Neither the partner nor the witness server instance for database "masterserver" is available. Reissue the command when at least one of the instances becomes available.

The partner is available through telnet. I've also checked ports vai netstat and have no found errors.

There are two noteworthy erros in the error log at mirror server
Error: 9642, Severity: 16, State: 3.
and
An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')

Security settings it seems are set accurately.

Ok, find out the problem.
I leave database yesterday in restoring state and today morning it has recovering state.

When I synchronize logs again mirroring has worked fine. I think during server startup (I restarted server today morning) it tries to recover mirror database. It leads database status changing and impossibility to set up partner.

Error Creating User on Database

Hi there,

I am setting up a database for the first time using SQL Server Express.

I have managed to create a database and create a table with data etc, all straight forward.

The problem I am having is when I come to creating a user for the database. I have the following users in there already, which I am guessing are put in by default:

dbo

guest

INFORMATION_SCHEMA

sys

When I try creating a new user via this screen I get the following error:

TITLE: Microsoft SQL Server Management Studio Express

Create failed for User 'growstudiouser'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+User&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

'growstudio' is not a valid login or you do not have permission. (Microsoft SQL Server, Error: 15007)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15007&LinkId=20476

I was wondering if anybody could advise me as to what I'm doing wrong. I am typing in the name as "growstudiouser" and the login name as "growstudio".

Or am I just using the wrong section to do what I want. I'm trying to create a user so that when the database is built I can connect to it using a username and password that I have created. I'm not sure I'm taking to the correct route as there is no password option anywhere when creating a new user.

Thanks in advance,

Kevin

hi Kevin,

usually a database user is associated with a server's login, if you do not define a user as

USE tempdb; GO CREATE USER testUser WITHOUT LOGIN WITH DEFAULT_SCHEMA = dbo; GO DROP USER testUser;

where the database user is not associated with a server level principal, but this is another story..

so you should first create the server login as

USE master; CREATE LOGIN testLogin WITH PASSWORD = 'his strong password'; GO USE tempdb; GO CREATE USER testUser FOR LOGIN testLogin WITH DEFAULT_SCHEMA = dbo; GO DROP USER testUser; GO USE master; GO DROP LOGIN testLogin;

regards

|||

SQL Server follows two level security architecture. Login and User . Login is to access to the server. If you have login it does not mean that you have access to all the databases in that server. NO. To access database, the Login has to be mapped/added to the database as user. So , in your case what your are probably doing is you are not maping the user with a login . You should select a login while creating user

Madhu