Community

I tried to select one of the products (such as the Lunar Duo) and got this error:

---- 

Microsoft VBScript runtime error '800a001c'

Out of stack space: 'checksystemrestart'

/shop/shopinitapplication.asp, line 85

---

The url was: http://www.sixmoondesigns.com/shop/shopexd.asp?id=36

This seems to happen a lot. I am in the business, so I generally have a lot of tolerance for IT problems (I know it is hard keeping a website running) but this is ridiculous. It seems to happen quite often. Again, I don't mean to be critical and I hope I haven't hurt anyone's feelings, but whoever is responsible for the web site should look into solving this problem (it has happened quite a bit over the last six months, if not longer).

Ross,

Yes, we've been getting more of this problem lately and for the life of me I don't know why. No changes have been made in the website software in months. Unfortunately I'm unable to replicate the problem on my system which makes debugging impossible. I spent over 20 years writing software so it's equally frustrating on my end. Server software is about as difficult to debug as anything I've ever done.

I do plan on upgrading the website software in a few weeks after I get back from Trail Days. However, at this point I've no idea weather this will either improve or make things worse.  In the meantime bear with us as we struggle through this quagmire.

Thanks,

Ron

Ron,

I feel your pain. I write server software as well, so I know these types of bugs are hard to track down. Since it is a system level bug, it could easily be a bug with the .Net system. I write in Java now and although I've written some web server .Net code, I don't have much experience with it. Reproducing this sort of bug often requires an identical test environment and a good stress test system (I've used JMeter, but there are a lot of other good free tools out there). It is, as you suggested, a time consuming task even to reproduce the bug, let alone fix it.

Sometimes you can get lucky with Google. I found this that might be of help: http://support.microsoft.com/default.aspx/kb/174685 

It mentioned a couple of bugs that are with the .Net system, so updating (as you suggested) might solve the problem.

Good Luck,

Ross