Skip to content

x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 4 replies
  • Subscribers 102 subscribers
  • Views 287 views
  • Users 0 members are here
Browse Forums
Announcements
320
topics
380
replies
Business Object Interface
1k
topics
8k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
8k
replies
General Discussion
1k
topics
4k
replies
Partner Cloud
58
topics
118
replies
Payroll, Time Tracking, and Job Cost
817
topics
1k
replies
Reporting and Analytics
1000
topics
3k
replies
Sage CRM for Sage 100
169
topics
370
replies
Technical and Installation
2k
topics
10k
replies
Year-end Forum
93
topics
245
replies
sevendogzero

Sage 2023 - Admin stuff - sy_workstation / sessions.pvk

Posted By

In our old Sage 2014 (ProvideX) we would periodically make sure all the users were out. Shut down the Sage Server and delete

the following files.

\SY\SY_Workstation

\Home\Lib\_appserv\sessions.pvk

Are there any suggested maintenance chores like this in Sage 2023?

Parents
  • 0

    If you're still running the Providex version, those are still valid

  • 0 in reply to bethbowers

    Can you tell me what those files do? 

    I do not find SY_Workstation on my 2022 Sage 100 

    The sessions.pvk file is 15MB file, so not big compared to others like 1.8GB audit files.  

    When you say if you are still running Providex, does that insinuate you would say to get off Providex and get on SQL? 

    Thank you for sharing any insight you can, 


    Chris

  • 0 in reply to Beevet

    These are old notes which I maintained for Sage 2014, but I believe the records in the sessions table. is a reflection of what is listed in the Sage 2014 providex application configuration utility "Sessions" tab.

    On occasion we would have a network issue that left open sessions. These sessions could not be ended using master console so I would log off all the users on our Terminal Server, then I could then stop the application server.

    Then I would delete the sessions.pvk file in "\MAS90\Home\Lib\_appserv" folder. The sessions would be cleared, and the table would be created again after the first user logged into Sage.

    The sy_workstation table is in the \mas90\sy folder. I haven't seen the file in Sage 2023, so I thought it might be in a different

    location on Sage 2023.

    I did a weekly offsite backup where I removed all the users, shut down the providex db server and did a backup with no

    users connected. Then I zipped the backup and copied into our offsite cloud server.

    So far Sage 2023 has been operating very nicely. Our current environment is Server 2019 and Sage 2023 in a Remote Desktop Services platform.

    We have three RDS session servers with approx 20-30 users on each session server.

    Not going to the SQL version.

    .

  • 0 in reply to sevendogzero

    We typically only do this when there are issues with something related to connectivity, but I don't see any harm in doing it as part of routine maintenance.

    https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=224924650066909

Reply Children
No Data

*Community Hub is the new name for Sage City