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?
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
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.
In 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.
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?
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
I'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.
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
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...
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.
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
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
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.
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.
Hello. I have recently installed MS SQL SERVER 2005 and when I was installing it, it asked me for the username and password, and there I had 2 options: either write my own, either select "Use Windows Authentification". I selected the "Windows Authenthification" ( I guess that means that it uses my username and password from Windows ).
Now, Im trying to connect to the Server using Java and JDBC, but I have a problem: I have to specify the username and the password of the connection! My windows' only account is "Vlad" and I have no password. I tried these options, but it didn't work. I also tried with empty string "", and with "sa", "sa" but it didn't work either. I get an error saying that "Login failed for user 'Vlad'. The user is not associated with a trusted SQL Server Connection."
Any ideea of what the username/passwords are or how to get them?.
I have an SSIS package that uses an FTP connection manager. When running the package in BIDS, it runs fine and maintains the password for the remote ftp site's user account. Once I deploy the package and attempt to run it, it fails with the following error:
Started: 4:06:15 PM Error: 2015-08-27 16:06:20.09   Code: 0xC001602A   Source: Export and FTP New Jobs Connection manager "FTP Connection Manager"   Description: An error occurred in the requested FTP operation. Detailed error description: The password was not allowed End Error Error: 2015-08-27 16:06:20.09   Code: 0xC002918F   Source: FTP Jobs Listing to Concur FTP Task   Description: Unable to connect to FTP server using "FTP Connection Manager". End Error DTExec: The package execution returned DTSER_FAILURE (1).
I've tried Don't Save Sensitive With Password and that still fails.
Does the FTP connection manager just not retain passwords outside of BIDS?
I have a simple FTP task that I am trying to connect to an FTP server. I can test the connection fine, however, when I try and execute the package from Visual Studio 2005 I get the "The Password was not allowed" message. I have found some threads that mention setting the protection level on the package to EncryptSensitiveWithPassword, however, I still get the same message appearing.
Has anyone any idea as to what is causing this and how I can get around it
I'm trying to setup a dynamic ole db connection using the SA user ID, it has to be dynamic because the server name will change and it has to be SA because we're pulling information from system databases that some users don't have access to.
If I setup a regular static connection using SA credentials it works like a charm of course. When I create an expression to use the User:erver variable it doesn't work, it throws an error message saying that "The login failed for user sa" among other things, I'm thiking that the sa's password is not being saved.
Where exactly do I place a password for dynamic connections using sql server users? On the connection string? On the password property of the source? Any ideas?
The problem I am facing is related to dynamic configuration of package one of the package connection is DB2 connection, I tried to set the expression connection string for that connection to the variable which contains the connection string to the DB2 but when I set connection the String property then i get the error message in transformation that password is missing, I dont want to write password in connection String for security reasons so I tried to save password in connection which is not helpful I am getting the same error message package security setting I changed to "Encrypt Sensitive Data with User Key" , anywayout to overcome this problem?
I'm creating an xml configuration file to hold the connection string including the password (sql server authentication). My package protection level is set to 'EncryptSensitiveWithPassword'. I set up my connection manager and I check the 'Save my password' box. The 'Test connection' button reports that the connection is OK. I enable the package configurations and I go through the Package Configuration Wizard and I specify 'xml configuration file' and I choose 'Specify configurations settings directly' and I specify a configuration file name with the same directory as the package. I check the 'ConnectionString' property and the 'Password' property and then click 'Close'. Then I save my package changes. Now I look at the xml configuration file in a text editor and I see the Password property has an empty element:
<ConfiguredValue></ConfiguredValue>
Is it supposed to be empty? When I right-click the package in solution explorer and pick 'Reload with upgrade' then I have to enter the password, but the validation fails with 'Acquire connection' error. Should I just be saving the 'Connection string' property, or should I save all the connection elements (i.e. ServerName, UserName, Password etc.)? If I edit the xml configuration file and I type the password into the <ConfiguredValue> element above, and then I do 'Reload with upgrade', then the 'Acquire connection' validation error goes away. Could this mean that I am not able to encrypt the password? Thanks.
Just downloaded and installed the VS 2008 Express and created/tested some websites. I have done several aspx websites using VS 2005 during the last 2 years. Still I don't quite understand the details of coding the database connection and DataBing. For example, what does 'providerName',and Integrated Security really mean?Why in the Web.config file these are providerName="System.Data.SqlClient" and Integrated Security=True? Why in Default.aspxthere are both ntegrated Security=True;and USER ID=WEB; Password=webwebweb1". I know these may deal with the authentication mode of my SQL Serverdatabase.For the VS 2008 Express and SQL Server 2005 Express, I installed in my XP home PC, I used the file system websites, If I upgrade to XP Pro and install IIS web server, and use SQL Server 2005, what might be different? Jeffrey Web.config <connectionStrings> <add name="NorthwindConnectionString" connectionString="Data Source=D5MRY6G1SQLExpress;Initial Catalog=Northwind;Integrated Security=True" providerName="System.Data.SqlClient" /> </connectionStrings>Default.aspx <asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="Data Source=D5MRY6G1SQLExpress;Initial Catalog=Northwind;Integrated Security=True; USER ID=WEB; Password=webwebweb1" ProviderName="<%$ ConnectionStrings:NorthwindConnectionString.ProviderName %>"MasterDetail.aspx <asp:SqlDataSource ID="SqlDataSource2" runat="server" ConnectionString="<%$ ConnectionStrings:NorthwindConnectionString %>"
I create a connection to an OLE db source and use SQL Server authorization and save the password, the connection manager seems to "forget" the password. That is, when I click the 'save password' check box, and do a test connection, it connects fine. But as soon as I close that connection window, and reopen it, the password box is empty, and the 'save password' box is still checked.Â
While using the connection manager name in the SSIS component (say script task) the connection is failing . As a workaround, the whole connection string has been put in a variable and used that variable in the SCRIPT task.
Is it a bug or some other property need to be set to use ConnectionManager Name .
User A creates the SSIS Package and provides the password for the connection manager for a task (for OLE DB source) with SQL authentication.Â
When User B tries to run the SSIS package, the error is thrown as : The package may be damaged.
On typing the password again inside the connection manager, the execution occurs successfully. Is there any workaround to save the password permamanently for the connection manager rather than each user entering it in order to run the package ?
I'm learning SSIS, and just started to use SSIS Package Configurations. I want to be able to switch between a dev and prod instance of our database.
I did not specify the password in the Configuration file (XML), figuring it would get it from the package itself. (That will be the same between dev and prod). But once I set up to use the Configuration, I started to get a "Login failed..." message. I added the password to the configuration, and it's the same. I quit using the configuration file at all, and then it works again.
This may be related, but when I show the properties on my connection, it shows stars for the password. When I go to the editor, the password field is blank, and if I test the connection, it fails. I type in the password, and then the connection works. I have the "Save my password" checked, but every time I go back, the password is blank. In fact, if I type in the password for the connection in the editor, and then go to the "All" page, the password is blank. It may be a red herring, but it sure looks like it's not really storing the password, and thus the Configuration file can't connect when it tries to get it. I can type in the password, test the connection (it works), close the editor dialog, open the editor dialog, test the connection again, and since the password is now blank, the connection fails.
What do I have to do to make that password actually stick!?
Without the Configuration file, when I save the package to SQLServer, it will run as a job, in spite of the password appearing to not stick. With the configuration file, it's not even running while still in Studio.
Here are at least some of the version information, which may or may not be useful.
Microsoft Visual Studio 2005 Version 8.0.50727.42 Microsoft .NET Framework Version 2.0.50727
Installed Edition: Professional
Microsoft SQL Server Analysis Services Designer Version 9.00.3042.00
Microsoft SQL Server Integration Services Designer Version 9.00.3042.00
Microsoft SQL Server Reporting Services Designers Version 9.00.3042.00
SQL Prompt 3.5
Thank you for any help you can provide. -thursday's geek
After I had transfered SSIS package to another PC I tried to open package and I got an error. ".. Failed to decrypt protected XML node "PackagePassword" with error . ". It turned out, that the password wasn't saved in a OLEDB connection manager of the Package. However "save password" options checked! But password field was empty.
As soos as I enter password the package executes successfully.
Question: How can I transfer a password for OLEDB Connection within a SSIS package to another developer's VS2005?
I have connected to Database using my credentials by checking remember password option. After few days I forgot my password. How can I recover the password as SQL remember it. Is there any way to recover my password instead of resetting it.
I have a package protected by a password - I am already unhappy that to get it to use the configuration file to change connection strings for the production servers I have had to hardcode the password into the config file - very insecure! However, the package now deploys correctly to the production server and will run from there OK, but NOT if scheduled as a SQL Server Agent Job. Thus is because however often I edit the command line to include the password after the DECRYPT switch (which it has prompted me for when I click on the command line tab), the Job Step will not retain it. If I open it up after I have edited it and closed it, the password has disappeared.
I know that if I run dtexec plus the code in the Command Line tab (with the password), the package runs OK.
This is driving me insane! I have read all the other posts and so I tried replacing the SSIS package step with a CmdExec step and pasting that code into there - then I get an OLEDB error..
The code I use is: DTEXEC /SQL "ImportRateMonitoringTables" /SERVER servername /DECRYPT password /CONFIGFILE "D:Microsoft SQL ServerSSISDeploymentsRateMonitoringImportTasksDeploymentImportRateMonitoringTables_Production.dtsConfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
and I get
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8000FFFF
although the same code executes perfectly from a command prompt.
Please does anyone have any experience with a similar problem and if so, how did you get round it?
