Hello again everyone!

Here is the current solution we're testing. Let me know if you try it and what the results are. Please include load times prior to and after implementing the fix. The solution is implemented on the workstation so you can test with just one or two for now to see how it works for you.

On the workstation (logged in to the workstation using the Sage user's windows credentials):

1. Close all Sage applications
2. Open the Windows Registry editor (regedit)
3. Browse to HKEY_CURRENT_USER\Software\Timberline\Desktop
4. Right-click on Desktop and select New String Value
5. Enter "UpdateTaskInformationFileIntervalInMinutes" and press ENTER.
6. Right-click on Desktop again and select New String Value
7. Enter "UseTaskInformationFile" and press Enter.
8. Double click the new string values and enter "1" in the Value Data field for both of them.

This will create a file in the workstation that is accessed when you launch Sage Desktop. Note that it can take up to 5 minutes for the file to be created.

Thanks!

This is the fix we applied days ago.  Mark said it's only good for approximately 15 workstations or less and that a larger network would create havoc so I'm mentioning this, too.  It fixed the problem we were experiencing so that the load times are nearly instantaneous. 

However we are still having problems on two workstations that are a little different.  This is new:  One is Windows 10 and today, just starting Sage, before the log on, Sage was "not responding" (and it loaded fine yesterday). 

This is since Vs 17 install November 2018:.  Another, Windows 7, has problems where the "log in" box is greyed out and unavailable repeatedly.  In both instances, we found restarting the workstations remedied the problems. 

This is the fix we applied days ago.  Mark said it's only good for approximately 15 workstations or less and that a larger network would create havoc so I'm mentioning this, too.  It fixed the problem we were experiencing so that the load times are nearly instantaneous. 

However we are still having problems on two workstations that are a little different.  This is new:  One is Windows 10 and today, just starting Sage, before the log on, Sage was "not responding" (and it loaded fine yesterday). 

This is since Vs 17 install November 2018:.  Another, Windows 7, has problems where the "log in" box is greyed out and unavailable repeatedly.  In both instances, we found restarting the workstations remedied the problems. 

Jesse,

I am working in an environment with a large number of client machines, just wondering if there is something I need to be aware of based on this statement from Rhonda V: "This is the fix we applied days ago.  Mark said it's only good for approximately 15 workstations or less and that a larger network would create havoc so I'm mentioning this, too.  It fixed the problem we were experiencing so that the load times are nearly instantaneous."

Do you by chance have any details on what is being referenced? I would like to start applying this through our network.

Thanks.

I'm referencing the regedit that Jesse Gordon has given above.  Mark (Sage Senior Analyst) gave me the same registry edit to apply.  But Mark also said it would cause havoc if larger networks (more than approximately 15 workstations) applied this fix.  I was surprised that Jesse Gordon posted this because I thought doing so could be dangerous for some.  This is why I mentioned Mark's statement about larger nettworks because it might be important.