Sage 100

Tired of dealing with my client that feels everything that happens is related to the upgrade 9 months ago. v2015 Standard, on a TS environment. They do VI importing daily and when they click the spyglass or the browse button or F2, they get kicked out of VI and possible Sage. I of course and connect to the TS and don't have any problems. Of course they don't want to pay for me to resolve this but then ask if I'm looking into it. Any ideas on what would cause the 'getting kicked out' issue. They claim that sometimes after the 3rd try, it finally works and opens the window to select the file.

Nancy, If it typically happens in the morning, They need to be sure to log out of their session before they go home at night, not just disconnect. if they leave their session active past midnight, there is a session tracking file that get's confused, and may also throw errors. If the issue happens throughout the day, or still happens on a newly logged in user, it's likely something else.

It's a stretch but could it be the Microsoft sticky key feature?

Ooh. This happens to me on an rdp session to two of my clients when I browse to locate a file - sometimes in VI but more often in Data File Display and Maint. It's been going on for years and if I try two or three times, I'm usually successful like @NancyHanson describes. Hope there's an answer.

We get this, too. I've always suspected it had to do with mapped drives being disconnected or just not connecting fast enough, but since it works 99% of the time when I try again, I never spent the time to really dig into it.

In response to Chris, user claims they 'log off' rather than close via the X. Thanks everyone for acknowledging it's more common and not related to just them. If anyone has any ideas to fix, sounds like we could all use the fix!

It funny how clients always stiff the consultants for anything that doesn't work. This may not be your exact scenario but this is a phrase I've been using with my Epicor related engagement letters. Bug resolution: All software has bugs. At different stages of development the number and severity can decrease or increase, usually based on the amount of change from a prior version. We generally recommend waiting some time between major releases in order to allow the most severe to be addressed by the vendor. As a consultant for the software and not a developer of it, we have limited control over bugs. Unfortunately software vendors make no reimbursement to consultants for this time so we must bill it along with normal services. Your Epicor maintenance covers phone support which can be used to try and resolve bug issues and you can always choose to

This happens to me with some (not all) clients too, on a variety of versions. Usually if I wait an extra 3-5 seconds before trying to navigate in the Browse window it doesn't crash, but if I try immediately it does. This could lend evidence to Steve's idea about mapped drive connection speeds.

Catching up on this thread, and this happens to me all the time on one particular client when I click the Browse folder in DFDM. It's so annoying and I have to remember to wait about 10-15 seconds before daring to click that Browse folder.