Upgrading from 07.00.175 to 07.02.00 may appear to 'hang' at upgrade script 34163
Problem
Upgrading from version 07.00.175 to 07.02.00 may appear to 'hang' or stop responding.
It will do so at upgrade script 34163 7.0.186.480 if someone has logged in to Jiwa. This script checks for whether any users are logged into the database during upgrade.
The upgrade hasn't stopped and isn't 'Not Responding' it is simply waiting for users to log out. This will never happen though, because in 07.00.175 logins create an uncommitted transaction.
Even though all your users have logged out, you may still have services logging in such as the Jiwa Plugin Scheduler Service.
Solution
Ideally you should stop all services before attempting the upgrade.
If services have logged in and you are stuck in the upgrade process you will have to cancel the upgrade. Don't worry, Jiwa will remember where you're up to.
You may need to cancel the upgrade by using the Task Manager and End Task on Jiwa.
If Jiwa still thinks users are logged in use Management Studio to kill those sessions.
sp_who2
This will give you the SPID
kill XX
Where XX is the SPID where ProgramName = 'Jiwa Financials'
You can then restart the upgrade using the upgrade wizard.