Replies: 4 comments 3 replies
-
This is kinda hard to diagnose without having that specific module and the starting situation which makes this issue not really actionable, for that reason, I'll move it to a discussion until something actionable can be establishes. When you install the module, in the DNN UI do you get any errors ? |
Beta Was this translation helpful? Give feedback.
-
Thank you, @valadas. Yes, it is hard to diagnose and just wish that there were some additional logging somewhere that could provide more detail. I've done installer build file comparisons between previous versions that did upgrade successfully and subsequent ones that haven't without any pointers. It is a weird situation that just popped up back in April in some of our builds. We were hoping that someone had experienced this before in Azure WebApps (e.g. permissions issues, timeouts) as a cause since we can't replicate it in our dev environment with the exact same DB and files. Perhaps it isn't ideal for the installer to completely fail without a response simply due to a file error and at least have a Host Alert with logging of any failures. |
Beta Was this translation helpful? Give feedback.
-
@valadas as far as errors in the UI, there aren't any. I'll be upgrading the custom module tonight and will keep Dev Tools open and check the Console and Network tabs to see if anything pops up. I'll also install an upgrade of a separate module to see if the same issue occurs. If there are any other logging/debugging methods you think may provide more visibility that would be welcomed. We have Log4Net set to Error, but will set it to Debug just in case it provides more info. Thank you again, and have a great evening! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Description of bug
Not sure if anyone has come across this before on an Azure WebApp, but when we install one of our custom modules the installation never completes with the success message or creates the Host Alert with the install details.
We provisioned an exact replica of the production server in our local environment and the installs complete as expected with the proper confirmation and host alert.
There are errors from Log4Net (provided below), and the module's Temp folder under Install isn't deleting (which is probably a result of the issue). This has continued to occur across a couple of subsequent release builds.
This poses an uncomfortable situation in that we're not able to get any confirmation that the SQL scripts have completed and that all the files have been copied successfully. The only way we can kind of guess it has been updated is by the version that appears in Extensions, reviewing some of our code updates or even manually running the SQL update scripts.
The installerlog files only includes references like these on both the Azure WebApp and our local server following an install. No further details are provided:
Here are some of the log entries we see, which seem to relate to the deletion of either temp data or files in the custom module's folder under DesktopModules:
This is deep in DNN's internals and being an Azure production environment we're not sure how to diagnose the issue any further.
We've verified that all the files (e.g. DLLs, license, ReleaseNotes) and SQL providers in the manifest are included in the install file, so we're not sure what the "The system cannot find the file specified" is referencing.
This is a list of the folders and files that remain in the temp folder under installs, which is leading me to believe that perhaps deleting the backup files may point to the source of the issue:
Thank you for any pointers!
Affected version
We don't believe it is related to the DNN version since we upgraded sometime around December 2022 and we've done a couple of installs of the same custom module afterwards.
Beta Was this translation helpful? Give feedback.
All reactions