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.

Hyperlink not appearing for Posted reports

Posted by on December 30, 2008 No comments

Problem:

Under Process Monitor (PeopleTools > Process Scheduler > Process Monitor), reports are completing successfully, but hyperlinks to the posted reports are not appearing.

Solution:

The hyperlink appears under the Details column:

1. Select
2. Instance
3. Seq.
4. Process Type
5. Process Name
6. User
7. Run Date/Time
8. Run Status
9. Distribution Status
10. Details

Also, ensure that Publish/Subscribe (Pub/Sub) is enabled in the Application Server.

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.

COBOL targets failed to compile or link

Posted by on December 29, 2008 No comments

Problem:

After deploying files from MP5, the COBOL programs must be compiled. However, some files do not compile:

E:tempcompile>set PS_HOME=E:PSOFTFS900
E:tempcompile>set COBROOT=E:cobolBase
E:tempcompile>cd /d E:PSOFTFS900setup
E:PSOFTFS900setup>cblbld E: tempcompile

ASCII Cobol Compilations Proceeding
Logging progress to file E:tempcompileCBLBLD.LOG
COBOL compiler found in E:cobolBase
Target directory (E:PSOFTFS900CBLBINA) exists and is writable

Copying source files …

Building the COBOL targets …
File(s) that failed to compile or link:
.
Compile error for CPPIPRDN.obj
Compile error for INPFVALD.obj
Compile error for INPGPROC.obj
Compile error for INPGREPL.obj
Compile error for INPJIURV.obj
Compile error for INPPPROC.obj
Compile error for INPTVALD.obj
Compile error for INPVPROC.obj
Compile error for INPVVALD.obj
Compile error for INPZPWFB.obj
Compile error for SFPBPCFG.obj
Compile error for SFPDCDRV.obj
Compile error for SFPDCOMP.obj
Compile error for SFPDCVAL.obj
Compile error for SFPDISUE.obj
Compile error for SFPSGBRC.obj
Compile error for SFPSUPDT.obj
Compile error for SFPSVALD.obj
The error list is in E:tempcompileERROR.LIS
.
Aborting this process !!! EXEs/GNTs/INTs are not going to be copied/replaced…
.
Please fix the errors and rerun this batch file !!!!!!!
.

Symptoms:

The problem is with COBOL compiles, where if the customer doesn’t have all the products licensed when we compile the COBOLs from recent Maintenance Packs we get errors. This is due to the fact that CA is not looking at the licensed products or dbcodes to validate licensed products. Therefore errors are displayed during the compilation as copybooks are not supplied for the non licensed products.

Here’s an example list of the COBOLs that don’t compile:
CEPCSQL2, CPPICSTI, CPPIPRDN, INPADYN3, INPADYN4, INPAPROC, INPIVALD, INPOTEST, INPSDRCT, INPVIADJ, INPVPROC, INPVVALD, INPXPROC, SFPDISUE, SFPEPROC, SFPFPROC, SFPREVAL

Here’s a copy of what’s in the dbcodes.ep:
EP PeopleSoft FIN/SCM Database
EP PeopleSoft FIN/SCM Demo Database
AM PeopleSoft Asset Management
CM PeopleSoft Cash Management
CO PeopleSoft Common Objects
TR = PeopleSoft Deal Management
EO = PeopleSoft Enterprise Components
EPO = PeopleSoft eProcurement
GL = PeopleSoft General Ledger
AP = PeopleSoft Payables
PO = PeopleSoft Purchasing

Cause:
Not Applicable

Solution:

Tools incident 714685000 was created. The incident is considered to be an enhancement for change assistant in a tools versions greater than 8.45.

If the customer does not have licenses for the modules related to the cobol files that are failing, they can ignore the compile errors. If they do not want to ignore the error messages, they can remove the erroring files from the src directory (move them to another directory) and run compile again.

Reference:

E-CA Change assistant not checking the license before compiling the cobols (Doc ID 623178.1)

Cannot locate any Change Packages in the apply directory

Posted by on December 27, 2008 No comments

Problem:

In Change Assistant (on glwebapp), navigated to Tools > Apply Change Packages. Went through wizard and reached Select apply directory. Chose directory E:staging, but the following error appeared:

Cannot locate any Change Packages in the apply directory

Solution:

Choose directory that contains the zip file of the downloaded patch (e.g. the directory that contains upd745700.zip, E:stagingCDImagescd849-FinMP5Cumulative).

Compiling COBOL Programs Using cblmake

Posted by on December 24, 2008 No comments

set PS_HOME=E:PSOFTFS900
set COBROOT=”C:Program FilesMicro FocusNet Express 5.0Base”
E:PSOFTFS900srccblwin32cblmake FSP*
E:PSOFTFS900srccblwin32cblmake GLP*

Note that the above commands assume that the current working directory is the directory with the COBOL programs. It may be a good idea to run the cblmake, after running cblbld and the current working directory is that with the output of the cblbld programs (e.g. E:tempcompile_20081223b).