プロフィール
Share Your SuiteWorld Experience & Earn a Special Badge!
コメント
-
A datacenter-wide incident in our NA West facility has resulted in delay with the delivery of outbound email. On-Call engineers were notified and resolved the issue as quickly as possible. status.netsuite.com has been updated and this problem should be resolved. Please follow up with Support if you are still experiencing…
-
This is should be resolved now. status.netsuite.com has been updated.
-
status.netsuite.com was updated and this should be resolved now. A datacenter-wide incident in our NA West facility has resulted in a very serious degradation in performance for customers local to that datacenter when attempting to access SuiteCommerce Webstore or SuiteCommerce Checkout functionality. Operations Engineers…
-
Some accounts experienced an interruption in service and status.netsuite.com has been updated. Support filed Defect 414896 for those that are effected.
-
If you receive an error on fulfillment, Support filed Defect 414720 Item Fulfillment > Save > Unexpected error > Error occurred making a FedEx Ship request.
-
We have filed Defect 417925 for webstore performance.
-
status.netsuite.com was updated with the following message at 2:25 PM EST: A datacenter-wide incident in our NA Northwest facility has resulted in a degradation in connectivity for customers local to that datacenter. Operations Engineers were notified of the issue by monitoring and are working to resolve it as quickly as…
-
Support is filing a Defect for those accounts still affected. The Defect # will be posted shortly.
-
Try logging in using https://system2.netsuite.com/pages/login.jsp or system2.na2.netsuite.com. Users may notice better performance logging in on system2. If the system2 domain provides better performance, then you can continue to use this domain to work as usual in your NetSuite account. For more info on getting Help with…
-
Our engineers have identified the cause and are preparing to release a fix. Eta is 30 minutes.
-
Support filed the following Defects: [LIST] [*]413227 Webstore > login > Throws Unexpected error: An unexpected error has occurred. Technical Support has been alerted to this problem [*]413160 Performance > NetSuite > Slow and Freezing > Getting Session Time out [*]413378 Unable to Login to NetSuite [/LIST] Please contact…
-
Any new incidents should be reported to Support for further investigation. All recent incidents are listed on status.netsuite.com.
-
status.netsuite.com was updated today 9/19 - An incident in our database infrastructure has resulted in an interruption of service for some customer accounts. 02:50 AM - 02:52 AM (Resolved) If you continue to experience a performance problem, please contact Support and they will investigate further.
-
Some accounts are receiving a maintenance message when logging into NetSuite. Status.netsuite.com has been updated and Support filed Defect 415126.
-
It appears that Fedex was experiencing connectivity issues causing the fulfillment error.
-
Support is investigating similar reports and will provide an update asap.
-
status.netsuite.com has been updated with the following message - A datacenter-wide incident in our NA West facility has resulted in a degradation in performance for customers local to that datacenter when attempting to access Application UI functionality. Operations Engineers were notified of the issue by monitoring and…
-
This is being tracked in Defect 411634 NetSuite UI > Overall Slow Performance in accessing records. It appears that this may be resolved now. status.netsuite.com has been updated.
-
It should allow you to override the existing numbers as in the SuiteAnswers article. It looks like you would need to override all existing customer numbers with a higher number to bring it back down to your preferred starting point. Once all customers have been renumbered, auto-generated numbers should pick up from there.…
-
You should be able to reset the auto-generated numbers to a lower sequence using the steps in SuiteAnswers Answer Id: 38158.
-
Support filed Defect 410099 for this. The problem has been resolved and status.netsuite.com was updated - 8/29/2016 An incident in our database infrastructure has resulted in an interruption of service for some customer accounts. 06:50 PM - 08:43 PM (Resolved) Please contact Support if you are still experiencing this issue.
-
The status page has been updated to reflect this incident.
-
Support filed Defect 406796 for this.
-
status.netsuite.com was updated with the following message on 7/27/2016 - A datacenter-wide incident in our EU West facility, caused by planned maintenance, has resulted in a very serious degradation in service for customers local to that datacenter. This should be resolved now.
-
FedEx confirmed the problem has been resolved and real time shipping costs should now be calculated as expected.
-
The fix was released on 7/22. Please contact Support if you are still experiencing this issue.
-
Support filed Defect 403173: Calculate FedEx shipping cost > Could not calculate cost for the selected Realtime rate. Remote EJB method: getRates called on interface. Please contact Support to have your case attached.
-
Support filed Defect 401450 Performance > All records are slow. This was resolved at 1:11 am PST.
-
I'm not aware of any performance problems at the moment. Have you filed a case with Support yet?
-
status.netsuite.com was updated to reflect this - An incident in our database infrastructure has resulted in an interruption of service for some customer accounts. 04:07 PM - 06:10 PM (Resolved)