We have discovered the cause of the SMT login issue. It was due to the SSP2 Application not being deployed to the website. I reviewed the SuiteCommerce release notes and found the following statement in the 2019.2 SuiteCommerce release notes “_Expanded SSP Application support for SuiteScript 2.0. This change impacts all Commerce web store SuiteApp installation and setup procedures.”_ We are changing the URL root to something like “/sca”. I noticed the SSP2 application record also has a URL root field, but it doesn’t look like it’s used, or at least not SMT. I changed the URL root in the SSP2 application to “/sca-ss2”. When I logged into SMT, the errors returned. When I examined the error, I noticed it was looking for “/sca_ss2". It appears the code is taking the SSP application’s URL root and appending “_ss2” instead of using the URL root in the SSP2 application record.

Thanks for sharing the solution of this issue, I have not had this issue however, in order to make the cases work on my account section, you also need to deploy the SSP2 and both root url have to match, in your case, /sca for ssp1 and /sca_ss2 for ssp2