Sage 100

Customer says shipping data entry closed sporadically while someone is in there. Sage 100 STD 2014 with Starship installed (latest - vtech installed). Before I open cases with Sage and Vtech and prepare to track it and twiddle my thumbs for two months - anyone seen this and have a solution? Sage does not close just shipping data entry.

WAG: Autologoff set for user?

Good thought. It's possible though I get the impression they are actively working but I'll check. Tx

This was reported to me by a client a few days ago ... No Starship, v2014 Premium. I haven't called Sage yet. I thought it may be a one time only event but client has reported it happening a few times over the last week. Users mysteriously kicked out of shipping data entry with no warning.

A customer on v2014 Std reported this on May 26th. They have 2 dedicated shipping workstations with Smartlinc and it is randomly occurring on both machines. I attributed this to Smartlinc and opened a case with them but have not had any resolution yet.

I haven't seen this is a while, but I recall once a long time ago where two workstations were similarly named (e.g. WORKSTATION10, WORKSTATION11) when one workstation would close a window, the other similarly named workstation would also close. I believe this was fixed with a service update, but it's been too long for me to remember much else about this.

Customer just ""upgraded"". Happening half dozen times a day.

I'm going to open a case with Sage on this today. I continue to believe the Sage 100 on premises business is not long term sustainable so long as these types of issues continue to appear on upgrades. We cannot go to larger customers convincing them to upgrade when the upgrade is more bug ridden than what they've moved from. Customers are going to push their upgrade times even farther apart. Some are going to drop maintenance altogether as they compute that their likelihood to need Sage (for what - to get a case # that has no action for weeks/months??) is very small.

If anyone has a Sage case # on this and can post here I'd like to cross reference it with Sage. As soon as I get mine (or a Sage resolution) I will update.

Sage met my expectation of not knowing anything about this or having ever heard an issue existed. Case # 8004514049

As expected Sage blamed the third party enhancements and kicked this back on the shoulders of the customer for testing. I've had a few of these (and seeing more) where the end user has numerous third party solutions and they encounter some type of random bug. In my opinion this type troubleshooting -- essentially project managing the diagnosis of someone else's bug discovery -- is outside the scope of support (we say that our responsibility ends when we report to the publisher). We are not developers and don't aspire to be the QC department for the different third parties. The dirty secret of integrations? When there's a bug it's damn near impossible to know whose problem it is an Sage will quickly blame the enhancements (who will quickly blame another enhancement and/or Sage).

If anyone calls Sage please mention our case # 8004514049

Does your customer have ACSG Multi-bin and/or ScanForce? The installation that I have that has this issue has both of these enhancements.

Neither. They have V-Technologies/Starship and SO-1241 Multiple Due Dates. It can be a nightmare to go through this type of isolation testing since it requires the customer dedicate a decent amount of time. More often than not they have higher priorities and this never gets tested. They also import some sales orders and I think will first focus on identifying which orders cause the issue and then see if it might be traced back to the Sales Order import.