Thanks to user "njuaire" we finally figured out the cause of several failed installs - the SqlDataProvider scripts for versions 04.00.00, 04.01.00, and 04.02.00 were not fully compatible with MS SQL Server 2000. These have been now modified and tested against MS SQL Server 2000 on his website. I have also found that even if one's DNN site is currently running on MS SQL Server 2005 but has the database's Compatibility Mode set to 80 (that is MS SQL Server 2000) rather than 90, while there would have been fewer errors raised, there would have been syntax errors in 6 stored procedures due to ordering of the (nolock) hint when an alias was also being applied to a table name in the FROM clause. Note that if you had upgraded your MS SQL Server installation from 2000 to 2005 or had transfered a database from 2000 to 2005, the Compatability Mode will be set to 80 not 90, effectively causing the module install to fail even though you may have reported that you were running against MS SQL Server 2005.

A new package for WESNet_EPrayer_04.02.01_Install.zip has been created and is now available in the downloads section. I have not incremented the version number as none of the prior versions would have had successful installs against MS SQL Server 2000. If you are running your site against MS SQL Server 2005 with Compatibility Mode set to 90 and have had a successful install of this version, do not upgrade the module.