michaelg@exaktime.com
04-04-2005, 10:21 AM
We have successfully moved the ShipRush database from the default instance to our primary SQL server. Our desktop clients successfully communicate with the server and we have been shipping all day.
We cannot run end-of-day, however. The ShipRush server will not start, because it will not connect to our primary SQL server. We have entered the proper server, user, and password settings in the "Build ADO connect string" dialog found in the "ShipRush Shipping Server (SOAP Server)" settings area.
Bottom line - ShipRush appears to ignore the settings.
The error log reports:
"3/31/2005 4:40:36 PM WARNING (Connect) Unable to connect to server/instance "PLUTO\ShipRush3": [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen (Connect())"
which indicates that it's ignoring the ADO settings that we're configuring.
Test Connection from the ADO config dialog works just fine.
Bottom line: We know databases, ADO, and MSDE well - we're a Microsoft programmiing ship. THIS SHOULD BE A SIMPLE FIX. Everything else is (finally) working - we just need to get the SOAP Server running so we can do our end of day.
We cannot run end-of-day, however. The ShipRush server will not start, because it will not connect to our primary SQL server. We have entered the proper server, user, and password settings in the "Build ADO connect string" dialog found in the "ShipRush Shipping Server (SOAP Server)" settings area.
Bottom line - ShipRush appears to ignore the settings.
The error log reports:
"3/31/2005 4:40:36 PM WARNING (Connect) Unable to connect to server/instance "PLUTO\ShipRush3": [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionOpen (Connect())"
which indicates that it's ignoring the ADO settings that we're configuring.
Test Connection from the ADO config dialog works just fine.
Bottom line: We know databases, ADO, and MSDE well - we're a Microsoft programmiing ship. THIS SHOULD BE A SIMPLE FIX. Everything else is (finally) working - we just need to get the SOAP Server running so we can do our end of day.