4.2.35 cripples ERA server

[SalC]

FYI -- running on a W2k3 VM just fine until I uninstalled 4.0.474, rebooted, and installed 4.2.35 -- now I can't connect to the ERA from the server itself or from my desktop.

I can't stop the service either:
Stopping ERA Server service...
Checking server state...
Current server state: service running
Service operation failed (attempts: 50, code: 0)

Operation failed

-- I'm going to have to reboot, hopefully it won't damage the database, and then reinstall 4.0.474 -- hope this works..

[SalC]

Database was corrupted.. server just sits there not accepting clients.. service won't stop.. had to set it to manual startup, reboot, and then do a database repair with MS Access -- and start the service.. that works until you reboot the server, at which point it starts not accepting clients again.. trying some more stuff now... ugh...



-{ Quote: "FYI -- running on a W2k3 VM just fine until I uninstalled 4.0.474, rebooted, and installed 4.2.35 -- now I can't connect to the ERA from the server itself or from my desktop.

I can't stop the service either:
Stopping ERA Server service...
Checking server state...
Current server state: service running
Service operation failed (attempts: 50, code: 0)

Operation failed

-- I'm going to have to reboot, hopefully it won't damage the database, and then reinstall 4.0.474 -- hope this works.." }-

[SalC]

That fixed it.. working again now. Did a repair install of the ERA server, then had to do another DB repair, then bring the service back up, and all is well. Still OK after reinstalling 4.0.474 and restarting the server.