Rank: Member
Joined: 5/30/2019(UTC) Posts: 8 ![United Kingdom]( "United Kingdom")
|
After upgrade, I can no longer see my payment methods on my live store.
There is no payment method grid on the BVAdmin/Configuration/Payment.aspx page.
There are also no payment methods on the checkout page.
The payment methods are still in the database.
|
|
|
|
|
|
Rank: Administration
Joined: 4/2/2004(UTC) Posts: 2,393 ![United States]( "United States") Location: Hummelstown, PA Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
|
Restart the application. You can do this by recycling the App Pool in IIS or by re-uploading the Web.config file |
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012 |
|
|
|
|
|
Rank: Member
Joined: 5/30/2019(UTC) Posts: 8 ![United Kingdom]( "United Kingdom")
|
Thanks for your help so far and now we appear to be getting closer but another problem has cropped up. Whenever I try to view an order I now cannot see the credit card details. When I trace the code I get the following exception when I hit the PciEncryption.Decode line in BVSoftware.BVC5.Core.Orders.OrderPayment.vb (line359) Failed to decode CC. You may need to generate a new encryption key
Exception details: BVSoftware.Payment.AesEncryption.Decode: Padding is invalid and cannot be removed.We have not changed the encryption keys yet this error occurs on every order payment even though the same order payment displays perfectly fine with V2017. Edited by user Tuesday, June 4, 2019 6:21:14 AM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Administration
Joined: 4/2/2004(UTC) Posts: 2,393 ![United States]( "United States") Location: Hummelstown, PA Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
|
Damon, Can you please open a support ticket for this? Thanks. |
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012 |
|
|
|
|
|
Rank: Member
Joined: 5/30/2019(UTC) Posts: 8 ![United Kingdom]( "United Kingdom")
|
Hi Aaron
Okay have found the problem, both bvkeym.config and bvkeys.config have been regenerated and now contain totally different keys.
Once these have been restored back to the old v2017 versions obviously it started working.
I take it these should have not been updated or that the database didn't get re-encrypted with the new keys for some reason.
Should I be using the new keys or sticking with old? If new then I will have to somehow invoke the upgrade process again...
|
|
|
|
|
|
Rank: Administration
Joined: 4/2/2004(UTC) Posts: 2,393 ![United States]( "United States") Location: Hummelstown, PA Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
|
From the information provided it's difficult to determine how you arrived in this situation. If you upgraded an existing site new keys would not have been generated. If you started with a fresh install then new keys would have been generated.
A mistake we often see is deploying different keys from a dev or test environment to production. |
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012 |
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.