Wondering if anyone else has run into this in the past. We are trying to move an individuals transactions to the household using the standard tool. But we are getting the following error:
"Msg 50000, Level 16, State 1, Procedure AP_MOVE_TRANSACTIONS_TO_HOUSEHOLD, Line 415
Transactions cannot be moved: Error in T_ACCOUNT_DATA_TI on line 27: Error #50000 Cannot store null as protected data. "
I initially thought this was related to credit cards as that's the one place I could think of with encrypted data. However, after removing all credit cards from the account, I am still getting the error.
It looks like the error message is coming from the INSERT trigger on T_ACCOUNT_DATA making a check to ensure that the encrypted copy of the cc number is present. But the credit card record (when it existed) definitely wasn't null, and now the cards are gone. So I'm not sure where the issue lies.
Any takers?
- Levi
Hi Levi -
I ran into this problem earlier this year and put in a support ticket about it - they were super helpful in digging through the info and finding the issue. My issue was actually with something in T_PAYMENT, where the payment_no was referencing an act_id that didn't have a matchup in T_ACCOUNT_DATA.
If that doesn't lead you in the right direction, I'd put a support ticket in and those lovely folks will spot it. I actually stared right at the data and missed it - sometimes you just need another set of eyes.
HTH,
Heather
Levi,
If you open a support ticket, we can help you with this.
+Ryan Creps
+Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Levi Sauerbrei Sent: Thursday, September 19, 2013 4:56 PM To: Ryan Creps Subject: [Tessitura Technical Forum] Move Transactions problem
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thanks Heather and Ryan!
I probably have a little more digging to do to get some additional details, but I'll submit a task ticket when I get there.
I found the culprit. There was an order on the account with act_id = -1. It looks like a payment plan was created but not associated to a credit card and somewhere along the way that field got flipped to a bad value.
We got the transactions moved and are working out the issues with the scheduled payments.