Untitled Document
Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: end of day report not printing

  1. #11
    I Have Tried Following These Steps Several Times And Have Not Been Successful. The Tab Marked End Of Day Paperwork Does Not List The Packages. When I Go Into The Packages Tab I Can View The Packages But Tried Copyinh Them To The End Of Day Report Tab And Cannot. Is There Any Otherway Of Retrieving The End Of Day Paperwork?

  2. #12

    Join Date
    Apr 2004
    Posts
    16,462
    SYSOPS is offline
    Could you please post back with the information from the shiprushserver.log file again?

    They should be listed in the end of day paperwork area if they indeed uploaded correctly.

    Thank you,
    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  3. #13
    I Followed These Steps And Cannot Print Or View The End Of Day Reports. I Can View Them Under Packages But Not End Of Day Paperwork.

  4. #14

    Join Date
    Apr 2004
    Posts
    16,462
    SYSOPS is offline
    Christy,
    I need to see the information from the shiprushserver.log file, like we did before. I need to see if there is anything noted in there as to why they didn't complete to the end of day paperwork tab.

    Thank you,
    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  5. #15
    8/17/2004 8:56:54 AM PC_CONFIG No version changes detected
    8/17/2004 8:56:54 AM EOD Start processing EOD request
    8/17/2004 8:56:54 AM EOD Processing EOD, 1 activities found
    8/17/2004 8:56:54 AM MAIL Start checking/processing mail
    8/17/2004 8:56:54 AM MAIL Receiving UPS Mail
    8/17/2004 8:56:57 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 8:56:59 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 8:57:01 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 8:57:01 AM MAIL Sending UPS Mail
    8/17/2004 8:57:01 AM MAIL 0 messages to send
    8/17/2004 9:03:13 AM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 9:03:13 AM PC_CONFIG No version changes detected
    8/17/2004 9:03:13 AM EOD Start processing EOD request
    8/17/2004 9:03:13 AM EOD Processing EOD, 1 activities found
    8/17/2004 9:03:13 AM MAIL Start checking/processing mail
    8/17/2004 9:03:13 AM MAIL Receiving UPS Mail
    8/17/2004 9:03:16 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:03:19 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:03:21 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:03:21 AM MAIL Sending UPS Mail
    8/17/2004 9:03:21 AM MAIL 0 messages to send
    8/17/2004 9:07:47 AM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 9:07:47 AM PC_CONFIG No version changes detected
    8/17/2004 9:07:47 AM EOD Start processing EOD request
    8/17/2004 9:07:47 AM EOD Processing EOD, 1 activities found
    8/17/2004 9:07:47 AM MAIL Start checking/processing mail
    8/17/2004 9:07:47 AM MAIL Receiving UPS Mail
    8/17/2004 9:07:49 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:07:52 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:07:54 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:07:54 AM MAIL Sending UPS Mail
    8/17/2004 9:07:54 AM MAIL 0 messages to send
    8/17/2004 9:21:53 AM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 9:21:53 AM PC_CONFIG No version changes detected
    8/17/2004 9:21:53 AM EOD Start processing EOD request
    8/17/2004 9:21:53 AM EOD Processing EOD, 1 activities found
    8/17/2004 9:21:53 AM MAIL Start checking/processing mail
    8/17/2004 9:21:53 AM MAIL Receiving UPS Mail
    8/17/2004 9:21:56 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:21:59 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:22:01 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 9:22:01 AM MAIL Sending UPS Mail
    8/17/2004 9:22:01 AM MAIL 0 messages to send
    8/17/2004 10:22:25 AM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 10:22:25 AM PC_CONFIG No version changes detected
    8/17/2004 10:22:25 AM EOD Start processing EOD request
    8/17/2004 10:22:25 AM EOD Processing EOD, 1 activities found
    8/17/2004 10:22:25 AM MAIL Start checking/processing mail
    8/17/2004 10:22:25 AM MAIL Receiving UPS Mail
    8/17/2004 10:22:28 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 10:22:32 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 10:22:34 AM MAIL Checking mail - Listed 0 messages
    8/17/2004 10:22:34 AM MAIL Sending UPS Mail
    8/17/2004 10:22:34 AM MAIL 0 messages to send
    8/17/2004 11:24:34 AM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 11:24:34 AM PC_CONFIG No version changes detected
    8/17/2004 11:24:34 AM EOD Start processing EOD request
    8/17/2004 11:24:34 AM EOD Processing EOD, 1 activities found
    8/17/2004 11:24:34 AM MAIL Start checking/processing mail
    8/17/2004 11:24:34 AM MAIL Receiving UPS Mail
    8/17/2004 11:24:34 AM ERROR Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/17/2004 11:24:34 AM MAIL (TUPSCommunicator.ReceiveMail) Error receiving UPS Mail: Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/17/2004 11:24:34 AM MAIL Sending UPS Mail
    8/17/2004 11:24:34 AM MAIL 0 messages to send
    8/17/2004 11:26:31 AM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 11:26:31 AM PC_CONFIG No version changes detected
    8/17/2004 11:26:31 AM EOD Start processing EOD request
    8/17/2004 11:26:31 AM EOD Processing EOD, 1 activities found
    8/17/2004 11:26:31 AM MAIL Start checking/processing mail
    8/17/2004 11:26:31 AM MAIL Receiving UPS Mail
    8/17/2004 11:26:31 AM ERROR Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/17/2004 11:26:31 AM MAIL (TUPSCommunicator.ReceiveMail) Error receiving UPS Mail: Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/17/2004 11:26:31 AM MAIL Sending UPS Mail
    8/17/2004 11:26:31 AM MAIL 0 messages to send
    8/17/2004 1:14:42 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 1:14:42 PM PC_CONFIG No version changes detected
    8/17/2004 1:14:42 PM EOD Start processing EOD request
    8/17/2004 1:14:42 PM EOD Processing EOD, 1 activities found
    8/17/2004 1:14:42 PM MAIL Start checking/processing mail
    8/17/2004 1:14:42 PM MAIL Receiving UPS Mail
    8/17/2004 1:14:45 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 1:14:48 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 1:14:50 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 1:14:50 PM MAIL Sending UPS Mail

  6. #16
    8/17/2004 2:10:10 PM Server Server stopped
    8/17/2004 2:11:01 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/17/2004 2:11:43 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 2:11:44 PM PC_CONFIG Phone List version change detected, Old: "20040628", New: "20040730"
    8/17/2004 2:11:44 PM PC_CONFIG Rates version change detected, Old: "2003", New: "2004"
    8/17/2004 2:11:44 PM PC_CONFIG PC_Config message prepared
    8/17/2004 2:11:44 PM MAIL 1 messages to send
    8/17/2004 2:11:44 PM MAIL Sending mail : Type "PC_CONFIG", File: "c:\program files\z-firm llc\shiprush v3\20040817141144900.MAIL"
    8/17/2004 2:11:50 PM MAIL Done sending mail
    8/17/2004 2:11:51 PM EOD Start processing EOD request
    8/17/2004 2:11:51 PM EOD Processing EOD, 1 activities found
    8/17/2004 2:11:51 PM MAIL Start checking/processing mail
    8/17/2004 2:11:51 PM MAIL Receiving UPS Mail
    8/17/2004 2:11:53 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 2:11:56 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 2:11:58 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 2:11:58 PM MAIL Sending UPS Mail
    8/17/2004 2:11:58 PM MAIL 0 messages to send
    8/18/2004 7:46:08 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 7:55:58 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 8:00:09 AM ERROR (Disconnect) Connection failure
    SQL: SELECT C.BOLD_ID, C.BOLD_TYPE, C.IPAddress, C.ComputerName, C.LastAccess,
    B.READ_ONLY
    FROM ConnectedClient C, ZFRM_OBJECT B
    WHERE B.BOLD_ID = C.BOLD_ID AND C.BOLD_ID = :ID1

    8/18/2004 8:09:43 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 9:20:13 AM Server Server stopped
    8/18/2004 9:21:08 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 9:31:44 AM WARNING (Connect) [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find database ID 5. Database may not be activated yet or may be in transition.
    [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
    8/18/2004 9:31:44 AM CRITICAL (Connect) Cannot open database requested in login 'ShipRush-v3'. Login fails
    8/18/2004 9:31:44 AM SERVICE (ERROR) Unable to start shipping service: Cannot open database requested in login 'ShipRush-v3'. Login fails
    8/18/2004 10:02:42 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 12:01:14 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/18/2004 12:01:15 PM PC_CONFIG No version changes detected
    8/18/2004 12:01:15 PM EOD Start processing EOD request
    8/18/2004 12:01:15 PM EOD Processing EOD, 1 activities found
    8/18/2004 12:01:17 PM EOD Saving PLD, 16 shipments
    8/18/2004 12:01:20 PM EOD PLD saved to file : "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD"
    8/18/2004 12:01:20 PM EOD PLD File saved, activity closed, creating Manifest papers
    8/18/2004 12:01:20 PM EOD Manifest papers created
    8/18/2004 12:01:20 PM EOD Uploading PLD File "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD"
    8/18/2004 12:01:53 PM EOD Uploading PLD - File: "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD", MailBoxID: "SYSTEM_MOS05625988189542", Pickup Date: "20040818", sPLDSeqNum: "000000000000104"
    8/18/2004 12:02:10 PM EOD PLD File "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD" Uploaded
    8/18/2004 12:02:10 PM EOD PLD file uploaded : "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD"
    8/18/2004 12:02:10 PM MAIL Start checking/processing mail
    8/18/2004 12:02:10 PM MAIL Receiving UPS Mail
    8/18/2004 12:02:11 PM ERROR Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/18/2004 12:02:11 PM MAIL (TUPSCommunicator.ReceiveMail) Error receiving UPS Mail: Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/18/2004 12:02:11 PM MAIL Sending UPS Mail
    8/18/2004 12:02:11 PM MAIL 0 messages to send
    8/18/2004 1:03:34 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/18/2004 1:03:34 PM PC_CONFIG No version changes detected
    8/18/2004 1:03:34 PM EOD Start processing EOD request
    8/18/2004 1:03:34 PM EOD Processing EOD, 1 activities found
    8/18/2004 1:03:34 PM MAIL Start checking/processing mail
    8/18/2004 1:03:34 PM MAIL Receiving UPS Mail
    8/18/2004 1:03:37 PM MAIL Checking mail - Listed 0 messages
    8/18/2004 1:03:40 PM MAIL Checking mail - Listed 0 messages
    8/18/2004 1:03:43 PM MAIL Checking mail - Listed 0 messages
    8/18/2004 1:03:43 PM MAIL Sending UPS Mail
    8/18/2004 1:03:43 PM MAIL 0 messages to send

  7. #17

    Join Date
    Apr 2004
    Posts
    16,462
    SYSOPS is offline
    You were able to upload the data from yesterday though, and it shows as being uploaded in the End of Day Paperwork tab?

    I show an error yesterday as of 12:02 that it had not uploaded correctly:
    Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610]

    I don't think we've resolved anything as of yet. I think we're still dealing with the issue that's described in the kbase article:
    http://www.zfirm.com/knowledge_bases...h/sr3p-023.txt

    SYSOPS
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

  8. #18
    not printing

    --------------------------------------------------------------------------------

    8/17/2004 2:10:10 PM Server Server stopped
    8/17/2004 2:11:01 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/17/2004 2:11:43 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/17/2004 2:11:44 PM PC_CONFIG Phone List version change detected, Old: "20040628", New: "20040730"
    8/17/2004 2:11:44 PM PC_CONFIG Rates version change detected, Old: "2003", New: "2004"
    8/17/2004 2:11:44 PM PC_CONFIG PC_Config message prepared
    8/17/2004 2:11:44 PM MAIL 1 messages to send
    8/17/2004 2:11:44 PM MAIL Sending mail : Type "PC_CONFIG", File: "c:\program files\z-firm llc\shiprush v3\20040817141144900.MAIL"
    8/17/2004 2:11:50 PM MAIL Done sending mail
    8/17/2004 2:11:51 PM EOD Start processing EOD request
    8/17/2004 2:11:51 PM EOD Processing EOD, 1 activities found
    8/17/2004 2:11:51 PM MAIL Start checking/processing mail
    8/17/2004 2:11:51 PM MAIL Receiving UPS Mail
    8/17/2004 2:11:53 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 2:11:56 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 2:11:58 PM MAIL Checking mail - Listed 0 messages
    8/17/2004 2:11:58 PM MAIL Sending UPS Mail
    8/17/2004 2:11:58 PM MAIL 0 messages to send
    8/18/2004 7:46:08 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 7:55:58 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 8:00:09 AM ERROR (Disconnect) Connection failure
    SQL: SELECT C.BOLD_ID, C.BOLD_TYPE, C.IPAddress, C.ComputerName, C.LastAccess,
    B.READ_ONLY
    FROM ConnectedClient C, ZFRM_OBJECT B
    WHERE B.BOLD_ID = C.BOLD_ID AND C.BOLD_ID = :ID1

    8/18/2004 8:09:43 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 9:20:13 AM Server Server stopped
    8/18/2004 9:21:08 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 9:31:44 AM WARNING (Connect) [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find database ID 5. Database may not be activated yet or may be in transition.
    [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
    8/18/2004 9:31:44 AM CRITICAL (Connect) Cannot open database requested in login 'ShipRush-v3'. Login fails
    8/18/2004 9:31:44 AM SERVICE (ERROR) Unable to start shipping service: Cannot open database requested in login 'ShipRush-v3'. Login fails
    8/18/2004 10:02:42 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.281 ******************
    8/18/2004 12:01:14 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/18/2004 12:01:15 PM PC_CONFIG No version changes detected
    8/18/2004 12:01:15 PM EOD Start processing EOD request
    8/18/2004 12:01:15 PM EOD Processing EOD, 1 activities found
    8/18/2004 12:01:17 PM EOD Saving PLD, 16 shipments
    8/18/2004 12:01:20 PM EOD PLD saved to file : "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD"
    8/18/2004 12:01:20 PM EOD PLD File saved, activity closed, creating Manifest papers
    8/18/2004 12:01:20 PM EOD Manifest papers created
    8/18/2004 12:01:20 PM EOD Uploading PLD File "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD"
    8/18/2004 12:01:53 PM EOD Uploading PLD - File: "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD", MailBoxID: "SYSTEM_MOS05625988189542", Pickup Date: "20040818", sPLDSeqNum: "000000000000104"
    8/18/2004 12:02:10 PM EOD PLD File "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD" Uploaded
    8/18/2004 12:02:10 PM EOD PLD file uploaded : "c:\program files\z-firm llc\shiprush v3\PLD\20040818120115546.PLD"
    8/18/2004 12:02:10 PM MAIL Start checking/processing mail
    8/18/2004 12:02:10 PM MAIL Receiving UPS Mail
    8/18/2004 12:02:11 PM ERROR Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/18/2004 12:02:11 PM MAIL (TUPSCommunicator.ReceiveMail) Error receiving UPS Mail: Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
    (Low level error: Unable to connect to server www.upslinkvendor.ups.comNetwork address type not supported. [53610])
    8/18/2004 12:02:11 PM MAIL Sending UPS Mail
    8/18/2004 12:02:11 PM MAIL 0 messages to send
    8/18/2004 1:03:34 PM PC_CONFIG Checking if UPS Components versions need to be updated...
    8/18/2004 1:03:34 PM PC_CONFIG No version changes detected
    8/18/2004 1:03:34 PM EOD Start processing EOD request
    8/18/2004 1:03:34 PM EOD Processing EOD, 1 activities found
    8/18/2004 1:03:34 PM MAIL Start checking/processing mail
    8/18/2004 1:03:34 PM MAIL Receiving UPS Mail
    8/18/2004 1:03:37 PM MAIL Checking mail - Listed 0 messages
    8/18/2004 1:03:40 PM MAIL Checking mail - Listed 0 messages
    8/18/2004 1:03:43 PM MAIL Checking mail - Listed 0 messages
    8/18/2004 1:03:43 PM MAIL Sending UPS Mail
    8/18/2004 1:03:43 PM MAIL 0 messages to send

  9. #19
    THIS INFORMATION WAS PROVIDED BY FOLLOWING THE STEPS YOU REQUESTED. IF I AM READING THIS COORRECTLY IT IS SAYING BY OPENING THIS PORT IT COULD BE HARMFUL TO THE SYSTEM. YOU ARE SUGGESTING THAT THE PROBLEM WITH THE SERVER CONNECTING COULD BE THAT THIS PORT IS NOT OPEN?


    Purpose:
    World Wide Web HTTP

    Description:
    This is the primary port used by the world wide web (www) system. Web servers open this port then listen for incoming connections from web browsers. Similarly, when a web browser is given a remote address (like grc.com or amazon.com), it assumes that a remote web server will be listening for connections on port 80 at that location.

    Related Ports:
    81, 82, 443, 8080, 8090




    Background and Additional Information:


    This port will generally be open only when a web server of some sort is running on the machine. However, as you can see from the extensive list of Trojan sightings below, there is no shortage of malicious software trying to inhabit this port. The widespread Code Red and Nimda worms are still alive, and are likely to survive out on the Internet for many more years. They continue searching for vulnerable systems into which they can reproduce wherever and whenever possible. Since they attempt to infect unpatched Microsoft web servers — even the "Personal Web Server" sometimes installed in end-user versions of Windows — Microsoft servers must always be patched and protected against worm infestation.
    Due to the popularity of this port for malicious exploitation, it should never be open unless it is being actively and deliberately used to serve web pages. And then, any publicly accessible web servers must be proactively maintained and kept current with the latest security patches to keep them safe.

    Many ISPs now block incoming traffic to this port before it reaches their customers. This is done for several reasons: The prevalence of malicious port 80 Trojans renders outside access to this port dangerous. Many Windows users are inadvertently running or have not patched and are not maintaining copies of Microsoft's web servers. As we know, active scanning by self-propagating worms is constantly attempting to locate and infect such servers. Additionally, the terms of service of many ISPs forbids end-users to offer web services to the Internet. Blocking incoming traffic to port 80 can be an enforcement of ISP policies as well as a significant boon to end-user security.

    Poorly configured DSL and NAT routers sometimes expose their web-based configuration management interfaces to the Internet. If you are not running a local web server, and our tests show that port 80 is open on your machine, you will certainly want to determine what's going on. If you have a DSL or NAT router, be sure to check that its web interface is disabled on the "WAN" — wide area network (Internet) — side.

    For information about secure web (https) connections, please see the Port Authority page for port 443.

  10. #20

    Join Date
    Apr 2004
    Posts
    16,462
    SYSOPS is offline
    As discussed on the phone, the issue was you did an update to ShipRush to resolve an error. I was never told what that error was. It was related to the kbase article:
    http://www.zfirm.com/knowledge_bases.../sr3p-0008.txt

    StringTooLong.

    Once that was established, we could finish up the resolution according to the kbase article.

    SYSOPS
    Last edited by SYSOPS; 08-19-2004 at 09:29 AM.
    Have Questions? Ask the ShipRush Knowledge Base: https://shiprush.com/kbase
    Reply With Quote

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •