Sametime and Domino LDAP using directory assistance

I recently had a problem with IBM Sametime v8.5.2 and with a Domino LDAP that were using directory assistance.

I was installing Sametime and everything went fine until I installed the Meetings component... After I installed the Meeting component, I tried to login in Meeting and I was getting the following exception:

0000000a ContextManage E SECJ0270E: Failed to get actual credentials. The exception is javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient Access Rights]; remaining name ''

After some debugging, the problem seemed that the bind user didn't have access to one of the databases used on directory assistance. However, the user HAD access and could open the database...

In a desperation try, we just removed, in the directory assistance database that was giving problems, the option "LDAP Clients" from the property "Perform LDAP searches for" and, after restarting the LDAP task on Domino, the users started to be able to login on Sametime Meetings.... Very Strange...

I have to say that the following technote was very useful to understand and debug the problem: http://www-01.ibm.com/support/docview.wss?uid=swg21318176

IBM Sametime 8.5.2 - Media Server installation

Hello everyone,

I recently had a problem installing the Media Manager (or Media Server, I think that IBM si still confused about how to call it) component of IBM Sametime 8.5.2 on a Windows 2008 R2 server.

In the middle of the installation an error popped up whit the message: "Not enough storage is available to process this command".

My first idea was that I had not enough disk space - but I had like 5 GB available, which I thought it was more than enough.
Then, a small search on Google told me that this message is a Windows message generally related with Virtual Memory problems.
I checked that the server was configured to manage automatically the virtual memory, so my idea was that due to the only 5GB available on disk, Windows didn't get the enough virtual memory space to install Media Server... So, I just made more space on the disk (until I had 20GB available) and restarted the Windows server.

After that I just deleted the profile folder that the failed installation created and I was then able to successfully install Sametime Media Server!!!

Regards