x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 249 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Larry Thompson

v4.50.5.0

Posted By

I have a client using WIN11 and MAS90 (v4.50.5.0) and for one work station when you launch MAS90 the tree structure "flashes" and disappears.

But if you create a new user on the same work station then tree structure appears and stays.  Also this is the only PC that this is happening on in the network.

We either have to copy over all the programs and documents over from one user to another or figure out where the launcher is stored.  There is no C:\My Documents\Sage to rename to *.old

Does anyone know where in the registry the launcher is held?  Or where the C:\My Documents\MAS90 would be?

Sincerely,

Larry Thompson | Customer Support Manager
Phone: (800) 882-6705 ext 1003
[email protected]
BCS ProSoft | Technology Consulting & Cloud Strategy

Parents
  • 0

    Thank you everyone for chiming in :) - our developer emailed me and said 

    1. From a workstation that IS working, open DFDM, and then open the SY_User table in the MAS_SYSTEM folder.  Identify the 10-digit UserKey$ for the user having the issue.
    2. Now, open the SY_Workstation table, and navigate to the WorkstationName + UserKey$ key combination.
    3. Delete this record from SY_Workstation and then close DDFM.
    4. Have that user attempt to log into that workstation again. 

    And this solved it in case anyone else wants to know.

    -Larry

Reply
  • 0

    Thank you everyone for chiming in :) - our developer emailed me and said 

    1. From a workstation that IS working, open DFDM, and then open the SY_User table in the MAS_SYSTEM folder.  Identify the 10-digit UserKey$ for the user having the issue.
    2. Now, open the SY_Workstation table, and navigate to the WorkstationName + UserKey$ key combination.
    3. Delete this record from SY_Workstation and then close DDFM.
    4. Have that user attempt to log into that workstation again. 

    And this solved it in case anyone else wants to know.

    -Larry

Children
No Data

*Community Hub is the new name for Sage City