Hi
I've run a few (failed) site upgrades on our test server and its beginning to look like its due to some new sql commands (like "ON") introduced after the switch to the 5.x series of releases that are supported in SQL 2005 and 2008 but not 2000. I know we're about a decade behind the times running 2000 but are our suspicions true that 5.1 will not play nice with 2000? I don't remember reading that anywhere in the specs. Is there something we have to finagle to get 5.1 working with 2000?
Thanks
Mike

Cant tell you how much I hate this forum set up. Every other post is lost. Anyway, second attempt,  thanks for your reply. I don't have the original logs but they dealt primarily with 'invalid column name 'portal id''. Just wanted your core team to be aware that there may be some issues surrounding 2000.

• upgrade package 5.1 used on 4.8.3 site. Errored out after hitting 5.00.00.sqldataprovider
• upgraded incrementally and all upgrades were successful until hitting that same spot
• altered some of the sql causing even more errors then decided it would be less painful to upgrade sql.
• we did not try any of the install packages

Mike

I just doublechecked this.  It appears that there is not an error with a clean install, but upon upgrading, there is an error with a DROP INDEX statement using non-SQL Server 2005 compliant syntax.  This causes a host of other problems later on in the script, the main one being that the PortalID column does not get added to the Packages table, so all stored procedures that try to access the table then can't be created.

I've created a Gemini issue for this, DNN-10354.

Hope it helps,