PDA

View Full Version : Save State/Backup Problems



videoshelf
06-17-2005, 07:41 AM
I need to move ShipRush Server from a PC to a Server. I tried to use the 'Save State' function in the Database Manager but it gave me the same error twice. The error was a time out error in restarting one of the services. First of all, is this the tool I should be using or should I use backup or migration instead?

Rob
Aesthetic VideoSource

Note: Have you found a fix for the Hot Fix problem we had? (using ver. 664 with previous version's .exe file)

SYSOPS
06-17-2005, 07:54 AM
No on an update for ShipRush yet.

Here is the helpfile discussion on moving ShipRush:
http://www.zfirm.com/Product_Documentation/ShipRush_v3_Pro_Edition/Move_ShipRush_to_a_New_Computer.htm

If the services are not starting correctly, they may not be running correctly in the first place. Make sure that the following services are running before attempting a data backup:

- MSSQL$SHIPRUSH3
- ZFirm Shipping Service

If they are not started, see if you can start them and then try the database backup again.

SYSOPS

videoshelf
06-17-2005, 08:19 AM
Thanks for your reply and the link to the migration document. I verified that the following services were running:

- MSSQL$SHIPRUSH3
- ZFirm ShipRush v3

Next, I tried the Save State tool and the same thing happened -- time out error.

Rob
Aesthetic VideoSource

SYSOPS
06-17-2005, 08:44 AM
Have you tried logged in as a different user? You are on the server install of ShipRush doing this correct?

Something is keeping the service from starting back up in a timely fashion. Can you go into services and stop\restart the ZFirm Shipping Service, or does it time out on restart?

SYSOPS

videoshelf
06-17-2005, 11:40 AM
I was logged on as the administrator of the PC. I was able to stop/restart the ZFirm Shipping Service from the services window. There were no problems. Does it matter that we're using a hybred 5XX/664 version of ShipRush?

Rob
Aesthetic VideoSource

SYSOPS
06-17-2005, 11:57 AM
Shouldn't matter since the only thing that was replaced was the EXE for ShipRush application itself (everything else should be the same build).

If you browse out to c:\documents and settings\<username>\application data\z-firm llc\shiprush v3, is there a backup folder created out there with today's date? I'm wondering if it is actually able to generate all the backup data.

SYSOPS

videoshelf
06-17-2005, 02:56 PM
It did create the folders. However, they are empty. Here is the log file of the last backup I attempted.

6/17/2005 10:19:22 AM INFO ********** Backup Started ******************
6/17/2005 10:19:22 AM INFO Check folders
6/17/2005 10:19:22 AM INFO Check user rights
6/17/2005 10:19:22 AM INFO Stop ShipRush server
6/17/2005 10:19:27 AM INFO Restart ShipRush Database Engine
6/17/2005 10:19:54 AM INFO *** ERROR : "Timeout error during service startup"
6/17/2005 10:19:54 AM INFO ********** Backup Failed ******************



Rob
Aesthetic VideoSource

SYSOPR
06-20-2005, 08:21 AM
Does it matter that we're using a hybred 5XX/664 version of ShipRush?

RE saving state: the hybrid should not matter.

But mixing builds that like IS asking for trouble in other respects.

Why can't you run 664 on all systems? (Sorry to ask, but it is not clear to me.)

SYSOPR
06-20-2005, 08:24 AM
6/17/2005 10:19:27 AM INFO Restart ShipRush Database Engine
6/17/2005 10:19:54 AM INFO *** ERROR : "Timeout error during service startup"
6/17/2005 10:19:54 AM INFO ********** Backup Failed ******************

Ummm, OK. That will certainly stop the process cold.

You can check how long it takes to cycle the service manually. Steps:

a) All out of ShipRush
b) In NT service mgr, stop the ShipRush Server process
c) In NT Service mgr, stop the ShipRush MSDE process. Then start it. Does it start quickly?

Perhaps there are other MSDE / SQL instances that can be stopped during this process.

Another possible trick is to start the save state with the ShipRush Server and ShipRush MSDE processes stopped. So it only has to start them.

Bottom line is that hopefully these tricks will work, but it is a very tricky thing if they do not. Would take a real PC hacker at that point to make it all fly.

videoshelf
06-21-2005, 11:03 AM
I timed the restart for the Server and the MSSQL instance of ShipRush (11 sec, 5 sec). I also tried the Save State while the services were stopped. No luck. Any other suggestions?

Rob Smith
Aesthetic VideoSource

videoshelf
06-21-2005, 11:07 AM
We're running a 563/664 hybrid because of some Microsoft HotFixes we installed. The fixes killed the connection between the clients and server under the 664 exe file. The 563 exe file seems to work fine with the 664 installation. I've been waiting for a fix for this problem for a few months. If you hear anything, please let me know.

Rob Smith
Aesthetic VideoSource