Apurva Tripathi
Author Archives: Apurva Tripathi
Apurva Tripathi
How to Configure SES with Multiple PeopleSoft Instances
E-SES: Using SES with Multiple PeopleSoft Instances (Doc ID 1560981.1) Requirements for a shared SES: All the systems sharing the SES should have a unique database name All of the systems should be on same tools release (different patch level is fine) When same user id exists on two systems it should be ok […]
Continue reading
3
Deploying Search Definition Errors Out with Message “The current user has insufficient privileges to complete this operation”
When attempting to deploy a search definition in Search Framework, the deploy for most Search Definitions results in application timing out, or user gets the following “insufficient permissions” error: “The current user has insufficient privileges to complete this operation” This error can occurr for multiple reasons including: 1) User does not have sufficient privileges to […]
Continue readingHC_HRS_JOB_POSTING_NON_GLOBAL Has Not Been Deployed (262,665)
When you perform search in Recruiting -> Postings -> Search job Postings, following error is received:Search Category HC_HRS_JOB_POSTING_NON_GLOBAL has not been deployed. (262,665) PT_SEARCH.SESIMPL.MESSAGE.QueryRequest.OnExecute Name:AddDataGroups PCPC:7576 Statement:91Called from:PT_SEARCH.SESIMPL.QueryService.OnExecute Name:createQueryRequest Statement:207Called from:PT_SEARCH.SESIMPL.QueryService.OnExecute Name:ExecuteQuery Statement:46Called from:PT_SEARCH.SESIMPL.Query.OnExecute Name:Execute Statement:39Called from:HRS_COMMON.SEARCH.BUS.JobSearchProvider.OnExecute Name:searchSESCollection Statement:79Called from:HRS_COMMON.SEARCH.BUS.JobSearchProvider.OnExecute Search cannot be made on Search Categories which are not deployed. Please deploy the Search […]
Continue reading
1
EQG17074: Invalid facet path
After configuring SES, sometimes there is a situation wherein some of the functionalities start to work fine whereas some surprisingly give errors. I saw this situation twice – once in Recruiting Solutions and once in ELM wherein many of the search functionalities started to work fine except for one: Browse Applicants Browse Applicants in Recruiting […]
Continue readingValidation failed : Call back URL does not match with Target Location URL (262,1313)
When running validation on the Search Instance “Call Back Properties”, the validation fails with the error: Validation failed : Call back URL does not match with Target Location URL (262,1313) Validation failed : Call back URL does not match with Target Location URL If you’re not sure where it is – here is the navigation […]
Continue reading