Hi all,

I get an error while trying to synchronize nodes, the application server starts fine.

I also deleted the content inside WSTEMP AND TEMP inside appsrv01 folder and dmgr01 folder.

Error on log file: insufficent privileges

Even though I can start and stop the node.

Anyone plz help.

Many thanks 

synchronization is .. syncing configuration betweeb DMGr and node hence start/stop previllage is not enough.

try with an account that has admin previllages.

I have but still doesn't let me.

Does this mean I have to delete and create a new node? 

Hi Bishal,

  No!!!! you don't need to delete the node.
 
  How are you trying to synchronize node, from console or from command line (synchNode)?

  could you sync at some point? or has occurred after some configuration change?

regards,

Hi Gabriel,

No I cannot synch the node even with the highest privileges.

 

Excuse me Bishal,

  to help you I need to know the next questions:

  How are you trying to synchronize node, from Admin console or from command line (synchNode)?

  The problem has occurred after some configuration change (f.e enable security)? or nodes never has been synchronized.

regards,

Hi Gabriel,

I am trying to sync Node from both the command line and the console, but in vain.

I have actually followed your advice in resetting the admin name and password as I could not get logged in.

when I try to syncNode with command line, it returns back saying I do not have the privilege to do so but I can log on to the console fine with the same username and password.

I can start the server fine, but I am having difficulty with the Node. I can start it first, then I can not syn or stop it later on.

 

To be more precise, the node has not been able to synchronize since I configured the standalone active directory.

I am still perplexed as when are the details used from the active directory to login to  the console. Example if i have Bish as an active directory name, and wasadmin as a console username, when I have configured to use standalone active directory to current instead of the federated resources. When logging in which login do i use.

Because when i set the settings as standalone active directory to current and restarted the deployment, server and node - I could not log back in. I used both the logon in details i.e. Bishal / wasadmin but to no avail.

Please help. 

Sync Node command:

syncNode dmgr 5424

is the above syntax correct to sync the node 

Bishal,

  You need to check in DMGR the next ports:


    RMI - ORB_LISTENER_ADRESS
    SOAP - SOAP_LISTENER_ADRESS

  the from your node host launch synchNode command

   synchNode.sh DMGR_HOST PORT

  The PORT is depending on the conntype attribute.

  You can check default conntype attribute in

  NODE_PROFILE\properties\wsadmin.properties

  or put direcctly in command

  synchNode DMGR_HOST DMGR_PORT -conntype RMI/SOAP


  Hope this helps.

reagards,

Hi Gabriel,
Below is the syntaxs I have tried:

For deployment manager  

C:\>cd C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin

C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>startManager
ADMU0116I: Tool information is being logged in file
C:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\startServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 300

Trying to Sync the Nodes

C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>synchNode dmgr 300 -conntype SO
AP
'synchNode' is not recognized as an internal or external command,
operable program or batch file.

C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>syncNode dmgr 300 -conntype SOA
P
ADMU0116I: Tool information is being logged in file
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\syncNode.log

ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to connect to
host dmgr at port 300., resulting from: [SOAPException:
faultCode=SOAP-ENV:Protocol; msg=;
targetException=java.net.MalformedURLException]
ADMU4123E: Ensure that the Deployment Manager is running on the specified host
and port.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\syncNode.log

SyncNode.log

, resulting from: [SOAPException: faultCode=SOAP-ENV:Protocol; msg=; targetException=java.net.MalformedURLException]
[2/20/13 14:24:07:143 GMT] 00000000 AdminTool A ADMU4123E: Ensure that the Deployment Manager is running on the specified host and port.

[2/20/13 14:24:07:143 GMT] 00000000 AdminTool A ADMU1211I: To obtain a full trace of the failure, use the -trace option.

[2/20/13 14:24:07:143 GMT] 00000000 AdminTool A ADMU0211I: Error details may be seen in the file: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\syncNode.log

 

Hi Bishal,

  You are not putting the right DMGR port. The port isn't 300.

  Have you DMGR and NODE in the same machine?
 
  After start DMGR. you need to:
 
    1.- Logon in admin console.
    2.- Go to System Administration->Deployment Manager->Ports
    3.- Check SOAP_CONNECTOR_ADDRESS

  Or go to:
 
   C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\CELNAME\nodes\CELLNODENAME\serverindex.xml    
     
  Open the file a search for SOAP_CONNECTOR_ADDRESS
    

  Then from node launch:
 
    C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\synchNode.bat DMGR_HOST_IP SOAP_CONNECTOR_ADDRESS
    
  If you have DMGR and NODE in the same machine:
 
    C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\synchNode.bat localhost SOAP_CONNECTOR_ADDRESS
    
  Tell us if you can synchronize.
 
Regards

Gabriel,

Thanks very much, this has resolved to synched my Node.

I appreciate your patience and answers.

Many thanks,
Bish 

Great Bishal!!!!! What a good news, congratulations.

Glad to help.

Regards

Now then back to just configuring a database and Lotus Connection...
hhahaha

This will surely take me another year...