Is it possible to set up an ODBC connection on a domain computer that does not prompt for the SA password? When using Microsoft Access with linked tables to SQL, a prompt pops up asking for the SA password. Obviously it is not a good idea to give everyone the password. Any ideas?
View 1 Replies
Hello everybody,
I'm a SSiS newbie and I'm trying to reproduce my old DTS from sql server 2000 into this new SSiS.
I need to retrieve data through ODBC from a SAP db. I've got the right DNS and it works (Test connection succesful), but I'm unable to store password in connection manager.
I tryied to foigure out why and how to solve this problem, and I found somehthing on this forum talking about changing configuration files or something else... I'm a newbie, I don't know which files you're talking about..
Can you explain me in the simplest way possible how to store password in connection manager?
thanks in advance
Hi,
When I call certain reports from an ASP application, some prompt for password and some are not.
I wonder why is this happen?
Under the Directory Security of Reports under IIS 6, I already enable Anonymous Access for IUSR_XXXX with the correct password.
I also assign IUSR_XXXX as Browser in Report Manager of Reporting Services.
The enviroment is Windows Server 2003 standard edition, IIS 6, SQL Server 2005.
Thanks in advance.
Best regards,
Pop
I am using SSIS 2014 with the below .net framework version and installed in Windows server 2012 R2 . I have installed my client's odbc drivers (both 32 bit and 64 bit) in my production server and created ODBC system DSNs for 32 bit and 64 bit.
When i open SSIS 2014 and tried to create the odbc connection but i can able to see only the 32 bit system DSN connection ,i can't able to see my 64 bit odbc system dsn connection.
Microsoft Visual Studio 2012 Shell (Integrated)
Version 11.0.50727.1 RTMREL
Microsoft .NET Framework
Version 4.5.51650
SQL Server Integration Services  Â
Microsoft SQL Server Integration Services Designer
Version 12.0.1524.0
And i installed my client odbc drivers(32,64 bit) and created ODBC system DSNs in my local system and when i open ssis 2014 and i can able to see both the ODBC system DSNS(32,64) connections from SSIS ODBC connection.
I am using below version of .net framework in my local system which was installed in windows 7 and i have SSIS 2012 also installed in my system and i can able to see both ODBC connections using 2012 as well in my local system.
Microsoft Visual Studio 2012 Shell (Integrated)
Version 11.0.50727.1 RTMREL
Microsoft .NET Framework
Version 4.5.50938
SQL Server Integration Services  Â
Microsoft SQL Server Integration Services Designer
Version 12.0.1524.0
why i can not see the ODBC 64 bit system DSN connection from SSIS in my production server ?
I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.
I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
I have an app that uses ODBC for connection. Everytime the users log in it prompts the user to enter a password.
Is there any way (reg key entery ????) for the password to be saved so the user is not prompted?
Thanks
MPM
All --
Please help.
I have some questions about connection strings.
BACKGROUND...
Note that I am using the "SQL Native Client OLE DB Provider", SQL Sever 2005 Express, ASP.NET, C#.NET, and VS.NET 2005.
Note that I do not want to use the "Attach a database file" type of connection string.
Note that I am using the site http://www.ConnectionStrings.com as a reference.
Note that this "Standard security" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Uid=MyDatabaseUser;Pwd=MyDatabasePassword;" />...does not work and causes the following run-time error...A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
Note that this "Trusted connection" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Trusted_Connection=yes;" />...works but is less-than ideal because it uses a Trusted Connection rather than a Username/Password combination.
QUESTIONS...
(A) What exactly does the error in Item 4 mean?
(B) Do 4 and 5 imply that one must use a Trusted_Connection for all SQL Server 2005 Express connection strings when the database does not reside in the web application's App_Data folder or use a "Attach a database file" type of connection string?
(C) Are there any alternatives?
(D) What do you suggest?
Please advise.
Thank you.
-- Mark Kamoski
Hi,
I have an SSIS package that pipes data from an iSeries data source to a SQL Server table. The connection manager I am using is the .Net ProvidersOdbc Data Provider
When I run this SSIS package on my developer PC (from inside BIDS or using the Management Studio Execute Package Utility) it works. However when I run the package from within a SQL Server Agent Job it fails.
I have enabled logging and the error message given is:
System.Data.Odbc.OdbcException: ERROR [28000] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8002 - CWBSY0002 - Password for user MALLPRESS on server SMICHC is not correct, Password length = 0, Prompt Mode = Never, System IP Address = 172.16.0.4 ERROR [28000] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8002 - CWBSY0002 - Password for user MALLPRESS on server SMICHC is not correct, Password length = 0, Prompt Mode = Never, System IP Address = 172.16.0.4
It gives the message €œPassword length = 0€? despite the fact that I have specified a password in the package.
To try to get around this I have added an XML configuration file to the SSIS package. In this configuration file I€™ve set values for the ConnectionString, UserName, and Password.
I still get the above error about a password length of 0.
I have also tried to execute the package using dtexec, but this gives a similar error.
The SQL used to run this is:
xp_cmdshell 'dtexec /sq "SCSRV-06DTS PackagesStagingStagingBranchImport"'
This has got me stumped, and I€™m not sure where to go from here as these packages need to be programmatically run each morning. At the moment I am manually running them from within BIDS.
All packages that don€™t use an iSeries connection manager run successfully in SQL Agent jobs.
I have also tried using the OLEDB connection manager (ibm db2 udb for iseries ibmda400 ole db provider) without success.
Any help would be very appreciated.
Thanks, Matt
Both the OLE DB Connection and ADO.Net Connection in SSIS Package does not remember password.
Im connecting to a SQL Server 2000 box using its sa password as test.
The SSIS package runs fine when you first set up the connection in bids
The bottom line is that SSIS keeps forgetting the password I feed into
the two Connections that I'm using. I double-click a connection,
type the password in, check "Save my password" and hit "OK" but the
password disappears from there whenever I run the package or
double-click the connection again.
is there any known workaround for this issue as I would like to schedule my SSIS package using a SSIS Step in a SQL Server 2005 Agent job.
the only thing I found when googling this error was link below but the workaround described here is a little harsh
http://www.developersdex.com/sql/message.asp?p=1921&ID=%3C1146409399.447345.7470@j73g2000cwa.googlegroups.com%3E
thanks in advance
Dave
the box SSIS is running on is Windows 2003 Server Standard Edition latest service pack
SQL Server 2005 (no service packs )
Hello,
I have a package that contains an ADO.NET connection mananger using an ODBC provider. There is a user name and password configured in the connection mananger. The connection is to a DB2 database.
I install the package on SSIS by setting the package ProtectionLevel to ServerStorage. I then save the package to the server using FileSave Copy of (package name), and save it to the server. I also set the protection level there to use server storage.
When I enable package configurations (SQL Server), the package fails when run by a Job. In the log, I get the following error message from the DataReader source that uses the connection manager:
******
System.Data.Odbc.OdbcException: ERROR [08001] [IBM][CLI Driver] SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)
****
The DataReader fails validation. When I disable package configurations, the Job executes the package without a problem. The server that the package runs on is 64 bit.
Why do I have this password problem when package configurations are enabled? The connection manager password is include in the package configurations.
Thank you for your help!
cdun2
Hi guys,
My users are unable to view reports on server A. When trying to access it shows up as users have no access to the reports.
We have another server B which also deploys the same set of reports,to the same set of users as Server A.Users are able to view the reports on Server B.
Both server B & A are used for deploying reports that are created on another development server.I am very new to the concepts of IIS and report administration.Could someone tell me what I can start checking on? What are the settings that I can compare on both server ?
If I am not very clear on the problem explained above.Do let me know I would be glad to explain futher.
When I create a new odbc connection to a SQL server 2005 Db I get a failure telling me dat de SQL server does not allow remote connections.
How can I allow the server to allow this.
Any help appreciated
regards
Our project is on SSIS 2012 and we are using the project deployment model. We have parameter the connection managers, created environments, environment variables and configured the references. Hence, when we deploy the solution to higher environments, the connection strings are picked from the environments and not the ones stored in the connection manager.
However, we face issues when in development environment, we need to run the same package but by entering the values manually in the connection manager. Even though the connection details are correct, when we execute the package from Visual Studio, SSIS is not able to connect to the database. Is there any way to have SSIS prompt for the connection details after we have click on "Execute Task" or "Start" from Visual Studio?Â
In my ssis package,
I have a DSN connection like this: "DSN=myDSNname". Which decide from i have to pull the data.
By using OLE DB Source Editor, I want to assign that ODBC Connection to it.
By data source Reader i can achive this but where i have to pass the hard-code SQL Query that i don't want.
i'm using the variable for dynamic SQL command.
Thanks.
Manoj
hi all
i want to connect to SQL Server using DSN.
I create a System DSN, say 'DSN_PWD', provide SQL server authentication in that step and test the connection which works fine.
Now, currently i am using a code by my seniors which is as below
Dim objConn
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open "DSN_PWD","username","password"
objConn.Close
Set objConn =Nothing
what i am concerned is that this will be saved as ASP file, i don't want any login informatoin to be saved in a physical file openly.
i have tried this but it gives error
Dim objConn
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.ConnectionString="DSN=DSN_PWD;"
objConn.Open
objConn.Close
Set objConn =Nothing
Error
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
is there any effective way?
Thanks all
Yogesh Jangam
I am having a terrible problem with an SSIS Package. I created a connection in the Connection Manager and the option "Use a specific user name and password" is selected. I enter the ID and PW and make sure “Blank password� is not checked and “Allow saving of password� is set, but after I test the connection and it succeeds the password is no longer remembered. Has anyone had a similar problem. This is frustrating.
View 3 Replies View RelatedIn connection manager in ssis, I am able to choose 'Microsoft OLE DB Provider for Oralce' and
provide server name, username/ password. The test connection results is successful. and I check 'Save Password', however, when I try to run the package it keep getting an error:
ora-01017 - invalid username/ password.
it seem si can not save the pasword.. what should i do to resolve this problem
I want to allow access to a database from another computer via tcp/ip connection.
When i use Windows authentication, this works if access from the same Windows account name; it is not necessary to supply any UserID or something else. But how to authorize access from another windows user account?
When i don't use  Windows authentication ( SqlConnectionStringBuilder.IntegratedSecurity=false in C#) i never succeed to access to the database even on the pc where the database is. I created a login+password+user using code like
command.CommandText = String.Format( "CREATE LOGIN {0} WITH PASSWORD='{1}';", login, password );
command.ExecuteNonQuery();
command.CommandText = String.Format( "CREATE USER {0} FOR LOGIN {1};", userName, login );
command.ExecuteNonQuery();
but how to use these Login, user, password ? What i'd like to do is simple: allow access to my DB by supplying a Name and a Password.
I use VS express2014, C#, .net 4.x and VS CE 2013, Windows 8.1&7
For my db connection managers the password is not being saved. I have 'remember password' checked for each connection manager, but when I close down the BIDS and open it again, I have to re-enter the password again. Even when I import the dtsx file into SQL IS, its not in the connection manager information. I have to re-enter the password again every time prior to running it,.
What is causing this? I don't want to have to enter in the password everytime I run it because the jobs are going to be scheduled and no user interaction unless one fails.
Is there a way to find out my user id and password that should be used in my connection string? If I can not find this information out for myself, do I need to go to some type of system administrator.
Here is the connection string in my web.config file.
<connectionStrings>
<add name="SPK" connectionString="Server=localhost; User ID=AppUser;Password=meander;Database=atstdb01;
Persist Security Info=True" providerName="System.Data.SqlClient"/>
</connectionStrings>
When I access this connection string via my code, A little dialog box pops up with the following error message:
Login failed for user AppUser. Reason: Not associated with a trusted SQL Server connection.
I am trying to use SSIS to read a flat file into an Informix table.
When I create a OLEDB connection manager, I can connect to the DB. When I do test connection I get successful back. But when I close the manager & come back, the PW is gone. I have tried unselecting Blank Password and clicking the Save Password button.
When I try to get a list of tables in the SQL destination object, it won't work and gripes about the missing PW
What am I missing?
Thanks JPS
Hi,
View 33 Replies View RelatedI'm stuck with a very annoying problem - any help would be greatly appreciated.
I created a package using Business Intelligence Project. The package reads from a Flat File source and saves to a SQL Server table.
The package has a Data Source for the database connection. In this I have opted to save the password.
When I run the package in VS on my machine it works fine.
I then deployed the package to our SQL 2005 database server using the Deployment Utility. It then appeared in the MSDB section.
I then tested the package ran from my machine using Management Studio and all was fine.
However, if I try to run the package from the database server itself I run into problems. Specifically, the log gives me the following error:
"The AcquireConnection method call to the connection manager "<My Database>" failed with error code 0xC0202009"
....and further down I get:
"Error: an OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source "Microsoft SQL Native Client" Hresult 0x80040E4D Description: "Login failed for user 'sa'.".
What seems to be happening is the password is not being saved in the connection string. Sure enough, if I look at the Connection Managers section of the Execute Package Utility in Management Studio, then my database connection manager has only a User ID specified and no "pwd=". If I add "pwd=<my password>" to this connection string here then the package works.
How do I get this password to be remembered by the Package?
Incidentally, I have also tried writing a VB.NET program to call the package programmatically. Using this, I have tried to set the connection string of my Data Source in the code to try to get round the problem above. However, even after this I still find the only machine the package runs on is mine, and everywhere else it fails to connect.
Please help! Thanks in advance.
Richard F
Hello world.
I have a big problem.
Im writing an application in Sql 2005 Etl.
This application use 2 kind of ole db connection. One towards a Sql Server, and the other towards As400
to use ole db towords As400 is necessary to save user and password to connect.
There is a flag to save password.........and obviously a checked it. !!!!!
The problem is:
If I stay inside Visual studio and i use this application.......all is correct.
If I use my application in sql like a job.........loose password information and crash immediatly
someone can help me ?????????
thanks all in advance.
Alberto.
Hi;I am making a software (.Net) which is going to connect a ms sql server but I cant conect yet :(.1- I dont know what I have to type for user id (name)2- What is my password, it has been long time that I hvae installed it but I dont need any password with Microsoft SQL Server Management Studio Express which has windows authentication option. My software can work via internet or network. So I need to know my user name and password. I am using oledbconnection. Do I need any password?3- I visited www.connectionstrings.com already so I have the format of it.Thanks very much for any help...
View 1 Replies View RelatedHi,
I have developed a .dtsx package than runs normally from my computer. When I import it on the server and assign it to a job it always fails.
I tried also to run it directly from the server (remote desktop) and also faild. I exported the dtsx file on server and refresh the db connections and after that workd fine from the server.
Another work-around was to use windows authentication. Then runs normally from the server.
It seems that connection password is lost when importing the report on server. (The import is done in MSDB not in the filesystem)
But I can not design all the jobs on the server (work-around A) or use windows authentication (work-around B)
What is the problem and what can I do?
I have also played around with "save sensitive information" but with no results.
Thanks
Hi,
I would like to know how to programmatically extract username and password from an ftp connection manager. Thanks.
I got this code but I want to get the values of every available property in a connection manager. Please help. Thanks!
For Each connMgr In myConns
Dim connProperties As DtsProperties = connMgr.Properties
Dim connProp As DtsProperty
For Each connProp In connProperties
MsgBox(connProp.Name)
Next
Next
All,
I am using the Oracle Provider for OLE DB (32 bit) to connect to an Oracle 10g database. I enter all the connection parameters and test the data source and I it says that the connection is successful. I then open the connection manager for the data source and see that the password has disappeared.
After reading entries on this forum, I tried to setting the package permission to UserKey, Password and others. Still no luck. Then I created an XML configuration file and set the connection string and password there as well. Still no luck.
Below is the message I am getting:
Error: 0xC0202009 at Package1, Connection manager "******": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
Error: 0xC00291EC at Execute SQL Task, Execute SQL Task: Failed to acquire connection "****". Connection may not be configured correctly or you may not have the right permissions on this connection.
Here is my XML config file:
- <DTSConfiguration>
- <DTSConfigurationHeading>
<DTSConfigurationFileInfo GeneratedBy="******" GeneratedFromPackageName="Package1" GeneratedFromPackageID="{63C53905-74EC-4AD5-9523-3A4B4BEF4CB5}" GeneratedDate="3/27/2008 8:39:47 AM" />
</DTSConfigurationHeading>
- <Configuration ConfiguredType="Property" Path="Package.Connections[*********].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=*****;User ID=*****;Password=******;Provider=OraOLEDB.Oracle.1;Persist Security Info=True;</ConfiguredValue>
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[*****].Properties[Description]" ValueType="String">
<ConfiguredValue />
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[*******].Properties[InitialCatalog]" ValueType="String">
<ConfiguredValue />
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[*******].Properties[Name]" ValueType="String">
<ConfiguredValue>******</ConfiguredValue>
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[*******].Properties[Password]" ValueType="String">
<ConfiguredValue>******</ConfiguredValue>
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[******].Properties[ProtectionLevel]" ValueType="Int32">
<ConfiguredValue>1</ConfiguredValue>
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[********].Properties[RetainSameConnection]" ValueType="Boolean">
<ConfiguredValue>0</ConfiguredValue>
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[*******].Properties[ServerName]" ValueType="String">
<ConfiguredValue>******</ConfiguredValue>
</Configuration>
- <Configuration ConfiguredType="Property" Path="Package.Connections[********].Properties[UserName]" ValueType="String">
<ConfiguredValue>*******</ConfiguredValue>
</Configuration>
</DTSConfiguration>
I am a local administrator on the box as well. Any help would be greatly appreciated.
Hi All,
I'm new to SSIS. I'm trying to build a simple package, run it on dev and migrate it to our stg and tst environments. It works on my dev environment great! It simply loads data from a flat file into a table. The trouble i'm having is exporting the connection string info to an xml file and runnign it on other environments. I am not storing the package on the db. I am saving to a file and running through SQL Server BI Development Studio.
I go to "Configuration File" and export InitialCatalog, ServerName, User, Password to the file. I can manually change the xml to the new environment but don't know how to set the password. It's not in the xml and i am constantly getting "Login failed for 'sa'" errors. Anyone know how to do this. I CAN get this whole process to work if i use Windows authentication security but this isn't an option. I need to use the db security.
Thanks,
Dave
Has anyone had an issue with the ODBC data source that when you set it up for SQL, it does not retain the username and password you entered and keeps defaulting back to the NT windows verification instead of using the SQL verification that you choose?
I add a datasource, select validation based off of SQL profile/password assigned, enter the user and password I assigned on SQL, go through the setup and test successfully. Then I try to connect using that datasource with my VB application and it says connection failure. When I go back to the datasource, it has changed back to NT verification and removes the user/password I entered for SQL verification. Maybe there is an service pack from MS on this?
any help is appreciated. At the very least, I can just hard code into my VB app, but that is my last resort. Thanks!
Hi everyone
I installed the MS SQL server 7.0 on a Windows NT 4.0 SP 4 server. The network runs with TCP/IP.
I want to connect the SQL server by a ODBC-connection. Only a connection on the server (local) was successful.
The odbcping-utility reports following:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08001 Native Error: 6
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNMPNTW]Selected SQL server not found.
SQLState: 01000 Native Error: 53
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNMPNTW]ConnectionOpen (CreateFile()).
Do I forget to install a SQL server component? Or a network service?
Thank you for your help.
Greetings
Steven
I am currently running a application and a database server they are connected via ethernet. Only the application is connected to our network. Is there a way to connect MS Access to the database server without connecting the database server to the network? I've tried several different approaches and it still dosent work. Any help would be greatly appreciated.
Dale
Would someone provide a code snip example of a T-SQL script using an ODCB connection against a non-SQL2K database. I can hit the outside database using DTS (so I know it is possible) but I'm having trouble with the parameters using a script.
Thanks,
Fred.