A couple of gotchas on the Sametime Advanced install to watch out for
Category Sametime Advanced
Update: He he that was a fun subject line.
Here are a couple of gotchas if you should decide to undertake a Sametime Advanced installation.
1. Do not use a windows account that is longer than 12 characters. Honestly I don't know why IBM keeps doing crazy crap like this with stupid undocumented limitations. But I found an issue where things weren't running correctly, after a few installs it still didn't work correctly. Technotes on Sametime Advanced on pretty scarce, and I'm not sure anyone in support really understands Sametime Advanced so you feel pretty much alone figuring out these obscure reasons. If you see an error like this in the Windows Event Logs:
Then check your system account login name. Mine was 13 characters long and was the problem. Obviously, the error message doesn't tell you anything useful like the field holding the username or anything. Oh how do you fix it? Well as with anything Websphere based, you put yourself in a little time machine and run a batch file. In this case, I reran the ConfiugreEB batch file with a new shorter admin name, I wish I could bill IBM for the time they waste for us.
Number 2. Don't have two spaces in your install folder. 2 spaces will let it look like the installer has been successful, but in fact it will fail. To be on the safe side, don't put any spaces in your extracted installer folder.
This public service message comes to you courtesy of the "If you're going to put stuff on Websphere test it properly" club.
Update: He he that was a fun subject line.
Here are a couple of gotchas if you should decide to undertake a Sametime Advanced installation.
1. Do not use a windows account that is longer than 12 characters. Honestly I don't know why IBM keeps doing crazy crap like this with stupid undocumented limitations. But I found an issue where things weren't running correctly, after a few installs it still didn't work correctly. Technotes on Sametime Advanced on pretty scarce, and I'm not sure anyone in support really understands Sametime Advanced so you feel pretty much alone figuring out these obscure reasons. If you see an error like this in the Windows Event Logs:
( BRKR_SCCS.default ) Source field ''410064006d0069006e006900730074007200610074006f007200'' is too long for a target field of length '12' when converting from unicode to codepage '850'.
Then check your system account login name. Mine was 13 characters long and was the problem. Obviously, the error message doesn't tell you anything useful like the field holding the username or anything. Oh how do you fix it? Well as with anything Websphere based, you put yourself in a little time machine and run a batch file. In this case, I reran the ConfiugreEB batch file with a new shorter admin name, I wish I could bill IBM for the time they waste for us.
Number 2. Don't have two spaces in your install folder. 2 spaces will let it look like the installer has been successful, but in fact it will fail. To be on the safe side, don't put any spaces in your extracted installer folder.
This public service message comes to you courtesy of the "If you're going to put stuff on Websphere test it properly" club.
| Permalink | 
Comments
Posted by Gab Davis At 03:44:12 AM On 04/27/2010 | - Website - |
Posted by Ben Williams At 04:12:30 AM On 04/27/2010 | - Website - |