Did a search and couldn't find anything on the boards to resolve this. Wondering if anyone has had to silently deliver the SQL Client Tools. I was able to create the ISS file and build the silent install, but the silent crashes because the install puts an error message up claiming "SQL will not run on this OS, only Client Tools will be available".

Has anyone found a work around? Since its MSI based I was trying to avoid repackaging it since it can get crazy...and our maintenance on WPS has expired (no one is signing the damn P.O.'s!!!)
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Are you talking about MS SQL Server Enterprise tools? If so the install is likely trying to install the server component which has some OS restrictions.
Answered 02/11/2005 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Yes, Enterprise tools. The manual install gives you the warning message that "SQL SVR cannot be installed on this OS" I am able to create the ISS file for the silent install, but the job doesn't run because of this warning (i assume) occuring in the backgroound. I tried using the included batch file (sqlclnt.iss) but Its still not working. Before I start repackaging, I was wondering if anyone came up with a solution around this utilizing the ISS file. Any help would be greatly appreciated.
Answered 02/14/2005 by: fozzi58
Senior Yellow Belt

Please log in to comment
0
Well you can repackage the app but that is not simple as well. You are either going to repackage the SQL server package or figure out why the .iss file is trying to do a server install rather than client.

To repackage the app you will need the correct SQL Server merge modules. If it is SQL 2000 then get the SP3 modules off of the CD. The ones you download or find on the base media will fail on systems with IE6. When you repackage the app exclude the SQLBASE.MSM or SQLSVR.MSM. Just double check to see which one actually installs the databases because that one you don't want if you are only installing the client tools.
Answered 02/14/2005 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity