I have only seen this on adding a node to a cluster, and I think that was only on SQL 2008. if you had an .INI file with the key pre-populated, the install would refuse that key on the second node. The solution was to remove the key from the .INI file, and enter the key manually.
Hi thx for reply
Well, I am not doing a cluster.
However, I am not so sure the key code is good
since the vendor had issued me one which did not work and
this is the replacement key (also no good)
so in talking to the vendor, rep said it may be a whole batch that they received
that may need to be sent back to their supplier
we'll see
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.