System DSN

We have a 3rd party application that uses a system dsn to connect to a database. We moved the database to a new server. We kept the database name and the username. We have to use SQL Authentication. Pointing the dsn to the new server is easy. I can do this
through the registry. On the new server, we changed the password for SQL Authentication. We have not gone live yet. I have to change the password on the system dsn for 400 workstations. Can some one point me to a tool or script that allows me to change
the password.
Thank you.

It's more a question for powershell/system administration.
System DSN's are saved into registry. If you have access to their registry them you can execute it to all remote workstations.
You can do it with powershell.
I'd do it with psexec (www.sysinternals.com) and a batch file to execute the
Create e.g. a file named regimport.bat
regedit.exe /S exportedregistry.reg
on the remote machines
Command Line:
psexec @filewithallcomputers.txt -u domain\admin -p password \\server\\share\\regimport.bat
You also should create a text file containing all the computers you want this to run... (I named filewithallcomputers.txt)
You can export the value from the registry so you can remotely import it(careful for differences between 32/64bit).
This will help:
http://blogs.technet.com/b/heyscriptingguy/archive/2005/07/25/how-can-i-retrieve-a-list-of-the-system-dsns-on-a-computer.aspx
Hope this is enough...
"If there's nothing wrong with me, maybe there's something wrong with the universe!"

Similar Messages

Cannot see System DSN ODBC Data source (however user DSN is Ok)

We have installed BO 6.5.1 on Windows 2008 R2 64 bit and set up ODBC Data source to the existing SQL server.
When we try to set the BO up (Administration>Safe recovery etc.), in the "Database middleware selection" - "Define new connection" - "Data source name" we cannot see the System DSN name that we've created in the Window's "ODBC data source administration" control panel applet. If we create a User DSN, we can see it ok but it works for one user only (as it should).
So, in a nutshell, if we setup a User DSN it works fine but if we setup a system-wide System DSN BO cannot see it. I've got no idea why...
Can anyone point me to the right direction, please?

Are you using the ODBC Administrator from control panel? If so, try launching this instead: odbcad32.exe from start/run.
This is the 32-bit ODBC administrator and since we are a 32-bit application, a 32-bit DSN will need to be configured.
Here's another forum thread that may be helpful:
http://social.msdn.microsoft.com/Forums/en/sqldataaccess/thread/49e206c3-f4f8-4757-8990-71b93120d2bc
and this one too:
http://forums.techarena.in/windows-x64-edition/698703.htm
Thanks
Jonathan

MySQL System DSN: Host is not allowed to connect to this MySQL Server

Hi all,
I'm creating a FileMaker database to keep track of support and to-do items, for a large forum-site I'm managing here in Denmark.
The site runs on our webhosts servers, but I have a MacMini server we use for development. I'd like to connect the MacMini's MySQL server to FileMaker, and have purchased Actuals ODBC pack witch works great. I can connect to the MySQL server on the MacMini via Navicat, by enabling an SHH Tunnel.
When trying to create a System DSN via the Actual ODBC drivers, to connect to the MacMini, I get this error:
Link to screenshot: http://img.skitch.com/20100104-82xe6j7x9b8cjmj357t33p9sb1.png
The one very strange thing is, that the Mac I'm trying to connect from, is at 192.168.1.15 and not 10.0.0.5! The MacMini is at 10.0.0.2 so it makes no sense what so ever, and as I said, I can connect fine to 10.0.0.2 via Navicat, even though it only works when I enable SSH Tunneling.
But of course the Actual ODBC (or any for that matter?!) drivers does not support creating an SSH Tunnel, so I need to be able to connect directly to the MacMini's SQL-server, but when I try I get the above error.
Port 3306 IS open on the server, so I must be overlooking something obvious. I've tried to change the socket when setting up the System DSN to /var/mysql/mysql.sock or /var/mysql but that changes nothing.Ohh yeah, that is ignored for remote servers by the way!
Can anyone help? How do you guys setup your System DSN to a Mac-server with Snow Leopard Server on it?
Thank you so much in advance
Thomas
PS: I can connect fine to our Webhosts MySQL server with the Actual Drivers, but to decrease load on that server, I'd like to get the data for the FileMaker Support Database from our development-server instead!

bump
Anyone got an idea on this? If I've posted in the wrong forum, please advise, because I was a little in doubt as to where this was to be placed

Data loads at Repository, but error in dashboard, System DSN

Error in Dashboard UI:
ORA-01017: invalid username/password; logon denied at OCI call OCISessionBegin. [nQSError: 17014] Could not connect to Oracle database. (HY000)
While creating the System DSN with Oracle 11g, the error is as follows -
Unable to connect
SQLState=IM003
Specified driver could not be loaded due to system error 127
Any inputs would be appreciated.
Thanks
KSK

hi
1.tnsping directly the OBAW from cmd prompt or putty
2.set the ODBC.INI tnsfile on linux box
3.set the tnsnames.ora file under Oracle client on windows box
4.try to directly view the data from repository
5. some times network issues, so ask your dba to bounce the database
6. take help of your DBA to investigate more from database side
hope iit helps
poinsts please
thanks
rakesh

Cannot see System DSN in Crystal Reports 2008 on Vista/Windows 2008

I've been making quite a bit of progress in switching migrating our Crystal Reports 8.0 reports and apps to Crystal Reports 2008 on our Windows 2008 server, but am currently stuck on a DSN issue that I hope someone here can help me out with.
When I go to select a new ODBC data source in Crystal Reports 2008, the only ODBC data sources that show up in the list are User DSNs. These reports will be served via our intranet website, so I need to use System DSNs. The same is true on both my development computer running 64-bit Vista and the production server running Windows Server 2008.
I'm using Visual Studio 2008 (C#) for development along with Crystal Reports 2008 (not the Crystal Reports Basic that comes with Visual Studio).
How can I use a System DSN? Any help or advice will be much appreciated!

Hi, Paul;
The first thing to check is to ensure you are creating a 32 bit ODBC DSN, and not a 64 bit one. Crystal Reports 2008 is 32 bit only.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=381384&SiteID=1
Best Regards,
Jonathan

Instant Client on 64-bit Windows 7: Driver does not appear in System DSN

Instant Client on 64-bit Windows 7: Driver does not appear in System DSN tab when creating a new Data source.
What I did so far:
I downloaded the basic and odbc zips for Window 64-bit.
Unzipped the basic zip.
Unzipped the odbc zip to the same directory.
Added the dir path to the System Environment Variable called Path.
Double-clicked on the odbc_install.exe to run it from Windows Explorer.
Then I tried to add the driver to create a new data source but it does not appear in the list of drivers.
From a cmd window, I navigated to the instant client directory and tried to run odbc_install again.
I got the message: Oracle ODBC Driver with same name already exists.
What am I missing?

hello, I did it like that you say,but the result also is "oracle odbc driver with same name already exists". I don't kown what can I do it ,Thank you!

How to use VBScript to access a 32bit ODBC System DSN (Excel) on a Windows 7 64bit system?

What is the correct way to connect to a 32bit System DSN (Excel) on a Windows 7 64bit system?
I've recently switched from Windows XP Pro x32 to Windows 7 x64. Now, one of my scripts that uses an ODBC connection will no longer work. After a bit of searching, I discovered that Windows 7 x64 does not currently have 64bit Excel drivers. However, you can set up 32-bit connections by running "C:\Windows\SysWOW64\odbcad32.exe". Unfortunately, my script still won't work even though I set up the System DSN exactly like I did on my old computer.  When I run my script, I get the following error:
Quote:
Script:  X\XML_Check.vbs
Line:  212
Char:  3
Error:  [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.
Code:  80004005
Source:  Microsoft OLE DB Provider for ODBC Drivers
Line 212 contains:
objConnection.Open "DSN=charge_codes_XLS;"
It seemed to me that wscript.exe will only communicate properly with an identical environment (x32 to x32 or x64 to x64, but not x64 to x32 or x32 to x64). With that in mind, I found a way around the error by running my script via the 32bit version of Windows Script Host. I changed the shortcut path from "X:\XML_CHECK.vbs" to "C:\Windows\SysWOW64\wscript.exe X:\XML_CHECK.vbs" and the script appears to function ok.
What I really want to know is if there is a way to run my script via the 64bit version of wscript.exe yet have it connect to the 32bit ODBC subsystem? Is there a specific connection string I can use or am I just out of luck until Microsoft puts out 64bit Excel drivers?

I faced the same issue recently. There was a 32bit MSOffice installed on the 64bit server and the same visual basic code worked from MS Office script debugger, and did not in the cscript/wscript.
It seems that
- the cscript/wscript used 64bit ODBC driver
- the office used 32bit ODBC driver
Excel drivers are installed for 32bit ODBC (because of 32 bit office the ODBC manager 32bit was a full hand of drivers).
Excel drivers are NOT installed for 64bit ODBC manager (because of 32 bit OFFICE) and can not be installed while the 32bit MS OFFICE is installed.
The SQL drivers are installed for 64bit ODBC (so that is why the SQL connection was established well)
The solution would be to run .js .vbs scripts in 32 bit environment:
\windows\SysWOW64\cscript.exe or \windows\SysWOW64\wscript.exe
Search for more with: how do i run a vbscript in 32 bit mode on a 64 bit machine

Cannot access remote FoxPro dbf file using jdbc-odbc and system DSN

Hi all,
I have a foxpro database sitting on remote server (netware server). the dbf folder is shared and I can access it using windows explore on my weblogic server (windows 2003). I created a system dsn for that. I can access the database from the a stand alone java program using
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection surgConn = DriverManager.getConnection("jdbc:odbc:FoxDB", " ", " ");
But when I use the same thing in my weblogic 8.1 application, I cannot access the database. I didn't config any data source in weblogic 8.1
Why?
When I try this on my own computer - windows 2000, weblogic 8.1 workshop. remote foxpro database dbf folder. it works.
Any idea?
Thanks very much

Laura Ren wrote:
Hi all,
I have a foxpro database sitting on remote server (netware server). the dbf folder is shared and I can access it using windows explore on my weblogic server (windows 2003). I created a system dsn for that. I can access the database from the a stand alone java program using
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection surgConn = DriverManager.getConnection("jdbc:odbc:FoxDB", " ", " ");
But when I use the same thing in my weblogic 8.1 application, I cannot access the database.What exception do you get? WebLogic is just like any other Java App. That code
should work OK (though I have a better way)... Be warned that the JDBC ODBC
bridge is specifically dangerous. It is not threadsafe.
Joe
I didn't config any data source in weblogic 8.1
Why?
When I try this on my own computer - windows 2000, weblogic 8.1 workshop. remote foxpro database dbf folder. it works.
Any idea?
Thanks very much

Problem with System DSN (HELP!!!)

We have a customer running Oracle 817. Our application (Powerbuilder-based) uses the Oracle 817 ODBC driver to connect to the DB.
We normally set up a System DSN so that in situations where more than one user logs into the PC (using their own domain account), they will be able to use our application as well. In all of the situations in the past, we've never had multiple users needing access to the same computer at different times with different logins.
Well guess what? We now have a customer that has three people accessing the same computer at different times with different logins.
We set up the odbc with an Admin account, but only THAT Admin account can be used to access the DB using that System DSN.
We've tested our app with SQL Server (ODBC) and Sybase (ODBC) as well using different logins and they work fine, but our app fails to connect to the DB using the Oracle System DSN!
What is happening?????? We set up a File DSN for now and it works, but the customer prefers not having to save that info to a file.
Any suggestions?

1) How are you authenticating users? If you're using O/S authentication, do all the users have appropriate accounts on the database? (They do have the appropriate DB account)
2) Did you specify a username in the DSN? Did you mean to? If you want multiple users to log on with different database accounts, don't specify a username. (the app uses the same username and password to access the DB)
3) Can you elaborate on what "can't log on" means? I assume you get some sort of error message, so please post that. (it's telling us that the selected datasource is invalid.)
4) Can you simply create a user DSN for each Windows user account? We could and we did and it works fine that way, but the System DSN eliminates the need for that. We would have to set up DSNs for each PC (50+) that has more than one user.
Justin

How to read System DSN entries -Urgent

Hi,
I need to show list of System DSN entries in JComboBox. So, I want to know the way of reading the entries in Java. Can you please help me ??
Thanks in Advance
Kumar

please stop posting this question.
the answer.. which you already know is JNI or native code. but a better question which was already asked of you is WHY do you want to show a list of available DSN's on a machine? it sounds like using a dynamic DSN would probably help you.
please see here...
http://forum.java.sun.com/thread.jsp?forum=48&thread=200603
if dynamic DSN's will not help you and you MUST retrieve a list of DSN's available on a system you are looking at native code to do this... good luck.

ODBC System DSN's are invisible in teh Data Sources even though they exist

For a long time I had a problem with Windows XP Pro systems that had NI-DAQ installed. These machines were ATE controllers which had Labview applications deployed with NI-DAQ cards. I needed database connectivity through several system DSN's for Access, Pervasive, and SQL server. The problem was that after I installed NI-DAQ all the system DSN's would disappear in the Data Sources control panel in windows. Then if I tried to create them again it would say they were already there. I could actually edit them by name, delete them and recreate them, but they would not appear in the WinXP Data Sources Manager. They would exist, but would be invisible. They actually worked fine from an application perspective, but would be a pain to edit or know if I had set one up or not.
I finally solved it with the help of my network admin and I wanted to post the solution for someone else with the same problem:
I solved the invisible ODBC problem. NI installs an ODBC DSN called Citadel 4. When this is installed it adds its entry via a registry setting. The problem is it changes the "Default" key in HKLM\Software\ODBC\ODBC.INI from "No Value Set" to blank. For some reason, when ODBC Manager reads the list in this key, the blank screws it up. Deleting the Default setting causes the Default setting to be recreated as No Value Set and all appears again.
-Devin
I got 99 problems but 8.6 ain't one.

I've accidentally answered my own question. I did a Software Update including the combo update to take me to 10.5.8 (Jeez, that took AGES! do all Software Updates in Leopard take that long?) - then I launched Mail and suddenly everything was there - receiving messages, and the mailboxes full of my messages. Perhaps it was a bug in 10.5.6

Using System DSN Credentials in OBIEE 10g

Hi Gurus/Experts
This is what i read in one of the blogs... that If the Shared Logon option is not selected, connections through the connection pool use the database user ID and password specified in the DSN
http://oracle-bi.siebelunleashed.com/articles/more-on-connection-pools/
Thought of giving it a try..
so created a System DSN
In Connection Pool, Disabled the shared logon and chose the ODBC 3.5 and gave the DSN name from the dropdown.
Now i am getting the below error in the Physical layer itself while viewing data...
A general error has occurred. [nQSError: 16001] ODBC error state: 28000 code: 1017 message: [Oracle][ODBC][Ora]ORA-01017: invalid username/password; logon denied.
My Question
Can we really use the credentials from the System DSN , if the Shared Logon is unchecked?
Note: The DSN is working fine when i test it...
Thanks
Ashish

Let me tell you what i did..
My Rpd was working fine and i had Shared Logon thing checked...
Then i read this blog... and i thought of trying it out.. ie trying to use System DSN's credentials to see data... [can we store password in System DSN?]
After that i went to the connection pool and removed username and password ( ie gave blank or null there) and unchecked the shared logon thing.
[If i am disabling the shared logon then whether i give username, password or not should be immaterial .. right?]
Now i saved the Rpd... and then tried to view the data in physical layer ... its throwing the above error... or in other words its not taking the credentials that i had given while creating System DSN in windows [ ie in Run type odbcad32 then that DSN stuff]
Make sure the Physical Schema in Physical Layer RPD (green folder) is same as you have schema name is Database. Its same
If this option is not selected, connections through the connection pool use the database user ID and password specified in the DSN or in the user profile.Specified in the DSN... see i mean the System DSN ie accessed in windows... and i havent given any user specific logon in OBIEE...
You can also check the checkbox for required fully qualified names..Its already done...
Let me know if you need more details
Thanks
Ashish

Remove odbc system dsn using batch file and odbcconf

I create user system dsn entries by using a batch file and odbcconf call. I've found references here on how to do that, yet cannot seem to find any results on how to remove them using that same call. The library information (http://msdn.microsoft.com/en-us/library/ee388579(VS.85).aspx) states add and modify a system dsn for configdsn and configsysdsn and references equivalent to SQLConfgDataSource function. (http://msdn.microsoft.com/en-us/library/ms716476(VS.85).aspx) but the config data source function has a a removal and this doesn't seem too.
Apologies for being obtuse, but I can't seem to locate it. Any links to how this is done from a batch file are much appreciated.
Regards,
NR.

John C is basically correct, you can remove a System ODBC data source via the registry, but there is apparently no way via odbcconf.exe. That is of course really stupid and poor programming!
John, however, forgot another important registry entry. That key deletion he mentioned will disable the odbc connection, but not remove it entirely. If you just do that and then open the "ODBC Data Source Administrator", you will find the
connection is still listed, but you can't remove it or modify it. It becomes completely screwed up! There is a value to delete as well which dictates if the connection is listed. Consider it the "header" to the data source.
Also, in Windows 2003 and 2008 at least, the registry key John C listed is not quite the location to modify either. This is where to find them in those OSs:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\%DSN%
or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\%DSN%
The "header" I reffered to is a string value in inside a key (not the whole key!)
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources
or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources
The string value is the data source name. This entry must be removed to remove the data source listing entirely.
Here are some batch snipets for creating and then removing an odbc data source. I'm leaving out some premiliary chunks, but you can figure it out from here. If you can't, you probably shouldn't be messing with this stuff in the first place!
In these scripts, I create and remove a 32-bit data source in either a 32-bit or 64-bit version of windows. The windows folder variable gets set to either "C:\Windows\System32" or "C:\Windows\SysWOW64" depending on the os. In case you didn't
know, on a 64-bit machine there is are also 2 differrent versions of the "ODBC Data Source Administrator" gui tool and the data source lists differ (32-bit vs 64-bit lists). The 32-bit version on a 64 bit OS is found at "C:\Windows\SysWOW64\odbcad32.exe".
The one in the start menu will load the 64-bit version so you will never find your 32-bit connections there.
Note - for simplicity I use the database name as the user name and and the data source name as well (in case there was any confusion).
Create the connection like so:
echo Creating 32-Bit System ODBC Connection "%DatabaseName%"...
"!WindowsFolder!\ODBCCONF.EXE" CONFIGSYSDSN "!ODBCDriver!" "DSN=%DatabaseName%;Server=localhost;Port=3306;Database=%DatabaseName%;UID=%DatabaseName%;PWD=%DatabasePassword%"
And then remove it like this:
echo Removing 32-Bit System ODBC Connection "%DatabaseName%"...
if "%WindowsBits%"=="32" (
If Exist "!TempRegFile!" Del "!TempRegFile!"
echo Windows Registry Editor Version 5.00>>"!TempRegFile!"
echo.>>"!TempRegFile!"
echo [-HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\%DatabaseName%]>>"!TempRegFile!"
echo [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]>>"!TempRegFile!"
echo "%DatabaseName%"=->>"!TempRegFile!"
regedit /s "!TempRegFile!"
) else (
If Exist "!TempRegFile!" Del "!TempRegFile!"
echo Windows Registry Editor Version 5.00>>"!TempRegFile!"
echo.>>"!TempRegFile!"
echo [-HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\%DatabaseName%]>>"!TempRegFile!"
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources]>>"!TempRegFile!"
echo "%DatabaseName%"=->>"!TempRegFile!"
regedit /s "!TempRegFile!"
If Exist "!TempRegFile!" Del "!TempRegFile!"

Setting up ODBC System DSN

I have successfully installed the Oracle 8.1.7.3.0 ODBC driver (through the Universal Installer) on a Win 2000 Pentium 4 pc. When I attempt to add a new System DSN using the installed Oracle ODBC driver, as soon as I select "Oracle in DEFAULT_HOME", I get the following error message... "The setup routines for the Oracle in DEFAULT_HOME ODBC driver could not be loaded due to system error code 126."...any ideas???? I am using Microsofts standard Microsoft ODBC for Oracle to access a few 8.0.5.2.0 databases, but when I try using that same driver to access the 8.1.7.3.0 database, I can only access 1 table from any schema. Help!!! I read elsewhere in this forum that the driver installed must match the Oracle client software version. If this is true, how do I determine what version my client software is (my SQL*Plus version is 8.0.5.2.0). Any recommendations?
Thanks!
Torrey

It sounds like you have an 8.0.5 Oracle client. Try using the 8.0.5.x ODBC driver.
Justin

Setting System DSN for MS Access Database using Java Code

How to set the system DSN for Access database using Java Code at runtime....???
Replies are deeply appreciated...

I found a 3rd Party MS Access JDBC Driver from a Google search. I downloaded and tried the free trial version. It worked fine but we opted not to purchase the full version and went a different route. If you don't find it, let me know and I'll see if I can track down the name of the product we tested.

System DSN not visible to 'domain users', why??

We have a Windows Server 2012 R2 Remote Desktop Services RDS farm.
I set up a 32-bit *system* DSN properly with the 32-bit ODBC app for Crystal Reports 2011, a 32-bit app.
When a domain user opens CR the newly created DSN does not appear in CR, though it appears for an admin user.
Why is the system DSN not visible to the domain users per se??
I checked the proper registry item and gave 'Domain Users' read permission to it, still no work.
Certain users need to see the DSN so they can configure the report to talk to the proper server, database, etc.
System DSNs are supposed to be visible/usable to all users.
What should I do??
Thank you, Tom

FWIW some other DSNs are visible to CR2011 but nothing we can use, they were somehow automagically created during installation of other software stuff.
I've tried every way I can think of to install the DSNs (different providers, different accounts) but I still can not get the desired DSN visible to my domain user login after opening a Crystal Reports 2011 report and clicking 'change database location'...
I thought about and tried using a DSN-less connection string but that did not go very far...it would be usable, people could type in ID and password if they must, but I could not get it to even let that happen...I also did not quite know what the string
should be, the database itself is SQL Server 2012 (11.0), I don't know the exact version OTOH.
The Remote Desktop Services Hosts are all Windows 2012 R2...could that be the cause of the problem?? Every other server I've put system DSNs was 2003 or 2008...
Thank you, Tom

System DSN

Similar Messages

Maybe you are looking for