Reopen Bug ID: 258528 cannot show requested dialog (sqlmgmt) there is no row at position 0 system.data

Reopen Bug ID: 258528 cannot show requested dialog (sqlmgmt) there is no row at position 0 system.data by Yatish Ram

Closed

as Not Reproducible Help for as Not Reproducible

Type:	Bug
ID:	641305
Opened:	2/4/2011 3:53:40 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Sql server managemet studio fail to show propertie dialogue box for any database. it return error
cannot show requested dialog (sqlmgmt) there is no row at position 0 system.data

Details (expand)

English

SQL Server 2008 R2 - Developer Edition

Tools (SSMS, Agent, Profiler, Migration, etc.)

Windows 7 Ultimate

English

1. Restore a backed up database from some other machine.
2. Create another empty database
3. Generate create schema script from database 1 and run on database 2 to have identical schema
4. Now import data from database 1 to database 2
5. Right click on any database and select properties

Unable to manage any databases. Errors are as follows:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Cannot show requested dialog.
------------------------------
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
------------------------------
There is no row at position 0. (System.Data)
------------------------------
BUTTONS:
OK
------------------------------

Property dialogue box should appear and display information

X64

0 attachments

Posted by martin capodici on 1/18/2012 at 3:00 PM

This is the solution:

http://social.msdn.microsoft.com/forums/en-US/sqltools/thread/4e245a84-0663-4967-a5e1-470ddf546ded

Incase that thread is deleted, here is what it said:

"Just got off the phone with MS on the same problem.

The cause is that the system table spt_values has been deleted. But don't know who did it and why that could happen.

Solution: run u_tables.sql from your instance's install directory. e.g: C:\Program Files\Microsoft SQL Server\MSSQL$SQL2005\MSSQL.1\MSSQL\Install\u_tables.sql

It solved my problem.

Best regards.

Ed Sun"

Posted by martin capodici on 1/17/2012 at 9:47 PM

This bug happened to me today. Exact same error message.

Perhaps you should try again :-)

It coincided with one of the databases becoming too full, if that helps.

Posted by Microsoft on 3/29/2011 at 3:06 AM

Hello:

Greetings from the Microsoft SQL Server Manageability Team.

We triaged this bug along with several others that had come in. We are unable to reproduce this issue. Hence we are closing this issue. If you continue to face this issue, please get back to us with exact repro steps, and we will relook at this.

Thanks much for writing into Microsoft.

Cheers,

Chandramouli
SQL Server Manageability