Announcement

Collapse
No announcement yet.

Error reading from ../html/acatalog/OrderLock.num ()

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Error reading from ../html/acatalog/OrderLock.num ()

    Hi all

    A strange problem occurred today in our V5 business. Suddenly we can't take orders as all customers get the error message "Error reading from ../html/acatalog/OrderLock.num () " Checking OrderLock.num I note that it's empty and so is Backup.num. Also, just before this happened we got an order confirmation without customer details. The "ship to" field is empty. Here's what it looked like:

    We have received and are processing the following order:

    ******************************************************
    Order Number: 19992410001058
    Order Date: 5/21/2003 02:45

    Ship To:


    Shopping Cart (Prices in US Dollars)
    DESCRIPTION QUANTITY PRICE COST
    ----------------------------------------------------------------------
    Bonnie B 1 $20.99 $20.99
    alumtag 1

    Heartbreak Hotel 1 $20.99 $20.99
    alumtag 1

    HVH Special Blend Fertilizer 1 $9.99 $9.99
    3 lb 1
    ======================================================================
    Subtotal: $51.97
    Handling: $4.95
    CA Tax: $3.90
    Total: $60.82

    Note that the confirmation email was sent to us, the order was given an order number without the first two initials but no order file was ever generated and when trying to download we get the message "no orders". HELP!!!

    yvonne
    Hidden Valley Hibiscus

    #2
    Check out the knowledge base here as this tells you exactly what you need to do.

    Comment


      #3
      Error OrderLock.num

      Thanks Chris

      In this instance the Order.num file was missing (renamed) and both the OrderLock.num and Backup.num files blank so no recovery possible. However, after deleting all perl scripts and making a complete site refresh we got the store working again although the order numbering started over from 0000001. Note that a complete site refresh was NOT enough to fix this script error. The old scripts had to first be manually deleted and uploaded afresh before the changes took effect.

      Btw, I did a search trying to find this problem in the Actinic knowledge data base before posting and struck out. Any idea why?

      yvonne
      Hidden Valley Hibiscus

      Comment

      Working...
      X