Error Handling and Resolution

Outgoing Messages from the PeopleSoft server to the TCD server: TL_OUTTCD is successful: No messages generated.

Make sure that:

—Queues are in Run mode.

—Routings are specified in the service operations.

—Service operations are active.

—Batch Publish Rule is selected.

—External Node and Transaction Routing Type is specified as Explicit, instead of Implicit.

Incoming messages from the TCD server to the PeopleSoft server. This error message appeared:

"<?xml version="1.0" ?><reply><operations><exception><title>Publish Subscribe Message Exception</title><defaultmsg>psft.pt8.gateway.PublicationHandlerException: </defaultmsg><msgset>94</msgset><msgid>1</msgid><parameters count="1"><parm>psft.pt8.gateway.PublicationHandlerException: </parm></parameters></exception></operations></reply> <?xml version="1.0" ?><reply><operations><exception><title>Publish Subscribe Message Exception</title><defaultmsg>psft.pt8.gateway.PublicationHandlerException: </defaultmsg><msgset>94</msgset><msgid>1</msgid><parameters count="1"><parm>psft.pt8.gateway.PublicationHandlerException: </parm></parameters></exception></operations></reply>"

This error message signifies that the transaction is not specified for that TCD Server node.

Ping does not work from the People Soft server to the TCD server.

Make sure you are using the appropriate target connector as discussed in Node configuration.

How do I purge message details?

DELETE FROM PSAPMSGPUBHDR;

DELETE FROM PSAPMSGPUBDATA;

DELETE FROM PSAPMSGPUBCON;

DELETE FROM PSAPMSGSUBCON;

DELETE FROM PSAPMSGPUBCERR;

DELETE FROM PSAPMSGPUBERR;

DELETE FROM PSAPMSGSUBCERR;

DELETE FROM PSAPMSGPUBCERRP;

DELETE FROM PSAPMSGPUBERRP;

DELETE FROM PSAPMSGSUBCERRP;

DELETE FROM PSAPMSGARCHPC;

DELETE FROM PSAPMSGARCHPD;

DELETE FROM PSAPMSGARCHPH;

DELETE FROM PSAPMSGARCHSC;

Flat files were not created for outbound messages, but messages were generated in the Service Operations Monitor.

Make sure that:

Routing are defined properly in the service operations.

—Handlers are active on all the service operations.

—You are looking at the right location, which is specified on TL Installation page (TL General setting).

—TL_OUTTCD has not generated any errors.

—Your Application server and process scheduler has read and write access to the file location.

The flat file is not empty after the Inbound File Publish process is run.

Make sure that:

—The file location is properly specified on the Inbound File Rule page.

—Inbound File Rule is active.

—The Inbound File process run control has Process Frequency set to Always or Once (as needed).

—You are following comma delimiter for each column.

—The Inbound File Rule is active.

—The file name is ELAPSED_TIME*.CSV or PUNCHED_TIME*.CSV

The messages transactions are not same as in the flat file.

Make sure that each row in the flat file has a carriage return in the sense each transaction should be a new line in simple sense each line by hitting your return/key.

I am getting a large message.

When the message size exceeds the size set on the PeopleTools, Options pages, the message splits into multiple messages. For Full-sync, there would be one header followed by multiple data messages and then one trailer.

I am receiving header and footer information only.

Service Operations are active but probably TCD Type setup is not appropriate, or no data to publish Task elements and or time reporting elements or schedules.

Where can I find the Message log and the Error log?

Msg Log : http://server/PSIGW/msgLog.html and,

Error Log : http://server/PSIGW/errorLog.html