PDA

View Full Version : Can't start Z Firm ShipRush service



bschwarz
04-18-2005, 12:55 PM
Get the error, The service did not return an error. This could be an internal Winodws error or an internal service error. MSDE server started.

Thanks

SYSOPS
04-18-2005, 01:17 PM
Locate a file called shiprushserver.log (usually located under program files\z-firm llc\shiprush v3) and post back with the last 10 to 15 lines from that logfile.

It may indicate why the service doesn't start.

Thank you,
SYSOPS

bschwarz
04-18-2005, 01:23 PM
4/18/2005 9:26:11 AM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 1:33:53 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 1:35:26 PM WARNING (Connect) Unable to connect to server/instance "JBM01\ShipRush3": [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen (Connect())
4/18/2005 1:35:45 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
4/18/2005 1:35:45 PM SERVICE (ERROR) Unable to start shipping service: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
4/18/2005 1:38:21 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:08:13 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:12:32 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:13:24 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:14:16 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:15:07 PM WARNING (Connect) Unable to connect to server/instance "JBM01\ShipRush3": [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen (Connect())
4/18/2005 2:15:23 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
4/18/2005 2:15:23 PM SERVICE (ERROR) Unable to start shipping service: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
4/18/2005 2:19:13 PM WARNING (Connect) Unable to connect to server/instance "JBM01\ShipRush3": [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen (Connect())
4/18/2005 2:19:30 PM CRITICAL (Connect) [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
4/18/2005 2:19:30 PM SERVICE (ERROR) Unable to start shipping service: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
4/18/2005 2:31:26 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:34:43 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:41:49 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.
4/18/2005 2:56:41 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.

SYSOPS
04-18-2005, 01:44 PM
Error:
4/18/2005 2:56:41 PM SERVICE (ERROR) Unable to start shipping service: Could not bind socket. Address and port are already in use.

Means the port 1123 is already in use by another program.
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