I was looking at the issue travking and have seen a couple of related incidents and efforts to clean them up. (posted at end)

Well, if you think the upgrade to 4.0.2 will clean the old procs...then I'll try the upgrade.  ....And 99% seems pretty good to me! 

From EVT-3895 it follows that there may be other obsolete procs in there, but let's see about these first and see what happens.  Will let you know.

Thanks.

Hey Roger,

Ok, the upgrade to Events 4.0.2 does clean up the two obsolete procs. 

I ran the publish process again and as I expected, I ran into one of the procs referenced in EVT 3895 (Forum_ForumUserViewsUpdate).  I dropped it manually and that solved the obsolete proc problem.

Now I have to deal with another problem.  The publishing wizard tries to assign object permissions to the \"localmachine"\ASPNET user and that user doesn't exist in the remote host.  When I installed DNN initially, I used Windows Authetication for the database (I guess a bad move?).  I probably also read somewhere I needed to add some DB object permissions to the ASPNET user, so I did that.

Now I have to find out if I can change the DB security back to SQL Server Autentication or how to make the database go through the publishing process without trouble.  It's the way I can move a Local Development installation to the remote hosted installation. (I know this is not the forum for it, but any hints will be appreciated.)

Thanks for the help.