Application Engine Program PTIAREFMATVW not Defined error in change assistant target database upload in PT 8.55

Following error occurs in People tools 8.55.x. This happens when you try to upload the target database information into PUM image.


Application Engine Program PTIAREFMATVW not Defined


Solution :
This is know bug and solution is apply patch 8.55.05 or install the 8.55.01 and upload target database information into PUM image and again install 8.44.04 tools. I prefer installing patch 05 is better.

Application server boot up error - GenMessageBox(0, 0, M): Database Signon: Could not sign on to database XXXX with user PS

If you get following set of error then follow these steps to fix the issue



PSADMIN.3628 (0) [2016-11-15T14:07:00.998](0) Begin boot attempt on domain xxxxx
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.167](0) PeopleTools Release 8.54.X (Windows) starting. Tuxedo server is APPSRV(99)/2
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.167](3) Detected time zone is Eastern Standard Time
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.277](0) Cache Directory being used: d:\xxxx\appserv\xxxx\CACHE\PSAPPSRV_2\
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.370](3) File: SQL Access ManagerSQL error. Stmt #: 1  Error Position: 0  Return: -1 -
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.370](1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 1  Error Position: 0  Return: -1 -
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.370](0) Database Options: override_connection_reset: 0
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.370](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database XXXX with user PS.
PSAPPSRV.4888 (0) [2016-11-15T14:07:12.386](0) Server failed to start
PSADMIN.3628 (0) [2016-11-15T14:07:19.765](0) End boot attempt on domain xxxxx


Solution :


This is very common error and solution for basic checks is available on support and you can easily find in internet.
I am posting this because the regular way to fix this did not work and later I found Oracle doc Id 1621660.1 which has similar details to fix the issue. So this is known issue and is caused by using the same database for different tools patch version. Basically after applying patch on PSHOME the encryption algorithm of passwords gets changed and so the new tools patch unable to use the existing encrypted passwords. Solution is to reset and encrypt access id and password. After that encrypt all application ids. Let me know if it helps you too.

Unable to setup PeopleTools trace through configuration manager with message workstation configuration error peoplesoft please enter a valid trace filename

If you get following error while setting up PeopleSoft Peopletools trace through configuration manager then simply close you all Peopletools sessions of application designer, data mover and delete the Peopletools cache ( usually in C:\PS\CACHE\) and try again.


Error : "workstation configuration error please enter a valid trace filename"

Issue that PeopleSoft object with Dell STAT 5.7.* don't get migrate to target database.

This was unique issue that came across where through STAT the PeopleSoft object were getting migrated to staging database but not to target. It was not for all object but for record field object type. Following attempts did to fix the issue.

1. Clear STAT cache and PeopleTools (Application designer) cache. - Did not fix issue
2. Attempt migration with option "Project in Archive Set" , as soon you select this option the action flags changed which caused the issue. Select "User Defined Project"  and migrated, still caused issue.
3. Created new archive set and sync up objects again with source and migrate. This fixed the issue.

So issue was with bad archive set. Please post if you fixed it other ways.