The UpdateDocument stored procedure that you posted is actually that from the 03.01.01 version of the documents module. It was modified in the 04.01.00.SqlDataProvider script to include @ModuleID int as its first parameter and to use this parameter in the WHERE clause. It appears that the 04.01.00.SqlDataProvider script (and perhaps one or both of the intervening 03.01.02.SqlDataProvider and 04.00.0.SqlDataProvider scripts) did not execute during the install or upgrade of this module.

The fix would be to rerun (in order of version) each of the scripts which did not execute by executing them in the Host --> SQL module with the "run as script" option checked. A careful examination of the database tables and stored procedures related to the documents module compared to the changes that should have been made for each version's SqlDataProvider script will be necessary to determine which scripts need to be re-run.

Another option if your documents modules contain only a few documents would be to completely uninstall the module, reinstall it, and then re-add the content (which I think but can't guarantee without testing/looking at the module code) should still be available in your site's file system.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

There should be five SQL scripts named xx.xx.xx.SqlDataProvider in the DesktopModules/Documents folder. We know that the 04.01.00.SqlDataProvider script did not run successfully but do not know without further investigation if the 03.01.02.SqlDataProvider and 04.00.00.SqlDataProvider scripts ran.

The 03.01.02.SqlDataProvider script does not need to run as its changes will be replaced in the 04.01.00.SqlDataProvider script anyway.

Look at the DocumentSettings table in the database. If it already contains columns named DefaultFolder, CategoriesListName and AllowUserSort then the 04.00.00.SqlDataProvider script apparently ran. If not, the 04.00.00.SqlDataProvider script will need to be re-run.

Then re-run the 04.01.00.SqlDataProvider script.

When running these scripts in the Host-->SQL page, be sure to check the "Run As Script" option.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner