Has anyone successfully run Great Plains on a windows 2003 cluster server, running SQL Enterprise 2000? We have 2 applications: ONe that accesses data via ADO and GP with ODBC. For some reason, Great Plains goes down, but the other does not. Users cannot log in even though the server is fine. If you attempt to run a select statement on the SY01500 table from query analyzer (which is the first table that GP access when you login), it does not return any results and just hangs.
The only way to get people logged in again is to shutdown each cluster, then bring primary node up, then secondary node up.
If another application that accesses the same sqlcluster server, why is it fine, but GP dies???
The only way to get people logged in again is to shutdown each cluster, then bring primary node up, then secondary node up.
If another application that accesses the same sqlcluster server, why is it fine, but GP dies???