Sage 100

SAGE has Stopped Working."" Am I the only one seeing these message on client with Sage 100C and terminal server ? There was a patch that was included with SAGE v2016 PU2 which I am already on. I understand this has to do with the STANDARD Interface and conflicts with the Classic one. Has anyone broke the code on this issue other than making customer use the classic interface?

We have the same issue as well and have not been able to find any other work around. Anxious to see what others are doing.

Jim, Christine has this as well on a 2016 Advanced with remote users, users would lockup everyday, changed all remote users to classic and that fixed it. Hoping Sage gets a fix out for this.

We found some issues with the Sage 100 Documents folder that is new with 100c. The resolution steps are: 1. Close Sage 2. Go to My Documents 3. Find the folder called Sage 100 and Rename it 4. Open and sign in to Sage, the system will create a new Sage 100 folder. That has fixed several oddball errors with the standard desktop on 100c

This is what I've received from Sage at the moment. The above solution from @BernieLehman will clear it for now, but in my experience, it re-appears. The secondary window with the prompt is in an unreachable area on your monitor. Use the following steps to pull the window into a visible area: 1. Alt+Space Bar 2. Select Move 3. Position Cursor in screen 4. Click Arrow key 5. Hidden screen will appear Hopefully you system will recall the location where you ended up putting the secondary window the next time you run it.

Just re-reading Jim's email. My solution above was not for that problem. In our internal installation, we have two users accessing Sage from a RDT. Aaron uses Classic because he got tired of freezing (my earlier solution). I've been trying to use Standard and you're right, my session freezes, when he is using Classic. I've reported this to Sage on Jan 6, but no feedback yet on a solution. Ronnie Aspe, Laura Dy, and Diane Coffman are all working on it (or at least that is who I've reached out to)

I will call Sage and see if we can add some heat!!

If you are going to retrieve window locations from the registry or a preferences file, you need to add a check so that if the location is off the screen you reset it to (0,0)

@BernieLehman answer above is what we got at the official answer from Sage.

We have set them back to classic. I was also under the impression this was fixed with a patch. IT is not though.

I have a client that uses 3 Terminal servers with load balancing and roaming profiles. They have the same problem - everyone has to use classic. PLUS one Sage Tech told me they didn't think it would work with load balancing due to the ""SAGE100"" folder being stored in the user's ""documents"" folder.

@GaryFeldman and @BernieLehman - is that because of redirection of My Documents not being taken into account by Sage?

I appreciate this is a problem, but the message itself has a much deeper meaning to me.

No Sage does not work even without redirection.

This seems like a 100c showstopper. ""So Ms/Mr client ... we have this new improved UI with Sage 100c which you'll pay more for and be on subscription with expiring keys .. .and BTW you can't even us the new UI"" ... I'm not sure how this isn't a priority for Sage unless it's an unsolvable technical limitation.

You can use it, just periodically delete the folder and then choose it again. Or choose the old UI and not deal with the hassle or change your font size and color scheme.

One of you fine folks who are going to be face to face with the Sage team at Meeting of the Minds will bring this little gem up with them, right?

That depends, who is the designated curmudgeon this year?

We need to have it resolved before then

I've tried to impress upon the people at Sage that I've spoken to that this is a huge issue and cannot wait until the 2018 release. As @WayneSchulz said, it's hard to convince someone who has paid for the new UI to use the Classic desktop because what they bought is not working. I recommend everyone who has experienced this problem to create a case with Sage and once you've got a case number, escalate, escalate, escalate! We reported this issue in October, I think it was, and 4 months later still trying to get traction.

I was hoping we would present Sage with a list of things we want to hear their resolution for by MOTM, if that has not been done already. I see another post today where setting the app scaling to Large can hang up custom office screens, and so far Sage's answer is ""don't do that

Sage, my software hurts when I do this. Well, don't do that. (Reminds me of a Sharon Jackman answer.)

I think if we all open a case we might get some traction, we have all bought into 100C or forced into it, our clients have bought into it, Sage needs to buy into it snd fix it soon.

Should we have a post to suggest ""improvements"" (ahem) then a poll to vote on the top X? Not that this one can wait.

We did have a post with suggestions for Sage's presentation this year. We did that last year too, and Sage being Sage, went and did their own thing. If we want Sage to know about these issues at MOTM we need the Town Hall session at MOTM to be a true Town Hall and not another marketing spin.

I don't blame them for not wanting to address the hard issues in the town hall, on the record and all. I wonder how we can deliver our requests in a non threatening, but wrapped around a brick way. Like a closed door meeting with a MOTM rep. and Linda et al?

@RhondaMcNamara has a good idea. Perhaps some of the 90Minder BPAC members can either persuade or participate in the session to raise the urgency and improtance.

I have been working with Ronnie Aspe @ Sage . They believe they have a fix (In testing) but to get it you need to have your customer sign a PRA (Pre Release Agreement) Ronnie said that it seems to related to customer using Terminal server and Sage 100 v2016 PU2 Email Ronnie **Michael.Aspe@sage.com** if you have a customer willing to sign a PRA to get it

@GaryFeldman I am sure you are interested.

LOL - so now to get working software from Sage you're required to sign a waiver? How about Sage just ships a tested fix?

@KatrinaEddins - Please coordinate with the partners who have experienced this issue with their customers in our environment.

I was told the fix is in testing and if all goes well maybe a fix for ""PRA"" customers tomorrow.