Great Plains will not work after failover on cluster server

[Luvsql]

We have a Windows 2003 server running SQL 2000 Enterprise with 2 nodes. We have tested the failover many times with users running our applications on citrix. There is a small hiccup when we shut down the primary node, but the users can then carry on with their work ie existing connections to Great Plains are okay.

However, if we now try to launch Great Plains, we enter our login ID, then okay. It says "Initializing Great Plains" then just hangs and hangs. Locally installed Great Plains on desktops also do not work. If we open the ODBC connection, we can connect fine. I can run my crystal reports to the server no problem. Our other applictions can connect no problem. Only Great PLains does not work.

The dexsql log shows no errors. We cannot use the application at all right now and we are down.

 

[Luvsql]

It seems the last stored procedure that runs is on the SY01500 table. I then tried to run a select statement on it, but it just hung. It seems this table somehow got corrupted. I ran checkdb on the DYNAMICS database and now users can log in.

How can a failover cause data corruption?