My Stuff

user12048007 Newbie

Comments

  • Some late-breaking news: We've gotten a number of requests for better session management and speed when logging in to NetSuite. As such we are changing our login mechanism ... This will greatly increase the speed of login. It also eliminates the question of "has my session timed out" if you think it may be a while between…
  • We are not suggesting any user interrupt a time sensitive processes to gather a use case/reproducible steps. Rather, if you can note the time of occurrence and the email address with which you logged in, filing a case with that information will be very helpful in diagnosing the cause. Additionally, please specify the…
  • Not very encouraging. Please let me know if anything has been done to investigate and fix the problem of unexpected premature time out while actively working. Also please stop the error: "Someone else has logged in using your account from another location" Both of these problems are very irritating, and it is even more…
  • After switching to v2008.1, we're consistently getting time out problems. Many times, it's in the middle fo entering a sales order. Unfortunately tech support was with me on webex to try to reproduce the problem and of course, we couldn't "reproduce" it. I can say that the problem is still there and it's extremely…
  • We are actively investigating these reports. For anyone who is experiencing "time outs", please reply to this thread with a case number that includes the steps that lead to the timeout. Please include the email of the affected user (login) and time it occurred. Without this information, it can be challenging to determine…
  • I wanted to provide an update. Issue 133270 is still actively under investigation with the highest priority. It tracks the case of users being unexpectedly logged out of the system. This issues does not track reports of slowness with specific reports ("Report has timed out"). Any issue of this type requires its own case.…
  • A resolution for Issue 133270 is currently undergoing verification by QA. It is scheduled for release on 10/18. Thanks, Ted
  • For anyone who is experiencing this, please respond to this thread with the following. [LIST=1] [*]Case Number [*]Email of the user that was affected [*]Time of the occurrence [/LIST] Thanks, Ted
  • Ray, We are still investigating both cases of being logged out (via reports and accepting credit card payments), but have no information to provide at this point. It is being investigated with the highest possible priority. Ted
  • Issue 133270 is tracking this and being worked on with top priority. I will provide updates as available. Please note, this Issue tracks a user being logged out following the execution of a report. It does not track reports that fail to complete due to a "Report has timed out" message. These are performance issues and…
  • All of a sudden we cannot use the "add matrix items" feature. I cleared my browser cache and tried in both FF 2.0.0.7 and Safari 2.0.4... And I continue to get the following message:[INDENT]Notice Your session has timed out. Please re-enter your information and try again. [/INDENT]EDIT: I reproduced it in IE7.…
  • Im getting this when I try to run a credit card from the backend. case 632887. Now I cannot accept payments ! not good. My message is: Notice Your connection has timed out. Please log in again. Ray, Can you please provide an email and time? Thanks, Ted
  • The reports of web services slowness is being investigated. If you have not already done so, please file a case and reply to this thread with the case number so we can attach it to the appropriate Issue. Thanks, Ted
  • We have confirmed that the slowness/timeouts this morning, due to the Northern California external ISP Routing issue, is no longer present. However, that does not preclude other routing issues from being present. From our local, and remote, locations I have been able to visit shop.mudhole.com without any slowness or…
  • We have re-tested from our remote location and the switch to our alternate bandwidth provider has resolved the issue. If you are still experiencing issues, please file a Case and your issue will be promptly investigated. Thanks, Ted
  • There are currently no systemic issues affecting performance in the manner reported. However, we will follow up and investigate each of your performance issues. In order to facilitate that process, please file a performance case and include page, email and time when you encountered the issue. Thanks, Ted
  • Issue 131152 has been released to production. We apologize for any inconvenience this may have caused. Thanks, Ted
  • This is being investigated as a top priority and we will provide more information as it becomes available. Also, have you verified that the slowness is only associated with your site and does not reproduce going to other web sites? This would rule out any Internet Provider Issues (i.e. http://www.internetpulse.net/).…
  • Issue 131152 tracks the item stock status message being corrupted and has been attached to Case # 618067. We have reproduced the Issue and are currently testing a fix that we hope to release later today. Thanks, Ted
  • This issue affects less than 5% of incoming requests. We have just forced traffic over to our alternate bandwidth provider. This will resolve the only issue we are currently tracking. We are continuing to monitor and will know more shortly. Thanks, Ted
  • Issue 131420 has been created and attached to your case. QA is investigating. Thanks, Ted
  • The fix for this Issue has been released to production. We apologize for any inconvenience this caused. Thanks, Ted
  • We have been able to reproduce this issue from our remote location. The problem seems isolated to certain ISP Pairings and is external to the NetSuite network. We are still investigating and will provide updates as they become available. Thanks, Ted
  • Your WSDK scripts will continue to work on the 'netledger' domain, so there is no immediate need to change all the scripts at once. The change to 'netsuite' is a recommended best practice, but we will maintain backwards compatibility with the 'netledger' domain. Thanks, Ted
  • The resolution for the "document.write('Error - Company id parameter (c=xxx) was not provided on the URL\n');" Issue has been released. Can you confirm that this particular issue is no longer a problem? The Item Stock Status message corruption is a separate Issue and is currently being investigated. On your site, when I…
  • In addition to the previously mentioned ISP latency (http://www.internethealthreport.com/), we have discovered an external ISP routing issue in Northern California. We are currently looking into options to help our customers avoid the problem. Thanks, Ted
  • Angelika, If you provide a Case #, I will be sure that an associated Issue is created/attached and investigated. Thanks, Ted
  • The issues you encountered were related to the use of the 'netledger' domain, instead of the 'netsuite' domain, for the WSDK calls in your web store. The 'netledger' domains have been deprecated for some time now and the issues arose from an interaction with the release of new code and the deprecated domains. To avoid any…
  • We are still having the same problem. When trying to print multiple invoices, one of our users gets an error indicating that they are logged in as another user. They have to then print the invoices one at a time. I have filed case 627586. Anne Anne, What is the email address of the user who is experiencing this behavior?…
  • To all whom this issue affects, We sincerely apologize for any inconvenience this issue is causing you. This evening we will be releasing a patch to gather more diagnostic information that we hope will enable us to track down the root cause. Without an in-house reproducible test case it has been very difficult to isolate…