Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...Error Adding ModulesError Adding Modules
Previous
 
Next
New Post
12/2/2010 3:33 PM
 
Bill,
Thanks again for your advice/explanations. I logged on as "host" and pulled up "Dashboard" and saw the path under ASP.NET Identity, which was "NT AUTHORITY\NETWORK SERVICE".

Would the next step be go back to the .Net/SQL/IIS tech who installed DotNetNuke 5.3.1 and have him look into folder/permission settings for "NETWORK SERVICE" and then check boxes or click "yes" to whatever access settings need to be configured within---or for---that directory? Or does the required task mean granting permissions to a series of directories/folders within my website?

My last request for hand-holding is how to recognize "database objects" created by the SQLDataProvider scripts from previous install attempts: could I be lazy and just try to install these modules after permission-granting in the "NETWORK SERVICE" directory has been performed? Or is it wiser to hunt down these "database objects" and delete them before attempting anything?
Thanks again!

Regards, Glenn
 
New Post
12/2/2010 4:21 PM
 
you need to grant full file system permission to Network Service for your DNN install directory and check the option to adjust all files and folders contained as well.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/2/2010 6:45 PM
 
As Sebastian indicated you or your IIS tech will need to grant the Network Service account full filesystem permission on the install folder and check the option that will propagate the change in permissions to all child folders and files.

Regarding your question about checking the database for module related objects (especially tables) that might have been created during the failed module installs. Knowing what objects are related to what failed module install will be the hard part unless you or your IT tech are very familiar with a DNN database. Unfortunately, many modules, particularly older versions, do not prefix the object name with that of the module name or module folder. In the error you posted it appeared that the failure occurred before database object creation scripts ran. Although I'd prefer to check the database first, I think your safe to try installing one module again (after the permissions issue is fixed) and see what happens.

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
 
New Post
12/3/2010 4:31 PM
 
Thanks for the advice again. Permissions were set and I tried installing the Documents Module and there WAS progress I should say: this time I got "Module Installation Failed" and the code in Event Viewer revealed this...

Install Package:: DNN_Documents
Info:: Reading files
Info:: File DotNetNuke.Modules.Documents.dll read successfully
Info:: File Resources.zip read successfully
Info:: File Uninstall.SqlDataProvider read successfully
Info:: File 03.01.00.SqlDataProvider read successfully
Info:: File 03.01.01.SqlDataProvider read successfully
Info:: File 03.01.02.SqlDataProvider read successfully
Info:: File 04.00.00.SqlDataProvider read successfully
Info:: File 04.01.00.SqlDataProvider read successfully
Info:: File 04.01.00.txt read successfully
Info:: File DNN_Documents.dnn read successfully
Info:: Reading files done.
Info:: Reading Installation Manifest file
Info:: Creating Manifest
Info:: Added File to manifest - 03.01.00.SqlDataProvider
Info:: Added File to manifest - 03.01.01.SqlDataProvider
Info:: Added File to manifest - 03.01.02.SqlDataProvider
Info:: Added File to manifest - 04.00.00.SqlDataProvider
Info:: Added File to manifest - 04.01.00.SqlDataProvider
Info:: Added File to manifest - Uninstall.SqlDataProvider
Info:: Added File to manifest - DotNetNuke.Modules.Documents.dll
Info:: Added File to manifest - resources.zip
Info:: Created Manifest
Info:: Reading Package Manifest - Module - DNN_Documents
Info:: Reading Component Manifest - Script
Info:: Found valid path () for 03.01.00.SqlDataProvider.
Info:: Found valid path () for 03.01.01.SqlDataProvider.
Info:: Found valid path () for 03.01.02.SqlDataProvider.
Info:: Found valid path () for 04.00.00.SqlDataProvider.
Info:: Found valid path () for 04.01.00.SqlDataProvider.
Info:: Found valid path () for Uninstall.SqlDataProvider.
Info:: Reading Component Manifest - Cleanup
Info:: Reading Component Manifest - Module
Info:: Module Manifest read successfully
Info:: Reading Component Manifest - Assembly
Info:: Found valid path (bin) for DotNetNuke.Modules.Documents.dll.
Info:: Reading Component Manifest - ResourceFile
Info:: Found valid path () for resources.zip.
Info:: Found valid path () for resources.zip.
Info:: Manifest file finished successfully
Info:: Starting Installation
Info:: Starting Installation - DNN_Documents
Info:: Starting Installation - Script
Info:: Begin Sql execution
Info:: Folder Created - E:\inetpub\CGWEB2\DCMS-34\DesktopModules\Documents\
Info:: Created - 03.01.00.SqlDataProvider
Info:: Executing 03.01.00.SqlDataProvider
Info:: Start Sql execution: 03.01.00.SqlDataProvider file
Info:: End Sql execution: 03.01.00.SqlDataProvider file
Info:: Created - 03.01.01.SqlDataProvider
Info:: Executing 03.01.01.SqlDataProvider
Info:: Start Sql execution: 03.01.01.SqlDataProvider file
Info:: End Sql execution: 03.01.01.SqlDataProvider file
Info:: Created - 03.01.02.SqlDataProvider
Info:: Executing 03.01.02.SqlDataProvider
Info:: Start Sql execution: 03.01.02.SqlDataProvider file
Info:: End Sql execution: 03.01.02.SqlDataProvider file
Info:: Created - 04.00.00.SqlDataProvider
Info:: Executing 04.00.00.SqlDataProvider
Info:: Start Sql execution: 04.00.00.SqlDataProvider file
Info:: End Sql execution: 04.00.00.SqlDataProvider file
Info:: Created - 04.01.00.SqlDataProvider
Info:: Executing 04.01.00.SqlDataProvider
Info:: Start Sql execution: 04.01.00.SqlDataProvider file
Info:: End Sql execution: 04.01.00.SqlDataProvider file
Info:: Created - Uninstall.SqlDataProvider
Info:: Finished Sql execution
Info:: Component installed successfully - Script
Info:: Starting Installation - Cleanup
Info:: Processing Cleanup File - 4.1.0
Info:: Completed Processing of Cleanup File - 4.1.0
Info:: Component installed successfully - Cleanup
Info:: Starting Installation - Module
Info:: Module registered successfully - DNN_Documents
Info:: Component installed successfully - Module
Info:: Starting Installation - Assembly
Info:: Assembly registered - bin\DotNetNuke.Modules.Documents.dll
Info:: Exception - Access to the path 'E:\inetpub\CGWEB2\DCMS-34\bin\DotNetNuke.Modules.Documents.dll' is denied.
Info:: Installation Failed - Assembly
Info:: Rolling back component install - Script
Info:: Component rolled back successfully - Script
Info:: Rolling back component install - Cleanup
Info:: Component rolled back successfully - Cleanup
Info:: Rolling back component install - Module
Info:: Module un-registered successfully - DNN_Documents
Info:: Component rolled back successfully - Module
Info:: Installation Failed - DNN_Documents
Info:: Deleted temporary install folder
Info:: Installation Failed
Server Name: HQSMS-WEB-002


Does this code reveal that ".dll" files pertaining to previously attempted module installations should be manually deleted from Modules directory---and other extension files associated to work WITH ".dll" files? Or should I search for any file with the name of a previously attempted Module I tried to install and remove it (myself or the IIS tech)?
I'm all ears: thanks again!
R, Glenn
 
New Post
12/3/2010 5:00 PM
 
there seems to be permission missing to replace .dll files in your /bin folder, please check permissions again.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...Error Adding ModulesError Adding Modules


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out