WebSphere Lombardi Edition V7.2 on Windows 7 – beware UAC

Running IBM WebSphere Lombardi Edition (WLE) V7.2 on MS Windows 7 might cause troubles depending on the User Account Control (UAC) settings. It results in SQL5005C System Error while logging in as the WLE user as shown below:

It may also prevent WLE environment from booting up upon executing Start Servers shortcut in Windows menu.

C:\Users\jacek>"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\IBM WebSphere Lombardi Edition 7\Start Servers.lnk"
ADMU0116I: Tool information is being logged in file
           C:\IBM\Lombardi7\performance-data-warehouse\logs\twperfsvr\startServer.log
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:260)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7707E: Failed while trying to determine the Windows Service name for server: twperfsvr;
probable error executing WASService.exe: com.ibm.websphere.management.exception.AdminException: ADMU7709E: Unexpected exception while processing server: twperfsvr;
exception = java.io.IOException: Cannot run program "C:\IBM\Lombardi7\AppServer\bin\WASService.exe": CreateProcess error=740, The requested operation requires elevation.
        at com.ibm.ws.management.tools.WindowsService.getWindowsServiceNameForServer(WindowsService.java:221)
        at com.ibm.ws.management.tools.WindowsService.<init>(WindowsService.java:154)
        at com.ibm.ws.management.tools.WindowsService.getWindowsServiceInstance(WindowsService.java:139)
        at com.ibm.ws.management.tools.WsServerController.getWindowsServiceIfAvailable(WsServerController.java:161)
        at com.ibm.ws.management.tools.WsServerLauncher.getWindowsServiceIfAvailable(WsServerLauncher.java:157)
        at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindows(WsServerController.java:129)
        at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:138)
        ... 5 more
ADMU0116I: Tool information is being logged in file
           C:\IBM\Lombardi7\process-center\logs\twprocsvr\startServer.log
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:600)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:260)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7707E: Failed while trying to determine the Windows Service name for server: twprocsvr;
probable error executing WASService.exe: com.ibm.websphere.management.exception.AdminException: ADMU7709E: Unexpected exception while processing server: twprocsvr;
exception = java.io.IOException: Cannot run program "C:\IBM\Lombardi7\AppServer\bin\WASService.exe": CreateProcess error=740, The requested operation requires elevation.
        at com.ibm.ws.management.tools.WindowsService.getWindowsServiceNameForServer(WindowsService.java:221)
        at com.ibm.ws.management.tools.WindowsService.<init>(WindowsService.java:154)
        at com.ibm.ws.management.tools.WindowsService.getWindowsServiceInstance(WindowsService.java:139)
        at com.ibm.ws.management.tools.WsServerController.getWindowsServiceIfAvailable(WsServerController.java:161)
        at com.ibm.ws.management.tools.WsServerLauncher.getWindowsServiceIfAvailable(WsServerLauncher.java:157)
        at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindows(WsServerController.java:129)
        at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:138)
        ... 5 more

Without delving into Windows security settings, which I hardly understand, I’ve been told that it’s pretty safe to disable UAC completely that eventually sorts out the aforementioned issues.

Go to Control Panel\User Accounts and Family Safety\User Accounts and select Change User Account Control settings.

You may also search for “uac” in Search Control Panel search field.

While in the User Account Control Settings, lower the bar down to Never notify, which effectively turns the UAC off (at least to the level of not being too intrusive and harmful to WLE).

Repeat the steps for the DB2 account created while installing WLE, namely WSLE (the default password is L0mbard1#BPM as described in DB2 failure during WLE 7.2 Express Installation and Configuration (Simple Installation)).

Restart the system as pointed out by the message after you’ve changed the UAC settings for each user.

With the changes you should never have to deal with the issues again. Problem solved. Happy WLEing!

Be Sociable, Share!
This entry was posted in WebSphere.

Leave a Reply

%d bloggers like this: