Tag Archives: Application Designer

Error: Could not resolve environment variable(s) in %PS_SERVDIR%logsPeopleTools.trc.

Problem:

When launching Application Designer on the PeopleSoft server, the following error appears:

Error: Could not resolve environment variable(s) in %PS_SERVDIR%logsPeopleTools.trc.

Note that PeopleTools 8.50 is running on this machine.

Solution:

Set the PS_SERVDIR environment variable to point to the process scheduler location.

Read more »

(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database

Problem:

After cloning fsdev to fstst, DDDAUDIT was run. It showed the following error:

(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database:
 Record Name Trigger Name
 --------------- ---------------
 CHARTFIELD1_TBL PSICHARTFIELD1_TBL
 CHARTFIELD1_TBL PSUCHARTFIELD1_TBL
 2 Total Rows

Solution:

In GLWEBAPP, launch Application Designer. Log on to FSTST (ensure FSTST ODBC Connection created).

(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.

DDDAUDIT Errors After Running FSCM MP5

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

(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.

Invalid User ID and Password Logging Into Application Designer

Problem:

When logging on to Application Designer as a new (Windows) user, the user is unable to login and the following error appears:

Invalid User ID and Password Logging Into Application Designer

Solution:

In Configuration Manager, under Profile, edit the Default program and create new entries for Database and Application Server.

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

Build and Alter Step While Applying MP5

The Build and Alter step (or ‘chapter’) consists of two tasks:

1. Build and Alter Task_1
2. Build and Alter Task

Under the first task (Build and Alter Task_1), there are two steps:
a. Build Step
b. Run Recreate Tables Script

No action is required for the Build and Alter Task_1 steps. Read the documentation in the right pane, and then mark the steps as Complete.

Under the second task (Build and Alter Task), there are seven steps:
a. Build and Alter Step
b. Run Create Tables Script
c. Run Alter Tables Script
d. Run Create Triggers Script
e. Run Create Views Script
f. Additional Step 02
g. Run Create Indexes Script

The first step (Build and Alter Step) can be run automatically. The step completes with warnings, as there are some records have over 16 keys or some record definitions do not exist. The log file is:
E:/temp/softwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5}/BuildAndAlter.log

The output scripts generated by the Build and Alter Step are located in E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5}

The second step, Run Create Tables Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateTables.sql script in SQL Server Management Studio. The CreateTables.sql script executed successfully in 59 seconds.

The third step, Run Alter Tables Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} AlterTables.sql script in SQL Server Management Studio. The AlterTables.sql script executed successfully in 1 minute 30 seconds.

The fourth step, Run Create Triggers Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateTriggers.sql script in SQL Server Management Studio. The CreateTriggers.sql script executed successfully in less than 1 second.

The fifth step, Run Create Views Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateViews.sql script in SQL Server Management Studio. The CreateViews.sql script executed successfully in 26 seconds.

The sixth step, Additional Step 02 is done by logging into PIA and populating the KEYLIST field.

The seventh step, Run Create Indexes Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateIndexes.sql script in SQL Server Management Studio. The CreateIndexes.sql script executed successfully in 10 seconds.

Note: When these steps were first run against the FSDMO instance, the Create Views step failed because the PTPATCH.DMS script and PATCH849 project were not run against the database.

PPLTLS84CUR Results

PPLTLS84CUR Results

Problem:

The following is the output on the Results tab in Application Designer when PPLTLS848CUR project is copied from file to the database. Note that this is run on PeopleTools 8.49.15.

Opening project …
4009 Records definition(s) in project. 77 Indexes definition(s) in project. 10782 Fields definition(s) in project. 1669 Translate Values definition(s) in project. 1255 Pages definition(s) in project. 36 Menus definition(s) in project. 401 Components definition(s) in project. 2780 Record PeopleCode definition(s) in project. 48 Queries definition(s) in project. 1 Trees definition(s) in project. 3 Access Groups definition(s) in project. 7 Business Processes definition(s) in project. 16 Activities definition(s) in project. 16 Roles definition(s) in project. 40 Process Definitions definition(s) in project. 4 Server Definitions definition(s) in project. 61 Process Type Definitions definition(s) in project. 1 Job Definitions definition(s) in project. 3 Recurrence Definitions definition(s) in project. 8 Business Interlink definition(s) in project. 1760 SQL definition(s) in project. 16 File Layout Definitions definition(s) in project. 25 Component Interfaces definition(s) in project. 96 Application Engine Programs definition(s) in project. 248 Application Engine Sections definition(s) in project. 11 Message Nodes definition(s) in project. 82 Messages definition(s) in project. 3 Message PeopleCode definition(s) in project. 2 Subscription PeopleCode definition(s) in project. 8 Comp. Interface PeopleCode definition(s) in project. 267 Application Engine PeopleCode definition(s) in project. 411 Page PeopleCode definition(s) in project. 272 Component PeopleCode definition(s) in project. 86 Component Record PeopleCode definition(s) in project. 503 Component Rec Fld PeopleCode definition(s) in project. 725 Images definition(s) in project. 26 Style Sheets definition(s) in project. 494 HTML definition(s) in project. 22 Permission Lists definition(s) in project. 2 Portal Registry Definitions definition(s) in project. 3388 Portal Registry Structures definition(s) in project. 11 URL Definitions definition(s) in project. 197 Application Packages definition(s) in project. 732 Application Package PeopleCode definition(s) in project. 1 Analytic Types definition(s) in project. 7 XSLT definition(s) in project. 1 Mobile Pages definition(s) in project. 1 Analytic Models definition(s) in project. 56 Services definition(s) in project. 65 Service Operations definition(s) in project. 50 Service Operation Handlers definition(s) in project. 65 Service Operation Versions definition(s) in project. 58 Service Operation Routings definition(s) in project. 29 IB Queues definition(s) in project. 2 XMLP Template Defn definition(s) in project. 1 XMLP Report Defn definition(s) in project. 4 XMLP File Defn definition(s) in project. 1 XMLP Data Src Defn definition(s) in project. 30945 total definition(s) in project.

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

DDDAUDIT Report Generates 136 Pages

Problem:

After running DDDAUDIT on fsdmo, the report generates the following errors:

(TABLE-1) SQL Table Names defined in the Application Designer that are not blank and not the same as the Record Name: No rows found.
(TABLE-2) SQL Table defined in the Application Designer and not found in the Database: (continued) 3,739 Total Rows
(TABLE-3) SQL Table defined in the Database and not found in the Application Designer: No rows found.
(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: 4,028 Total Rows
(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database: No rows found.

Solution:

Script to populate the database was not run. Logged on to Data Mover as user ‘sa’ (in bootstrap mode) and ran fsdmomss_fsdmo.dms script. Ensure that the fsdmomss script from the correct PS_HOME is used.

Did not complete the database installation. In the “Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server”, start from Task B-8 and import the projects. Run Application Designer and import PS

Invalid Access ID and password for signon

Invalid Access ID and password for signon — see your security administrator

Problem:

When signing on to FSDEMO using Application Designer, the following error appears:

Invalid Access ID and password for signon — see your security administrator.

Solution:

When configuring the FSDEMO ODBC connection, set ‘Change the default database to’ to FSDEMO.