DSXchange

A Windows Server that had an installation of DataStage became corrupted. It has been repared, but the DataStage services would not start. I uninstalled DataStage and attemped to re-install, but I am getting a error stating that the authorization code can not be validated. I am using the same serial number and auth code as per the initial installation and the expiration date is 1/01/2500.

I am attempting the install from the hard drive as opposed to the CD, could this be the problem?

That should not cause the problem. It is important to go through the registry after an unintall to make sure all DataStage related entries have been removed.

Make sure you've got the Authorization code exactly right... sometimes people mix up letters for numbers, or the case. If you've got the 'old fashioned' paper codes, the numbers are in italics from what I recall, which helps. The other problem we see once in a while is a cut-and-paste error where there is an extra space on the end. You also need to ensure the number of CPUs entered is correct.

I am sure that the auth code is being entered correctly. Is there a location on the disk that could be referenced that would cause the confirmation to be corrupted?

Nope. Not that I've ever seen or heard of anyway...

Make sure you are not using Client codes instead of Server codes by mistake.

The authorization code looks at your OS and number of CPUs and the actual product being installed. Could you be entering the DSDES codes for the server by misteak?

Me thinks it's your date You have the correct date... but the wrong format... I get caught by this everytime I do a re-install ...

Use "01-01-2500" instead of "01/01/2500" and see if that works.

LEN O'TOOLE
INTERNATIONAL PAPER-MEMPHIS

Greetings, Len! It's always wanted it like '1/01/2500' or perhaps '01/01/2500'. Me thinks yours may work as well (never tried) but that's not the problem.

'Misteak' Arnd? Cute.

I will give it another go, but I am fairly confident that the serial number and authorization codes are correct and that this is the only instance of datastage on the network.

It's always wanted it exactly like it is on the paper. So the date may actually be 01/01/2500 (leading zero).

The authorization code itself is always eleven characters long. On the paper they print numeric characters in italic, so you can differentiate between lower case "L" and the figure 1, and between upper case "O" and zero.

The authorization code does encode platform information (as well as serial number, CPU count and expiry date) so the fact that your Windows O/S got horked may be an explanation. But I doubt it. It's far more likely that one of the fields is not being entered accurately.

I had one experience (years ago) where the final character of the auth code was ".", but the poor client read that as "end of sentence" rather than part of the auth code. Knowing that the auth code has eleven characters was the key to solving that one.