Running on Windows7 I had problems with TortoiseSVN, I was unable to rename, move and such. Solution for this is to run Windows Explorer as administrator.
Initially I could also have checked out my working folder in the home directory of my own user, that should also solve the problem without the need to “Run As Administrator”
At IBM Hursley attending a workshop and having one-to-one meetings with WebSphere gurus together with Dino. Here just outside IBM Hursley.
At the Innovation Center, innovative clock…
Leaving IBM for the day. This picture is taken just at the roundabout outside of the area, we are really out in the backcountry
A bit further down, sheeps. Compared to IBM Hursley the main office of IBM in Norway is downtown.
Close to the end of the day, testing the Stonehenge Old Smokey, good one!
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!
Trying to configure Collabnet to authenticate using LDAP following the guideline at http://blogs.collab.net/subversion/subversion_ldap.
Got the error:
Invalid command 'AuthLDAPAuthoritative', perhaps misspelled or defined by a module not included in...Fixed by reading this blog post sleeplessmonkey./../joys-of-apache-webserver-and-modules
Switch AuthLDAPAuthoritative to AuthzLDAPAuthoritative, problem solved.
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.
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.propertiesAfter 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.
While preparing for the upgrade of FileNet from 4.0 to 5.1 we decided to upgrade WebSphere in the existing development environment from 7.0 to 8.0. We therefore uninstalled WAS, and left all other FileNet installation as is. While reapplying all FileNet configuration to the new WAS installation we got a problem with the Content Engine. The CE System Health page reports problems and both the p8_server_error.log and p8_server_trace.log was constantly filling up with enormous amounts of data. The errors being repeated was (showing only parts of it)
FNRCE0010E - ERROR method name: masterDecryptDecode principal name: xxxUSERNAMExxxx Global Transaction: false User Transaction.....
FNRCE0010E: E_BAD_VALUE: The value given for a property or list element lies outside the permitted range or value set...
It turned out to be caused by a change of admin uid. Initally the environment was installed using uid X, but at a given time it was decided to change it to uid Y. Since the CE ear-file was configured using X and we tried to use uid Y this was causing the error. ECM Place to the rescue, see P8 CE 4.5.1 on W2K3 x64 broke?.
List out and later reapply new user using the following commands
java -jar <CE>\lib\bootstraps.jar -e <old ear file> -l
java -jar <CE>\lib\bootstraps.jar -e <old ear file> -j <new ear file>
Windows/Java/Language settings and more for sure working against each other, creating chaos
Would prefer English only if you ask me
Had an issue just now trying to start an application server running on Windows 2008. Got error messages in SystemOut such as
CWXRS0024E: Failed to write out object:
CWRLS0008E: Recovery log is being marked as failed.
CWRLS0009E: Details of recovery log failure ... (Access is denied)In addition I also experienced that the NodeAgent would not start without any obvious reason, but if I deleted all log files it started.
Turned out to be caused by me not having started the command window with the “Run as Administrator”-option. I was allowed to create files, therefore the nodeagent started, but not allowed to change existing files, therefore the nodeagent did not start until I had deleted them. The app servers did try to write to other files as well, therefore it did not do the trick for them just to delete their log files.
Even though it is fun being on Facebook, it has its downsides…so I share this for the simple reason that I want to spread the word.
*VERY IMPORTANT NEWS!* Facebooks legal department have informed me, the developer of the F.B. P u r i t y browser extension, that I am *banned* from using Facebook. This effectively means I will no longer be able to work on the F.B. Purity project. I am assuming the F.B. Purity fan page will also be shutdown when they commence the ban. They have not said when the ban will start, but it could happen at any time.
They say the reasons for the ban are:
“Facebook’s terms specifically prohibit interference with the way Facebook is rendered to its users” and that the extension doesnt connect via their “API”, which they say is the approved method for interacting with Facebook’s services.F.B. Purity does not directly access facebook’s services anyway, it is a browser extension, and by definition, it “extends” the browsers functionality, therefore it is actually the web browser itself that is accessing Facebook, and web browsers do not need an API key or license to access Facebook’s services, as Facebook is designed to run in a web browser.
If a Facebook user chooses to download and use the F.B. Purity extension, it is entirely their own choice, I am not forcing them to download it and use it. Once they’ve installed it, F.B Purity gives the user options for customizing their own view of Facebook, which they can enable or disable to their own liking. If Facebook gave their users options to turn off the most annoying features of their user interface, then a product like F.B. Purity would not be necessary at all. The success and popularity of the extension, is a sure fire sign that something is not right with Facebooks design in the first place.
Perhaps instead of punishing me by disabling my account, and initiating legal proceedings against me, they should instead take heed of the discontent of the Facebook users, and offer them a browsing experience that won’t get them searching out third party methods for switching off the sites most hated and annoying features.
They are also trying to go back on the agreement that i could name my product “Fluff Busting Purity aka F.B. P u r i t y” which was agreed upon with Facebook’s Domain Manager, the last time they threatened me with legal action. They are now saying I need to stop using FB in the name of the product and in the domain name.
For a start, Facebook do not have a worldwide claim on the 2 consecutive letters FB. There are over 64 different trademarks that have the consecutive letters FB in them that are not owned by Facebook, so how can they claim total rights to those two letters? And to try and claim that “F.B” (short for Fluff Busting) is violating their trademark, is rubbish as in trademark terms it is completely distinct from “FB”.
Facebook should be thanking me for helping them to retain their users, who if they had not found this extension would have abandoned the site a long time ago.
In order to stay up to date on future FBP news, after they have banned me, you can:
- Keep an eye on the F.B. Purity website’s news page: http://tiny-url.org/fbpnews
- Subscribe to the F.B. Purity News mailing list: http://is.gd/fbpmail
- Follow F.B. Purity on Twitter: http://twitter.com/fbpurity
- Add F.B. Purity on Google+: http://gplus.to/fbpurity
It looks like this could be the end of the road for F.B. Purity, well at least Facebook hopes it is…
What do you think I should do? Keep up the fight, or let the *expletives deleted* win?
Please help spread the word about this news, Facebook should not be allowed to get away with this. Tweet it, Write a post on fb or g+ /write a blog post about it, repost, share, like comment, etc
In case this post is deleted by Facebook, it can also be accessed at http://tiny-url.org/fbpbanned