Recently had a problem re-introducing IS onto MS Cluster, I am experienced at building cluster with Exchange and not come across this problem before, Compaq Tech support are stumped, as are Microsoft engineers (no surprises there then).
The problem is this:
Build cluster servers, install exchange 5.5 enterprise. Run isinteg -patch to update IS, note that _CLUSTER_NETWORK_NAME_= variable is added before isinteg is run. I have built several clusters like this and had no problems but the latest throws up JET_errKeyDuplicate every time isinteg is run, technet goes so far to explain but goes no further when the error continues to occur, I have spent hours and hours with Compaq tech support to try and resolve, so we have gone through every troublshooting scenario, eventually had to run exchange on single server and all is fine. Will have to re-build cluster with exchange at a future date.
Just wondering if anyone has come across this problem before.
Cheers.
The problem is this:
Build cluster servers, install exchange 5.5 enterprise. Run isinteg -patch to update IS, note that _CLUSTER_NETWORK_NAME_= variable is added before isinteg is run. I have built several clusters like this and had no problems but the latest throws up JET_errKeyDuplicate every time isinteg is run, technet goes so far to explain but goes no further when the error continues to occur, I have spent hours and hours with Compaq tech support to try and resolve, so we have gone through every troublshooting scenario, eventually had to run exchange on single server and all is fine. Will have to re-build cluster with exchange at a future date.
Just wondering if anyone has come across this problem before.
Cheers.
