After upgrading to 4.9, and installing Javelin-4.8.130.0, Users that do not have full administrative permissions are unable to launch Javelin using their user account. However, they can successfully run the Javelin batch scripts. They just cannot access the Javelin UI to modify and create new flows. Javelin does launch for the System Admin, which has full admin privileges, so this seems to be a permissions issue. The Windows Application log shows Javelin crashing for the non-admin user.
Release : 4.9
Component : CA Test Data Manager - Javelin
For the non-admin account, javelin requires write access to the "E:\ProgramData" directory. You have the option of modifying the Security permissions of the directory and granting write access, or you can redirect javelin to use the original directory by modifying Javelin.config file in installation directory and changing property JavelinProgramDataDirectory to "C:\ProgramData".