Sage 100

Converting 4.4 data to 5.0. Conversion halts with message ""Unable to create Sage Vault Account"". They do not use CC Processing, but do have some CC's configured in Customer Maintenance. Anyone encountered this?

If they have CC's in place, doesn't it still store them in Sage Exchange? Dumb question, but is there internet connectivity??

Yes, there is.

It's supposed to store them in the Vault.

Is this a keys issue? I think you need to have the current customer keys -- I now L. Maloof had some comment about this (I think). Saw your other post about keys... Please update us when you know more.

Will do. I have a case open with Sage - waiting for a call back.

Update: Lori may have been telling the updated keys were needed for Payroll e-file - not sure.

When Sage called me back an hour later, I went to show him the issue, and lo and behold, no error - it just finished the conversion. Apparently, another analyst took another call reporting the exact same issue about the same time I opened my case. Theory is that perhaps Sage Exchange couldn't communicate w/ the ""Vault"" at that time. Ronnie Aspe was who I was working with, and he said he'd check in w/ Sage Payment Solutions to see if there was an interruption in service. I'll follow up on that. I also got an education on how to install Sage Exchange if it somehow doesn't install as part of WKSETUP (i.e. you don't see the SE icon in the system tray): 1. if you access any place in MAS that requires accessing CC data, it will get installed automatically (I think - either that or it prompts you first). 2. There are 2 components required for SE: The Module SDK and Sage Exchange itself. You should see them both in Control Panel\Programs. If they aren't present, you can manually install them from the 2013 install ""DVD"" by navigating in WIndows Explorer to the folder \Prerequisites\SageExchange\setup.msi to install the SDK, and \BARESETUP\SageExchange.application to launch the SageExchange installer. Note: you can also launch the SDK from inside the WKSETUP\Prerequisites folder. But the SageExchange installer is not located there. You can also launch the SDK from the installer program for Sage 100 under Productivity Applications.

Nice info @BarbaraGoldstein - Thank you!

If you have credit cards in a company but are not using SPS will it still convert? Example is - a backup of a company from 6 years ago before SPS on PCCharge at the time. But still want to keep the archive company in the new verison. Will it convert? I am living the dream now and try to figure out why 20 companies will not finish converting when the get to the sage exchange part.

My understanding is whether the company is using integrated CC or not if there is CC info in there it gets pulled up to Sage Exchange Vault. I have also said that I believe that this is something that customers should acknowledge because if there's a data breach of some sort I don't want the phone call about why ""I uploaded data without their knowledge"" ..... I'm adding verbiage into the upgrade proposal that acknowledges this new feature as well as the new EULA which seems to allow for Sage to shut off service if the maintenance isn't paid (but so far as I know is not happening).

You're right, @WayneSchultz, CC's move to the cloud regardless of whether CC Processing is activated. In Company Maintenance, Credit Card tab, you should see Sage Exchange Vault info. See my attachment.

Do different keys get generated per company, or are they all the same across one Sage 100 installation?

The Sage Vault keys are company-specific.

having this same issue. I went back to version 4.4 and found one credit record record, so I deleted it, purged all history, remigrated and still get the error. Sage Exchange seems to be installed properly but there is a communication error ""Unable to start communication services"" when i try to fire it up. There should be nothing left to move to the vault, so I'm not sure why it makes a difference, but maybe I'll just try again in the morning and see if it works.

@EricAnderson please report back on this - it seems like an error we may all encounter as we do more 2013 upgrades. Will be good to have some shared knowledge on what (if anything) is the fix.

I ended up calling Sage - initially they sent me the attached article talking about rebuilding, uninstalling/reinstalling, etc. I pushed back a bit and Dennis at Sage was nice enough to connect. Although I had deleted and purged credit card history, there was still one credit card record in the 4.4 AR_CustomerCreditCard table (deleted using DFDM). We also cleared out the SY_CreditCardRestart table (in 5.0) where it was getting stuck on the conversion, also using DFDM. Then copied the company data back over, converted and it worked.

In sage exchange - bottom right - make sure you go to settings - and then work your way down on left to register and look at the right - there should be a long random key if not keep toying with it and restart till a key is there also. This is critical to communications and conversions to the sage vault conversion.

Also - looking at the logs helps troubleshoot where the issue is.