David Lee wrote:
Hi J,
Interesting problem. I currently have a website I need to upgrade, but I'm holding off until we get somekind of understanding of this issue.
Do you know if anything is logged on Gemini about it? I can't find anything, but I suppose we need to identify what's happening before it can be logged.
Hi, we did not see anything. We had been testing our DNN 5.5.0 and DNN 5.5.0 release already for a couple of weeks. We tested all main features and also always move a production site to an acceptance environment and perform a test on all new issues. We have no resources to do a unit/ system test with many requests.
We finally reverted back to DNN 5.4.2 since we lost already 3 to 4 days of revenue at
www.bzoox.nl . We could continue to handle backorders to customers with our Microsoft Dynamics AX ERP system. But the number of orders dropped significantly and customers started calling us (which is costly also). We have now lost customer and sales order information which we will not restore in the restored database. This would cost more than it would bring. We will sent out an email to the customers that their data has been lost somehow. Also we found a PR drop by Google since we had no stable or reachable website. That is a very costly penalty since we got most of our orders from SEO.
We have also decided that we want to remove the third party rewrite tool of Ifinity since the settings are changed in the new version 2.0.x and not taken over from the old version. We had to spend a lot of time to get things back working again and double check: can this be related to the rewrite? However, some things are not present in the new version anymore so we cannot serve all our foreign customers anymore. We actually only require that DNN does rewrite a space to a dash (-) instead of removing the space. Such rewrite would do in most cases for our ecommerce software and seo purposes. Also the aspx should be taken off. I will post this request in another thread or we will build our own rewrite for that since we can debug and keep track of product changes more likely.
David Lee wrote:
@J
Earlier you stated your using .net4.0, I'm currently not using this, where your initial tests using .Net4.0? And have you thought about changing your web.config back to the .Net 2.0?....Not sure about this effects of doing this??...I;ve done some very basic tests on .Net4.0 and it seems to be OK, but going back to .Net2.0/3.5 might just eliminate one more thing, in order to trace the actual issue!
Also you mentioned authenticated users, could you expand on this, does it mean you only have a problem when the user is logged in?, or is the site slow for all users?
Regards,
Dave.
We did not try .net 2.0. We changed our ecommerce software www.bbayt.com to version .net 4.0 also since the security of custom code in report viewer reports has been changed. Also we might benefit from the new caching implementation. But I guess we will not further investigate this. We changed our code already to DNN 5.5.x so I guess we need to spend a lot of time in changing back stuff and reverting code changes. A pain and three times work: once to make it, second to undo it, and then to redo the work again once it is more likely we can step to DNN 5.5.x. What still bothers me is the 'critical update' notification which clearly indicates we need to upgrade. But clearly that was a dead end. .net 4.0 worked fine on all environments: development and acceptance prior to go to production.
I still cannot login from one IE browser. I can add stuff to my shopping cart. But still unable to stay authenticated. I cleared all browser data, but still no go on this pc.
We saw many spikes in network and disk utilization although cpu was low. We found a patch for a setting issue in ifinity which we applied. But at that point we already had the feeling we wasted too much time here and we needed to move into an acceptable situation. We removed ifinity as url rewrite, but the problems persisted. It looked like the webserver was already at a stage it needed a restart. Physical memory was about 93-94% used. But that is now also the case now and it works. It is a 64 bit 2008R2 2 GB server with SQL advanced services 64 bit. We do not have the money to split database and webapplication as we know it should. Actually it makes MS stuff quite expensive and SQL express + web edition of 2008 where ment for a single source solution...but it still likes GBs of memory.
Compression on/off did not seem to help. It first did, but after authentication performance was lost again. We also turned off the item search on the site since we found a lot of timeouts there. To be honest we do not fully understand what is the best scheme for output caching on page, host and module level.
J.