PDA

View Full Version : SQL Server ODBC DSN are not created on Target system



NewsArchive
11-12-1997, 01:00 AM
James,
I've played some (but not enough) with ISQL.EXE and believe this will
work if I'm installing our app on the same system as the SQL server -- what if
I'm dealing with two seperate systems and the SQL Server is somewhere else??
Is ISQL self-contained enough to run from a remote system??

Thanks for the help, I'm _really_ new to SQL Server and appreciated any
assistance I can get...

Thanks,
BB

James Frater wrote:

> Just create a SQL script in a text file and execute ISQL.EXE, telling it to
> run this file. You will need to look up for yourself the doc on ISQL & how
> to successfully use. I am using LaunchAppAndWait to launch a VB program
> which does some input & in turn launches ISQL w/a script written by the VB
> program, but you could also launch ISQL directly from LaunchApp[AndWait].
>
> Good luck,
> James Frater
> James.Frater@HBOC.com
>
> Brian Bergstrom <bbergstrom@earthlink.net> wrote in article
> <3468D43F.E728A790@earthlink.net>...
> > Hi,
> >
> > I was wonder if anyone out there has used IS5 to manipulate an SQL DB in
> > any manner, either the command line via a LaunchAppAndWait() or some
> > type of connection to the SQL Server?
> ...> Thanks,
> > BB
> > --
> > *********************************************************
> > Brian Bergstrom
> ...

NewsArchive
08-20-1998, 12:00 AM
The application I am installing uses 4 DSN's 2 SQL Server, 1 Dbase IV,
1 Access 97. The Access 97 and the Dbase DSN are transfered to the
targer, The SQL DSN's are dropped. I even created a test with only SQL
DSN's and in that case no DSN's were created on the target. NOTE: The
Source are User DSN's and the Target are System DSN's. Where do I go
from Here ? ...

NewsArchive
08-21-1998, 12:00 AM
Michael Couture wrote in message <35DC89EE.92FC886@datacoreeng.com>...
>The application I am installing uses 4 DSN's 2 SQL Server, 1 Dbase IV,
>1 Access 97. The Access 97 and the Dbase DSN are transfered to the
>targer, The SQL DSN's are dropped. I even created a test with only SQL
>DSN's and in that case no DSN's were created on the target. NOTE: The
>Source are User DSN's and the Target are System DSN's. Where do I go
>from Here ? ...
>

You probally dont have a value for the DSN Description. For some reason ISX
requires this fiel.


Bill Gauvey
Acxiom Corporation

NewsArchive
08-21-1998, 12:00 AM
On Thu, 20 Aug 1998 15:41:19 -0500, Michael Couture
<mcouture@datacoreeng.com> wrote:
>DSN's and in that case no DSN's were created on the target. NOTE: The
>Source are User DSN's and the Target are System DSN's. Where do I go
>from Here ? ...

Create the SQL Server System DSNs on your system first, and then add them
to your project.

Stefan Paetow
InstallShield Software Corp.

NewsArchive
11-30-1999, 01:00 AM
Another solution is if you have access to Microsoft MSDN Library. In the
section about SQL Server, all valid keys for a SQL Server DSN is listed.
/Andreas Magnusson

"Jim Kang" <?@installshield.com> wrote in message
news:38432a52.0@news.installshield.com...
> In article <383f169d.0@news.installshield.com>, "John D. West"
<JohnDWest@ibm.net> wrote:
> > Hi.
> >
> > I am trying to install two ODBC DSNs, one for Visual FoxPro and one for
MS
> > SQL Server. The FoxPro one installs with no problems, but the SQL
Server
> > one give me an error during install "error 8: Invalid keyword-value
pairs".
> >
> > Following the advice seen elsewhere in this newsgroup, I have set the
ODBC
> > data source name and description to identical strings, I have deleted
the
> > Driver and LastUser settings, and I set the destination for the
Translator
> > to [SystemFolder]. I still get the error.
> >
> > Any other ideas?
>
> Try to incrementally delete attributes (such as Driver and LastUser) until
you
> get a successful. It's likely that the problem is an invalid attribute.
>
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
12-02-1999, 01:00 AM
http://msdn.microsoft.com/library/psdk/sql/odbc_c_4.htm


Andreas Magnusson <andreas_ch_m@hotmail.com> wrote in message
news:384396ec.0@news.installshield.com...
> Another solution is if you have access to Microsoft MSDN Library. In the
> section about SQL Server, all valid keys for a SQL Server DSN is listed.
> /Andreas Magnusson
>
> "Jim Kang" <?@installshield.com> wrote in message
> news:38432a52.0@news.installshield.com...
> > In article <383f169d.0@news.installshield.com>, "John D. West"
> <JohnDWest@ibm.net> wrote:
> > > Hi.
> > >
> > > I am trying to install two ODBC DSNs, one for Visual FoxPro and one
for
> MS
> > > SQL Server. The FoxPro one installs with no problems, but the SQL
> Server
> > > one give me an error during install "error 8: Invalid keyword-value
> pairs".
> > >
> > > Following the advice seen elsewhere in this newsgroup, I have set the
> ODBC
> > > data source name and description to identical strings, I have deleted
> the
> > > Driver and LastUser settings, and I set the destination for the
> Translator
> > > to [SystemFolder]. I still get the error.
> > >
> > > Any other ideas?
> >
> > Try to incrementally delete attributes (such as Driver and LastUser)
until
> you
> > get a successful. It's likely that the problem is an invalid attribute.
> >
> > ----
> >
> > Jim Kang - Developer Support Engineer
> > InstallShield Software Corporation
> >
>
>

NewsArchive
12-15-1999, 01:00 AM
Jim Kang <?@installshield.com> wrote in message
news:3856b5a7.0@news.installshield.com...
> In article <3856133e.0@news.installshield.com>, "Carmel Magen"
<carmel@onsettechnology.com> wrote:
> > I'm trying to create a new SQL Server DSN in my setup and I keep getting
> > Error -3016: Error building ODBCDataSource And ODBCSourceAttribute table
in
> > component ThruFaxDSN1 can anybody tell me what to do?
> >
> > I've defined the following attributes:
> > Driver Name of the default SQL driver
> > login Id Name of a valid user in the SQL server
> > password password of said user
> > DataBase name of the database I need to work with (exists on the SQL
server)
> > Description ThruFaxDSN ( name of the DSN)
> > with the correct information but that doesn't seem to do any good.
>
> What exactly is in these attributes' fields?
see above
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
12-15-1999, 01:00 AM
Remove the driver parameter. SQL Server does not need it and hiccups on it.

--
David Thornley
Lead Developer Support Engineer
InstallShield Software Corporation
http://www.installshield.com



Carmel Magen wrote in message <3857a171.0@news.installshield.com>...
>
>Jim Kang <?@installshield.com> wrote in message
>news:3856b5a7.0@news.installshield.com...
>> In article <3856133e.0@news.installshield.com>, "Carmel Magen"
><carmel@onsettechnology.com> wrote:
>> > I'm trying to create a new SQL Server DSN in my setup and I keep
getting
>> > Error -3016: Error building ODBCDataSource And ODBCSourceAttribute
table
>in
>> > component ThruFaxDSN1 can anybody tell me what to do?
>> >
>> > I've defined the following attributes:
>> > Driver Name of the default SQL driver
>> > login Id Name of a valid user in the SQL server
>> > password password of said user
>> > DataBase name of the database I need to work with (exists on the SQL
>server)
>> > Description ThruFaxDSN ( name of the DSN)
>> > with the correct information but that doesn't seem to do any good.
>>
>> What exactly is in these attributes' fields?
>see above
>> ----
>>
>> Jim Kang - Developer Support Engineer
>> InstallShield Software Corporation
>>
>
>