web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Dynamics 365 by Manish / Error connecting to LCS Rep...

Error connecting to LCS Repo/ GlobalRepo: Sorry, something went wrong The authentication process was not successful. Please contact your system administrator.

ManishMoothedath Profile Picture ManishMoothedath 7
After moving to service update 10.0.23, For customer hosted environments , users are not able to open Global repository/RCS repository/LCS repository and it fails with error message "Sorry, something went wrong The authentication process was not successful. Please contact your system administrator."
Steps to reproduce the error:
  1. Organization administration -> Workspaces -> Electronic Reporting
  2. Click on Repositories under a Configuration Provider
  3. Click on Global/RCS repository and then Open (from the top bar)
  4. Alternatively, click on Add and create repository for RCS.
  5. Click on the link from dialog box.
Workaround:
Execute this SQL script against the environment database. This should only be executed once you follow the reproduction steps at least once.
BEGIN TRANSACTION [T1] 
BEGIN TRY 
        -- Step 1. Get correct certificate name from RCS appkey 
        DECLARE @RCS_APPKEY NVARCHAR(100) 
        SET @RCS_APPKEY = (SELECT APPKEY FROM SYSOAUTHCONFIGURATION WHERE SECURERESOURCE = 'http://configure.global.dynamics.com') 

        IF @RCS_APPKEY LIKE 'CN=%' 
                SET @RCS_APPKEY = SUBSTRING(@RCS_APPKEY, 4, LEN(@RCS_APPKEY)-3) 

        -- Step 2. Update SysOAuthConfiguration with correct appkey 
        UPDATE SYSOAUTHCONFIGURATION SET APPKEY = @RCS_APPKEY WHERE SECURERESOURCE IN ('https://lcsapi.lcs.dynamics.com', 'http://configure.global.dynamics.com') 

        COMMIT TRANSACTION [T1] 
END TRY 
BEGIN CATCH 
        ROLLBACK TRANSACTION [T1] 
END CATCH 


source - LCS Details for issue 643616 (dynamics.com)

Comments

*This post is locked for comments