My Stuff
Comments
-
Have you looked to see what scripts are deployed on your Sales Order form? Setup > Customisation > Scripted Records Could it be a recently modified Workflow?
-
Just testing our 2013.1 beta - and we're seeing exactly the same issue. All custom transaction columns are missing from the Picking Note - in our situation this includes the warehouse location, so no one will be able to find anything! What's the ETA for this defect to be fixed?
-
We're having a similar issue. Our Script is creating Invoices, and occasionally we're getting back the same "this record has changed" error, even though the record has only just been created. What's even more annoying, is that NetSuite is then going ahead and actually creating the Invoice anyway - and because our script…
-
That's a misunderstanding and/or red herring. You can't use a hostname in that search, you have to use a domain name. The system.netsuite.com resource records (RRs) are contained within the netsuite.com zone file, which checks out. Try putting netsuite.com in the search, you'll like the results better. -Darren Apologies, I…
-
I do also have to say that the general reply I got from NS Support, was less than helpful. "Can you ping “system.netsuite.com” from your end? It appears that this is not issue on NetSuite's and appears to be ISP issue. Thanks again and have a great day. Cheers!" Would have been nice to think they cared at least a little…
-
We're still down generally, but our hosting company have modified their firewall to hardcode the route for our requests to NS - bypassing the problem - and we're back in business!
-
This was posted on twitter earlier by @levesquejf, relating to this issue. #Netsuite - Routing issues with 167.216.128.0/22 being advertised by two AS (14919+26554) since 6:04am EST. That timestamp relates exactly to when our issue started.
-
North America is down as well. System2 is working, regular login does not. Engineers are saying it is an ISP issue via Announcement board, however this seems to be a world wide issue.... Where is the engineer announcement?
-
Seems to be down for us again now.
-
Our NS account is online - but none of our Suitelets or hosted forms are working. Our scripts connect our external website into NS - so our entire business is offline right now!
-
Should be up and running now. Got this from US Signal: Why couldn't NetSuite have done that? So, some small-ish local ISP managed to bring down NetSuite?
-
Interesting, none of the VPN connections I've tried have routed the traffic through ussignalcom.net & level3.net - so perhaps the issue is solely with traffic through there.
-
Looking at a traceroute for system - it's showing quite a complex routing issue. Seems to be stuck in a loop and never actually getting to system.netsuite.com traceroute to system.netsuite.com (167.216.129.11), 64 hops max, 72 byte packets 1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 1.685 ms 1.263 ms 1.206 ms 2 212.140.157.181…
-
At the moment, I'm VPNng into Washington - I can log into system.netsuite.com fine from here. I've also tried VPNing into France, Hong Kong and Holland, and they all work fine. Seems to only be a UK issue from what I can see.
-
We are using both BT and Virgin, and both are unable to reach system.netsuite.com
-
Well they have redundancy- NetSuite has a fully duplicate backup server facility on the US east coast as well as their West coast server facility.
-
It's definitely a routing issue, I've logged in via a US based VPN just fine. NetSuite is up, we just can't get to it from the UK it seems. With a much shorter Traceroute too! traceroute to system.netsuite.com (167.216.129.11), 64 hops max, 72 byte packets 1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 84.026 ms 83.526 ms 83.537 ms 2…
-
In our newly installed 2012.2 it's in the following location: Setup > Company > Company Information : "Return Email Address" I don't believe this has moved at all.
-
NetSuite - can we all have a full update on the cause of this 5 hour outage please.
-
I'm getting a slightly different error: An error occurred while processing your request. Reference #97.68843554.1344648008.51e9d9db These outages seem to be getting pretty regular! :(
-
This issue now appears to have been resolved for us.
-
Exactly the same here - errors started appearing at 10am GMT Support, as always tried to pretend there's no issue. "They said that this is not an error and it is due because the database is locked to other customization changes when there is another customization object change that is running." Which, is odd being as no…
-
Working fine for us. What errors are you getting?
-
We've been having massive speed issues since last year, but recently it has got much much worse. We currently are virtually unable to run any report without it timing out, and have a defect (170330) open to cover this problem.
-
Pretty much the same as I got too. And this was only after having to ask. Is it that hard to remember that at the end of the day, we're customers - and we expected to be treated as such, and not as some inconvenience. Every other third-party IT supplier we use, contacts us immediately with a full and (often) frank outline…
-
OK, so I've now been told that the ETA for this fix is December 12!! Netsuite, hello??? Are we on the same planet here? Are you seriously expecting us to renew our service after this?
-
Glad to report, that someone at NetSuite listens. This fix was applied to our account early this morning!
-
Well, we're almost at two weeks now - and this S1 defect is still not fixed. Not even an ETA has been provided. So, it's now time to talk about SLA · NetSuite commits to provide 99.5% uptime with respect to the Customer’s Service during each calendar quarter of the Term, excluding regularly scheduled maintenance times. ·…
-
Credit where credit is due! Just want to take this opportunity to thank the NetSuite team for their professional handling of this major defect - it was handled well, we were kept informed, and as of 2 hours ago this defect was fixed. Thanks again.
-
OK, now this is simply getting stupid. Just had our 2012.1 upgrade complete - and this defect is back again!