May 17, 2017
When there is a problem with a Rumpus server, it's usually best to carefully review, reproduce and diagnose the problem to find a solution. But sometimes, especially after attempting to move a Rumpus server from one PC to another, a complete re-install of Rumpus makes more sense. In those cases, here's what to do:
Open the folder "C:\Rumpus\" and make safe copies of the necessary files and folders within that folder.
You will always want to make a backup of the "Config" folder, which contains all Rumpus configuration files.
By default, Rumpus stores user content in the "FTPRoot" folder, so if you've used that folder for user content, make a backup copy of that folder as well (or simply move the folder out of "C:\Rumpus\" to some safe location). If your user content folders are stored elsewhere, the data is most likely safe and won't need to be backed up and recovered through the rest of the re-install process, although a safe backup is always a good idea.
Finally, if you need to have drop shipments preserved, be sure to also backup (or just move to a safe location) the "WorkStorage" folder.
In Rumpus, if the service is running, click "Stop Server", then quit the Rumpus control application.
Run the uninstaller at "C:\Rumpus\unins000.exe".
Manually delete the "C:\Rumpus\" folder.
Optionally at this point, you may want to restart the PC, though it's normally not necessary.
Go to the Maxum Web site, Downloads page, and download the current version of Rumpus. Run the installer normally, as if you were installing a trial version of Rumpus on a new server. After installation, you will be presented with the Setup Assistant. Complete the assistant normally, again, as if it were a fresh install.
At the end of the Setup Assistant, local connection instructions are displayed. On another computer on the local network, follow the instructions to confirm that you can connect to the server and log in using the account defined in the Setup Assistant. Make sure the server can be stopped and started, and that the basic installation performs as it should.
Now that server functionality has been restored, you can begin to carefully recover the configuration from the previous setup. Start with the Rumpus users database.
From the backup made earlier, copy the "Rumpus.users" file into the config folder at "C:\Rumpus\Config\". Quit Rumpus and relaunch (to make sure the Rumpus control application picks up the recovered users database) and click "Stop Server" and "Start Server" (to make sure the server daemon picks it up, too). Connect and log in as one or two user accounts to confirm access.
One at a time, in the same manner you recovered the Rumpus.users file, recover other configuration files that will be time-consuming to recreate manually.
Never attempt to recover files you don't recognize or that you don't need to restore, including: rumpusd.exe, various ".dll" files, etc. These aren't configuration files, and are managed by Rumpus.
I also don't recommend restoring "Rumpus.conf", as that configuration file includes options which may be server-specific. For example, configuration problems that were previously causing issues may be replicated on the new installation by recovering that file. You can try recovering it if you like, but be sure to make a backup copy of the clean "Rumpus.conf" file first, then carefully testing server accessibility before continuing on. It's usually best, though, to simply run through the Rumpus control application setup windows and set needed config options manually.
Other key config files you may optionally recover include:
Rumpus.notices - This file contains Event Notice definitions.
Rumpus.fsets - This file contains Folder Set definitions.
Rumpus.cert and Rumpus.key - These files contain your SSL certificate and private key.
Rumpus.rips - This file contains the Blocked Clients ("Reject IPs") list.
Rumpus.aips - This file contains the Allowed IPs list.
Rumpus.types - This file contains File Type definitions.
Files Ending in ".domain" - These are the Web Settings appearance definitions for each defined domain, including "Default.domain".
Again, recover only those files that will be time-consuming to recreate manually. The fewer files brought forward, the cleaner the new setup and the less chance of accidentally recovering a file with configuration problems.
If you use drop shipping, existing drop shipments can also be restored. Recover the "Rumpus.drops" file and the "WorkStorage" folder. (By default, the WorkStorage folder is in the Rumpus config folder, but the location is configurable on the "Web Settings" window, Advanced tab.)