I upgraded a DNN installation to the 4.0.0 Links module a few weeks back, then today upgraded the DNN core to 4.8.4 from 4.8.2.  The upgrade went smoothly except that one instance of the Links module errored with a "The stored procedure 'dbo.GetLinks' doesn't exist" error.  Reinstalling Links 4.0.0 Install package corrected this.  What's strange is that other instances of the Links module were fine.  The only possibility I can attribute this to is the instance that errored was added after I had upgraded to the 4.0.0 version of the Links module, while the others already existed when I upgraded the module.

No problems, just figured someone might care.  Or run into it and need a fix.

Jeff

stored procedures were renamed for the links module, so the only possibility would be that you upgraded the module somehow, but the module dll was not written correctly to the bin folder. That could be caused by a lot of things, but you would always get an install error for that module.

To Kaycee: just install the links module again, and see if the error goes away

DNN Blog | Twitter: @erikvb | LinkedIn:

we were running Links module 3.something and during an upgrade up to DNN 4.9.1 all other modules and upgrades went well but now the links module does not work... a user clicking on teh link will receive an error from the linkclick page. downloading and installing Links module 4.0.1 did not fix the issue for us.