Problem / Bug:
For the last one and a half day I have been investigating a very curious problem. On one Windows XP machine here on our company network (my machine) the following line of code fails without any exceptions thrown:
The test.txt file is there. It opens normally when I double click it. Furthermore I can open it from Java using the (platform specific) Runtime API code:
Runtime.getRuntime().exec("rundll32 url.dll,FileProtocolHandler C:\\test.txt");
Also, if I invite some other user to log on to my machine and run the test application, it does work for him. I have created a new (local) account and for that account it did work. If i log onto some other machine with my network account and run the test application there, it works normally. Only on this specific machine with this specific account does the problem occur.
The machine is a Windows XP machine with SP3 applied and all patches installed, also the optional ones.
An interesting thing is that if I put the local test account, for which the test app is working, in the local Administrators group, suddenly this account has the problem as well. If I remove it from the Administrators group, the problem disappears again. Very strange. It must have something to do with profiles/policies/permissions… but what? I have no idea.
I am giving up on this for now because it’s eating so much time, but I will post a link to this message around in some relevant places and invite anyone seeing similar behaviour to post their findings here. Together we may be able to crack this nut.
- Desktop.open() fails without throwing any exception
- Desktop.isDesktopSupported() returns true
- Runtime.exec() does work
- Occurs for some user account, but not for others
- Windows file associations etc. all normal, app launches when double-clicking file in Windows.