Today was going to be a nice quiet day all by myself in the office.  I was here by 5:30 a.m. and the plan was to spend all day making sure everything was ready for the big release of Active Social.  A couple hours later, I take a few minutes to check out some of the popular topics on our forums.  A few of the more popular topics have been about upgrading to DotNetNuke 5.  One of the topics included a reply that had a really old stored procedure of ours listed in the error log.  Obviously I wanted to keep an eye on that topic.  Mainly because a few ours earlier I wrote a fairly dismissive reply stating we didn't cause the problem.  Which at that point we didn't, in my opinion.  I knew that this same issue came up back in February with another customer.  At that time, our stored procedure was also listed with a couple other stored procedures that absolutely did not belong to us.  Looking at the names of the other stored procedures it looked like our stored procedure was modified by some custom development work he had done.  The customer accepted that answer, said he didn't use it any more and deleted the items. Problem solved!

Now we go back to the topic where I so arrogantly said "For the record, that stored procedure was not created by us".  In my defense, I did post at 3:40 a.m. so I wasn't entirely in the right frame of mind.  I know, still not acceptable and I'm sure wasn't appreciated.  A moderated email message comes in from a customer basically stating that the only module he has ever used is Active Forums.  Knowing this to be true his message gets approved and I go through the topic again.  I begin to realize that in less 24 hours, one topic has 10 customers reporting upgrade issues, 5 of whom have the same NTForums error.  Obviously there is a problem somewhere.  At that point I asked for any customer with the error to send me their log files.

While I was waiting, I checked one of our test machines and found the same error message.  The error message tells me exactly where in the upgrade process the problem occurred.  Other customer logs provided additional confirmation.  I won't bore you with the remainder of the debugging process. 

No other way to put it, but I screwed up.  On the technical side, this error is caused when a stored procedure is created without a databaseOwner qualifier specified.  The problem was created 3 years ago, corrected immediately but not cleaned up properly.  On the professional side, I didn't troubleshoot the problem properly back in February.  Had I handled the situation differently, we could have been more proactive and reported the problem to DotNetNuke early in the DNN 5 release process.  Finally, I'm simply embarrassed by the way I responded to my customers that initially reported this problem.  I was arrogant and I apologize.

I have submitted this issue to DotNetNuke because there other factors beyond our stored procedure.  For more information regarding this issue visit http://support.dotnetnuke.com/issue...p;PROJID=2
Topic on DotNetNuke Forums with steps to fix and my response
http://www.dotnetnuke.com/tabid/795...fault.aspx


Anyone that is having problems upgrading to DotNetNuke 5 because of our stored procedure is welcome to post in our Active Forums support forum and we gladly help.

Thanks,
Will