DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Upgrade from 9.6 to 9.10 to 9.11 >> DDay.iCal DLL Errors

 6 Replies
 1 Subscribed to this topic
 33 Subscribed to this forum
Sort:
Author
Messages
New Around Here
Posts: 1
New Around Here

Hello everyone,

We have 2 site that we are trying to upgrade. The first site successfully upgraded from 9.6 to 9.10.  Then we tried to upgrade from 9.10 - 9.11 and got stuck on the "Security" page on the upgrade wizard. The second site started at 9.10 and when trying to upgrade to 9.11 it resulted in the same stuck on "Security" page problem.

In looking at the logs for both sites, the same error is thrown in their respective log files:

2024-07-12 08:14:06,785 [][Thread:1][ERROR] DotNetNuke.Web.Extensions.StartupExtensions - Unable to configure services for DDay.iCal, Version=1.0.2.575, Culture=neutral, PublicKeyToken=null, see exception for details 
- LoaderException: Could not load file or assembly 'antlr.runtime, Version=2.7.6.2, Culture=neutral, PublicKeyToken=1790ba318ebc5d56' or one of its dependencies. The system cannot find the file specified.

We noticed that the 9.10 Upgrade ZIP did not have the DDay DLL but the 9.11 Upgrade ZIP does have this DDay DLL.

Can anyone please provide any insights as to why it is there, and what problem the 9.11 upgrade is trying to solve by including this library?  Also should there be an "antlr.DLL" file in this 9.11 Upgrade ZIP?  If not, should we try to find it somewhere and include it?  Is there a different path towards moving through this issue?

Thank you!


 

 

 

Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!

First of all, there is a more tested upgrade path documented here https://docs.dnncommunity...rade-path/index.html

So you should upgrade to 9.13.3 directly instead of 9.11.0 as more people have tested this scenario.

Secondly, I am not aware of either DDay.iCal or antlr being DNN dependencies, when you say you found it in the upgrade package, where did you download that package from and in which path did you find that file ?

New Around Here
Posts: 1
New Around Here
Hi Daniel, thanks for the reply. Apologies, as it turns out that we were incorrect regarding the DDay.iCal DLL. It was part of our DNN site, and not part of the upgrade package. As per your recommendation we are going to fast track the upgrade to 9.13.3 and see how that turns out.
Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
Ok, so before you go to far though, I would start with 3 things:

1: Check if there are any unused extensions you could remove before upgrading
2: For the extensions that are left (and 3rd party) I would check if they have updates available that are still compatible with you starting DNN version
3: I would try to figure out which module is using that dll. If it was installed properly, you will have that dll listed in the database table called "Assemblies". When you find it, take note of the PackageID for it and then look into the "Packages" table for that ID and in the Name you should see what extension that is. From there you can take a look if that has updates available or if that extension was maintained recently to support newer DNN versions.
Advanced Member
Posts: 207
Advanced Member
Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
New Poster
New Poster
Congrats on posting!
The DDay.iCal looks to be very old and obsolete now, it looks like they have moved to iCal.Net. It's probably a third party module. If the direct upgrade does not work you can try uninstalling the module that uses DDay.iCal, if the module has been done correctly the assembly should also be removed. (Be careful of dependencies) Then try the upgrade. Of course this method will probably remove data from your database and maybe the filesystem so you may need to deal with exporting and importing data from your database. Sometime simply saving data in a temporary table in the database is easy and simple, sometime not.

This approach should be a last resort. But sometimes it's an option that can work.

Good luck.
Senior Member
Posts: 1322
Senior Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
Lifesaver
Lifesaver
You're Life Saver!
New Poster
New Poster
Congrats on posting!
3 Engaged Reader
Engaged Reader
You are an engaged reader!

I have seen this issue too, IIRC I just removed the DDay.iCal dll and my upgrade worked.
I concluded it was a left-over from an old third party extension I previously uninstalled

Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
Now that Timo mentions it, this rings a bell, an old module which left that behind. Of course, follow best practices and cleanup using the UI first, but if it stays and is not referenced, probably deleting it is the correct way.

These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

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

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. 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.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved