problem with DB after upgrade to 2005

Hi all.
I just ran my first test upgrade from 2000 to 2005 on a system with
several db's. All of them but one seem to be fine. I get a message
that says the following when I try to expand the table list:
Value cannot be null parameter name: context (object explorer)
the details of the message are here:
===================================
Value cannot be null.
Parameter name: context (ObjectExplorer)
Program Location:
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NodeContext..ctor(SqlOlapConnectionIn foBase
connection, String name, String context, INodeInformation parent)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItemBuilder.BuildDynamicItem WithQuery(IList
nodes, INodeInformation source, INavigableItem sourceItem, String
urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItemBuilder.BuildDynamicItem (IList
nodes, INodeInformation source, INavigableItem sourceItem,
IFilterProvider filter)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItemBuilder.Build(INodeInfor mation
source, INavigableItem sourceItem, IFilterProvider filter)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NonContextFilterNavigableItemBuilder. Build(INodeInformation
source, INavigableItem sourceItem, IFilterProvider filter)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItem.GetChildren()
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.SummaryView.get_Items()
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.ListViewVirtualStorage.CopyItems(ISumma ryView
summaryView)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.ListViewVirtualStorage..ctor(ISummaryVi ew
summaryView, List`1 columnDescriptors)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneListViewer.PopulateView()
Like i said, this is the only db out of 4 user db's that is having
this problem.
any suggestions on where to start?
Meredith
Hi Meredith
"mryan" wrote:

> Hi all.
> I just ran my first test upgrade from 2000 to 2005 on a system with
> several db's. All of them but one seem to be fine. I get a message
> that says the following when I try to expand the table list:
> Value cannot be null parameter name: context (object explorer)
> the details of the message are here:
> ===================================
> Value cannot be null.
> Parameter name: context (ObjectExplorer)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NodeContext..ctor(SqlOlapConnectionIn foBase
> connection, String name, String context, INodeInformation parent)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItemBuilder.BuildDynamicItem WithQuery(IList
> nodes, INodeInformation source, INavigableItem sourceItem, String
> urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItemBuilder.BuildDynamicItem (IList
> nodes, INodeInformation source, INavigableItem sourceItem,
> IFilterProvider filter)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItemBuilder.Build(INodeInfor mation
> source, INavigableItem sourceItem, IFilterProvider filter)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NonContextFilterNavigableItemBuilder. Build(INodeInformation
> source, INavigableItem sourceItem, IFilterProvider filter)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.NavigableItem.GetChildren()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.SummaryView.get_Items()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.ListViewVirtualStorage.CopyItems(ISumma ryView
> summaryView)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.ListViewVirtualStorage..ctor(ISummaryVi ew
> summaryView, List`1 columnDescriptors)
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneListViewer.PopulateView()
>
> Like i said, this is the only db out of 4 user db's that is having
> this problem.
> any suggestions on where to start?
>
> Meredith
>
There doesn't seem to be much on this error!
[url]http://groups.google.com/groups/search?hl=en&lr=&q=%22Parameter+name%3A+context+%2 8ObjectExplorer%29%22[/url]
Does this error occur for all databases (including master/tempdb or new
ones), if so it is most likely an issue with the installation or tools.
If specific databases, then can you restore a SQL 2000 backup onto the SQL
2005 server and see if it still occurs?
Check the compatibility mode of the original database and the upgraded one.
John
|||I know there seems to be nothing really out there on this error. It
is only happening on one db on the server, so I find it unlikely as
well that it is an install issue - even stranger, I can expand the
views list, and other objects in that DB just fine. The compatibility
modes are the same (80). My next step is to do a restore, but I am
trying to exhaust all other options since it is a 500gig db, and the
restore is going to take 10+ hrs.
Meredith

> There doesn't seem to be much on this error!
> http://groups.google.com/groups/search?hl=en&lr=&q=%22Parameter+name%...
> Does this error occur for all databases (including master/tempdb or new
> ones), if so it is most likely an issue with the installation or tools.
> If specific databases, then can you restore a SQL 2000 backup onto the SQL
> 2005 server and see if it still occurs?
> Check the compatibility mode of the original database and the upgraded one.
> John- Hide quoted text -
> - Show quoted text -
|||There really isn't much out there on this. The error is only
happening on the table list of a single user db. The compatibility
mode is the same (80), and it is happening on several different
installs of SSMS. A restore is my last hope since it is a 500gig db
and the restore will take 10+ hrs.
Meredith

> There doesn't seem to be much on this error!
> http://groups.google.com/groups/search?hl=en&lr=&q=%22Parameter+name%...
> Does this error occur for all databases (including master/tempdb or new
> ones), if so it is most likely an issue with the installation or tools.
> If specific databases, then can you restore a SQL 2000 backup onto the SQL
> 2005 server and see if it still occurs?
> Check the compatibility mode of the original database and the upgraded one.
> John- Hide quoted text -
> - Show quoted text -
|||On May 16, 2:26 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Meredith
>
>
> "mryan" wrote:
>
>
>
>
> There doesn't seem to be much on this error!
> http://groups.google.com/groups/search?hl=en&lr=&q=%22Parameter+name%...
> Does this error occur for all databases (including master/tempdb or new
> ones), if so it is most likely an issue with the installation or tools.
> If specific databases, then can you restore a SQL 2000 backup onto the SQL
> 2005 server and see if it still occurs?
> Check the compatibility mode of the original database and the upgraded one.
> John- Hide quoted text -
> - Show quoted text -
I figured it out! The problem seems to be that there are two tables
in the DB not owned by dbo. When you query information_schema.tables
the table_schema value for both is NULL. Of course I can't modify
ownership or drop either table, so I am going to have to restore a new
copy of the db, with the ownership of those tables fixed.
Meredith
|||Hi Meredith
"mryan" wrote:
> I figured it out! The problem seems to be that there are two tables
> in the DB not owned by dbo. When you query information_schema.tables
> the table_schema value for both is NULL. Of course I can't modify
> ownership or drop either table, so I am going to have to restore a new
> copy of the db, with the ownership of those tables fixed.
> Meredith
>
Does the user who owned the object exist in the restored system and is that
user associated to a login?
John