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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Commercial Module version released killed DNN for 19 days!Commercial Module version released killed DNN for 19 days!
Previous
 
Next
New Post
7/9/2008 4:56 PM
 

I'm kind of with Chris here as well, and it's not as Devil's Advocate.  I tend to thoroughly test new modules but not be as careful about upgrades, but I can restore the database after any upgrade because the first step is a backup.  I also test modules on a replica of the server, basically restored from a backup of the live server, though like I said, I'm a bit lax on a simple upgrade.  I do usually watch forum posts for a bit before upgrading, depending on severity of the upgrade and what developer, and let others get bit before me.

On the other hand, I would not have been hiring extra people to track down the error, I would have relied on the original developer.  I may have been willing to pay for the work, or guarantee payment if it's not a confirmed bug, but getting a third party in can cause all kinds of finger pointing.

All that said, what DNN needs is a good "Undo" button for upgrades and installations of modules.  Maybe for version 6.0, code named Pleistocene...  :)

Jeff

 
New Post
7/9/2008 5:44 PM
 

To add a bit of context (David’s original please-help-me thread was here), the error in question was: “’aspnet_isapi.dll’ reported itself as unhealthy for the following reason: ‘Deadlock detected.’”. 

David's problems were intermittent, not immediately associated with the module installation, and appeared (to myself and many others who assisted him in the thread) to be a system-, hardware-, or ASP.NET-related problem.  This was nowhere near a cut-and-dried "I get an exception when I try and instantiate a module" problem.  Determining what was causing the problem was most of the battle, and without this information, there would be no way of knowing which developer to contact.

Just something to keep in mind.

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
7/10/2008 2:23 PM
 

It was the OnyakT. NukeAl*rt module that had killed my site... a module I'd run with few problems for nearly a year... so an update - and with the way the error appeared, it wasn't even clear it was something in DNN, let alone which module it might have been.

I have been happy with the modules they provide, and from what I've seen and heard I felt they had a good reputation also.  I am not sure what it is with this module, and how the problem happened but I am not running the latest now as I am a bit exhausted from the problem previously - apart from that everything is pretty much back to normal and no other changes (everything else is the latest etc - except DNN since it has moved on 2 versions for security.

I do take backups regularly, but for some reason there was a mess made between the back-ups, trying to run DNN with minimal things, clearing up anything and everything else on the server, and wiping and starting from scratch (then not knowing which DNN backup to use anyway).

It just created a mess out of a few weeks - so even though I am happy otherwise with the modules I will not be renewing my subscription and will look at other options after receiving a subscription renewal notice... it's just hard to want to send more money that way after what happened.

Brandon was great too... offering suggestions and to take a look outside the forums. Thanks for that Brandon!

 

 
New Post
7/10/2008 2:25 PM
 

I just want to add - even backups alone might not make it easy if the problem appears some time after a module is uploaded or something is changed.

To not receive any hints to what is causing the problem... I can only think keeping not only backups but some sort of tracking for what's been done - so you have an idea how far back to step, and what may have caused it when it is fixed.

 
New Post
7/10/2008 3:45 PM
 

Well, my "pretty good idea" of the developer was correct - based solely on David's description of the support he received.

Don't feel too bad David I made that $100 mistake when I first started with DNN too.

'nuff said

Greg

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Commercial Module version released killed DNN for 19 days!Commercial Module version released killed DNN for 19 days!


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