Home > Odbc Error > Odbc Error 8 Invalid Keyword-value Pairs

Odbc Error 8 Invalid Keyword-value Pairs

The Windows Authentication (INTEGRATEDSECURITY = “Yes”) is working correctly and without error. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed At least it is believed so, since the SQL Server Name and the Database Name work like a charm with Windows Authentication. ConfigDSN can accept keywords that are not valid keywords for SQLBrowseConnect and SQLDriverConnect. navigate here

What is the reason of having an Angle of Incidence on an airplane? You may download attachments. Expand "SQL Server 2005 Network Configuration" and click on "Protocols for MSSQLSERVER" On the right hand pane, right click "TCP/IP" and select properties On the TCP/IP Properties window, click on the Verify that the file VBusSQLServer exists and that you can access it.

current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list. The time now is 01:11 AM. -- Desktop -- Default Mobile Style Archive Service-Level Agreement Top Stay Connected RSS YouTube Twitter LinkedIn Xing Weibo What We Do Software License Optimization Application You could also embed the credentials as part of the connection string directly in your application but again this is insecure and not recommended. Reply With Quote 07-30-2003,09:33 AM #5 usarif View Profile View Forum Posts User (5+ Posts) Join Date Jul 2003 Posts 23 when i tried to run msiexec /i c:\setup.exe /lv c:\error.txt

The command below should create the DSN for you. Verify that the file VBusSQLServer exists and >>>that you can access it. >>> >>>What is wrong? >>> >>>Terje >>> >>> >> >> > > NewsArchive11-02-1999, 01:00 AMI am having the same I know its not secure, but thats not something is a concern to us. When running the project (only tested on a XP machine at this stage) I get the following error:- Error Error configuring ODBC data source: TESS_SC5_LIVE, ODBC error 8: Invalid keyword-value pairs.

Wednesday, September 27, 2006 3:03 AM Reply | Quote 0 Sign in to vote Thanks Uwa Agbonile this is right, that it is insecure, is there any way to do that, remove this and the error shoudl go away. -- David Thornley Lead Developer Support Engineer InstallShield Software Corporation http://www.installshield.com Terje Pedersen wrote in message <[email protected]>... >I have used the Component Wizard Wednesday, September 27, 2006 3:03 AM Reply | Quote All replies 0 Sign in to vote Persistence of login credentials in a DSN is not supported (it's insecure). You cannot delete your own posts.

Back to top #8 Kannan Kannan Members 22 posts Posted 20 October 2001 - 06:21 I am using Windows Installer Version - 1.20.1827.0Is there any way to solve this problem.my requirement Post Reply Print view Search Advanced search 8 posts • Page 1 of 1 Tesseract_Support Posts: 12 Joined: Mon Jul 30, 2007 10:24 am Issue when creating ODBC DSN in InstallAware this software require Mdac2.7. I keep encountering "error 8".

Because this is called Description in the .msi file, I am concerned this is a MSFT problem, not an Installshield problem.) If you have blank DESCRIPTION fields, you will not install Trademarks belong to their respective owners. and that it shouldnt use Windows NT authentication? I'd like to dynamicaly (during setup) add server, database, uid, pwd, etc.

You cannot post IFCode. check over here Monday, September 10, 2012 6:22 PM Reply | Quote 0 Sign in to vote I need the same as T. Praveen Lokhande InstallShield Software Corp. Username Password I've forgotten my password Remember me This is not recommended for shared computers Sign in anonymously Don't add me to the active users list Privacy Policy

Several functions may not work. Through some research, i think it has to do with uid and pwd being unsupported for SQL connections due to security. For a work-around, go to Control Panel/ODBC Data Sources and set the DESCRIPTION of the DSN to the same thing as the name of the DSN, and the install should work his comment is here I get the same issue if I do not use variables at all and just harcode in the details.

Output the Hebrew alphabet How to avoid intersection of elements in tikz How do I come up with a list of requirements for a microcontroller for my project? Thank you for your suggestion.Regards,Cosmin Cosmin Pirvu - Advanced Installer TeamFollow us: Twitter - Facebook - YouTube Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year ConfigDSN calls SQLWritePrivateProfileString in the installer DLL to add any additional keywords and values used by the driver.Modifying a Data SourceTo modify a data source, a data source name must be

Im using 1.10.I wonder if there may be another way of creating DSNs...

Build the install package, remove the DSN from Control Panel/ODBC Data Sources, then run the installation. Thank you again. –PerPlexSystem Dec 7 '12 at 20:01 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using All Rights Reserved. Register now!

I've tried with loginid, uid but did not work... odbcconf.exe /a {CONFIGSYSDSN "SQL Server" "DSN=blabla|Description=blablubb|SERVER=vsnet1|Trusted_Connection=Yes|Database=dm"} Hope this helps Uwa. Any help would be very very appriciated. weblink You cannot post or upload images.

Privacy statement  © 2016 Microsoft. The command below should create the DSN for you. For SQL Server, specifying any of the attributes related to authentication will cause the installation to fail.Hope this helps.Regards,Ionut Denis Toma Advanced Installer Team http://www.advancedinstaller.com/ Top PLT Posts: 13 Joined: Wed How would I embed the username and password?

When you get to the part that has the database name, driver, etc. > You need to delete all entries except: database name, database server, and > trusted connection. For more information, see "Comments."ReturnsThe function returns TRUE if it is successful, FALSE if it fails.DiagnosticsWhen ConfigDSN returns FALSE, an associated *pfErrorCode value is posted to the installer error buffer by We appreciate your feedback. Is it possible??

Go the Director Editor and Select the ODBCSourceAttribute table. To find out which one is not supported, start removing parameters one at a time. This makes me think that the ODBC connection needs to be set up through a custom action rather than the ODBCDataSource... Using trusted connection would be the best way to achieve connecting without specifying credentials since the logged on user credentials is used for authenticating to the server.

You cannot edit other topics. Below is a sample command line to create a user DSN named JoeyUSERDSN   odbcconf.exe /a {CONFIGDSN "SQL Server" "DSN=JoeyUSERDSN|Description=Joey's User DSN|SERVER=yourserver|Trusted_Connection=Yes|Database=yourdbname"}     This also sets the default database to Security is not an issue in this environment.