Error using wsadmin to check-out Lotus Connections configuration

February 24, 2011 1 Comment

After reading Dave Hay’s article (WASX7015E seen when using WSAdmin to work with Lotus Connections 3.0 configuration) on problems with checking out Lotus Connections configuration using wsadmin commands it reminded me of a similar “Doh! moment” I had a few weeks ago doing the same thing, which I think is worth sharing as it might help someone resolve the problem more quickly than I did.

I started the wsadmin client using the following command (so far so good):

cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/
./wsadmin.sh -lang jython -user wasadmin -password ********* -port 8879

WASX7209I: Connected to process “dmgr” on node connectionsCellManager01 using SOAP connector; The type of process is: DeploymentManager
WASX7031I: For help, enter: “print Help.help()”

Then from the wsadmin prompt I went to check-out the Files configuration:

wsadmin>execfile(“/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/bin_lc_admin/filesAdmin.py”)

Unfortunately it returned this error:

WASX7015E: Exception running command: “execfile(“/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/bin_lc_admin/filesAdmin.py”)”; exception information:
com.ibm.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File “”, line 1, in ?
File “/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/bin_lc_admin/filesAdmin.py”, line 14, in ?
ImportError: no module named lotusConnectionsCommonAdmin

I tried running the commands several more times, but the same error occurred each time (definition of insanity: doing the same thing over and over again and expecting different results), even searching Google didn’t help pinpoint the issue.

Anyway, eventually I found my mistake, the directory I’d run the wsadmin command from was wrong.
I’d run it from:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/

When it should have been:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/

As soon as I ran the wsadmin command from the correct directory it all just worked

Filed under Connections Tagged with , ,

Blog error when trying to “Notify Other Users”

September 25, 2010 3 Comments

A Blog owner was trying to notify the members of the Community (to which the Blog belonged) about a blog post by clicking on “More Actions” -> “Notify Other Users” and then selecting all from the  “Pick From Community” list but it caused the error shown below when they clicked send:

Notification could not be sent because the email address 123456AB-A1B2-1234-1234-12345678ABCD was not valid. Check the spelling of the email address and try again.

The error message is not very helpful because there was no way for the end user to be able to know which of the people they had selected was causing the error (as you can see the error returned a hex string instead of an email address) and they couldn’t proceed until it was resolved.

The hex string in the error is the UUID of the person affected, which meant I needed to find the persons name from their UUID which I did using the wsadmin command line tool.

1. Load the wsadmin client:

./wsadmin.sh -lang jython -user <username> -password <password> -port 8879

2. Load the Communities script:

execfile(“/opt/IBM/WebSphere/AppServer/profiles/Dmgr/config/bin_lc_admin/communitiesAdmin.py”)

3. Run the fetch command to return all the Communities and then call the output and write it to a text file:

commList=CommunitiesService.fetchAllComm()
CommunitiesService.listCommToFile(commList,”/opt/IBM/WebSphere/commList.txt”)

4. From the text file find the name of the Community and then copy its UUID. Using the Communities UUID call the member list.

errorComm=CommunitiesService.fetchCommById(“00000001-0001-0001-0001-000000000001″)
CommunitiesService.fetchMember(errorComm)

5. Search the output for the UUID from the original error message you’ll then be able to see the name of the affected person. As a temporary work around you could avoid adding them to the notification list whilst you investigate/correct the issue with their Profile.

Filed under Connections Tagged with , ,

Follow

Get every new post delivered to your Inbox.