Error on Javascript in PeopleTools 8.52: "hAction_win0 is not defined"

Below code may not work from PeopleTools 8.52. But this will work on below version of tools release (i.e. 8.50, 8.51).

hAction_win0(document.win0,pageFldName,0,0,inlabel,false,true); 

Reason:

"hAction_win0" is no longer used in PeopleTools 8.52.

Solution:

"hAction_win0" can be replaced with "submitAction_win0" for 8.52 PeopleTools.

Sample code:

submitAction_win0(document.%FormName,pageFldName,0,0,inlabel,false,true); 

An error has occurred that has stopped this transaction from continuing

Reason 1:

This message appears due to 0 rows in PS_INSTALLATION Table.

Solution:

Insert a row in PS_INSTALLATION table and  restart the appservers.

Reason 2:

some error code in the events PreBuild, Activate, PostBuild or any FieldDefault.

Change Access Password

The symbolic ID is the account used by PeopleSoft to link users (operators) to the system account which is stored as ACCESSID in the PSACCESSPRFL record and encrypted.
Syntax to change or update password is:
CHANGE_ACCESS_PASSWORD [SymbolicID] [Password]
Alternative Method:
If user(“SYSADM” for Oracle and “SA” for MSS) is altered by the below query,

ALTER USER username IDENTIFIED BY password

then below scripts need to execute.

UPDATE PSSTATUS SET OWNERID = 'SYSADM';
UPDATE PSOPRDEFN SET SYMBOLICID = 'SYSADM1', OPERPSWD = OPRID, ENCRYPTED = 0;
UPDATE PSACCESSPRFL SET ACCESSID = 'SYSADM', SYMBOLICID = 'SYSADM1', ACCESSPSWD = 'SYSADM', VERSION = 0, ENCRYPTED = 0;
GRANT SELECT ON PSSTATUS TO people;
GRANT SELECT ON PSOPRDEFN TO people;
GRANT SELECT ON PSACCESSPRFL TO people;

Now login to Data-Mover in bootstrap mode and execute the below script.

 
REM - ENCRYPT PASSWORD
/
SET LOG d:\dbsetup_log\encrypt.log;
ENCRYPT_PASSWORD *;
/

Note: Make sure Connect-ID (people) account is not locked and correctly entered to configuration manager.

SQLExec : Return: 8015 - Bind value is too long

You get this error in an online page or while running a Application engine program. This error happens when you try to insert more than 254 characters in a long field using sqlexec and do not use %TextIn meta sql.

Resolution

Use %TextIn meta-sql for the bind variable that is used for inserting into a long field. For e.g. %TextIn(:1)

%TextIn is documented in peoplebooks and is mandatory for all insertions/update of LongChar fields using sqlexec for all database platforms.

Here are some resolutions that discusses this issue in Metalink – Oracle support site.

E-AE Application Engine PeopleCode Step with SQLExec Receives Error; return code 8015 "Bind value is too long" [ID 889806.1]

E-PC:"Bind value is too long" Error When Using SQLExec to Insert into Long Char Field [ID 620874.1]

 

Source: Some Blog.