Category Archives: PeopleSoft - Page 5

Invalid Access ID and password for signon

Posted by on January 7, 2009 1 comment

Problem:

When logging on to Data Mover as a PeopleSoft user (PTDMO, VP1), the following error appears:

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

In the Security Table Manager (Get) dialog box, the following message appears:

The database is at release 8.48. The PeopleTools being run require databases at release 8.49.

Solution:

In Query Analyzer, check the PSSTATUS table:

select * from PSSTATUS

If the TOOLSREL column shows 8.48, then the scriptsrel849n.sql script must be run.

Obtaining PeopleTools 8.49.15

Posted by on January 6, 2009 No comments

Log on to Metalink3 and click the Patches and Downloads tab. Click PeopleSoft Products. Enter the following search criteria:

Search for:
Product Line: PeopleTools
Product: PeopleTools
Release: 8.49

Check the Bundles checkbox.
Then click the search button (a right arrow).

Update ID: 768890
Name: PT 8.49.15 Product Patch

https://psft-updates.oracle.com/psc/UGPRD/CUSTOMER/CUST/c/ICE_MAIN_MENU.ICE_SRCH_COMPONENT.GBL

https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915-PSCA.htm
https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915UserDoc_rev2.htm

Errors on SYSAUDIT Report

Posted by on January 5, 2009 No comments

Problem:

After completing installing FSDEMO, SYSAUDIT is run. The following errors appear on the report:

Application Engine Audits Result: OK
Clear List Audits Result: OK
Electronic Commerce Audit Result: OK
Field Definition Audit Result: OK
Menu Definition Audit Result: OK
Security Audits Result: Exception(s) Found
(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
Page Definition Audit Result: OK
PeopleCode Definition Audit Result: OK
Process Scheduler Audit Result: OK
Query Definition Audit Result: Exception(s) Found
(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
Record Definition Audit Result: OK
Language Definition Audit Result: OK
SQL Audits Result: OK
Tree Definition Audit Result: OK
Version Check Audits Result: OK
XLATT Definition Audit Result: OK
Analytic Audit Result: OK
XML Publisher Audit Result: OK
Integration Broker Audits Result: Exception(s) Found
(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
(IBRK-21) : Operations with duplicate routings:
Operation Version Routing
 - -------- ------- -------
 QAS_CRASH_MSG VERSION_1 ~GEN_UPG~18727
 QAS_CRASH_MSG VERSION_1 ~GEN~UPG~19278
 2 Total Rows

Solution:

Apply the latest Financials/SCM Maintenance Pack to resolve some of these errors.

Invalid Access ID and password for signon

Posted by on January 4, 2009 No comments

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.

Database creation fails when creating views

Posted by on January 3, 2009 No comments

When running fsdmomss_fsdmo.dms to create the FSDMO instance, the createvw.dss script completes with message “Unsuccessful Completion”.

The last three rows of the views.log shows:

SQL Views: 27069 Error: 198
Ended: Tue Dec 16 12:20:08 2008
Unsuccessful completion

Solution:

Apply PTPATCH.DSS script

Error has occurred while establishing a connection to the server

Posted by on January 3, 2009 No comments

When connecting to SQL Server database using SQL Server Management Studio, the following error appears:

TITLE: Microsoft SQL Server Management Studio
——————————

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

——————————
BUTTONS:

OK
——————————

Solution:

The SQL Server instance service (MSSQLSERVER) is not started. Start the service using the Control Panel Services panel, or use SQL Server Configuration Manager:

SQL Server Configuration Manager (Local) > SQL Server 2005 Services > SQL Server (MSSQLSERVER)

Unable to connect to database

Posted by on January 2, 2009 No comments

No connection could be made because the target machine actively refused it

Problem:

When logging on to VP1, the following error appears:

File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 – [Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.

Solution:

The MSSQLSERVER service was shut down on the database node. Restart it, and then log on to PeopleSoft.

Fixing Views-1 Errors on DDDAUDIT

Posted by on January 1, 2009 No comments

To fix Views-1 errors on DDDAUDIT:

1. Load Application Designer.
2. Click Insert > Definitions into Project.
3. In Definition Type, choose Records and press Enter.
4. Scroll down the list and select the record which appears in the DDDAUDIT.
5. The record appears in Application Designer. Click Build > Project.
6. Check Create Views.
7. Click Settings and change the Log file name and Output file name. Ensure that you choose Recreate view if it already exists.

IBM WebSphere 6.1.0.17 Download Location

Posted by on December 31, 2008 No comments

Problem:

Where is the IBM WebSphere 6.1.0.17 for PeopleSoft located?

Solution:

ftp://ftp.peoplesoft.com/outgoing/ptools/websphere/WAS61017

Invalid parameter for GetAttachment()

Posted by on December 30, 2008 No comments

Problem:

After running the following process:

Instance: 7082
Type: Application Engine
Name: GL_JRNL_IMP
Description: Flat File Journal Import

The following error appears in the message log:

Invalid parameter for GetAttachment(). Check environment variable PS_FILEDIR in process scheduler. (5825,118)

Solution:

In My Computer, navigated to E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warhtmldoc

Searched under this htmldoc directory for all files containing PS_FILEDIR.

In file:///E:/PSOFT/FS900/webserv/PSOL_fsdmo/installedApps/PSOL_fsdmoNodeCell/PSOL.ear/PSOL.war/htmldoc/eng/psbooks/fglr/htm/fglr07.htm#d0e5496

the following appears:

You must define an environmental variable, PS_FILEDIR. This variable defines the temporary flat file location on the process scheduler that runs the file import process. If you have a Unix or OS390 process scheduler, you define this in the psconfig.sh file. If you have an NT process scheduler, you define this in the control panel [Micro Focus XDB Server for NX 5.1 Service Controller]. Please refer to the GetFile PeopleCode reference for more details or contact your system administrator.

Also in:
file:///E:/PSOFT/FS900/webserv/PSOL_fsdmo/installedApps/PSOL_fsdmoNodeCell/PSOL.ear/PSOL.war/htmldoc/eng/psbooks/tibr/htm/tibr25.htm#d0e44891

Setting PS_FILEDIR in Microsoft Windows Environments To set the PS_FILEDIR environment variable in Microsoft Windows environments:

Close any open DOS windows.

On your desktop, right-click the My Computer icon and click Properties.

The System Properties dialog appears.

Click the Advanced tab.

In the Environment Variables section, click the Environment Variables button.

The Environment Variables dialog box appears.

In the User variables for section, click New.

A New User Variable dialog box displays.

In the Variable Name field enter PS_FILEDIR.

In the Variable Value field, enter c:.

The path you specify is the location from where the system will upload files.

Click the OK button to exit the Environment Variables dialog box.

Click the OK button again to exit the System Properties dialog box.