Forms not launching from self service after migration to new app tier

Raju reported the issue of forms not launching from self service after migration to new desktop. Sure enough it was happening for me too.

192.168.10.188 - - [03/Jun/2009:23:21:22 -0400] "GET /dev60cgi/f60cgi?&appletmode=nonforms&HTMLpageTitle=&HTMLpreApplet=&code=oracle/apps/fnd/formsClient/FormsLauncher.class&width=400&height=100&archive=/OA_JAVA/oracle/apps/fnd/jar/fndforms.jar,/OA_JAVA/oracle/apps/fnd/jar/fndformsi18n.jar,/OA_JAVA/oracle/apps/fnd/jar/fndewt.jar,/OA_JAVA/oracle/apps/fnd/jar/fndswing.jar,/OA_JAVA/oracle/apps/fnd/jar/fndbalishare.jar,/OA_JAVA/oracle/apps/fnd/jar/fndaol.jar,/OA_JAVA/oracle/apps/fnd/jar/fndctx.jar,/OA_JAVA/oracle/apps/fnd/jar/fndlist.jar&gp14=jinit_appletcache&gv14=offjinit_appletcache=off&gp2=resp_app&gv2=SYSADMIN&gp3=resp&gv3=SYSTEM_ADMINISTRATOR&gp4=sec_group&gv4=STANDARD&gp5=function&gv5=FND_FNDCPQCR_SYS&gp6=other_params&gv6=&gp7=forms_url&gv7=http%3A%2F%2F11ioltp.justanexample.com%3A8029%2Fpls%2Ferppgrd2%2Ffnd_icx_launch.runforms%3FICX_TICKET%3D%26resp_app%3DSYSADMIN%26resp_key%3DSYSTEM_ADMINISTRATOR%26secgrp_key%3DSTANDARD%26start_func%3DFND_FNDCPQCR_SYS%26other_params%3D&encoding=UTF-8&gp8=error_url&gv8=http%3A%2F%2Fdev56.justanexample.com%3A8029%2FOA_HTML%2Fjsp%2Ffnd%2Ffnderror.jsp&gp12=port&gv12=6945&gp13=dbc&gv13=dev56&gp15=icx_ticket&gv15=qT_sKHY-DtwzZo6CWStyqg.. HTTP/1.1" 200 42954 0




Do you wish to force regeneration of all jar files? [No] ? Yes


Forcing generation of all product jar files.
Creating and signing every jar file can take about thirty
minutes depending on the hardware being used.
You can watch the file $APPL_TOP/admin/$TWO_TASK/log/adadmin.log to see the progress of jar file generation.

Signing product JAR files in JAVA_TOP -
$OA_JAVA
using entity DEV21_ERPDEV21 and certificate 1.

Successfully created javaVersionFile.

Generating product JAR files in JAVA_TOP -
$OA_JAVA with command:

adjava -mx512m -nojit oracle.apps.ad.jri.adjmx @$APPL_TOP/admin/$TWO_TASK/out/genjars.cmd

After regenerating jar files and logging in as administrator on my laptop, it worked fine. It did not work for Raju as he did not have administrator rights on his laptop.