Difference between revisions of "TF400Gateway TroubleShooting"
(→Using In Conjunction With Cloud Fax 400) |
|||
(23 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | The first thing to do | + | The first thing to do is check the log files in the C:\TF400Gateway\Log directory for the word "error" |
+ | |||
+ | For general diagnosis the logging can be set to level 4. | ||
+ | |||
+ | For optimum performance, and minimum logs we can set the level to 0. | ||
Anything other than a Socket Error is considered fatal and needs to be investigated further. | Anything other than a Socket Error is considered fatal and needs to be investigated further. | ||
− | Once a message has been released from the as400, this should appear as an AQR in the TF400Gateway log, so | + | Once a message has been released from the as400, this should appear as an AQR in the TF400Gateway log, so check the gateway logs for that. |
After this we see a variety of packet types:- | After this we see a variety of packet types:- | ||
− | + | AQR - Add Queue Request | |
− | + | ||
MOQ - Message On Queue | MOQ - Message On Queue | ||
− | |||
MNQ - Message Not Queued | MNQ - Message Not Queued | ||
− | |||
QRU - Queue Request Update | QRU - Queue Request Update | ||
+ | DQR - Delete Queue Record | ||
+ | IRR - Incoming Resource Request | ||
+ | AYT - Are You There | ||
+ | |||
+ | == Clearing Out Files == | ||
+ | |||
+ | Before stopping and starting the TF400Gateway services and the as400 drivers you may want to clean out the following folders:- | ||
+ | |||
+ | TF400Gateway\Log | ||
+ | |||
+ | TF400Gateway\TF400\Cache | ||
+ | |||
+ | TF400Gateway\TF400\In | ||
+ | |||
+ | TF400Gateway\TF400\Out | ||
+ | |||
+ | TF400Gateway\TF400\Temp | ||
+ | |||
+ | TF400Gateway\TF400\Queue | ||
+ | |||
+ | Note, the Queue folder contains files relating to items that have been queued but haven't yet gone or failed, | ||
+ | so deleting these files will result in their status's being lost. | ||
+ | |||
+ | == Sending Faxes == | ||
+ | |||
+ | When sending a fax the AQR travels down to the TF400Gateway. | ||
+ | |||
+ | The message is then requested from the AS400 and downloaded to the TF400Gateway and converted into the correct format. | ||
+ | |||
+ | The TF400Gateway then interacts with FaxCom via an api to create the fax. | ||
+ | |||
+ | This can be found in the log:- | ||
+ | |||
+ | TFQueueMgr : tr333 Entering AddItemFaxCom | ||
+ | |||
+ | Later on the TF400Gateway asks FaxCom where the message is:- | ||
+ | |||
+ | FaxCom : tr333 Entering Query | ||
+ | |||
+ | The TF400Gateway first looks in the pending and then looks in sent queue for the message. | ||
+ | |||
+ | == Sending Emails == | ||
When the message type is an email as opposed to fax, we should see CreateFile | When the message type is an email as opposed to fax, we should see CreateFile | ||
+ | |||
+ | ProjEmail : Entering CreateFile | ||
+ | |||
+ | Then Later | ||
+ | |||
+ | ProjEmail : sfcn7307 Updating File E:\Tf400Gateway\tf400\HostQNum_A.ini | ||
+ | ProjEmail : Writing line 'A64083' | ||
+ | ProjEmail : strDirPath=E:\Program Files\IMPSGATEWAY\FILES\SMTP\SMTPimpsscan\A64083\ | ||
+ | |||
+ | HostQNum_A.ini contains the Next Reference that will be created in the Impsgateway scan directory. | ||
+ | Once this folder has been created the HostQNum_A.ini will be incremented. | ||
+ | |||
+ | Because the TF400Gateway can interact with several AS400s there may be more than one HostQNum file. | ||
+ | One for each driver, eg HostQNum_A.ini, HostQNum_B.ini etc. | ||
+ | |||
+ | == Using In Conjunction With Cloud Fax 400 == | ||
+ | |||
+ | It is possible to use the TF400Gateway with a FaxCom server and use the FaxAttendant/CloudFax400Gateway by setting:- | ||
+ | |||
+ | FaxCloudSendLogAuditRequest=true in the TF400.ini file. | ||
+ | |||
+ | The TF400Gateway will then send packets of info for logging as well as copies of faxes to the FaxAttendant/CloudFax400Gateway so that we can use the FaxAttendant/CloudFax400Gateway for logging and diagnosis. | ||
+ | |||
+ | To use just the CloudFax400Gateway and send faxes through the CloudFax400Gateway, you should set:- | ||
+ | |||
+ | FaxCloudSendLogAuditRequest=false | ||
+ | |||
+ | FaxCloudEnabled=true | ||
+ | |||
+ | So in this way, there are two modes in which to use the Cloud Fax 400 with the TF400Gateway | ||
+ | |||
+ | As an audit trail/reporting server | ||
+ | FaxCloudSendLogAuditRequest=true | ||
+ | FaxCloudEnabled=false | ||
+ | |||
+ | As a pure fax provider and audit trail/reporting server (this means that faxes are not set via a FaxCom server, but are sent instead through the cloud using FaxCom Anywhere) | ||
+ | FaxCloudSendLogAuditRequest=false | ||
+ | FaxCloudEnabled=true | ||
+ | |||
+ | |||
+ | Packets the TF400Gateway sends to the CloudFax400Gateway | ||
+ | |||
+ | LAR - Log Audit Request | ||
+ | IAR - Incoming Audit Request | ||
+ | FSU - Failed Status Update | ||
+ | AMR - Archive Message Request | ||
+ | SFR - Scan Folder Reuest | ||
+ | |||
+ | == TF400.Ini File == | ||
[TF400] | [TF400] |
Latest revision as of 15:33, 1 November 2011
The first thing to do is check the log files in the C:\TF400Gateway\Log directory for the word "error"
For general diagnosis the logging can be set to level 4.
For optimum performance, and minimum logs we can set the level to 0.
Anything other than a Socket Error is considered fatal and needs to be investigated further.
Once a message has been released from the as400, this should appear as an AQR in the TF400Gateway log, so check the gateway logs for that.
After this we see a variety of packet types:-
AQR - Add Queue Request MOQ - Message On Queue MNQ - Message Not Queued QRU - Queue Request Update DQR - Delete Queue Record IRR - Incoming Resource Request AYT - Are You There
Contents
Clearing Out Files
Before stopping and starting the TF400Gateway services and the as400 drivers you may want to clean out the following folders:-
TF400Gateway\Log
TF400Gateway\TF400\Cache
TF400Gateway\TF400\In
TF400Gateway\TF400\Out
TF400Gateway\TF400\Temp
TF400Gateway\TF400\Queue
Note, the Queue folder contains files relating to items that have been queued but haven't yet gone or failed, so deleting these files will result in their status's being lost.
Sending Faxes
When sending a fax the AQR travels down to the TF400Gateway.
The message is then requested from the AS400 and downloaded to the TF400Gateway and converted into the correct format.
The TF400Gateway then interacts with FaxCom via an api to create the fax.
This can be found in the log:-
TFQueueMgr : tr333 Entering AddItemFaxCom
Later on the TF400Gateway asks FaxCom where the message is:-
FaxCom : tr333 Entering Query
The TF400Gateway first looks in the pending and then looks in sent queue for the message.
Sending Emails
When the message type is an email as opposed to fax, we should see CreateFile
ProjEmail : Entering CreateFile
Then Later
ProjEmail : sfcn7307 Updating File E:\Tf400Gateway\tf400\HostQNum_A.ini ProjEmail : Writing line 'A64083' ProjEmail : strDirPath=E:\Program Files\IMPSGATEWAY\FILES\SMTP\SMTPimpsscan\A64083\
HostQNum_A.ini contains the Next Reference that will be created in the Impsgateway scan directory. Once this folder has been created the HostQNum_A.ini will be incremented.
Because the TF400Gateway can interact with several AS400s there may be more than one HostQNum file. One for each driver, eg HostQNum_A.ini, HostQNum_B.ini etc.
Using In Conjunction With Cloud Fax 400
It is possible to use the TF400Gateway with a FaxCom server and use the FaxAttendant/CloudFax400Gateway by setting:-
FaxCloudSendLogAuditRequest=true in the TF400.ini file.
The TF400Gateway will then send packets of info for logging as well as copies of faxes to the FaxAttendant/CloudFax400Gateway so that we can use the FaxAttendant/CloudFax400Gateway for logging and diagnosis.
To use just the CloudFax400Gateway and send faxes through the CloudFax400Gateway, you should set:-
FaxCloudSendLogAuditRequest=false
FaxCloudEnabled=true
So in this way, there are two modes in which to use the Cloud Fax 400 with the TF400Gateway
As an audit trail/reporting server FaxCloudSendLogAuditRequest=true FaxCloudEnabled=false
As a pure fax provider and audit trail/reporting server (this means that faxes are not set via a FaxCom server, but are sent instead through the cloud using FaxCom Anywhere) FaxCloudSendLogAuditRequest=false FaxCloudEnabled=true
Packets the TF400Gateway sends to the CloudFax400Gateway
LAR - Log Audit Request IAR - Incoming Audit Request FSU - Failed Status Update AMR - Archive Message Request SFR - Scan Folder Reuest
TF400.Ini File
[TF400] ActivitySortType=2 Archiving=None AS400Port=5203 CheckMissedStatusIntervalInMinutes=30 debug-level=4 DefaultAs400IPAddress=192.168.65.18 DefaultAs400Name=ep400p1 DialSuffix= DriverID=A EmailRecordsToCheck=5 EmailTimerIntervalBusy=5 EmailTimerIntervalQuiet=60 EuroCharRequired=TRUE FaxAtt33kConvertWaitTime=5 FaxAttTrysBeforeFail=10 FaxComServerName=E:\program files\Biscom\FaxcomQ_Queue01 FaxComUserName=Administrator FONT=CO ForcePCLOverlay= ForwardFaxMessagesToRouting=false HostAddress=@presencebpm.com ImpsGateWayPath=E:\Program Files\IMPSGATEWAY ImpsgatewayRoutingScanFolder=e:\Program Files\Impsgateway\Files\Routing\RoutingScan\ IncomingImpsgatewayRoutingScanFolder=e:\Program Files\Impsgateway\Files\Routing\RoutingScan\ IncomingNextImpsgatewayRoutingFolder= 2179 IncomingNextImpsgatewayRoutingTifFileNumber= 6000098 IncomingScanFolder=E:\Faxin IncomingUploadToAS400=true IncomingUploadToImpsgateway=false LincolnEPFaxCLPath=E:\program files\Biscom\FAXCOM Server\u\EPFax\Bin\EPFaxCL.exe LOCALE=EN-UK MAILGATE-MAIL=TF400 MainWindow=TF400 MAX_LEGALPAGE_LENGTH_USABLE=1425 MAX_LETTERPAGE_LENGTH_USABLE=1122 MAX_USA_LETTERPAGE_LENGTH_USABLE=1055 MaxDataRead=7168 MaxDelRecsInUploadQueue=40 MaximumActivitiesToQuery=3 MIN_LEGALPAGE_LENGTH=1245 OverrideConvertStatusToIdle= PCLPageSize=2280 Port=7773 PrintAllPages=TRUE PrintPageLimit=100 PrintServerCheck=2 ReverseSort=FALSE Service-Application=TF400$DIRECTORY:TFRequestHandler.exe SLEEP=15 SockInBuffer=8192 STD_LEGALPAGE_LENGTH_USABLE=1369 SystemDateFormat=MM/dd/yyyy Transport=TCPIP UseDefaultCoverPage=false UseLincolnConverter=True Version=7.6.4 FaxComPassword= [Logicals] TF400$DIRECTORY=E:\TF400Gateway\ TF400$LOG=E:\TF400Gateway\Log\ TF400$TF400=E:\TF400Gateway\TF400\ TF400$TF400_IN=E:\TF400Gateway\TF400\In\ [CloudFax400] FaxCloudDateFormat=dd/MM/yyyyHH:mm:ss FaxCloudDirectory=\\grahamxp\c$\CloudFax400_Files\ FaxCloudEnabled=false FaxCloudGatewayAddress=192.168.65.27 FaxCloudGatewayPortListen=4450 FaxCloudGatewayPortSend=4451 FaxCloudMOQTimeOut=120 FaxCloudSendLogAuditRequest=true FaxCloudTF400GatewayMachineName=SQLSERVEREP FaxCloudTimerIntervalBusy=5 FaxCloudTimerIntervalQuiet=60