IBM Support

Profiles WSADMIN command fails with NameError: bAskForNodeComm error

Technote (troubleshooting)


The WSADMIN ProfilesService.activateUserByUserId command fails with the error:

exception information: exception from Jython:
Traceback (innermost last):
File "<input>", line 1, in ?
File "", line 676, in activateUserByUserId
File "", line 803, in getMBeanName
File "", line 887, in promptAdminForBean
NameError: bAskForNodeComm

NOTE: this has also been reported with other ProfilesService commands, such as inactiveUserByUserId and publishUserData. However, the line specified by the error in the file will be different.

Resolving the problem

The root of the issue is that the user is never prompted to choose which node to run the command on. The following workaround can be applied:

- Start wsadmin as you normally would and run the command execfile("").
- Next run the command execfile("").
- Now try the ProfilesService.activateUserByUserId command again.

If that doesn't work, repeat the steps above, only this time try switching the execfile commands.

This issue does not occur in 4.5 CR2.

Document information

More support for: IBM Connections

Software version: 4.5

Operating system(s): Windows

Reference #: 1663535

Modified date: 03 February 2014