Tag Archives: SQL Server - Page 2

Invalid Access ID and password for signon

Posted by on January 8, 2009 No comments

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.

Login failed for user ‘sa’

Posted by on January 8, 2009 No comments

Login failed for user ‘sa’

Problem:

When logging on to Data Mover as VP1, the following error appears:

File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 404 - [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.

Solution:

Log on to Data Mover as user sa and run the following lines from fsdmomss.dms:

UPDATE PSSTATUS SET OWNERID = 'sa';
 UPDATE PSOPRDEFN SET SYMBOLICID = 'sa1', OPERPSWD = OPRID, ENCRYPTED = 0;
 UPDATE PSACCESSPRFL SET ACCESSID = 'sa', SYMBOLICID = 'sa1', ACCESSPSWD = 'train', VERSION = 0, ENCRYPTED = 0;
 GRANT SELECT ON PSSTATUS TO people;
 GRANT SELECT ON PSOPRDEFN TO people;
 GRANT SELECT ON PSACCESSPRFL TO people;
REM - ENCRYPT PASSWORD
 /
 SET LOG c:tempencrypt.log;
 ENCRYPT_PASSWORD *;

References:

http://peoplesoft.ittoolbox.com/groups/technical-functional/peopletools-l/app-server-start-up-failed-2106157

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.

Build and Alter Step (MP5) returns errors

Posted by on December 29, 2008 No comments

Problem:

When running the Build and Alter Task > Build and Alter Step, the follow appear in the log file:

SQL Build process began on 12/29/2008 at 3:43:44 PM for database FSDEV.
 Warning: SAC_SRCNODE_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: The record SPL_PEGGING_INF has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_SENT_DTL has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_SNT_D_HST has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TO_SND_DTL has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TO_SND_TMP has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TRXN_TMP3 has more than 16 keys. Table will be altered to support functional index.
 Warning: GM_CONT_CERT_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: GM_CONT_JHDR_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: GM_CONT_PROF_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: PL_SOHOLD3_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: RE_OPEXADT_PADD - Record definition does not exist. Record not processed. (76,73)
 Warning: RE_OPEXADT_RADD - Record definition does not exist. Record not processed. (76,73)
 Warning: SAC_TGTNODE_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: SHIPTO_ADDR_VW1 - Record definition does not exist. Record not processed. (76,73)
 Warning: SHIPTO_ADDR_VW2 - Record definition does not exist. Record not processed. (76,73)
 Warning: SPA_SP_RC_PD_V2 - Record definition does not exist. Record not processed. (76,73)
 Warning: VNDR_ORDER_TMP - Record definition does not exist. Record not processed. (76,73)
 Warning: VNDR_REMIT_TMP - Record definition does not exist. Record not processed. (76,73)
**** Begin Build Settings for this Run
 Create Tables = Yes
 Create Indexes = Yes
 Create Views = Yes
 Create Triggers = Yes
 Alter Tables = Yes
 Log to File = Yes
 Log to Window = No
 Write comments to script = Yes
 Always overwrite files = Yes
 Execute SQL Now = No
 Write SQL to script file = Yes
 Logging level = Log fatal errors and warnings only
 Table creation option = Skip table if it exists
 View creation option = Drop and recreate view if it exists
 IndexCreationOption = Recreate index only if modified
 Alter Adds = Yes
 Alter Changes = Yes
 Alter Renames = Yes
 Alter Deletes = Yes
 Alter even if no changes = No
 Alter Table Option = Alter in Place
 Write script output to: Separate files
 Log filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log
 Table creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql
 Index creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql
 View creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql
 Trigger creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql
 Alter table script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql
 Alter drop column option = drop column if data present
 Alter truncate column option = truncate column if data present
 Target database platform = MICROSFT
 Target sizing set = 0
SQL Build process ended on 12/29/2008 at 3:45:28 PM.
 1641 records processed, 0 errors, 19 warnings.
 SQL Build script for Create Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql.
 SQL Build script for Create Indexes written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql.
 SQL Build script for Create Views written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql.
 SQL Build script for Create Triggers written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql.
 SQL Build script for Alter Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql.
 SQL Build log file written to E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log.

Solution:

This is acceptable according to the documentation for the step:

Important!
If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the Record being deleted by the Project. Please ignore the warning: Record definition does not exist. Record not processed. (76,73). If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the field being deleted by the Project. Please ignore the warning: Field to be deleted has data present. Record processed. (76,23).DB2 Customers may need to recreate All Views manually by running createvw.dms using Datamover. This is because some views might become inoperable due to dependencies.If Run Create Triggers Script step fails because a trigger does not exist in the database then go to the CREATETRIGGERS.sql script in the Output directory, remove the offending statement and rerun the script.

Application Designer Crashes

Posted by on December 22, 2008 No comments

Problem:

When recreating database (on page 420-421 of Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server), Application Designer crashes on record 2746/4009 while copying project PPLTL84CUR.

Solution:

1. Run Application Designer on glwebapp, not gldbase

2. Copy the PTPATCH project using Application Designer

Others suggestions:

FSCM MP5 partially applied to node. Inconsistent libraries for Application Designer. Reapply MP5.

Allocate more memory to the Java runtime.

Error running rel849n.sql

Posted by on December 21, 2008 No comments

The following errors appear when running rel849n in SQL Server:

Msg 1913, Level 16, State 1, Line 2
The operation failed because an index or statistics with name ‘PSAPSROLECLASS’ already exists on table ‘PSROLECLASS’.
Msg 1913, Level 16, State 1, Line 2
The operation failed because an index or statistics with name ‘PSCPSTREELEAF’ already exists on table ‘PSTREELEAF’.

Solution:

These objects already exist in the database, and the error can be ignored.