ForceField email Order Acknowledgement Troubleshooter

1. Look in the /Jargonsoft/Reports/XXX on the handheld to see if the OA html file was created during the sync upload.
These files do not get removed after upload so s/b there still. (Only sig files get deleted).

2. Look in the /inetpub/wwwroot/Jargon_XXX/upload/Sigs folder on the server to see if the file exists on the server.

3. Look in the sync log on the server to see if the upload routine was run and whether it failed.
( see the upload function below for log message contents).

function UploadFile() {
  $upload_dir  = GetParam('HostDir');
  $path = $upload_dir . '/' . $_FILES['userfile']['name'];
  WriteLog ("Received {$_FILES['userfile']['name']} - its size is {$_FILES['userfile']['size']}");
  WriteLog ("Attempting to store as: $path");
  if (move_uploaded_file($_FILES['userfile']['tmp_name'], $path)) {
    WriteLog ("File upload succeeded");
    return true;
  }
  else {
    WriteLog ("** File upload failed **");
    return false;
  }
}


4. In the sync.xml app, for each order to be uploaded, it first builds an OA html file and uploads using the function in #3 above, before the order upload itself.
The users on these routes need to pay attention to the sync log on their handhelds after an upload, until this is resolved. They need to scroll thru and look at the messages for each order.

If it works, they will see a message:
'Sent: ' + (doc filename)

If it fails, they will see this error:
"Failed to create and upload OA print file: " + (doc filename)


Article Details

Article ID:
121
Date added:
2012-06-14 19:59:18
Views:
656
Rating (Votes):
(563)