December 18, 2009 at 6:42 am
(sorry, realized I posted in 2005 forum after the fact and I can't remove this)
Morning all,
Crazy issue here. I just got done installing a second instance of SQL2000 on a windows 2003 server, and the environment is up and running with one exception. I can not right click a database and view properties with SSMS (2008) as it errors out stating "Object reference not set to an instance of an object". It works fine with Enterprise Manager and SSMS (2005). I can connect to any other 2000 environment and view the properties of a database, even the other instance on this server without error with SSMS 2008. I've even tried on other servers/desktops with SSMS 2008, same problem. The full error is as follows:
===================================
Cannot show requested dialog.
===================================
Cannot show requested dialog. (SqlMgmt)
------------------------------
Program Location:
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider, CDataContainer dc)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolMenuItemHelper.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
Object reference not set to an instance of an object. (Microsoft.SqlServer.Smo)
------------------------------
Program Location:
[highlight=#ffff11] at Microsoft.SqlServer.Management.Smo.DatabaseOptions.get_DatabaseOwnershipChaining()[/highlight]
at Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.DatabaseData..ctor(CDataContainer context, String databaseName)
at Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype.LoadDefinition(String newName)
at Microsoft.SqlServer.Management.SqlManagerUI.CreateDatabaseData.DatabasePrototype..ctor(CDataContainer context)
at Microsoft.SqlServer.Management.SqlManagerUI.DBPropSheet..ctor(CDataContainer context)
Note the highlighted section. When I check sp_configure, the option of "Cross DB Ownership Chaining" is missing. sp_configure returns 36 rows; whereas any other SQL2000 environment I run has 37. I reinstalled SP4 for S&G's to no avail. At this point I think I'm going to simply tear down and reinstall, but was curious to as if anyone had any last minute thoughts on this matter. I've never seen this before and I'm beyond curious to know what happened here.
Thanks
December 18, 2009 at 7:58 am
Hi,
Check the following KB this might be help.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
December 18, 2009 at 8:03 am
Thanks Muthukumaran, but unfortunately that does not apply to this situation.
December 18, 2009 at 8:24 am
Well, reinstalling fixed it ... crazy, wish I knew what caused this.
August 13, 2014 at 9:50 am
http://sqlsolace.blogspot.co.uk/2009/05/management-studio-error-object.html
suggests that service pack has not been applied correctly – redo that and problem should go away
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply