I have a client with a 5-user Business Plus v9.05 installation who are having a problem whereby downloaded orders with credit card details (as opposed to those paid online) cannot be opened on all machines.
When attempting to open an order the message "The Credit Card Details Cannot Be Decrypted" appears twice, after which the order will open but with no credit card details. If we go to another machine on the network, the order will open fine with the card details being displayed normally.
There is no pattern to which machines will be able to open any given order, it seems to be the case that whichever computer was used to download the order will be OK, along with a random couple of others.
Initially we thought this may be a weird networking problem but we've ruled that out as the problem occurs just as often on the machine which both holds the data and runs the Synchronisation Server service.
The only 'change' that we can identify has having happened on the system prior to this problem appearing is that several hundred old orders were deleted and purged from the system, reducing the .mdb file from a little over 200Mb down to 130 after compacting. Whether that process is purely coincidental or not I don't know, but the problem is very frustrating and I'd be extremely grateful if anyone could shed some light on the issue.
When attempting to open an order the message "The Credit Card Details Cannot Be Decrypted" appears twice, after which the order will open but with no credit card details. If we go to another machine on the network, the order will open fine with the card details being displayed normally.
There is no pattern to which machines will be able to open any given order, it seems to be the case that whichever computer was used to download the order will be OK, along with a random couple of others.
Initially we thought this may be a weird networking problem but we've ruled that out as the problem occurs just as often on the machine which both holds the data and runs the Synchronisation Server service.
The only 'change' that we can identify has having happened on the system prior to this problem appearing is that several hundred old orders were deleted and purged from the system, reducing the .mdb file from a little over 200Mb down to 130 after compacting. Whether that process is purely coincidental or not I don't know, but the problem is very frustrating and I'd be extremely grateful if anyone could shed some light on the issue.
Comment