Issue Installing CS 6 SP1 on SQL 2005 SP2 - 64Bit

Dears,

Please I need ur help in this case urgently, I am in a critical situation...

I am trying to install CS 6 SP1 on a brand new Box. That part is done
but the configuration is having issues with MS SQL 2005 SP2 database
64-Bit.

[Error: The Installer failed to test case-sensitivity for the SQL Server. Error: "E:\Program Files\Microsoft SQL Server\90\Tools\Binn\isql.exe" is not recognized as an internal or external command, operable program or batch file.]

The database HAS BEEN installed in a case sensitive mode.

So has anyone encountered such an issue with version 6 SP1 and SQL 2005 64bit? My server OS all across is WIN Server 2008 R2 64bit.

Any help in this or ideas shall be appreciated.

Thank you,

Ahmad Asfour

Find more posts tagged with

Comments

dleggat

Have you found this - https://community.emc.com/message/487292 ?

The problem (as i ascertained from Johnny's and your links) is that the installer is still looking for the old client isql.exe when sql 2005 + has gone to SQLCMD.exe. I simply made a copy of the SQLCMD.exe and renamed it to ISQL.exe, and the install went as expected.

AhmadAsfour

Thanks a lot Dleggat for ur reply.

I do what you suggest in your reply and I undergo the ISQL.exe issue, but when the installer is trying locating the server default data file directory I recieved this exception.

CreateProcess: -n -w 800 /U sa /P "p@ssw0rd" /S RSAF-ECM /i "C:\Users\ahmadas\AppData\Local\Temp\ismp001\1390831.tmp" /o "C:\Users\ahmadas\AppData\Local\Temp\ismp001\533246.tmp" error=123

So please help in this issue also.

Thanks in advance.

Ahmad Asfour

Zeleres

I found this answer on a random Chinese website (ah, the places you have to go to find quality support these days...) Anyway, I had the exact same error as you and doing the following two steps actually worked for me - hopefully it will work for you, too.

Copy everything (files and folders) from “C:\Program Files\Microsoft SQL Server\100\Tools\Binn” and paste it all in “C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn”.
Copy "SQLCMD.exe" and rename as "ISQL.exe"

Note: I did Step 1 first and it worked for me after just doing that, but I had also previously messed around with copying/pasting/renaming SQLCMD.exe and iSQL.exe on my machine, so Step 2 is probably also necessary.

Here is the original site I found this answer at:

http://www.xioxu.com/?p=216001

I'm not sure who is at fault for this (Microsoft or Documentum), but this level of nonsense is enough to drive anyone insane. I really couldn't tell you why this solves the problem, and I also couldn't begin to explain what error=123 is supposed to mean. In SQL Server world, error 123 points to a process running out of memory; but clearly this is not the case here. What is error=123??? Useless garbage, that's what it is. I'd love to talk with the people responsible for the installer just to see what caused this - there has to be a good story. As a developer I am generally sympathetic to software issues, but the installer is really in a class of its own.