Sage 100

I am getting the ""The following conversion record failed while converting (company code here) 05.00.00.00 CI_SageExchange Processing occurs during conversion process in Sage ERP 100 2013"" error message during conversion and cannot get past it. Any ideas?

I have gotten something like this when they are not using SPS for credit card processing. Support said something about recalculating the credit card encryption. Sorry, that's all I can remember at the moment

I don't know if it's applicable to this situation but somebody passed this on to me: ----------------- I am working on a Sage 100 V2013 upgrade and apparently my client has old C/C information in their system and Sage 100 detected the C/C information. If there is any C/C information, Sage Exchange will have to be installed even if they are no longer retaining or processing credit cards in the system. If any of you are installing or upgrading to Sage 100 V2013 and you receive any errors in regards to Sage Exchange during the conversion process, below is what I had to do to correct the issue. Manually install Sage Exchange Open IE Go to www.SageExchange.com At the bottom of the webpage, click on ""Go here to install Sage Exchange Desktop"" Once this is installed you can then continue with the conversion -----------------

I have two test 4.30 > 5.0.3/4 upgrades going right now, and after regenerating the encryption keys, rebuilding keys and sorts, repairing the SY0CTL, reinstalling/updating Sage Exchange, purging expired cards and 7-8 remigrations and conversions, I am still getting Error 13s, 80s and 65s. I'm working with someone assigned to these types of cases at Sage, but so far, he has not been able to duplicate the errors. If anyone else has tried something that has worked, please post here. I'm desperate and will have to convert without CCs just to keep the projects going, but I have to find a resolution well in advance of the live upgrade.

@AmberPrayfrock - How do you regenerate the encryption keys?

do they use credit cards? I had one upgrade where I had to go back into the old version, wipe out any credit card history (there is a utility to purge) and maybe even go into DFDM and delete some old records hanging out there. This particular client didn't use credit cards so i could be fairly aggressive and just wipe out anyything I found hanging out there.

Sorry John - was on PTO. Here's the KB write-up: Starting with 4.30.0.18 and 4.40.0.1 MAS90 and 200 are certified and are PA-DSS compliance. The credit card encryption is been done using a Public key that get's generated during data conversion. In order to change the public key you can use Credit Card Encryption button which is accessible via company maintenance task under Library Master, Main menu Use Credit Card Encryption to maintain the public encryption key used to encrypt credit card numbers in the data files. For more information review the help files. Public Key Field: Type the public encryption key number. Asterisks will appear if a public encryption key is currently defined. After this key is entered, it is no longer enabled. A public encryption key is a user-defined string used to seed an encryption algorithm to ensure the encryption result is unique to the user's installation. Its objective is to prevent other users to decrypt the data by using the same algorithm. The public encryption key consists of a combination of uppercase characters, lowercase characters, numbers, and symbols. The more variety in the key, the stronger the encryption. Click Generate Key to create a random public encryption key for the selected company. Click Change Key to change the public encryption key for the selected company. Click Delete Key to delete the public encryption key for the selected company. Note The Delete Key button can be accessed only with the appropriate security event set up. Clicking this button will display a message dialog box warning you that deleting all customer credit card information is an irreversible process.

@AmberPrayfrock Thanks!

always convert a company like EEC first that has no credit cards- then go into that company and enter a credit card in customer maintenance - make sure that works first and then convert the company with credit cards. Far less headaches. Also it takes a long time to process as it runs through the inv header, sales order header tables etc. So if lots of history the slower it goes has been my experience.

Actually, I converted about 10 companies w/o cc's and then it hung up on this one company. Once I regenerated the encryption key for that company everything converted fine.

@Amber - did you ever get through your your conversion issues with Sage's help? I'm having the same thing - first regenerated an encryption key, tested, got the errors, they have very minimal credit card data and I just went and purged it all out (with permission), copied the ARxxx folder back in and restarted the conversion and still get these errors. Tried @Alnoor's fix as well but I receive ""unable to start communication services"" when I try to install from that site. The SE icon is up and running and sageexchange and sagepaymentsolutions are in the trusted IE sites - but I'm starting to think it's a connectivity issue.

@EricAnderson - Did you try and clearing out the SY_CreditCardRestart file via DFDM?

nope - I'll take a look at that - Thanks John. I'll also try Johnny's idea with a non-cc company like EEC, to see if it still hangs up.

I have not yet gotten any resolutions from Sage. I've uploaded two different sets of data to Ronnie and so far, he has not been able to duplicate the issue, but he is trying different things to help ""mirror"" the client's exact installation and then seeing where it breaks. I also tried clearing the SY_CreditCardRestart file at different times and that still didn't help my errors.

I deleted the one record in SY_CreditCardrestart and received a different CC conversion message - moved over a 4.4 version of XYZ and that converted fine. Might be calling Sage next.

I get the Sage exchange error when no companies ever used credit cards. No cc info in any customer records. ??

Installing Sage Exchange didn't solve it.

This is what I've sent internally just recently - hopefully it will help some people here: I think we've all had various credit card conversion errors with the 2013 upgrade over the last few months, whether the client is using Century Business Solutions' eBizCharge, or Sage Payment Solutions, or no processor at all. I've been encountering errors on multiple upgrades lately and I believe I have some steps that might help with both the test and the live upgrades. Of course, you may not be getting the same errors I am, but hopefully the info I have here will help in some way. If the client has CBS's eBizCharge program, I've been getting an Error 65 CI_SageExchange error during conversion. After talking with someone from their engineering dept last week, I've been able to get through that particular error by reinstalling all stock Sage 2013 program files and product updates, and any 3rd-party programs EXCEPT for eBizcharge. Remigrate data only and convert. CBS claims that they have a conversion program that will put all credit card information from the old system into the eBizCharge vault after the conversion is successful. I've asked for that program and instructions to run it, but haven't received anything yet. More than likely, they will need to get connected to the server anyways to install the program and enter/confirm setups anyways, so make sure they are scheduled well in advance, since support is tough to get in a time crunch with them. Regardless of the processor the client has, or if they do not process payments but maintain credit cards, I also have encountered an alternating Error 13 and Error 80 during conversion. In my experience so far, I have found Error 12 records within the ..\MAS90\MAS_XXX\05.00 Company Data Conversion Log which indicate files are missing, followed by the Error 13 you see on the screen. It is looking for some *_orig.M4T files that are not being automatically created by the conversion, so once I created them manually, my conversion went through. What I did is I made copies of the following files: AR_CashReceiptsDetail AR_CashReceiptsHeader AR_CashReceiptsHistory AR_Customer AR_CustomerCreditCard AR_DepositHistory AR_InvoiceHistoryHeader AR_PaymentType AR_TransactionPaymentHistory And appended them with an _orig, like so: AR_CashReceiptsDetail_orig AR_CashReceiptsHeader_orig Once the conversion is completed, those files are removed by the conversion process. I asked Sage why the program is not creating these files successfully, even though my directory has Full Control permissions, and they believes it could be due to anti-virus settings, so who knows yet. Engineering also claims that there is no known risk to creating these files manually if needed.

Per Sage Support. If destination company isn't using C/C, after Parallel migration, DFDM SY_Company for that company. Enter: ""DELETE"" in the AESEncrypt field. That solved it in my case.

FYI - I tried everything twice, including the ""DELETE"" for the encrypt field. My final solution was to copy the live company to a test company, convert that one, then copy back over to live company. Seemed to be an issue with the SY_Company record for our live company, but i'm not sure what exactly

Similar to @EricAnderson, I copied the live company to a new company code (in 4.40), migrated that new company, and then was able to successfully convert. I really didn't want to have to go thru this mess to try and resolve it: https://www.evernote.com/shard/s1/sh/c8454a28-060a-44ff-b580-7af0e365c679/18794c1ba375770bc07ce13572849c64

This was supposed to have been fixed in PU 5 3 The following conversion record no longer fails during company conversion. 05.00.00.00 DATA CI_SageExchange000000:000 (Error ##: Description of Error) DE 102454

We have to implement PU4 on this v2013 upgrade since the client's PU5-compatible Ext Sol isn't yet available.