Hi David,

As I'm sure you've noticed, with such an esotaric error, you're likely to get a lot more suggestions than solutions.  So, here are some additional suggestions that I would do if I were in your shoes:

1) Clear out your entire Temporary ASP.NET Files directory

2) Start removing non-core assemblies from your application like crazy.  See if you can find a set of assemblies that allow the application to start successfully (even if you wind up with a DNN exception, that's progress).

Also, I viewed this thread on a whim to see what your solution was since it had been marked as solved.  You might consider starting a new thread; I'm sure others that might be able to help might overlook it after seeing the checkmark.

Hope this helps!

Brandon

Well... somehow I've managed to not give up but I'm out of options I can think of.

The little budget I've had has been depleted by an MCSE that was unable to fix the problem... though he said he had done but it returned straight after.

On his advice, I've wiped the server and started from scratch - which worked for around 14 hours before the site just stopped again.  I am starting to wonder if it's something in my DNN that can possibly be corrupting .NET 2.  Would that even be possible?

I can only think of using a 3rd party hosting to try and get it online... but with next to no budget (business been crippled over 2 weeks this has happened) and I would want them to understand the situation and be able to run it without affecting other people's sites - and do some testing/tracking to see what actually might bring it down.

Does anyone have any suggestions or am I best to just give up after a year of work and look at some other system?

Hi Brandon

Thank you for the extra insight - and it does bring some relief seeing there may be other reasons for this.

I'm unable to run those tests though, as the only way I can access the server is via RDP and they both require a reboot which won't allow remote access for the tests when they run.

Thanks

David