Microsoft VBScript runtime error '800a0006'

[grace01]

My asp webpage was working well in the past 5 years. Recently it shows the message:

Microsoft VBScript runtime error '800a0006'
Overflow: 'addOrder'

The source code is as follow:
[code=asp]
'insert data into database

dim objCart
dim objOrder

set objCart = createobject("E Store.ShopCart" )
set objOrder = createobject("E Store.Order")

ret = objOrder.addOrd er(cart_id,bnam e,request("firs tname"), _
bemail,baddr,bc ity,bstate,bcou ntry, _
bzip,request("c ontactoffice"), bphone, _
request("contac tmobile"),reque st("pager"), _
request("fax"), saddr,scity,sst ate,scountry, _
szip,sphone,del Time,delivery,c type,cname,cno, _
cexpire,date(), sname,request(" delfirstname"))
[/code]

Anyone can help me? Many thanks.

Grace

[jhardman]

I hoped someone else would answer you, I'm not familiar with the estore object and I didn't want to steer you completely wrong. Is this something you bought and installed on your server? It sounds like it might no longer be supported, either because the files involved were corrupted, or because they were compatible with an older version of your server. Does that make sense?

Jared

[PWPWPW]

I've got the same problem.....it seems to be all over the place.....any ideas?? New OS patch?? Due to an upgrage?? I'm screwed!

[markrawlingson]

I don't know anything about e-store either. Frankly though, i doubt it's the object itself unless you recently reinstalled it or download a new version before this started happening. It could be corrupt, but you could rule that out by downloading the latest version, or just re-installing the current version if you still have the installer.

In any case, an overflow is usually generated when something "overflows" - for instance if you were to wrap CInt() around 875765764654656 457656745 - it would give an overflow error because the number is way out of range for the CInt() function. Or if you tried to insert 3000 ascii characters into an nvarchar(63) data column in your database, it would throw a stack overflow, etc.

It's best to take it back to basics, have you tried just doing a simple one column update? I would create a new table with 2 columns, an auto-increment, and an nvarchar(15). Then a simple ASP page to test insertion into this table to see if the error occurrs under controlled circumstances.

[CODE=asp]
ret = objOrder.addOrd er("Does it work?")
[/CODE]

Then, if that doesn't throw the error, I would stress test it by throwing it inside of a loop, and logging the amount of times it throws an error.

[CODE=asp]
On Error Resume Next
For i=1 To 100
ret = objOrder.addOrd er("Does it work?")
If err.Number <> 0 Then
'create a text file if this is the first occurrance.
'open the text file if this is not the first occurrance.
'keep a tally on the total amount of failures
Err.Clear
End If
Next
[/CODE]

This should at least identify whether it is the object itself throwing the error or not.

If all else fails, you could also contact the support team and ask them what is going on.

This seems to be the company that produces it... http://www.oneworldstorefront.com/default.asp

Hope this gets you to your answer!

Sincerely,
Mark