Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Product Migration Wizard fails with RemoteApplicationException



Product Migration Wizard fails with RemoteApplicationException: SOAP Service failed

Error Messages

RemoteApplicationException: SOAP Service failed

2015-06-25 02:12:59,157 [.PRPCWorkManager : 2] [  STANDARD] [     PegaRULES:07.10] (          internal.async.Agent) INFO    - System date: Thu Jun 25 02:12:59 CDT 2015 Total memory: 1,111,228,416 Free memory: 152,017,736 Requestor Count: 15 Shared Pages memory usage: 0%
2015-06-25 02:19:19,742 [    WebContainer : 5] [  STANDARD] [your_app:01.03.01] (orization.SessionAuthorization) ERROR your_server|  - Not adding Access Group "your_accessgroup" to runtime profile for 'operator1' No such Access Group: 'your_accessgroup' for thread STANDARD
From: (H6379D1C0709F95CD794A31F1F9798845:
        at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getBasicApplicationContext(
        at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(
        at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getPersonalApplicationContext(
        at com.pega.pegarules.session.internal.authorization.context.AuthorizationContextManagerImpl.getContext(
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.applyApplicationOperatorAuthorization(
        at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(
        at com.pega.pegarules.session.internal.authorization.Authorization.reset(
        at com.pega.pegarules.session.internal.authorization.Authorization.reset(

Steps to Reproduce

Create a product in PRPC 6 and try to migrate to Pega 7.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment. Application user is not mapped to PegaDiagnosticUser role.


This issue is resolved by making the following change to the operating environment: 

Map Application user to PegaDiagnosticUser role.

In your source system, verify that the PegaDiagnosticUser security role is defined for your Pega server node. Normally, this security role is configured during installation of your PRPC server. 

Also confirm that an instance of the Data-Admin-System-Security class exists with this security role as the key. The user and password information must match the ones specified at server for this security role. 
Refer below PDN link for help.

Published September 16, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us