PDA

View Full Version : Shiprush can't connect to server



Dennis Klein
06-02-2004, 09:05 AM
When I tried to start ShipRush this morning, as I do most mornings, it exhibited a screen I've not seen before - "Connect To...."

This happened whether I tried to start ShipRush under Quickbooks or stand-alone. Whichever choice I tried (ShipRush server at; or Connect to ShipRush server via ADO) ended up in error messages that denied me access to the server. Why??

Please respond urgently, as this is holding up my morning shipments.

Dennis Klein
Karmel Games, Inc.
805-499-3321

SYSOPS
06-02-2004, 10:35 AM
Afternoon Dennis,
What is the actual error that you're getting?

Please refer to the kbase article on this at:
http://www.zfirm.com/kbase/shiprush/sr3p-0003.txt

Also, could post back with information from the shiprushserver.log file located under program files\z-firm llc\shiprush v3 and from shiprushclient.log located under documents and settings\username\application data\z-firm llc\shiprush v3?

That may help indicate what the issue is.

Thank you,
SYSOPS

Dennis Klein
06-02-2004, 05:48 PM
Hi,

I checked the article to which you referred and found that "MSSQL$SHIPRUSH3" had started, but "Z-Firm ShipRush v3" had not (even though it was set for automatic). I started it manually, then tried to start ShipRush. On the opening window, it said Connecting... then simply hung the whole computer. I had to actually unplug the PC to turn it off. I tried several attempts, even re-installing ShipRush -- nothing works.

What next???

Dennis Klein

****************
Info from ShipRushServer.log:

5/24/2004 5:39:19 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/24/2004 5:56:28 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/24/2004 11:28:07 PM PC_CONFIG Checking if UPS Components versions need to be updated...
5/24/2004 11:28:09 PM PC_CONFIG Phone List version change detected, Old: "20040402", New: "20040430"
5/24/2004 11:28:09 PM PC_CONFIG PC_Config message prepared
5/24/2004 11:28:09 PM MAIL 1 messages to send
5/24/2004 11:28:10 PM MAIL Sending mail : Type "PC_CONFIG", File: "c:\program files\z-firm llc\shiprush v3\20040524232810195.MAIL"
5/24/2004 11:28:13 PM MAIL Done sending mail
5/24/2004 11:28:13 PM EOD Start processing EOD request
5/24/2004 11:28:13 PM EOD Processing EOD, 1 activities found
5/24/2004 11:28:14 PM EOD Saving PLD, 1 shipments
5/24/2004 11:28:15 PM EOD PLD saved to file : "c:\program files\z-firm llc\shiprush v3\PLD\20040524232813509.PLD"
5/24/2004 11:28:15 PM EOD PLD File saved, activity closed, creating Manifest papers
5/24/2004 11:28:15 PM EOD Manifest papers created
5/24/2004 11:28:16 PM EOD Uploading PLD File "c:\program files\z-firm llc\shiprush v3\PLD\20040524232813509.PLD"
5/24/2004 11:28:16 PM EOD Uploading PLD - File: "c:\program files\z-firm llc\shiprush v3\PLD\20040524232813509.PLD", MailBoxID: "SYSTEM_MOS05551077114634", Pickup Date: "20040524", sPLDSeqNum: "000000000000049"
5/24/2004 11:28:16 PM EOD PLD File "c:\program files\z-firm llc\shiprush v3\PLD\20040524232813509.PLD" Uploaded
5/24/2004 11:28:16 PM EOD PLD file uploaded : "c:\program files\z-firm llc\shiprush v3\PLD\20040524232813509.PLD"
5/24/2004 11:28:16 PM MAIL Start checking/processing mail
5/24/2004 11:28:16 PM MAIL Receiving UPS Mail
5/24/2004 11:28:17 PM MAIL Checking mail - Listed 0 messages
5/24/2004 11:28:18 PM MAIL Checking mail - Listed 0 messages
5/24/2004 11:28:18 PM MAIL Checking mail - Listed 1 messages
5/24/2004 11:28:18 PM MAIL Reading mail: Message ID: 51, RefNum: "04051814460123.04462579", sReadName: ""
5/24/2004 11:28:19 PM ERROR Unable to upload data to UPS. Please check your internet connection and configuration, and upload again.
(Low level error: HttpComm error: HTTP object not found. [53404])
5/24/2004 11:28:19 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: HttpComm error: HTTP object not found. [53404])
5/24/2004 11:28:19 PM MAIL Sending UPS Mail
5/24/2004 11:28:19 PM MAIL 0 messages to send
5/24/2004 11:51:35 PM CRITICAL Unable to start/stop server thread: REBUILD PROJECT FIRST (D:\Develop\components\production\shipping\UpsBold \BusinessClasses\zfb_UPSManager.inc, line 255)
5/25/2004 5:32:33 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/25/2004 2:12:16 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/25/2004 11:36:27 PM CRITICAL Unable to start/stop server thread: Access violation at address 0091AA0E in module 'ShipRushServer.exe'. Read of address 00000000
5/26/2004 5:43:48 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/26/2004 6:33:51 AM CRITICAL Unable to start/stop server thread: REBUILD PROJECT FIRST (D:\Develop\components\production\shipping\UpsBold \BusinessClasses\zfb_UPSManager.inc, line 255)
5/26/2004 6:36:10 AM CRITICAL (Connect) Timeout expired
5/26/2004 6:36:10 AM SERVICE (ERROR) Unable to start shipping service: Timeout expired
5/26/2004 3:02:42 PM CRITICAL (Connect) Timeout expired
5/26/2004 3:02:42 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
5/26/2004 3:43:43 PM CRITICAL (Connect) Timeout expired
5/26/2004 3:43:43 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
5/26/2004 4:25:26 PM CRITICAL (Connect) Timeout expired
5/26/2004 4:25:26 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
5/27/2004 4:58:33 AM CRITICAL (Connect) Timeout expired
5/27/2004 4:58:33 AM SERVICE (ERROR) Unable to start shipping service: Timeout expired
5/27/2004 8:35:28 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/28/2004 6:07:04 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/28/2004 10:51:12 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/29/2004 4:11:15 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/30/2004 5:49:46 AM CRITICAL (Connect) Timeout expired
5/30/2004 5:49:46 AM SERVICE (ERROR) Unable to start shipping service: Timeout expired
5/31/2004 2:33:46 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/31/2004 5:22:25 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
5/31/2004 5:46:52 PM CRITICAL (Connect) Timeout expired
5/31/2004 5:46:52 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/1/2004 4:39:38 AM CRITICAL (Connect) Timeout expired
6/1/2004 4:39:38 AM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/2/2004 7:48:31 AM CRITICAL (Connect) Timeout expired
6/2/2004 7:48:31 AM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/2/2004 2:54:52 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
6/2/2004 3:01:15 PM CRITICAL Unable to start/stop server thread: REBUILD PROJECT FIRST (D:\Develop\components\production\shipping\UpsBold \BusinessClasses\zfb_UPSManager.inc, line 255)
6/2/2004 3:03:21 PM CRITICAL (Connect) Timeout expired
6/2/2004 3:03:21 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/2/2004 3:13:23 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
6/2/2004 4:42:54 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
6/2/2004 4:52:03 PM CRITICAL (Connect) Timeout expired
6/2/2004 4:52:03 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/2/2004 5:17:12 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
6/2/2004 5:24:58 PM CRITICAL (Connect) Timeout expired
6/2/2004 5:24:58 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/2/2004 5:33:10 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
6/2/2004 5:38:28 PM CRITICAL (Connect) Timeout expired
6/2/2004 5:38:28 PM SERVICE (ERROR) Unable to start shipping service: Timeout expired
6/2/2004 6:22:41 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************
6/2/2004 6:27:00 PM Server ********** Server started: ShipRushServer.exe version 3.0.0.276 ******************

****************
Info from ShipRush3.log:

6/2/2004 2:59:05 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
6/2/2004 2:59:35 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
6/2/2004 3:04:35 PM CRITICAL (Connect) A connection with the server could not be established - URL:http://localhost:1123/SOAP/IBoldSynapse - SOAPAction:urn:BoldSynapseInterface-IBoldSynapse#SignOn
6/2/2004 3:04:46 PM CRITICAL (Connect) A connection with the server could not be established - URL:http://localhost:1123/SOAP/IBoldSynapse - SOAPAction:urn:BoldSynapseInterface-IBoldSynapse#SignOn
6/2/2004 3:05:52 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
6/2/2004 3:06:15 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
6/2/2004 3:07:46 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
6/2/2004 3:08:07 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
6/2/2004 3:08:45 PM CRITICAL (Connect) A connection with the server could not be established - URL:http://localhost:1123/SOAP/IBoldSynapse - SOAPAction:urn:BoldSynapseInterface-IBoldSynapse#SignOn
6/2/2004 3:09:01 PM CRITICAL (Connect) A connection with the server could not be established - URL:http://localhost:1123/SOAP/IBoldSynapse - SOAPAction:urn:BoldSynapseInterface-IBoldSynapse#SignOn
6/2/2004 6:21:44 PM CRITICAL (Connect) A connection with the server could not be established - URL:http://localhost:1123/SOAP/IBoldSynapse - SOAPAction:urn:BoldSynapseInterface-IBoldSynapse#SignOn
6/2/2004 6:21:51 PM CRITICAL (Connect) A connection with the server could not be established - URL:http://localhost:1123/SOAP/IBoldSynapse - SOAPAction:urn:BoldSynapseInterface-IBoldSynapse#SignOn

Peggy Payne
06-04-2004, 09:18 AM
I am having this same problem...what do I do?

SYSOPR
06-04-2004, 10:12 AM
Stand by. A resolution is in the works.

Dennis Klein
06-04-2004, 10:17 AM
Hi Peggy,

One of the support people at Z-firm contacted me because there was nothing obviously wrong from the logs I posted. He tried various tests using remote control of my machine, but the consistent 'hangs' prevented him achieving anything. Eventually, he provided me with access to the latest copy of ShipRush V3 for UPS, and I had to download it (over 62MB!), then uninstall my old copy and install the new. That resolved the problem, but at the expense of losing my history file.

I must compliment Z-firm. Their support is terrific.

By the way, I'd be interested to know if you use ZoneLabs software to protect your machine? I have both Norton Internet Security and ZoneAlarm Pro. Norton is of course updated frequently and automatically. But one thing I recall was that the ShipRush problems began after I had updated my Zone Labs software. I wonder if your problems are related to this?

Dennis Klein

Peggy Payne
06-04-2004, 10:39 AM
Thanks for the help... and yes I am using Zone Alarm.

SYSOPS
06-07-2004, 11:16 AM
Afternoon Peggy,
Please call into the office at 707.543.2747 so we may assist you directly on this matter.

Thank you,
SYSOPS

Peggy Payne
06-07-2004, 02:59 PM
Thanks for all your help. Everything seems to be working fine now. The staff has been exceptional.

Lstevens
05-04-2005, 04:30 PM
After paying tech support to resolve my problem with not getting an end of day, I then downloaded the newest version of shiprush pro for UPS per the tech instructions. Big mistake. The installation went fine on the second try, however now I can't get into shipRush at all. I checked to make sure the windows firewall is disabled (runing windows XP). Norton firewall is configured to allow ShipRush and server. Have restarted the computer twice. Have installed the update twice. Still can't get ShipRush to finish loading as it says "Unable to connect to server" "server name or address cannot be resolved" and asks me to select connection type and properties, which makes no sense to me at all. I can't exit ShipRush because it hangs up with this continual "Unable to connect to server" problem so I have to end task from the task manager window. The port is correctly configured. Disabeling Norton does no good. I can't ship anything. Everything is worse after downloading the update. :(

SYSOPS
05-05-2005, 06:23 AM
Easy to resolve Linda.

Something is blocking the connection. One way to work around the blockage (without knowing what is specifically blocking) is to change the connection type to ADO when it prompts for the connection method.

The steps to switch to ADO:
Choose ADO
Under the Provider choose OLE DB Provider for SQL Server
Connection Tab
- 1. enter the following: .\SHIPRUSH3 (please include the period at the beginning)
- 2. Use specific username password
- username: sa
- password: <deleted>
- check in Allow saving password
- 3. select the database on th server (click the dropdown)
- select ShipRush-v3

Click test connection. If the test works, OK out and see if connects.

SYSOPS

Lstevens
05-05-2005, 08:48 AM
Scott (tech support) called first thing this morning. Problem was caused by incorrect computer name/address, which was corrupted, so Scott fixed the problem via remote access. Remote access is fantastic. I didn't have to go through the agony of figuring out the ADO stuff, which would have taken me a looong time as I am not computer savvy. Many thinks to Scott!!!