Monthly Archives: January 2009

(IBRK-10): IB Routing referencing invalid handlers

Posted by on January 31, 2009 Comments Off on (IBRK-10): IB Routing referencing invalid handlers

Problem:

After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:

(IBRK-10): IB Routing referencing invalid handlers:
Routing On Send Handler On Receive Handler
 - ------ --------------- ------------------
 ~GENERATED~17288 ACK
 1 Total Rows

Solution:

Log on to SQL Server Management Studio and run the following queries against fsdev:

select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = '~GENERATED~17288'
select * from PSIBRTNGDEFN where ONRCVHDLRNAME = 'ACK'
select ONRCVHDLRNAME, count(*) from PSIBRTNGDEFN group by ONRCVHDLRNAME
select * from PSSRVHDLRRCV_VW

The outputs were:

ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG
 ------------------------------ ----------------------- ----------- ---------- ---------------------------------------------------------
 ~GENERATED~17288 2005-10-21 00:00:00.000 6 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-30 11:38:38.000 VP1 PPT GENERATED NULL
(1 row(s) affected)
ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG
 ------------------------------ ----------------------- ----------- ---------- ---------------------------------------------------------
 ~GENERATED~17288 2005-10-21 00:00:00.000 6 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-30 11:38:38.000 VP1 PPT GENERATED NULL
(1 row(s) affected)
ONRCVHDLRNAME COUNT(*)
 ------------------------------ -----------
 1500
 ACK 1
(2 row(s) affected)
IB_OPERATIONNAME ONRCVHDLRNAME DESCR
 ------------------------------ ------------------------------ ---------------------------
 CREATE_WORKLIST_ITEM OnAckForMarkedWorkedResp Create worklist entry
(1 row(s) affected)

On fsdmo, ran the following queries:

select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = '~GENERATED~17288'
select * from PSIBRTNGDEFN where ONRCVHDLRNAME = 'ACK'
select ONRCVHDLRNAME, count(*) from PSIBRTNGDEFN group by ONRCVHDLRNAME
select * from PSSRVHDLRRCV_VW

The outputs were:

ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG
 ------------------------------ ----------------------- ----------- ---------- ---------------------------------------------------------
 ~GENERATED~17288 2005-10-21 00:00:00.000 1 A ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-18 16:04:16.000 PPLSOFT PPT GENERATED NULL
(1 row(s) affected)
ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG
 ------------------------------ ----------------------- ----------- ---------- ---------------------------------------------------------
 CREATE_WORKLIST_ITEM 2005-10-21 00:00:00.000 1 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-23 11:11:56.000 PPLSOFT Create worklist entry NULL
 ~GENERATED~17288 2005-10-21 00:00:00.000 1 A ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-18 16:04:16.000 PPLSOFT PPT GENERATED NULL
(2 row(s) affected)
ONRCVHDLRNAME
 ------------------------------ -----------
 1513
 ACK 2
(2 row(s) affected)
IB_OPERATIONNAME ONRCVHDLRNAME DESCR
 ------------------------------ ------------------------------ ---------------------------
 CREATE_WORKLIST_ITEM ACK
 CREATE_WORKLIST_ITEM OnAckForMarkedWorkedResp Create worklist entry
 (2 row(s) affected)

Note that in PSSRVHDLRRCV_VW, there is a new row for ACK.

1. The simplest solution, however, is to delete the offending routing, ~GENERATED~17288.

2. In PIA, navigate to Integration Broker > Service Utilities > Service Administration. Select the Routings tab, and open the Delete section. Enter ~GENERATED~17288 into the Routing Name field and click Search. Check Select and then click Delete.

Under Results, the following message appears: Unable to delete. Routing belongs to a restricted service.

3. One way to resolve this is to change the restricted service to unrestricted. Navigate to Integration Broker > Configuration > Service Configuration. Click the Restricted Services tab, and search for PT_WORKLIST. Uncheck Restricted, and then Save.

4. Determine the field that is used as the lookup. Navigate to Integration Broker > Integration Setup > Routings. In the Find an Existing Value tab, in Routing Name, enter ~GENERATED~17288 and click Search.

5. Type Ctrl + J and note the Page name: IB_ROUTINGDEFN

6. On GL-WEB-APP, launch Application Designer and click Insert Definitions into Project. Choose Page and enter IB_ROUTINGDEFN. Choose IB_ROUTINGDEFN and click Close.

7. Double-click IB_ROUTINGDEFN. Right-click on the OnReceive Handler field and choose View Definition. On the ONRCVHDLRNAME field, right click and choose Record Field Properties. Click the Edits tab and note the Prompt Table: PSSRVHDLRRCV_VW.

8. In Management Studio, for the fsdev database, expand the Views navigator and locate PSSRVHDLRRCV_VW. Right click on PSSRVHDLRRCV_VW, choose Script View as, choose CREATE To, and click New Query. Note the command to create the view:

CREATE VIEW [dbo].[PSSRVHDLRRCV_VW] (IB_OPERATIONNAME, ONRCVHDLRNAME, DESCR) AS SELECT IB_OPERATIONNAME , HANDLERNAME , DESCR FROM PSOPRHDLR WHERE HANDLERID = 'RECV'

9. In PIA, navigate to Integration Broker > Integration Setup > Service Operations. In the Find Service Operation tab, in the Service Operation field, enter CREATE_WORKLIST_ITEM. Then click Search. Click CREATE_WORKLIST_ITEM to view it.

10. If the record is restricted, you will not be able to enter new Handlers. See step 3 above to resolve.

11. Click the Handler tab. Add a new Handler with the following information:
Name: ACK
Type: OnReceive
Implementation: Application Class
Status: Active

Click Details and add the following information:

Package Name: PT_WF_WORKLIST
Path: : [that is, only a colon must be entered]
Class ID: OnAckForMarkedWorkedResp
Method: OnAckReceive

12. Click Save.

(IBRK-08): IB Routing referencing invalid service operation

Posted by on January 30, 2009 Comments Off on (IBRK-08): IB Routing referencing invalid service operation

Problem:

After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:

(IBRK-08): IB Routing referencing invalid service operation:

Routing Operation Version
– —— ——— ——-
~GEN~UPG~24567 IB_INST_VER_ASYNC_MSG VERSION_1
~GEN~UPG~17626 IB_INST_VER_RESP_MSG VERSION_1
2 Total Rows

Solution:

Delete the above two routings:

1. Query records that appear in Integration Broker Audit section IBRK-08

select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = ‘~GEN~UPG~24567’ or ROUTINGDEFNNAME = ‘~GEN~UPG~17626’

2. Launch PIA and search for the page that contains these values. Navigate to Integration Broker > Integration Setup > Routings. In the Find an Existing Value tab, in the Routing Name begins with field, enter ~GEN~UPG~24567. Click Search. It returns ‘No matching values were found.’ Then click the Add a New Value tab. The record appears.

3. Type Ctrl + J to get the page information. Note the Page (IB_ROUTINGDEFN).

4. On GL-WEB-APP, launch Application Designer. Insert Definitions into Project. Choose Definition Type Page and enter IB_ROUTINGDEFN in the Name field. Then press Enter. Insert the IB_ROUTINGDEFN page.

5. Right-click the Service Operation field, and choose Field Definition. In the Record Definition, choose Record Field Properties. Click the Edits tab and note the Prompt Table: PSOPERATION.

select * from PSOPERATION
select * from PSOPERATION where IB_OPERATIONNAME = ‘IB_INST_VER_RESP_MSG’ or IB_OPERATIONNAME = ‘IB_INST_VER_ASYNC_MSG’

6. Delete the two routings above (~GEN~UPG~24567 and ~GEN~UPG~17626). In PIA, navigate to PeopleTools > Integration Broker > Service Utilities > Service Administration. Select the Routings tab, and expand the Delete section. For each routing name (~GEN~UPG~24567 and ~GEN~UPG~17626), enter the Routing Name and click Search. The routing name appears. Check Select and then click Delete.

Reference:

E-IB: IBRK-xx SYSAUDIT exceptions after applying Maintenance Pack(s) (Doc ID 654766.1)
EFSCM: Orphan routing issue for FSCM9 customers after upgrading to 8.49 tools (Doc ID 661088.1)

[amazon asin=0071664939&template=iframe image&chan=default]     [amazon asin=1430237074&template=iframe image&chan=default]     [amazon asin=0071787925&template=iframe image&chan=default]

 

(IBRK-05): Service Operation with missing service

Posted by on January 29, 2009 No comments

Problem:

After running the SYSAUDIT report, the following error appears under Integration Broker Audits:

(IBRK-05): Service Operation with missing service:
Service Operation Service
 - ---------------- -------
 PV_ORDER_XCBL3 PV_ORDER_XCBL3
 1 Total Rows

Solution:

1. Check the “Data Management” PeopleBook, under the “Ensuring Data Integrity” section for information on resolving Integration Broker errors.

2. Check the Service Operations (PSOPERATION) and Service’s (PSSERVICE) tables in the fsdmo and fsdev databases.

select * from PSOPERATION where IB_SERVICENAME like 'PV_ORDER%'
select * from PSSERVICE where IB_SERVICENAME like 'PV_ORDER%'

Note that PV_ORDER_XCBL3 appears in the PSOPERATION table in fsdev, but not in the PSSERVICE table. Note also that PV_ORDER_XCBL3 appears only in fsdev, but not in fsdmo.

Therefore, backup the row containing PV_ORDER_XCBL3 and then delete the row from the PSOPERATION table in the fsdev instance:

select * from PSOPERATION where IB_SERVICENAME = 'PV_ORDER_XCBL3'
delete from PSOPERATION where IB_SERVICENAME = 'PV_ORDER_XCBL3'

3. Deleting the record introduced an IBRK-06 error on the SYSAUDIT report. To restore the data that was deleted:

insert into PSOPERATION
 (IB_OPERATIONNAME, VERSION, DEFAULTVER, RTNGTYPE, IB_USERPWDREQ, IB_SERVICENAME, IB_ALIASNAME, LASTUPDDTTM, 
LASTUPDOPRID, OBJECTOWNERID, DESCR, DESCRLONG)
 values
 ('PV_ORDER_XCBL3', 1, 'VERSION_1', 'A', 'N', 'PV_ORDER_XCBL3', '', '2008-12-11 16:47:00.000', 'SVP1', 
'DPV', 'xCBL Order', NULL)

4. In PIA, navigate to Integration Broker > Service Utilities > Service Administration. Click the Service Operations tab. Expand Delete and in the Service Operation field, enter PV_ORDER_XCBL3. Check Select, and then click Delete.

Under Results, ‘Successful delete’ appears.

After rerunning SYSAUDIT, the exception no longer appears.

ZFSCM900_DROP5_PRE_DMS Errors

Posted by on January 28, 2009 No comments

Problem:

When running the ZFSCM900_DROP5_PRE_DMS step to drop unneeded views, many steps complete in error:

SQL Error. Error Position: 0 Return: 601 - [Microsoft][SQL Native Client][SQL Server]
Cannot drop the view 'PS_XXXX_XX_XXXX_VW', because it does not exist or you do not have permission.

The end of the log file states ‘Successful Completion’.

Solution:

This is expected behaviour. The MP5 documentation states:

Dropping Views
In this step, if you encounter an error, due to some tables and views previously dropped or already do not exist in the database, please ignore the error, mark this step as Complete and continue with the Maintenance Pack installation. Note that the script log would still mark as Successful completion.

Unable to install WebLogic

Posted by on January 26, 2009 No comments

Problem:

When installing BEA WebLogic from the command line, the following error appears:

Step 1 – Installation preparation.
WebLogic was unexpected at this time.

Solution:

Remove spaces from folder name:
Rename E:stagingCDImagesBEA WebLogic to E:stagingCDImagescd849-WebLogic.

DDDAUDIT Errors After Running FSCM MP5

Posted by on January 24, 2009 No comments

DDDAUDIT Errors After Running FSCM MP5

Problem:

After completing FSCM MP5, the DDDAUDIT report is run. The following errors appear:

(TABLE-2) SQL Table defined in the Application Designer and not found in the Database:
 Record Name Ownerid
 --------------- -------
 BP_ACT2_TAO FGL
 BP_APA_S_TAO FAP
 BP_APN_S_TAO FAP
 BP_APV_S_TAO FAP
 BP_ARM_S_TAO FAR
 BP_ARR_S_TAO FAR
 BP_BDHDR_TAO FGL
 BP_BDLN_TAO FGL
 BP_BI_S_TAO DBI
 BP_BKOUT_TAO FGL
 BP_CF_TAO FGL
 BP_CM_S_TAO DCM
 BP_EX_S_TAO FEX
 BP_FSRC_TAO FGL
 BP_GEN_S_TAO FGL
 BP_GLB_S_TAO FGL
 BP_GL_S_TAO FGL
 BP_GM_S_TAO FGM
 BP_HR_S_TAO FGL
 BP_LQDFS_TAO FGL
 BP_LQD_TAO FGL
 BP_PC1_S_TAO FPC
 BP_PC_S_TAO FPC
 BP_PFS1_TAO FGL
 BP_PFS2_TAO FGL
 BP_POA_S_TAO DPO
 BP_POC_S_TAO DPO
 BP_PO_S_TAO DPO
 BP_PRNT_TAO FGL
 BP_PST1_TAO FGL
 BP_PST2_TAO FGL
 BP_REFDBK_TAO FGL
 BP_REFD_TAO FGL
 BP_RQN_S_TAO DPO
 BP_RQ_S_TAO DPO
 BP_TA_S_TAO FEX
 BP_XCF2_TAO FGL
 BP_XCF_TAO FGL
 BP_XLBP_TAO FGL
 EX_ADVLN_TAO FEX
 EX_ADVLSS_TAO FEX
 EX_STGSHT_TMP FEX
 FS_CE_CFV_TAO FGL
 VUN_DOC_TAO FAP
 VUN_RVS_TAO FAP
 VUN_UNP_TAO FAP
 46 Total Rows
(TABLE-3) SQL Table defined in the Database
 and not found in the Application Designer:
 SQL Table Name
 ------------------
 PS_VNDR_ORDER_TMP
 PS_VNDR_REMIT_TMP
 PS_WEBLIB_EX_TV
 3 Total Rows
(TABLE-4)INFORMATIONAL ONLY - Tablespace not
 defined for SQL Table in the Application
 Designer: No rows found.
(TABLE-5) Table Contains More Than 500
 Fields : No rows found.
(VIEWS-1) Views defined in the Application
 Designer and not found in the Database: No rows found.
(VIEWS-2) Views defined in the Database and
 not found in the Application Designer: No rows found.
(INDEX-1) Index defined in the Application
 Designer and not found in the Database:
 Record Name Index ID Ownerid
 --------------- -------- -------
 BP_ACT2_TAO A FGL
 BP_ACT2_TAO B FGL
 BP_ACT2_TAO _ FGL
 BP_APA_S_TAO A FAP
 BP_APA_S_TAO B FAP
 BP_APA_S_TAO _ FAP
 BP_APN_S_TAO A FAP
 BP_APN_S_TAO B FAP
 BP_APN_S_TAO _ FAP
 BP_APV_S_TAO A FAP
 BP_APV_S_TAO B FAP
 BP_APV_S_TAO _ FAP
 BP_ARM_S_TAO A FAR
 BP_ARM_S_TAO _ FAR
 BP_ARR_S_TAO A FAR
 BP_ARR_S_TAO _ FAR
 BP_BDHDR_TAO 0 FGL
 BP_BDHDR_TAO _ FGL
 BP_BI_S_TAO A DBI
 BP_BI_S_TAO B DBI
 BP_BKOUT_TAO A FGL
 BP_CF_TAO A FGL
 BP_CF_TAO B FGL
 BP_CM_S_TAO A DCM
 BP_CM_S_TAO B DCM
 BP_CM_S_TAO _ DCM
 BP_EX_S_TAO A FEX
 BP_EX_S_TAO B FEX
 BP_EX_S_TAO _ FEX
(INDEX-1) Index defined in the Application
 Designer and not found in the Database:(continued)
 Record Name Index ID Ownerid
 --------------- -------- -------
 BP_FSRC_TAO A FGL
 BP_GEN_S_TAO A FGL
 BP_GEN_S_TAO _ FGL
 BP_GLB_S_TAO A FGL
 BP_GLB_S_TAO _ FGL
 BP_GL_S_TAO A FGL
 BP_GL_S_TAO _ FGL
 BP_GM_S_TAO A FGM
 BP_GM_S_TAO B FGM
 BP_HR_S_TAO A FGL
 BP_HR_S_TAO B FGL
 BP_LQDFS_TAO A FGL
 BP_LQD_TAO A FGL
 BP_PC1_S_TAO A FPC
 BP_PC1_S_TAO B FPC
 BP_PC_S_TAO A FPC
 BP_PC_S_TAO B FPC
 BP_POA_S_TAO A DPO
 BP_POA_S_TAO B DPO
 BP_POC_S_TAO A DPO
 BP_POC_S_TAO _ DPO
 BP_PO_S_TAO A DPO
 BP_PO_S_TAO B DPO
 BP_PO_S_TAO _ DPO
 BP_PST1_TAO A FGL
 BP_REFDBK_TAO A FGL
 BP_REFD_TAO A FGL
 BP_RQN_S_TAO A DPO
 BP_RQN_S_TAO _ DPO
 BP_RQ_S_TAO A DPO
 BP_RQ_S_TAO _ DPO
 BP_TA_S_TAO A FEX
 BP_TA_S_TAO _ FEX
 BP_XCF_TAO A FGL
 BP_XCF_TAO B FGL
 BP_XCF_TAO C FGL
 EX_ADVLN_TAO A FEX
 EX_ADVLN_TAO _ FEX
 EX_ADVLSS_TAO _ FEX
 EX_STGSHT_TMP A FEX
 EX_STGSHT_TMP B FEX
 EX_STGSHT_TMP _ FEX
 FS_CE_CFV_TAO A FGL
 VUN_DOC_TAO _ FAP
 VUN_RVS_TAO _ FAP
 VUN_UNP_TAO _ FAP
 75 Total Rows

Solution:

See the Acceptable Audit Errors section on page 53 for tips to resolving these errors, including deleting the tables under section TABLE-3

To rebuild the tables under the TABLE-2 section of the DDDAUDIT report, the RBL_MP5ERRORS_VS project was created in Application Designer and the SQL script was built to create the missing tables.

(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist in PSXLATITEM Table

Posted by on January 21, 2009 No comments

(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist in PSXLATITEM Table

Problem:

After running SYSAUDIT on FSDEV, the following error appears:

(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist In PSXLATITEM Table:
Query Name Field Name
 ---------- ----------------------
 ARDISH01 DRAFT_TYPE
 1 Total Rows

Solution:

1. Determine if scriptsPTPATCH.DMS was run. Log onto SQL Server Management Studio and running the following command:

select * from PS_MAINTENANCE_LOG where UPDATE_ID = '768890';

2. Next, load Application Designer and copy the PATCH849 project from file.

It was already copied.

3. Check PS_QRYFIELD_VW to see the fields used in the ARDISH01 query:

select * from dbo.PS_QRYFIELD_VW where QRYNAME = 'ARDISH01'

4. Get list of ‘DRAFT_’ field names from the PSXLATITEM table:

select distinct FIELDNAME from PSXLATITEM where FIELDNAME like 'DRAFT_%'

There is no DRAFT_TYPE field in this table.

5. Get list of ‘DRAFT_’ field names from the PSXLATITEM table:

Checked SYSAUDIT for FSDMO. This error is not present. Apply MP5 to FSDEV to resolve issue.

(SEC-30) Role User table (ROLEXLATOPR) should be populated

Posted by on January 20, 2009 No comments

Problem:

After running SYSAUDIT, the following error appears:

(SEC-30) Role User table (ROLEXLATOPR) should be populated when new User Profiles (entries in PSOPRDEFN) 
are created using User Profile component through PIA. The following User Profiles need to be fixed by 
simply opening and saving them through PIA:
 Oper ID Description
 ------- ------------------------------
 ENTMGR_PRO Procurement Catalog Manager
 1 Total Rows

Solution:

1. Launch the PeopleSoft instance (PIA) and log on as a user with access to the PeopleTools responsibility.
2. Navigate to PeopleTools > Security > User Profiles > User Profiles.
3. Click Search, and choose ENTMGR_PRO (Procurement Catalog Manager).
4. Make a change to the record (e.g. change Language Code from English to Finnish), and save the record.
5. Revert the change (e.g. change Language Code from Finnish to English), and save the record again.
6. Then run the SYSAUDIT report.

Uninstalling PeopleSoft PIA for WebSphere

Posted by on January 19, 2009 No comments

1. In WebSphere Administration Console http://server:9060/ibm/console, log on as user admin

2. Applications > Enterprise Applications

3. Check fsdmo and then Stop

4. Check fsdmo and then Uninstall

5. Save configuration changes

6. Repeat for 9061 (PSEMHUB) and 9062 (PSOL)

7. Stop WebSphere using the command:

webserv\binstopServer.bat server1

e.g.
E:PSOFTFS900webservPIA_fsdmobinstopServer.bat server1
E:PSOFTFS900webservPSEMHUB_fsdmobinstopServer.bat server1
E:PSOFTFS900webservPSOL_fsdmobinstopServer.bat server1

8. Uninstall profiles using the commands:

manageprofiles.bat –delete -profileName

e.g.
cd /d E:PSOFTFS900webserv
PIA_fsdmobinmanageprofiles.bat -delete -profileName PIA_fsdmo
PSEMHUB_fsdmobinmanageprofiles.bat -delete -profileName PSEMHUB_fsdmo
PSOL_fsdmobinmanageprofiles.bat -delete -profileName PSOL_fsdmo

9. Delete the PIA_fsdmo, PSEMHUB_fsdmo and PSOL_fsdmo directories.

10. Reboot the server.

Reference:

Page 173-174, Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server

Audit contents of PS_AELOCKMGR

Posted by on January 18, 2009 No comments

Problem:

Application Engine Audits Result: Exception(s) Found
 (AE-16) Audit contents of PS_AELOCKMGR:
Message
 ----------------------------------------------------
 PS_AELOCKMGR contains 2row(s). There should be 1.
 1 Total Rows

Solution:

In SQL Server Management Console, checked the contents of the S_AELOCKMGR table.

It returns:

AE_LOCK
 -------
 N
 N

Delete the extra row using:

SET ROWCOUNT 1
 DELETE FROM [FSDMO].[dbo].[PS_AELOCKMGR]