Evan, Thank you for the message. We did see that the issue was fixed and released last night and everything appears to be working again. Can you provide more information on what the problem was? It seems like a bug fix that went out last Thursday night during the bug fix window caused a new problem to be introduced which…

Support was able to help us. The credit card expiration date needed to be passed in with a correct time zone. If passed with GMT then depending on what the GMT time was it may roll back a day when Netsuite converts to their timezone which I was told is PST. It seems a bit odd to me that they don't use the timezone that I…

Emails coming from Netsuite from within our account are being blacklisted now as well. Submitted a case to support. The number is 1165298. Why does it seem like every 3 - 4 months this issue pops up again? Clearly a better system needs to be put in place. Maybe Netsuite should think of using a 3rd party email solution. I…

Found out our sandbox account was disabled. Would be a nice feature if there was a message on the dashboard stating when the account will terminate/expire.

I am not able to login to the sandbox UI. The message I am getting is "You have entered an invalid email address or password. Please try again" from the UI. Per my original message, I am not able to log in via the UI.

What is the official response/reason from Netsuite? This should be standard practice. BTW... Status.netsuite.com is not reporting downtime or even a status for the last 7 days.

Faye - Any updates as to the cause, resolution, and procedures put in place so this does not happen again.

Maria - thank you for confirming the outage. Can you provide details about what the actual problem was, what was done to fix the problem, and any procedures that were put in place to prevent this in the future?

Wiktor, Thanks for the information. You must have been the 'other' user that reported this issue. Did you notice the same issue on Friday? Did you notice on Monday that you were getting 404 errors when trying to connect to the web services? The issue got fixed last night as someone called me back. Hopefully they figure out…

We are using Sandbox for development and receiving: WS_CONCUR_SESSION_DISALLWD: Only one request may be made against a session at a time and literally 30 minutes ago we were ok. Something is going on. I reported this problem on Friday and was told it was unreproducible

The sandbox is down for me.

Easier to push it up the chain during business hours instead of ruining my weekend dealing with weekend support and no one around who can make a decision.

Can you post the information about the defect so I can make sure support ties us to the correct defect. They won't provide me info about a defect unless we created it.

Can someone from Netsuite provide a complete answer. Businesses depend on the answer and budgets/business expectations need to be set/adjusted based on these answers. We all need to know if we need to take on the task of scrubbing all our data. I am sure all our Cybersource "grace" periods are almost up and soon we will be…

Interesting. We were upgraded on Friday night / Saturday morning. How do we find out if the 2013.1 include a fix?

Wow... so the official line is "F*** Off and fix it yourself". Great customer service.

I received word last week that the problem has been resolved. Not sure if Cybersource has turned back on their data validation or not yet so no way to determine if the fix is actually working.

Elie - if this is true that would be great. I guess they finally realized they did have the ability to make the changes. Netsuite - Can you post an official answer and more information about this. Is the rumor true?

I have not seen an update on the issue. The current defect number is: 241573 It is classified as an S2. In my experience, this means that it is not a priority and it may never get fixed.

I think Netsuite was able to fix the parentheses issue which is why my transactions were successful. I am using the same customers on each test so that I can be sure it is fixed. Not sure why Cybersource is showing them, maybe Netsuite is encoding them or something. Now if they could just fix all the additional characters…

Thanks for the follow-up. I look forward to the hopeful resolution to this issue in the next few weeks. Eli - I believe this will solve your issue as well since you were experiencing the same thing we were.

Here is what I just learned from support: I have made a further research on this. Issue 243163 only seeks to put in "Cardholder first name" and "Cardholder last name" as substitute for Bill To First Name and Bill To Last Name, when sending out request to CyberSource (in case there is no Cardholder name). But with regard to…

for option 2 if you are using the Netsuite UI or webstore, I think you can create a custom script to fire after submit/save which you can have scrub your data for you. Not sure if this will work in your case. It does add some time to the adds/updates and will also get you into custom code (which you may not want to have)

We have not heard anything further on this. Since Netsuite will not help our plan is: 1) export all the records, scrub them, and then re-import 2) Since we use webservices to enter all data into Netsuite - we will scrub the data prior to sending it into Netsuite. We are also changing our ID for customers to hopefully get…

Netsuite is definitly stripping the parantheses off the company name now. I just looked at a sampling of transactions from yesterday and today and I now see the parantheses missing. I also was able to get the raw data from Cybersource and it shows the company name without the parantheses. Hopefully they can strip the other…

Go figure. Spoke with the account rep a few hours ago. It was like I was telling him the information for the first time. Attempted to sell me on switching payment processors away from Cybersource. Clearly does not get the issue. 3 more hours and I get to call again and will escalate up the food chain. Someone, somewhere…

Thanks for he heads up and reminder. I had a long chat with our account rep (4th one in 4 years) about various problems mainly focused on this particular one. He promised multiple times to get to the bottom of the issue and have it resolved. In fact he said to give him 1 day and he would have answers for me. Well, it is…

It is a bogus resolution to a real defect which still exists. As we are all aware, Netsuite is passing the Customer Id to Cybersource via the Cybersource field billTo_company. The reasoning behind this escapes me for multiple reasons: 1) billTo_company is optional for Cybersource, 2) the company name should be the actual…

Elie - We had Cybersource turn validation back on for our test account. We actually were able to get succesful transactions through in sandbox against test cybersource if the company name contained "(" and/or ")". Cybersource processed the transaction. For some reason the raw data as shown by Cybersource still includes the…

Please tie us to defect 241573. This is getting silly. This is now your third try at solving the problem. If one of my junior developers took 3 tries to get this right and notified the customer each time that it was fixed, they would have been fired by now and we would have lost the customer as well. At this point are we…