Sign in to follow this  
Followers 0

Changing password on System DSN

1 post in this topic

I need to change/edit the password on a system dsn that uses sql authentication. I need to modify this  on 400 workstations. I wrote the following to change the password: 


run("rundll32.exe shell32.dll,Control_RunDLL odbccp32.cpl",@SystemDir,@SW_HIDE)
winwait("ODBC Data Source Administrator")
ControlCommand ( "ODBC Data Source Administrator", "", "SysTabControl321" , "tabright")
winwait("Microsoft SQL Server DSN Configuration")
WinWaitActive("Microsoft SQL Server DSN Configuration", "This wizard")
WinWaitActive("Microsoft SQL Server DSN Configuration", "How should")
WinWaitActive("Microsoft SQL Server DSN Configuration", "")
WinWaitActive("Microsoft SQL Server DSN Configuration", "&Change the language of SQL Server system messages to")
winwait("ODBC Microsoft SQL Server Setup")
WinWaitActive("SQL Server ODBC Data Source Test", "Test Results")
winwait("ODBC Microsoft SQL Server Setup")
winwait("ODBC Data Source Administrator")

My dilemma is that I have more than one system dsn. I cannot get to the right system dsn to edit (click the configure button). The editor does not show this list or text. How can I move to the right dsn to modify.

This is for 3rd party software; I have to use sql authentication. Thanks to anyone that can help.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Similar Content

    • Skysnake
      By Skysnake
      How to detect / determine if requested ODBC driver is not available? Not installed?  Is there a specific function / error code to check for?
      I asked this on the ADO.UDF support page, but I think the issue is not limited to that UDF.  What test can be run to determine if the requested ODBC data driver is available?
    • cookiemonster
      By cookiemonster
      Im about to start making an autoit script that will read the current ODBC settings, have a drop down to select a different one which would then update the ODBC in windows to use the new settings.
      Can anyone point me in the direction of how to read the ODBC 32 bit settings? are they in the registry?
    • GarnetDagger
      By GarnetDagger
      I would love to have some help or guidance 
      I am able to Query from my database but I am not able to Update or insert etc because I lack the knowledge for it
      this is my code for to retrieve some data from and works perfect
      Dim $ueberschriften = "" Dim $anzahl = 0 Dim $dsncount = 1 Global $DSN = "MTXXV5" Global $Query = "Select * from VIEWS" Func SSSQL($SSQuery) ;SuperSonicSQL     ConsoleWrite($SSQuery & @LF)     $cmboVal = ""     $adoCon = ObjCreate("ADODB.Connection")     $adoCon.Open($DSN)     $adoRs = ObjCreate("ADODB.Recordset")     $adoSQL = $SSQuery     $adoRs.CursorType = 2     $adoRs.LockType = 3     $adoRs.Open($adoSQL, $adoCon)     With $adoRs         Global $QueryAnswer = .GetRows     EndWith     Return $QueryAnswer EndFunc   ;==>SSSQL and this is my failed attempt, The Query is correct but I want to able to use it in autoit instead of have to manual update or insert into flamerobin
      $SS_SQL_Insert_or_Update = "INSERT INTO DETECTION (DNAME,DTYPE,WINNAME,AREA,COLOR,MOUSE) VALUES ('PopUpTradeInviteYes        s                    ','SEARCH','XXX','175,240,550,240,65,228,82,234','5062478','0') " Func SSSQLIU($SS_SQL_Insert_or_Update) ;SuperSonicSQL :P     $cmboVal = ""     $adoCon = ObjCreate("ADODB.Connection")     $adoCon.Open($DSN)     $adoRs = ObjCreate("ADODB.Record")     $adoSQL =$SS_SQL_Insert_or_Update ;~     $adoRs.CursorType = 2     $adoRs.LockType = 4     $adoRs.Open($adoSQL, $adoCon) ;~     With $adoRs ;~         Global $QueryAnswer = .GetRows ;~     EndWith ;~     Return $QueryAnswer EndFunc   ;==>SSSQL I am at a total loss and I am just trying this at random but I am also going to sleep now
      I would love to have some minor examples
      "C:\_CC_V10_DetectionTAB.au3" (174) : ==> The requested action with this object has failed.:
      $adoRs.Open($adoSQL, $adoCon)
      $adoRs^ ERROR
    • jaeger52
      By jaeger52
      Hello all! I've been scouring the interwebs for a whiff of anybody else who's had this problem and come up empty. Here's the deal: I wrote a simple little script that I've used for months now quite successfully, but I'm also experiencing an error where the ODBC login window will pop up, garbage text will automatically dump into the username, password, and sometimes the source fields, and then it will automatically try to log in and cause it to fail. It's intermittent, and I have no idea what's causing it. It happens in databases that I've never automated, but it does exactly what the script I wrote should do except that it's garbage text being entered. I've attached the script I mentioned. I'd appreciate anything anybody can suggest or recommend. Thanks!
      Send ( "{LWin}" ) Sleep ( 2000 ) Send ("Drive:\Folder\Database.accdb /x Macro") Send ( "{ENTER}" ) WinWaitActive ( "Oracle ODBC Driver Connect" ) Send ( "Username" ) Send ( "{TAB}" ) Send ( "Password" ) ControlClick ( "Oracle ODBC Driver Connect", "OK", 1 )  
    • Tippex
      By Tippex
      I had a problem getting a connection to "SQL Server" on 64 bit PCs (running XP) even though 32 bit PCs connected easily.
      Even compiling for 32bit was (initially) insufficient and to get it working at all on a 64bit PC, I ended up forcing its use of TCP/IP protocol by specifying a port number (that is apparently picked up as a default by 32 bit PCs once "SQL Server" has been added with it configured in "Control Panel --> Administrative Tools --> Databases(ODBC) --> Add --> SQL Server --> Client Configuration"
      This worked for me on a 64bit PC, but only when compiled in 32bit:
      $sqlCon = ObjCreate("ADODB.Connection")
      $sqlCon.Open("DRIVER={SQL Server};SERVER=name.of.server,port_number;DATABASE=name_of_database;UID=logon_ID;PWD=password;")
      If @error Then
       MsgBox(0, "Problem", "SQL Connection Failed")
       MsgBox(0, "Success", "SQL Connection OK")
      Also, I found that the "SQL Server" needed to be added to the Databases(ODBC) as shown above (and tested OK) before the AutoIT script worked but (strangely) it could be later removed from Databases(ODBC) and it still worked (perhaps it just needed to setup defaults).
      Does anyone know how I can get the above working when compiled in 64bit too?
      On a X64 bit PC, the above script it will fail to work with:
      but works OK with