PDA

View Full Version : Incompatibility???



chazgk
03-15-2005, 09:34 AM
Greetings,

I just applied the new 3.0.664 update this morning. While first attempting the install on our server (w2k server), it gave me a choice of Update Shiprush. The installler later failed to respond during the service stopping, so I ended the task. On 2nd attempt, the installer acted as if a new intsall (i.e. Install ShipRush Server). In other words, the Update ShipRush choice was gone.

After install - server restarted,, still same problem. Followed instructions in article: http://www.zfirm.com/knowledge_base...h/sr3p-0003.txt

At this point, the Z-Firm ShipRush v3 service won't start. It comes up with a dialog reading that no error was reported. Could be an internal Windows error.

We were running just fine prior to the update!

Is it possible that the updtae is now conflicting with our sql-based antivirus/spyware detection software Panda BusinessSecure Antivirus? There are no settings in the antivirus to allow certain protocols/ports/apps etc. to be bypassed, nor have we installed winxp sp2.

Please advise as the boss is breathing down my neck to get ShipRush back up & running.

regards,
Chuck

SYSOPS
03-15-2005, 09:48 AM
Please locate the file called shiprushserver.log on the server PC.

Post back with the last 15 to 20 lines of that file. It may indicate the issue.

Thank you,
SYSOPS

chazgk
03-15-2005, 09:59 AM
Here are all of thenetries from today when we started the upgrade:

3/15/2005 8:28:10 AM Server Server stopped
3/15/2005 8:42:05 AM Server ********** Server started: ShipRushServer.exe version 3.0.0.664 ******************
3/15/2005 8:49:36 AM ERROR Access violation at address 02CF69B6. Read of address FFFFFFFF
3/15/2005 8:49:47 AM ERROR Access violation at address 02CF69B6. Read of address FFFFFFFF
3/15/2005 8:39:21 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 8:53:29 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 8:55:00 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 8:56:45 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 9:02:56 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 9:07:21 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 9:09:15 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
3/15/2005 9:10:12 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.

SYSOPS
03-15-2005, 10:10 AM
That is the error I was hoping to see:
3/15/2005 9:10:12 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.

A reboot of the server may resolve. If that does not, you will need to change the port that ShipRush is using because something else is using it on the server.

How to do that:
Search for the following two files on the ShipRush Server:
ShipRushServer.ini
ShipRushClient.ini

Modify the value for SOAPPORT on each of those files from 1123 to 1133
Reboot the PC and see if the services start correctly

If they do, you will need to make this modification to all other workstations with ShipRush installed. Modify ShipRushClient.ini to the same port

SYSOPS