Thursday, July 13, 2006
Crystal Report - Sub Report Unhandled Exception
If you are using sub reports in crystal Report and you want to suppress them, You must insert each sub report in a new section and suppress the section using the formula instead of suppressing the sub report directly. Otherwise it results in Unhandled exception error. This happens if the there are no rows returned by sub report for the last row of the main query. Assuming these sub reports are linked.
Wednesday, June 21, 2006
Portal registry search index No Success
Whenever I run the portal registry search index process (8.43.17) for all languages installed (CFR - French, ENG - English, ESP - Spanish), it errors out with No success message. The dump file shows the following error. The app engine process eventually runs fine, after multiple restart. Has anybody encountered similar issues?
PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0)
PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) PSAESRV crash dump at 2006-06-21 10.25.55.000000PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) Assertion (!nSqlRecurse) Failed at /local_home/build84/pt84317-retailr_o/src/pssys/samlib.cpp, line 1404.PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) Assertion (!nSqlRecurse) Failed at /local_home/build84/pt84317-retailr_o/src/pssys/samlib.cpp, line 1404.
PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0)
PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) PSAESRV crash dump at 2006-06-21 10.25.55.000000PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) Assertion (!nSqlRecurse) Failed at /local_home/build84/pt84317-retailr_o/src/pssys/samlib.cpp, line 1404.PSAESRV.28984 [06/21/06 10:25:55 CkSta1008857](0) Assertion (!nSqlRecurse) Failed at /local_home/build84/pt84317-retailr_o/src/pssys/samlib.cpp, line 1404.
Tuesday, June 20, 2006
Create Portal Registry Content Reference for a Query
You can easily create a new Content Reference for running the Query directly from Left hand menu, without navigating thru Query viewer. This allows easy execution of query by end user.
The Query URL is of the following format
q/?ICAction=ICQryNameURL=PUBLIC.MYQUERYNAME
Go to Structure and Content and Create a new Content reference, with following properties
Usage Type : Target
Select No Template check box.
Node Type : Always use Local, if you want to run the query hosted locally
URL Type : PeopleSoft Generic URL
Portal URL : q/?ICAction=ICQryNameURL=PUBLIC.MYQUERYNAME
Note : No forward slash before q. Otherwise Portal template will not be removed.
Content Reference Attributes
Name : NAVNEWWIN
Attribute Value : true
Uncheck Translate check box.
This will open the query page in a new window with no Portal wrapper.
If you want to pass parameters to query URL, you need to add the following at the end
"&<unique prompt name>=<value>"
You can find the unique prompt name from prompt definition page.
The Query URL is of the following format
q/?ICAction=ICQryNameURL=PUBLIC.MYQUERYNAME
Go to Structure and Content and Create a new Content reference, with following properties
Usage Type : Target
Select No Template check box.
Node Type : Always use Local, if you want to run the query hosted locally
URL Type : PeopleSoft Generic URL
Portal URL : q/?ICAction=ICQryNameURL=PUBLIC.MYQUERYNAME
Note : No forward slash before q. Otherwise Portal template will not be removed.
Content Reference Attributes
Name : NAVNEWWIN
Attribute Value : true
Uncheck Translate check box.
This will open the query page in a new window with no Portal wrapper.
If you want to pass parameters to query URL, you need to add the following at the end
"&<unique prompt name>=<value>"
You can find the unique prompt name from prompt definition page.
Wednesday, May 31, 2006
NewLine in Workflow Emails
If you want to insert a new line in workflow emails, add a derived/work record field to the page (newline). Set the value of this field as follows
derived_hr.newline = Char(13) | Char(10);
Add this field to Email mapping
Tuesday, May 30, 2006
Downloadble PeopleSoft Software and Documentation
Click here to download the PeopleSoft Enterprise Software
PeopleSoft Software
You can find the licensecodes at the following site
License Codes
You can download the PDF version of PeopleSoft Enterprise documentation here.
PeopleSoft Enterprise Documentation
Archive PeopleSoft Enterprise Documentation
PeopleSoft Software
You can find the licensecodes at the following site
License Codes
You can download the PDF version of PeopleSoft Enterprise documentation here.
PeopleSoft Enterprise Documentation
Archive PeopleSoft Enterprise Documentation
Thursday, May 04, 2006
Directory Interface Troubleshooting Tips
If Directory interface fails to update the Directory Server, an easy way to find list of upload errors is
select * from ps_eo_dsbiload_err order by ds_time_Stamp desc
Common Errors
Bad parameter to an ldap routine
Resolution: This error occurs, if you do not have cert7.db file present in your appserver domain directory. $PS_HOME/appserv/domainname/cert7.db. Make sure that this file is present in all the appservers not just one, configured for your database. I have seen this error appearing randomly, when the cert7.db file was present in only one domain and absent in other domain. Remember to copy this file, if you use SSL for LDAP, everytime you add a new appserver for your database.
If you use the custom function to modify the attribute values, and inside this custom function you change the value of
&AttrIN (Holds the value of the Rec.Field assigned to the current
Attribute.) For e.g. any assignment statement like
&AttrIN = GetCommonName(&AtttIN) or xyz;
will modify the value of &AttrIN and cause the above error. Never modify
this input variable.
No such attribute
This happens, when PeopleSoft Business interlink is trying to delete the
Attribute in LDAP and the value is not present. This is normally harmless.
I have also noticed that Function modifiers are not applied when it generated
action (DSAUDITACTN) = AD
Can't connect to the LDAP server
Please share any other errors and possible solution you encountered in setting up LDAP Directory interface process.
select * from ps_eo_dsbiload_err order by ds_time_Stamp desc
Bad parameter to an ldap routine
Resolution: This error occurs, if you do not have cert7.db file present in your appserver domain directory. $PS_HOME/appserv/domainname/cert7.db. Make sure that this file is present in all the appservers not just one, configured for your database. I have seen this error appearing randomly, when the cert7.db file was present in only one domain and absent in other domain. Remember to copy this file, if you use SSL for LDAP, everytime you add a new appserver for your database.
If you use the custom function to modify the attribute values, and inside this custom function you change the value of
&AttrIN (Holds the value of the Rec.Field assigned to the current
Attribute.) For e.g. any assignment statement like
&AttrIN = GetCommonName(&AtttIN) or xyz;
will modify the value of &AttrIN and cause the above error. Never modify
this input variable.
No such attribute
This happens, when PeopleSoft Business interlink is trying to delete the
Attribute in LDAP and the value is not present. This is normally harmless.
I have also noticed that Function modifiers are not applied when it generated
action (DSAUDITACTN) = AD
Can't connect to the LDAP server
- Invalid LDAP Directory Server Address
- Invalid Directory Server Port
- If using SSL, Expired SSL Certificate or invalid SSL Port
- No cert7.db locaed inside the appserver domain for e.g. $PS_HOME/appserv/domainname/cert7.db
- The above directory name is valid only if
If you have not modified the SSL_DB parameter under the settings tab in Business interlink LDAP_SEARCH or LDAP_SEARCH_BIND. For more information, check LDAP Authentication with PeopleTools Red Paper by Tom Lenz on customer connection (Last updated June 24 2005).
Please share any other errors and possible solution you encountered in setting up LDAP Directory interface process.
Tuesday, April 04, 2006
Run PeopleSoft Query from Excel or to Excel
I got inspired from this post in PeopleSoft Corner.
I found following issues with the above solution.
You can use following URL in IE or open it from inside Excel File Open dialog box. Remove the breaks from the URL before pasting it in ie or excel. Also change the portal registry (EMPLOYEE) and Portal Node (EMPL) and Site ID (ps) for your site.
http://hostname:port/psc/ps/EMPLOYEE/EMPL/s/>
WEBLIB_XXX.QRYRUN.FieldFormula.IScript_ToExcel?
userid=yyy&pwd=zzz&disconnect=y&type=public&
qryname=PT_SEC_PTLS_USERS&
MENUNAME=DATA_MOVER
You will need to create this IScript Function inside a Web Library Record (WEBLIB_XXX) as follows. You also need to assign the ISCript to appropriate permission list
Download Source Code
I found following issues with the above solution.
- You need to use third party XML PeopleCode Library
- XML files generated by this process can be viewed only in Microsoft Excel 2003
- XML Link is buggy in PeopleTools 8.43. It does not support special characters (#,$) etc. in password field. So if your site has implemented password controls which requires special characters, XML Link servelet will fail in 8.43 with error message Error: The return content is not xmllink data, please check log file.
- Also XML Link does not use configuration.properties parameters defaultXMLLinkUSERID and defaultXMLLinkPWD. It defaults to userid and pwd supplied in the url
You can use following URL in IE or open it from inside Excel File Open dialog box. Remove the breaks from the URL before pasting it in ie or excel. Also change the portal registry (EMPLOYEE) and Portal Node (EMPL) and Site ID (ps) for your site.
http://hostname:port/psc/ps/EMPLOYEE/EMPL/s/>
WEBLIB_XXX.QRYRUN.FieldFormula.IScript_ToExcel?
userid=yyy&pwd=zzz&disconnect=y&type=public&
qryname=PT_SEC_PTLS_USERS&
MENUNAME=DATA_MOVER
You will need to create this IScript Function inside a Web Library Record (WEBLIB_XXX) as follows. You also need to assign the ISCript to appropriate permission list
Download Source Code
Subscribe to:
Posts (Atom)