x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 1 reply
  • Subscribers 93 subscribers
  • Views 137 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
758
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
ValerieH

Sage 2023 Upgrade SP3 attempted reverted back to Sp1 with no SQL security integration Issues

Posted By

I upgraded a client from 2022 to 2023 SP3 at the time with the SQL security integration and had issues.   So I restored the data, uninstalled V2023 Sp3 and put SP1 on with no integration.  Now we are running into issues with BI and Customer account code change and I am now needing to upgrade.   I believe I am comfortable doing this upgrade however when I went to do it I see that even though i removed the Sage300Vaultowner and the Sage300Vault and Sage300Store DB's there remains some users in SQL from my attempt ie ##s3_login_Admin##Sage300Vault.  I am concerned that this is going to cause me issues trying to put Sp5 on and recreating the Sage300Vaultowner and the Sage300Vault and Sage300Store DB's.  I assume I could just use another name but I would rather clean it up.   Can the current users that are there that start with ##s3_Login be deleted? prior to me starting the upgrade?   Anyone have experience with this.

Parents
  • 0

    Hi  although I've never been through the same process you have, being on 2023 SP1 shouldn't require any of the ##s3_login's.  I would disable these logins, confirm the system still works normally, and if it does, confidently delete the accounts so they can be re-created fresh.

    If you're going to all the effort of SP5, why not get any third party codes you need and go 2024 latest service pack and get the awesome Financial Reporter for Web + an extra year of support?

Reply
  • 0

    Hi  although I've never been through the same process you have, being on 2023 SP1 shouldn't require any of the ##s3_login's.  I would disable these logins, confirm the system still works normally, and if it does, confidently delete the accounts so they can be re-created fresh.

    If you're going to all the effort of SP5, why not get any third party codes you need and go 2024 latest service pack and get the awesome Financial Reporter for Web + an extra year of support?

Children
No Data

*Community Hub is the new name for Sage City