Saturday morning I got my access to a new Win2K8 server. I feel really lucky: I have administrator Remote Desktop access, access to the SQL sa account and to the SQL file system. Moving should be child's play. It was not, because the SQL server is 2008 and mine is 2008 R2. So the easy methods, attaching a copy of the database files to the new server or restoring from a backup were not popssible and I had to script out the database to transfer it to the SQL 2008 system.

I've tried out all of the publishing methods, including the publish option in vs2008, but each and every method created errors.I finally broke up the script into pieces until I could locate the bit that caused the error. The offender turned ot to be a stored procedure Forum_ForumUserViewsUpdate. A search through the forums taught me that this was previously pointed out but that there was no solution for it. Removing the offending procedure allowed me to finish the transfer without further errors.

I met many more obstacles but all have been cleared. Now, Sunday noon, I have a working version of my portals on the server. But what about that missing stored procedure? Is it obsolete? Then, why doesn't DNN issue a script to remove it from the database? Can I remove it manually without repercussions and will it not reappear with subsequent upgrades of DNN?

---

____________________________________
The one-eyed in the land of the blind.

The procedure tries to write a date to the column [LastForumsview], but this column does not (or no longer?) exist in the table. Any piece of code that uses this procedure should recieve an error. That is why I guess the procedure to be obsolete, in which case it should be dropped, yet it is still there, causing an error during the import of the script.

After a first trial (with error), DNN gave me the installation wizard. This was not related to this error, but little did I know, so I spent an unreasonable amount of time researching it, while the installation wizard error was caused by an oddity in SQL server's security management. I could log in into the server with the exact same account/password combination, but I had to re-enter the password before the connection string would work correctly.

---

____________________________________
The one-eyed in the land of the blind.

It took some time because I wanted to check on a clean install of 05.05.00
http://support.dotnetnuke.com/issue/V...

---

____________________________________
The one-eyed in the land of the blind.