12 Nov 2008
17 Feb 2009
Link to this post
Hi Michael, did you do a fresh installation or did you update an existing Sitefinity 3.5 website?
I had the same issue on our development server when I updated our existing Sitefinity 3.5 installation to 3.6. It turned out that the database was only updated partially, leaving some of the stored procedures in a non-working state. In my case, the stored procedure that threw the error had not been updated at all.
On my local development machine, everything had worked fine though. And since I had copied the databases before the update, I could just copy it back from my machine to the development server which fixed the issue.
Since those stored procedures don't hold any data, you might want to try the following:
- Create a new database and do a fresh installation of version 3.6 in there.
- Copy all the stored procedures from this database into your current database.
Unfortunately, I could not find any scripts that would update an existing 3.5 database to 3.6 without manual labor.