Sage 100

Upgrading 4.5 standard to 2014 standard. Converting data in compamy maintenance. Error appearing stopping the conversion: ""the following conversion record failed while converting P07. 05:00:00:00 DATA CI_SageExchange Error #13: File access mode invalid"" Screen shot attached. Any ideas? They don't have SPS or PC Charge.

You can try renaming ARxxx. Convert. Rename back, and convert again. This worked for me.

Your suggestion worked like a charm @JohnWilder ! Thanks for the help and for working OT on a Sunday. It is greatly appreciated.

Glad it worked. @JonParkinson gave me the tip last week.

For future reference this is another was to fix them: Go into DFDM SY_Company Select the record for the company with the issue Change Field 51 EncryptionKeyAES$ to the word DELETE in caps now open SY_CreditCardRestart Delete any record in there Go back to company maintenance and Convert

Gracias @JimWoodhead

One more option. In the 4.x version goto Company Maintenance / Preferences click Credit Card Encryption button. On the dialog click on Generate Key and say Yes to create a new public key then Yes to the next message box that says this process will cause all cc numbers to be re-encrypted. Then remigrate. Side note: Even if not on SPS as long as there are CC numbers stored in MAS 4.x when converting to 2013 + it will store in the Sage Exchange Vault

Thanks for the information @AlnoorCassim . Is the reason a new public key must be generated because a key doesn't currently exist so the Sage Exchange private key can't authenticate?

No in this case it means whichever data file was being a converted that has an (Encrypted) CC number in it, that particular record it errored on, the public key in sy_Company doesn't match the encryption value for the card number in the record. Chances are there are other records with the same problem. IOW Conversion is decrypting the card number using the public key (and falling short on some records ergo the error) so it can re-encrypt it (with the SPS encryption scheme) and store it in the SPS cloud Vault (even if you don't have SPS). There are different variations of the error you're getting but usually this is what's going on. Either you delete the card numbers or generate a new public key and have system re-encrypt for you.

Got it. if some records have bad encryption keys, I wonder what error occurs in v4.x whenever the corrupt CC encryption key is compared to the key in sy_company. Also, I bet Sage didn't invent the ""SPS"" encryption scheme.. it is probably PGP or a derivative. Thanks for the hep.

@AlnoorCassim - Is this something you should do as a rule of thumb when converting to v2013 and beyond? It would seem to be the sensible thing to do.

I would put it in the same vein of those clients who you choose to Rebuild Key Files (RKF) as part of an upgrade. Some clients have a history of data corruption so you do RKF before upgrading. If these same client store CC numbers in MAS then yes do this CC re-gen too. Also I don't know the reason why the issue itself comes up. In version 4.early the Encrypted CC field was 24 bytes and then it became 64 in 4.30 maybe and my theory is perhaps this is where all the trouble started because a new encryption scheme was invented and either there were conversion errors or possibly V/I imports weren't using the new scheme. I seem to remember Dawn Anastasi saying something about that a long time ago.

Not sure if this is a coincidence but when i converted the data for the live company I didn't get the error. The error appeared when I began converting the backup payroll companies. I wonder if a new sy_company key gets created when a new company is created.. then when the data is copied over from the live company the encryption keys are different because the CC keys don't get re-calculated during the data copy. If that is the case then it is the laziness of Sage causing the issue.

Doug I just tested on 4.50. It boils down to this. If you create a Copy company and don't include the A/R module data you get a different CreditCardKey$ in Sy_Company on the Copy company. But if you include A/R in any way, it assigns the same CreditCardKey$ from the source company. So knowing that one can't use S/O w/o using A/R, are there are any other modules that store a Credit Card No on 4.x?

Interesting... Thanks for testing.

I'm having the same issue with an upgrade I'm doing at the moment. I followed @AlnoorCassim suggestion in 4.40 and then took the steps that @JimWoodhead suggested. The end result seems to be the elimination of credit card data in 2014. All that's left are the payment types. I have over 11k customers with credit cards in this company so needless to say any further suggestions would be very helpful.

do you try it again without any error?

Jim. After the initial error occurred I followed your DFDM suggestion and went back to company maintenance to restart the conversion process. The sage exchange conversion did appear on the screen and went through without error, although the end result was the elimination of the credit card info. I'm attaching a doc with screen shots and details of the steps that I took.

John try it with just the Generate Key on the previous version. Don't accompany it with the delete option for AESEncryptionKey

Thats what I did @AlnoorCassim . I went back to 4.40 and generated a new public key and then did a fresh migration. The error appeared during data conversion and at that point I went to DFDM and used the DELETE option. I then removed the SY_CreditCardRestart and began data conversion once more. Sage Exchange conversion appeared on the screen and conversion completed. Unfortunately after conversion the CC info was no longer visible, only the payment type field info was visible.