rblog

Cannot commit changes to SVN – Collabnet SVN Server

Just had an issue when trying to commit changes to SVN. Now using Collabnet Subversion Edge 3.2.2-3395.103. Have configured authentication using LDAP, that is Active Directory. Error message when trying to commit changes

svn: E175002: Commit failed (details follow):
svn: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/svn/reponame/!svn/me'

Found this very strange since it was working without problems yesterday. Tried to restart both services several times, no help. Nothing found in the logs either.

Then trying to log on to the Edge admin console with my AD-user…not possible. Using the superuser, logged in, changed LDAP from using port 389 to 3268 as the console provides a hint to do: Hint: try 3268 for Active Directory servers . Restarted Apache and voila, up an running again.

My conclusion: AD …arrghh!

Is this true? Top 10% most viewed profile in 2012

Got an email from Linkedin saying:

Rune, congratulations! You have one of the top 10% most viewed LinkedIn profiles for 2012.

They have 200 million profiles so I my first reaction is “yeah, rrriiighht!” And then they want me to share the below text on Twitter, FB and such:

Hurray! I have one of the top 10% most viewed @LinkedIn profiles for 2012. http://www.linkedin.com/pub/profile/0/70b/01b

Confusing, first time I tried the url I got this profile http://uk.linkedin.com/pub/odi-nanka-bruce/0/70b/1, but now it is pointing to my own profile. So maybe it is true, and then either

  • WebSphere is extremly hot all around the world, and therefore people view my profile
  • A lot of people have a profile, but no connections and such, and I am part of the 10% having updated the profile

FileNet – Error during installation of Workplace XT FP1 (v 1.1.5.1)

After having successfully installed Workplace XT v 1.1.5.0 applying FP1 of Workplace XT, version 1.1.5.1 fails. The error message showing in the Install Shield is plain and simple, that is meaningless: null. In the log file I found “JVM_HOME = null”.

Reported this as a PMR which helped me solve the problem. Simply just uninstalled v 1.1.5, then installed 1.1.5.1 since it is a cumulative fix. Info from IBM:

The Workplace XT 1.1.5.1-WPXT-FP001 fix pack installs a new, complete Workplace XT 1.1.5.1 system, or upgrades an existing Workplace XT system. Workplace XT fix packs are cumulative; each fix pack contains the base release and content from all previously released fix packs.

So seen, it would be possible just to scrap the existing installation including the registry path and install Workplace XT 1.1.5.1 directly.

FileNet – Workplace fails during startup

Had an issue today after having installed the application engine and then the latest fixpack. WebSphere reported that the application started just fine, but when accessing http://my_server/Workplace it failed with a NullPointerException. Part of the stacktrace

[07.02.13 18:10:45:986 CET] 0000002e SystemOut     O Loading logging config: null

This was in test, in the dev environment where it is working SystemOut.log reported

[2/7/13 18:39:24:274 CET] 00000043 SystemOut     O Loading logging config: D:\\AEShare\\FileNet\\Config\\AE\log4j.properties

After a lot of cursing it turned out that the problem was caused by Windows and access to the share where the log4j-file was located. As a wild guess I granted access to “Everyone” and voila…it worked…Windows shares…simply hate it. WebSphere running as local system account, did not cause any problems in the dev environment, but test…don’t know why yet.

Hjem