Tried to upgrade VIO from 2.0 to 2.5, now connection to OMS fails

I had a working VIO version 2.0 and tried to upgrade it to 2.5.

The upgrade steps succeeded through the viocli dbverify step.

I went to provision the new VIO deployment and vCenter can no longer connect to the OMS instance.  I can ssh to it just fine, I've shutdown and restarted the vApp that contains OMS to no avail.  I tried to connect directly to the web interface at https://<OMS_server>:8443/VIO and logged in with the vCenter credentials as it suggests and I get the resulting http 500 error page from the servlet.

Anyone else get this and get past it?

Thanks.