Hi,

There are possibilities for data reduction since there is some data duplication introduced in order to provide simple easy of access to event data and improve site performance. I'm not sure we will want to limit the functionality and flexibility though, but we will bear it in mind.

I think that cutting back some of your timelines will reduce the data requirement substantially. I can see you have Events such as 'Sunday Service' and 'Tai Chi' going out to 2099. Cutting these back to 2019 would reduce about 90% of the data, and bear in mind after the upgrade you could then extend these again, though this should be done via the interface to ensure events get created correctly.

Cheers
Roger

After further research I discovered that the installation itself is not timing out, but the tasks that spin up after the installation may be timing out?  I ran sp_spaceused during that long-running task and watched the database size creep up from 82 Mb to 152 Mb!

The installation generated 1 "Host Alert" for the actual installation with no errors, but then following that were 17 "Module Update" events that all ran for 10 minutes.  They all look succesful. The first one reads as follows:

Module Upgraded: DotNetNuke.Modules.Events.EventController, DotNetNuke.Modules.Events
Version: 03.01.00
Results: Events Module Updated: 03.01.00
Server Name: KEWLGEEK

And the last one reads as follows:

Module Upgraded: DotNetNuke.Modules.Events.EventController, DotNetNuke.Modules.Events
Version: 05.00.01
Results: Events Module Updated: 05.00.01
Server Name: KEWLGEEK

At then end of the 10 minutes I was able to reach the calendar page and it had the same "Argument 'Length' must be greater or equal to zero." and cross-site scripting errors.