If the table exists and you get that error all I can guess is that the user in your connection string is not a dbo (database owner) but in that case it will get errors on all tables and stored procedures that have the [dbo]. prefix nothing about upgrading should cause that. It means the user doesn't have dbo permission and does not see objects named with [dbo]. prefix.

I would check with your host and ask him to make your user in the database connection string a dbo on the database. I don't know any other solution to fix it. I don't see how it is possible that this is related to an upgrade unless your host changed something at the same time.

When you look at the table names in your database are they named with dbo. or with something else?

If it is a single site installation you might be able to solve it by this:

ALTER PROCEDURE [dbo].[mp_SiteHosts_SelectSiteIdByHost]

@HostName nvarchar(255)

AS

SELECT 1

GO

assuming 1 is the site id for your site which it usually is in a single site installation.

Hope that helps,

Joe

Glad that fixed it! But the solution is kind of a hack. I'd still like to know the answer to this question:

When you look at the table names in your database are they named with dbo. or with something else?

Because it may help me understand why this error happened in the first place. I'm sure it has something to do with the way the database is configured but I'm not sure yet exactly what the problem is. This error should not happen and I would like to figure out why it is happening and a way to prevent it.

Best,

Joe