/build/static/layout/Breadcrumb_cap_w.png

sql server 2000 client

i am facing an issue with app sql server 2000 client while repackaging. I captured my application in xp image and trying to install in NT and application shortcuts failed to launch.

so tried to capture in NT and install in XP it's throwing 1913 error. And the file it's mentioning in the error is not part of the MSI.the file is called odbcconf.rsp.

We need a single MSI to be installed in NT OS and Xp OS.

sugesstions are apreciated.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: wiseapp 19 years ago
Second Degree Green Belt
0
Hi Anitha:

Well I believe SQL Server 2000 is a complex installation and makes huge changes in the registry and windows file protection system, even if you try to capture the same there would be lot many things which will be skipped by WISE/Installshield during snapshot. It does'nt matter whether you're capturing in XP or NT however I would suggest that in this situation you should create a MSI wrapper that will call SQL Setup in silent mode. Still you got doubts buzz me anytime.

God Bless!
Posted by: Timanator 17 years ago
Third Degree Blue Belt
0
Hey fellas

I am having issues with getting the Silent install for the SQL client to even run.

x86\setup\setupsql.exe k=SMS -s -m -SMS -f1 "answerfile.iss"

When I run this, I get " Windows cannot find "-s". Anyone else having the same issues?
Posted by: marvinc 17 years ago
Orange Belt
0
Was there ever a reply or answer to this question? Looking to install the SQL tools using this command line.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ