New Post: Deleted Products & Google Crawler

Hi,

On my dev PC, I've just tried to re-create a high cpu usage, by doing everythign I can think on deleteing products and purging order, but nothing seems to create a peek in CPU usage???

Question :

• Are those products actual purged from the store or they linked to an order, in which case they still exist in the store and you can see them in the back office?
• What version of DNN are you running?
• Are they any errors in the DNN log, you say you can't see the error log?...you coudl try look directly at the DB "EventLog" table to see if you have any errors!
  

Next things to try:

• Try changing the app pool from the default app pool to one that only that website uses. (i.e. create a new app pool for the website). I never use the default app pool, but I'm sure many people do, so this is just to eliminate any possible corruption of the default app pool by another process.
  
• At the moment I don;t use .NET 4 framework for any of my NB_Store site (not moved to DNN7 yet)...if you not running DNN 7 are you running anythign else that needs .Net4.0..if not the try changing the new app poll to v2.0. (Try this after moving app pool)
  
• My other thought is have the DNN installation been corrupted in some way?.....maybe at a minimum try changing the page that display the products details to the client....I suppose the bigger option is to recreate the DNN install, but this is probably a deperate measure, only to do if we can;t identify what error is causing the issue.
  

I suppose the bottom line is we need some kind of error messge that points to a section of code in NB_Store or DNN, thing like this can be incredibly difficult to track down....sometimes it even quicker to start a fresh build...but lets eliminate the obvious before going that far.

Let me know how this goes, if you still have a problem I could login to you server and have a quick look, but nobody else has mentioned such problems, so although it's oviously and issue triggered by NB_Store, it's origin could be a DB corruption or any number of reasons....none of which I can think of !!!

Dave.