Tom Dalton · Owner · Silver Medal

Wow. Weird thread. I also received several emails about test@test.com failing to get access. We had several test@test.com users in our account. I merged them into one and confirmed that the user had no access. What could it be? Maybe be we all used the same developer at one time and they've been hacked? T

I agree. It serves no real purpose right now. I guess it might hurt NetSuite is the real status was bad and it appeared there in real-time and a potential customer or a competitor saw it. We've been down for an hour and it said "No Issues" when I was there 5 minutes ago. This web page says "Customers can see real-time…

I come here before I check that page. Yup, me too

The odd thing about status.NetSuite.com is that we've been down for an hour and it says "No Issues" and yet this web page says "Customers can see real-time information about any disruption". It doesn't appear to be "real time" information to me. To me it feels like something that gets manually updated more like a "status…

An uptime of 99.5% (calculated monthly) is guaranteed or you get a refund for the month that didn't meet the 99.5% uptime requirement. Is that correct ..and still in effect?

NetSuite offers (or offered) a 99.5% uptime guarantee (or else that month is free). So, my calculation comes to 3.5 hours = .5% of one month if the month has 720 hours. So, if iNetSuite is down more than 3.5 hours this month... you'll get a refund (if you ask for it). See this link

Back up. A little slow, but useable.

Back up. A little slow, but not timing out. Useable.

So, my calculation comes to 3.5 hours = .5% of one month if the month has 720 hours. So, if iNetSuite is down more than 3.5 hours this month... you'll get a refund if you ask for it. Is that correct?

Farrago, I have asked for a refund in the past. I cited three separate events and was denied a refund each time because the Operations Manager said that there was no interruption of service.. Been there. Done that. All I can say is that it is very difficult to do... but not impossible.

FIX: When updating prices via CSV import, if you encounter the above error...Open closed accounting periods. Even though you're only trying to update prices, make your import re-assign accounting accounts (GOGs, Income, Asset). -T

Our web store is down. -Tom

NEVER MIND. Found it. The new "Use Lead Time per Location" feature (in 2013.2) sent it to the bottom of the inventory tab (by each location). Makes sense. ooops

We're Back up.

It is like the store home page takes 5 minutes to load. Then after the home page loads, the site is fast. Close the window and start a new window at the home page and wait 5 minutes to load. Then its fast again. -Tom

our site is down

Webstore is up, but way slow. Time to break out that bottle of Tequila. T

Our site is down. I thought it might be an planned outage that I read about, but the error message that is displayed isn't the normal "down for scheduled maintenance" type of message. It looks like it is broke with no message and a broken image link. -Tom SignsDirect.com

NS found the issue. They said that this code was missing from our google Analytics... _gaq.push(['_setAllowLinker', true]);

Wasn't sure that you were. I mouse over the "!" and it has an entry from 5:25am pacific time saying some other issue was resolved.

Obviously this is killing our sales for the day!

status.netsuite.com still never showed last night's outage.

I get logged out every time I switch browser tabs (to two different NS windows). I use Chrome on a mac. -Tom

Did anyone else have PayPal issues over the weekend? -Tom

OK, apparently it spins endlessly AND gives the indication that submitting is in processes... WHEN it has in fact already created a case. I got an email 5 minutes ago saying "your case has been created". Yet, i'm looking at a browser window with a spinning graphic for submitting and it has the word "Submitting..." right…

Our support cases are created by our customers and are created via online form So, it sounds like the same issue.

Who should check their "Dev Console". I can't fix it if it is bad code on the NS hosted page. We don't have a similar issue anywhere else online. JUST in NetSuite. We just had a Java update today and since then I created a new NS case. The case submission bug is still active. Maybe it only effects mac users.

So, good. I needed that.

Went to Setup > Customization > Scripted Records None of them had "sales order" in the Record column. We use insideView and SuiteSocial and some Free NetSuite bundles. We haven't created any of our own scripts.

This happened again today. The same fix (described above) also fixed this order. I did notice that the customer (in this case) had attempted two credit cards before finding one that worked. I think it is somehow saving the default address with each attempt and not overwriting the address, but rather making a second…