Subject: FYI: 64-bit installer of TDP for MS-SQL v5.5.3 ate our license file
Thread-Topic: 64-bit installer of TDP for MS-SQL v5.5.3 ate our license file
Thread-Index: AcrRFgqHG0UwUEK5RhmmHrLCRJW9QwoArwT5
Message-ID: <c81c520e.57d8f%r...@cornell.edu>
In-Reply-To:
<of1f1a4206.7053630d-on852576f7.007335fc-852576f7.0073b...@us.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.4.0.100208
acceptlanguage: en-US
x-additional-recipients-added: 1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-CORNELL: hermes30
X-Barracuda-Connect: soapstone1.mail.cornell.edu[128.253.83.143]
X-Barracuda-Start-Time: 1274468816
X-Barracuda-Bayes: INNOCENT GLOBAL 0.1551 1.0000 -1.0725
X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at marist.edu
X-Barracuda-Spam-Score: -1.07
X-Barracuda-Spam-Status: No, SCORE=-1.07 using global scores of TAG_LEVEL=3.5
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.30424
Rule breakdown below
pts rule name description
---- ----------------------
--------------------------------------------------
We just upgraded our TPD for MS-SQL from v5.5.1 (the initial install
version, complete with license file) on a 64-bit machine, and discovered
that the installer ate our license file (the name of which escapes me just
now).
Our Windows admin eventually found a workaround - upgrading to v5.5.3 by
running the MSI installer directly, rather than through the setup.exe.
We are opening a ticket with IBM on this, but just wanted to share.
