do you think it would be safe to  open up Programmability >> Stored Procedures >>
and individually delete all the stored procedures not belonging to the 'dbo' schema?
(or run a script to delete all the duplicate stored procedures, which would be quicker).

or is there a safer / better way to getr around the problem of having 2 schemas - perhaps in code ? (by changing ownership).

I can't just delete one of the schemas becasue I get an error (3729) that it is being referenced by a stored procedure

thanks.

I've just checked the stored procedures again.
Even though there are duplicate entries, the items which are failing are not duplicated.

Under the dbo schema - the stored procedures which are failing do not exist.
They only exist under the other schema, i will call this schema 'nigel'.

Last time I ran the upgrade with 'nigel' as the default schema  - I got the permission errors.
however, I have reverted back to 'nigel' as the default schema (in >> Security >> users >> nigel >> Properties)
[note, I'm not certain what I used as the owner of the schema originally under security >> schemas >> nigel >> properties]

And now the upgrade has run successfully !
Albet except for minor errors, which don't seem to list any errors as such inside the log files:

These are all the failures:

00:02:31.114 -   Executing Application Upgrades: 05.03.00 Error!
00:02:34.349 -   Executing Application Upgrades: 05.04.03 Error!
00:02:34.474 -   Installing Package File HTML_Community_05.01.00_Install:  Error!
00:02:36.818 -   Installing Package File HTML_Community_05.01.02_Install:  Error!
00:02:39.349 -   Installing Package File HTML_Community_05.04.03_Install:  Error!
00:02:45.928 -   Installing Package File Messaging_01.01.00_Install:  Error!
00:02:46.084 -   Installing Package File Taxonomy_01.01.00_Install:  Error!
00:02:47.772 -   Installing Package File CorePermissionProvider_05.01.00_Install:  Error!

example of the log file errors:

05_01_00
/* change default logging to off */
/********************************/
UPDATE {databaseOwner}[{objectQualifier}EventLogConfig] set [LoggingIsActive]=0 where [LogTypeKey] is null and [LogTypePortalID] is null
GO
/*  add helper proc to create/update core audit events */
/********************************/
IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'{databaseOwner}[{objectQualifier}SaveCoreAuditTypes]') AND OBJECTPROPERTY(id, N'IsPROCEDURE') = 1)
  DROP PROCEDURE {databaseOwner}{objectQualifier}SaveCoreAuditTypes
GO
CREATE PROCEDURE {databaseOwner}{objectQualifier}SaveCoreAuditTypes
 @LogTypeKey nvarchar(35), 
 @LogTypeFriendlyName nvarchar(50), 
 @LogTypeOwner nvarchar(100), 
...............................................................................................

05_03_00
IF NOT EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'{databaseOwner}[{objectQualifier}ContentTypes]') AND OBJECTPROPERTY(id, N'IsTable') = 1)
 BEGIN
  CREATE TABLE {databaseOwner}[{objectQualifier}ContentTypes]
  (
   [ContentTypeID] [int] IDENTITY(1,1) NOT NULL,
   [ContentType] [nvarchar](100) NOT NULL,
   CONSTRAINT [PK_{objectQualifier}ContentTypes] PRIMARY KEY CLUSTERED ( [ContentTypeID] ASC )
  )
 END
GO
/* Add ContentItems Table */
...............................................................................................

_05_04_03
IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'{databaseOwner}[{objectQualifier}AddEventLog]') AND OBJECTPROPERTY(id, N'IsPROCEDURE') = 1)
  DROP PROCEDURE {databaseOwner}{objectQualifier}AddEventLog
GO
CREATE PROCEDURE  {databaseOwner}{objectQualifier}AddEventLog
 @LogGUID varchar(36),
 @LogTypeKey nvarchar(35),
...............................................................................................

btw,
I don't have a table called sysobjects - should I?