Anthony, you wrote in your blog:

"Note: The new version works with DNN 3.3.x / 4.3.x  Versions prior to DNN 3.3 are not supported"

Does it work in 4.4.0?
Thanks ArntK

---

Arnt O. Kvannefoss Software Consult AS Microsoft Certified Partner www.SwcWeb.net www.pamelding.net www.softwareconsult.no

Hi I get the following error when trying to install on DNN 4.4.0. I get the same problem with the new Reports module too - any ideas? Cheers, John

StartJob Starting Installation
StartJob Reading files
Info Loading Documents_03.01.02_ReleaseNotes.txt
Info File Documents_03.01.02_ReleaseNotes.txt read successfully
Info Loading Documents_03.01.03_ReleaseNotes.txt
Info File Documents_03.01.03_ReleaseNotes.txt read successfully
Info Loading Documents_03.01.04_ReleaseNotes.txt
Info File Documents_03.01.04_ReleaseNotes.txt read successfully
Info Loading Documents_03.01.05_ReleaseNotes.txt
Info File Documents_03.01.05_ReleaseNotes.txt read successfully
Info Loading Documents_03.01.06_ReleaseNotes.txt
Info File Documents_03.01.06_ReleaseNotes.txt read successfully
Info Loading Documents_03.01.06_TestCases.txt
Info File Documents_03.01.06_TestCases.txt read successfully
Info Loading Document.ascx
Info File Document.ascx read successfully
Info Loading EditDocs.ascx
Info File EditDocs.ascx read successfully
Info Loading EditDocumentsSettings.ascx
Info File EditDocumentsSettings.ascx read successfully
Info Loading module.css
Info File module.css read successfully
Info Loading DNN_Documents.dnn
Info File DNN_Documents.dnn read successfully
Info Loading DotNetNuke.Modules.Documents.dll
Info File DotNetNuke.Modules.Documents.dll read successfully
Info Loading 03.01.00.SqlDataProvider
Info File 03.01.00.SqlDataProvider read successfully
Info Loading 03.01.01.SqlDataProvider
Info File 03.01.01.SqlDataProvider read successfully
Info Loading 03.01.02.SqlDataProvider
Info File 03.01.02.SqlDataProvider read successfully
Info Loading Uninstall.SqlDataProvider
Info File Uninstall.SqlDataProvider read successfully
Info Loading DotNetNuke.Modules.Documents.SqlDataProvider.dll
Info File DotNetNuke.Modules.Documents.SqlDataProvider.dll read successfully
Info Loading Document.ascx.resx
Info File Document.ascx.resx read successfully
Info Loading EditDocs.ascx.resx
Info File EditDocs.ascx.resx read successfully
Info Loading EditDocumentsSettings.ascx.resx
Info File EditDocumentsSettings.ascx.resx read successfully
Info Loading DNN_Documents_Source.zip
Info File DNN_Documents_Source.zip read successfully
EndJob Reading files done.
 
StartJob Reading DNN file
Info DNN file is in valid 3.0 format.
Info xml loaded.
Info Loading files info
Info Found valid path (App_LocalResources) for Document.ascx.resx.
Info Found valid path (App_LocalResources) for EditDocs.ascx.resx.
Info Found valid path (App_LocalResources) for EditDocumentsSettings.ascx.resx.
Info Loading Modules info
Info Loading Control info for 'Documents' module
EndJob Dnn load finished successfully
 
StartJob Begin Sql execution
EndJob Finished Sql execution
 
StartJob Creating files
StartJob Expanding Resource file
EndJob Resource Files created
 
Failure ExceptionSystem.UnauthorizedAccessException: Access to the path 'C:\DotNetNuke\bin\DotNetNuke.Modules.Documents.dll' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.SetAttributes(String path, FileAttributes fileAttributes) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.CreateFile(String FullFileName, Byte[] Buffer) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.CreateBinFile(PaFile File) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.CreateFiles(PaFolder Folder) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.Install(PaFolderCollection folders) at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install()

That's definitely an access issue and not related to the Documents Module, per se'.  Although if this does not occur on other module installations, it could be affecting only that particular file.  I have heard of stranger things happening... but the suggestion to manually delete it (if it doesn't seem to be affecting anything else), would definitely be the most expedient solution.

---

Scott Willhite, Co-Founder DNN