Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cluster Server issues

Status
Not open for further replies.

Luvsql

Technical User
Apr 3, 2003
1,179
CA
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???
 
so - how do you have the cluster (and the odbc/ado) set up? I know that you can have SQL virtual servers and SQL stand alone instances running on the same box (and call it a cluster)... or - you can have a 'real' cf (cluster) and try to do some load balancing (which I was AMAZED to find was not automatic when we tried this).

Have you tried taking part of the cluster 'offline' and doing the same thing (go into GP and the ADO app)? Would help isolate the problem. I do not remember the cluster command and am away from my machine with that doc...
 
found it

cluster [cluster name] RESOURCE [resource name] /option

/option can be /offline -or- /online
 
We are running a true cluster (ie we have 2 windows 2003 server boxes, running in active-passive mode). We have no issues on any applications (including the shared files that are accessed on the cluster server) except for Great Plains. There is no issue connecting to ODBC either as we are able to log into the odbc connection and run crystal reports. The only thing that does not work is Great Plains itself. It doesn't even work on the server itself (ie try to login and cannot).

We are back up and running, but had to shut down our cluster servers 3 times on Friday. That's unacceptable.
 
check out the response that another Jim gave your question (today) on the GP forum - out of my league on three servers since it sound like how we did things (active-passive)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top