Category Archives: Network

load: class oracle/apps/fnd/formsClient/FormsLauncher.class not found

Posted by on May 3, 2012 No comments

Problem:

After installing fresh Release 12 instance (12.1.3), attempted to log on to application from client PC (Windows XPSP3). Was able to log on to R12, but forms could not be launched. The following message was displayed on the Java console:

load: class oracle/apps/fnd/formsClient/FormsLauncher.class not found.
java.lang.ClassNotFoundException: oracle.apps.fnd.formsClient.FormsLauncher.class
	at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.ClassNotFoundException: oracle.apps.fnd.formsClient.FormsLauncher.class

However, other client machines (Windows 7) were able to log on and launch the forms.

Solution:

After enabling logging (Control Panel > Java > Advanced tab > Debugging, check all options), the ‘java.net.SocketException: Connection reset’ error was seen in the Java console. This indicated a network issue rather than a Java or browser issue. The EBS server (192.168.63.49) was on a different network from the client PCs (200.65.1.x). Therefore, a network route was added to keep the connection alive:

route add 192.168.63.0 mask 255.255.255.0 200.65.1.1 -p

Login failed for user ‘sa’

Posted by on January 8, 2009 No comments

Login failed for user ‘sa’

Problem:

When logging on to Data Mover as VP1, the following error appears:

File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.

Solution:

Log on to Data Mover as user sa and run the following lines from fsdmomss.dms:

UPDATE PSSTATUS SET OWNERID = 'sa';
 UPDATE PSOPRDEFN SET SYMBOLICID = 'sa1', OPERPSWD = OPRID, ENCRYPTED = 0;
 UPDATE PSACCESSPRFL SET ACCESSID = 'sa', SYMBOLICID = 'sa1', ACCESSPSWD = 'train', VERSION = 0, ENCRYPTED = 0;
 GRANT SELECT ON PSSTATUS TO people;
 GRANT SELECT ON PSOPRDEFN TO people;
 GRANT SELECT ON PSACCESSPRFL TO people;
REM - ENCRYPT PASSWORD
 /
 SET LOG c:tempencrypt.log;
 ENCRYPT_PASSWORD *;

References:

http://peoplesoft.ittoolbox.com/groups/technical-functional/peopletools-l/app-server-start-up-failed-2106157

Changing DNS Settings on TSTT Paradyne Router

Posted by on November 26, 2007 No comments

After setting up TSTT’s Internet Broadband, users sometimes have difficulty accessing web sites. The user must click the Refresh button several times before the site loads. By default, TSTT’s ADSL router is configured to use TSTT’s DNS server. This DNS server is not very reliable. This documentation shows how to change the DNS Settings on TSTT’s Paradyne router to point to the freely available OpenDNS servers.

Step 1:        Load the web browser (for example, Internet Explorer).

Step 2:        In the Address Bar, type http://192.168.1.1 and press Enter.

Step 3:        The web browser prompts you for a username and password to log into the router. Enter admin in both fields. Then click OK.

Step 4:        The Paradyne ADSL CPE page appears showing the router’s settings.

Step 5:        Using the menu to the left of the page, navigate to Advanced Setup > DNS > DNS Server. The DNS Server Configuration page appears.

Step 6:        By default, TSTT’s DNS Server IP addresses will appear in the fields. Make a note of the current DNS server settings in the event you need to revert to them.

After this, ensure that the Enable Automatic Assigned DNS is unchecked. Enter the following new IP addresses into the fields. Then click Save.

Primary DNS server 208.67.222.222
Secondary DNS server 208.67.220.220

After saving the changes, the router must be rebooted. This can be done by unplugging the router, waiting ten seconds and then plugging back in the router. The router will detect the new settings and begin using them.

To learn more about OpenDNS and the advantages it provides, navigate to the web site http://www.opendns.com.