Portal 6.1.5 deployment manager federation fails - Websphere

This is a discussion on Portal 6.1.5 deployment manager federation fails - Websphere ; ./ConfigEngine.sh cluster-node-config-pre-federation -DWasPassword=wasadmin (the DM password again) In both cases, I receive the following credential error: [12/02/09 16:10:00.296 EST] ssl.disable.url.hostname.verification.CWPKI0027I Created admin client: com.ibm.ws.management.AdminClientImpl@6f746f74 Created config Service Proxy: com.ibm.websphere.management.configservice.ConfigS erviceProxy@17701770 CELL: myCell NODE: myNode com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Portal 6.1.5 deployment manager federation fails

  1. Portal 6.1.5 deployment manager federation fails

    ./ConfigEngine.sh cluster-node-config-pre-federation -DWasPassword=wasadmin (the DM password again)

    In both cases, I receive the following credential error:

    [12/02/09 16:10:00.296 EST] ssl.disable.url.hostname.verification.CWPKI0027I
    Created admin client: com.ibm.ws.management.AdminClientImpl@6f746f74
    Created config Service Proxy: com.ibm.websphere.management.configservice.ConfigS erviceProxy@17701770
    CELL: myCell
    NODE: myNode
    com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:473)
    at com.ibm.wkplc.was.registry.AdminConfigRegistry.get ExistingRegistry(AdminConfigRegistry.java:104)
    at com.ibm.wkplc.models.compregistry.ResourceWidget.s aveResourceToAdminConfig(ResourceWidget.java:358)
    at com.ibm.wkplc.models.compregistry.GenerateNodeRegi stryXML.syncCacheToRegistry(GenerateNodeRegistryXM L.java:430)
    at com.ibm.wkplc.models.compregistry.RegistryHelper.u ploadRegistryToWAS(RegistryHelper.java:87)
    at com.ibm.wps.config.ConfigEngineUtils.syncRegistryI fRequired(ConfigEngineUtils.java:608)
    at com.ibm.wps.config.ConfigEngine.process(ConfigEngi ne.java:705)
    at com.ibm.wps.config.ConfigEngine.main(ConfigEngine. java:247)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at com.ibm.wps.config.launch.ConfigEngineLauncher.pro cess(ConfigEngineLauncher.java:273)
    at com.ibm.wps.config.launch.ConfigEngineLauncher.mai n(ConfigEngineLauncher.java:315)
    Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:8 24)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:792 )
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:582)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:409)
    at $Proxy0.invoke(Unknown Source)
    at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:205)
    at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:448)
    ... 18 more
    com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:473)
    at com.ibm.wkplc.was.registry.AdminConfigRegistry.get ExistingRegistry(AdminConfigRegistry.java:104)
    at com.ibm.wkplc.models.compregistry.ResourceWidget.s aveResourceToAdminConfig(ResourceWidget.java:358)
    at com.ibm.wkplc.models.compregistry.GenerateNodeRegi stryXML.syncCacheToRegistry(GenerateNodeRegistryXM L.java:430)
    at com.ibm.wkplc.models.compregistry.RegistryHelper.u ploadRegistryToWAS(RegistryHelper.java:87)
    at com.ibm.wps.config.ConfigEngineUtils.syncRegistryI fRequired(ConfigEngineUtils.java:608)
    at com.ibm.wps.config.ConfigEngine.process(ConfigEngi ne.java:705)
    at com.ibm.wps.config.ConfigEngine.main(ConfigEngine. java:247)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at com.ibm.wps.config.launch.ConfigEngineLauncher.pro cess(ConfigEngineLauncher.java:273)
    at com.ibm.wps.config.launch.ConfigEngineLauncher.mai n(ConfigEngineLauncher.java:315)
    Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:8 24)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:792 )
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:582)
    at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:409)
    at $Proxy0.invoke(Unknown Source)
    at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:205)
    at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:448)
    ... 18 more
    Local registry is out of the sync with the application server. Synchronization must be performed before any configuration can continue.
    Please verify your WAS connection properties and retry the operation. Current input:
    WasUserId: uid=wpsadmin,o=defaultWIMFileBasedRealm
    WasPassword: PASSWORD_REMOVED
    WasRemoteHostName: mydmgr.myhost.com.au
    WasSoapPort: 8879
    CellName: MyCell
    NodeName: MyNode


    I really don't understand what is wrong here. I've tried the passwords for both the local WAS and the DM and neither of them work. I guess my question is, is this an issue with 6.1.0.3, or have I done something wrong even though I'm following two documents? It's saying that the Local registry is out of sync with the application server. Is this an issue, and if so, how do I make them sync again?

    All help will be appreciated!
    Thanks.

  2. Re: Portal 6.1.5 deployment manager federation fails

    On Dec 2, 6:25*am, Jen_C wrote:
    > *./ConfigEngine.sh cluster-node-config-pre-federation -DWasPassword=wasadmin (the DM password again)
    >
    > In both cases, I receive the following credential error:
    >
    > [12/02/09 16:10:00.296 EST] ssl.disable.url.hostname.verification.CWPKI0027I
    > Created admin client: com.ibm.ws.management.AdminClientImpl@6f746f74
    > Created config Service Proxy: com.ibm.websphere.management.configservice.ConfigS erviceProxy@17701770
    > CELL: myCell
    > NODE: myNode
    > com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:473)
    > * * * * at com.ibm.wkplc.was.registry.AdminConfigRegistry.get ExistingRegistry(AdminConfigRegistry.java:104)
    > * * * * at com.ibm.wkplc.models.compregistry.ResourceWidget.s aveResourceToAdminConfig(ResourceWidget.java:358)
    > * * * * at com.ibm.wkplc.models.compregistry.GenerateNodeRegi stryXML.syncCacheToRegistry(GenerateNodeRegistryXM L.java:430)
    > * * * * at com.ibm.wkplc.models.compregistry.RegistryHelper.u ploadRegistryToWAS(RegistryHelper.java:87)
    > * * * * at com.ibm.wps.config.ConfigEngineUtils.syncRegistryI fRequired(ConfigEngineUtils.java:608)
    > * * * * at com.ibm.wps.config.ConfigEngine.process(ConfigEngi ne.java:705)
    > * * * * at com.ibm.wps.config.ConfigEngine.main(ConfigEngine. java:247)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.pro cess(ConfigEngineLauncher.java:273)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.mai n(ConfigEngineLauncher.java:315)
    > Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficientor empty credentials.
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:8 24)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:792 )
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:582)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:409)
    > * * * * at $Proxy0.invoke(Unknown Source)
    > * * * * at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:205)
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:448)
    > * * * * ... 18 more
    > com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:473)
    > * * * * at com.ibm.wkplc.was.registry.AdminConfigRegistry.get ExistingRegistry(AdminConfigRegistry.java:104)
    > * * * * at com.ibm.wkplc.models.compregistry.ResourceWidget.s aveResourceToAdminConfig(ResourceWidget.java:358)
    > * * * * at com.ibm.wkplc.models.compregistry.GenerateNodeRegi stryXML.syncCacheToRegistry(GenerateNodeRegistryXM L.java:430)
    > * * * * at com.ibm.wkplc.models.compregistry.RegistryHelper.u ploadRegistryToWAS(RegistryHelper.java:87)
    > * * * * at com.ibm.wps.config.ConfigEngineUtils.syncRegistryI fRequired(ConfigEngineUtils.java:608)
    > * * * * at com.ibm.wps.config.ConfigEngine.process(ConfigEngi ne.java:705)
    > * * * * at com.ibm.wps.config.ConfigEngine.main(ConfigEngine. java:247)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.pro cess(ConfigEngineLauncher.java:273)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.mai n(ConfigEngineLauncher.java:315)
    > Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficientor empty credentials.
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:8 24)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:792 )
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:582)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:409)
    > * * * * at $Proxy0.invoke(Unknown Source)
    > * * * * at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:205)
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:448)
    > * * * * ... 18 more
    > Local registry is out of the sync with the application server. *Synchronization must be performed before any configuration can continue.
    > Please verify your WAS connection properties and retry the operation. *Current input:
    > WasUserId: uid=wpsadmin,o=defaultWIMFileBasedRealm
    > WasPassword: PASSWORD_REMOVED
    > WasRemoteHostName: mydmgr.myhost.com.au
    > WasSoapPort: 8879
    > CellName: MyCell
    > NodeName: MyNode
    >
    > I really don't understand what is wrong here. *I've tried the passwordsfor both the local WAS and the DM and neither of them work. *I guess my question is, is this an issue with 6.1.0.3, or have I done something wrong even though I'm following two documents? *It's saying that the Local registry is out of sync with the application server. *Is this an issue, and if so, how do I make them sync again?
    >
    > All help will be appreciated!
    > Thanks.


    It is more likely that you just write the wrong user id or password,
    re re re re check the WasPassword
    com.ibm.websphere.management.exception.ConfigServi ceException:
    javax.management.JMRuntimeException: ADMN0022E: Access is denied for
    the resolve operation on ConfigService MBean because of insufficient
    or empty credentials.

  3. Re: Portal 6.1.5 deployment manager federation fails

    On Dec 2, 6:25*am, Jen_C wrote:
    > *./ConfigEngine.sh cluster-node-config-pre-federation -DWasPassword=wasadmin (the DM password again)
    >
    > In both cases, I receive the following credential error:
    >
    > [12/02/09 16:10:00.296 EST] ssl.disable.url.hostname.verification.CWPKI0027I
    > Created admin client: com.ibm.ws.management.AdminClientImpl@6f746f74
    > Created config Service Proxy: com.ibm.websphere.management.configservice.ConfigS erviceProxy@17701770
    > CELL: myCell
    > NODE: myNode
    > com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:473)
    > * * * * at com.ibm.wkplc.was.registry.AdminConfigRegistry.get ExistingRegistry(AdminConfigRegistry.java:104)
    > * * * * at com.ibm.wkplc.models.compregistry.ResourceWidget.s aveResourceToAdminConfig(ResourceWidget.java:358)
    > * * * * at com.ibm.wkplc.models.compregistry.GenerateNodeRegi stryXML.syncCacheToRegistry(GenerateNodeRegistryXM L.java:430)
    > * * * * at com.ibm.wkplc.models.compregistry.RegistryHelper.u ploadRegistryToWAS(RegistryHelper.java:87)
    > * * * * at com.ibm.wps.config.ConfigEngineUtils.syncRegistryI fRequired(ConfigEngineUtils.java:608)
    > * * * * at com.ibm.wps.config.ConfigEngine.process(ConfigEngi ne.java:705)
    > * * * * at com.ibm.wps.config.ConfigEngine.main(ConfigEngine. java:247)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.pro cess(ConfigEngineLauncher.java:273)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.mai n(ConfigEngineLauncher.java:315)
    > Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficientor empty credentials.
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:8 24)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:792 )
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:582)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:409)
    > * * * * at $Proxy0.invoke(Unknown Source)
    > * * * * at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:205)
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:448)
    > * * * * ... 18 more
    > com.ibm.websphere.management.exception.ConfigServi ceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficient or empty credentials.
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:473)
    > * * * * at com.ibm.wkplc.was.registry.AdminConfigRegistry.get ExistingRegistry(AdminConfigRegistry.java:104)
    > * * * * at com.ibm.wkplc.models.compregistry.ResourceWidget.s aveResourceToAdminConfig(ResourceWidget.java:358)
    > * * * * at com.ibm.wkplc.models.compregistry.GenerateNodeRegi stryXML.syncCacheToRegistry(GenerateNodeRegistryXM L.java:430)
    > * * * * at com.ibm.wkplc.models.compregistry.RegistryHelper.u ploadRegistryToWAS(RegistryHelper.java:87)
    > * * * * at com.ibm.wps.config.ConfigEngineUtils.syncRegistryI fRequired(ConfigEngineUtils.java:608)
    > * * * * at com.ibm.wps.config.ConfigEngine.process(ConfigEngi ne.java:705)
    > * * * * at com.ibm.wps.config.ConfigEngine.main(ConfigEngine. java:247)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.ja va:263)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > * * * * at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:79)
    > * * * * at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
    > * * * * at java.lang.reflect.Method.invoke(Method.java:618)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.pro cess(ConfigEngineLauncher.java:273)
    > * * * * at com.ibm.wps.config.launch.ConfigEngineLauncher.mai n(ConfigEngineLauncher.java:315)
    > Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the resolve operation on ConfigService MBean because of insufficientor empty credentials.
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:8 24)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:792 )
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:582)
    > * * * * at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:409)
    > * * * * at $Proxy0.invoke(Unknown Source)
    > * * * * at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:205)
    > * * * * at com.ibm.websphere.management.configservice.ConfigS erviceProxy.resolve(ConfigServiceProxy.java:448)
    > * * * * ... 18 more
    > Local registry is out of the sync with the application server. *Synchronization must be performed before any configuration can continue.
    > Please verify your WAS connection properties and retry the operation. *Current input:
    > WasUserId: uid=wpsadmin,o=defaultWIMFileBasedRealm
    > WasPassword: PASSWORD_REMOVED
    > WasRemoteHostName: mydmgr.myhost.com.au
    > WasSoapPort: 8879
    > CellName: MyCell
    > NodeName: MyNode
    >
    > I really don't understand what is wrong here. *I've tried the passwordsfor both the local WAS and the DM and neither of them work. *I guess my question is, is this an issue with 6.1.0.3, or have I done something wrong even though I'm following two documents? *It's saying that the Local registry is out of sync with the application server. *Is this an issue, and if so, how do I make them sync again?
    >
    > All help will be appreciated!
    > Thanks.



    Just recheck the WasPassword


+ Reply to Thread