Showing posts with label logon. Show all posts
Showing posts with label logon. Show all posts

Tuesday, March 20, 2012

Connection Manager in SSIS packages

I am trying to run a package outside of the Business Intelligence development Studio. It continuously fails and tell me that my username cannot logon due to a password failure. When I check my connections the password never shows in the connection string and remains blank in the connection properties although I have checked Save Password in the connection properties. Does anyone know how I can save the password in the connection string being utilized in the SSIS package?Passwords are not shown in the properties due to security. I am assuming you are using SQL Server authentication instead of Windows Authentication. When you specify the password and save password, it saves it. But if you open the connection manager again, it won't show you the password (though it is still saved). However, to be able to leave it in the current state, you should now click Cancel to exit the connection manager, instead of OK. If you press OK, it will expect you to enter the password again. I think you must have opened the connection manager, and then pressed Ok, instead of Cancel, which erased the password.|||

I don't think that's the problem. I experiencing the same problem in my development Environment (using SQL Server authentication):

We're a group of developers working on the same package. after setting the connection managers with the correct username and password (and checking the save option) and saving the package by a certain user, when a different user accessing it, he cannot run the package and have to go through all the connection managers and ser the user and passwords all over again.

Any solution?

|||

Liran,

Check the ProtectionLevel property of your package. My guess is that you have ProtectionLevel=EncryptSensitiveWithUserKey

This means that all passwords are encrypted with a user-specific value meaning that only that user can run it.

If you follow best practice (http://blogs.conchango.com/jamiethomson/archive/2006/01/05/2554.aspx) of making your packages location-independant (http://www.windowsitpro.com/SQLServer/Article/ArticleID/47688/SQLServer_47688.html) then this should not be a problem.

-Jamie

sqlsql

Sunday, February 19, 2012

Connection and Logon Code Problem

Hi...

I am having problem with my Crystal Report XI Connection and Logon Code. I am using VB.NET 2003

1. I made a non-embedded report document named AccountReport.rpt and save it in "D:\Report\AccountReport.rpt"

2. AccountReport.rpt connection properties

a. I used an odbc(RDO) connection string

Provider=MSDataShape;Driver={Microsoft Access Driver (*.mdb)};Dbq=D:\Account.mdb;Uid=admin;Pwd=userxxx;

3. In My VB.NET code:

a. VB.NET Code:

Dim AccountRPT As New ReportDocument
'Instantiate my report document

AccountRPT.Load(Path.GetFullPath(".") & "D:\Report\AccountReport.rpt")
'Load the report

AccountRPT.DataSourceConnections(0).SetConnection("Account", "F:\Business\Grocerry\Account.mdb", "admin", "userxxx")
'You can see here that I change my database location from "D:\Account.mdb" to "F:\Business\Grocerry\Account.mdb".

AccountRPT.SetParameterValue("BALANCE", 2000)
'Passed a value into a parameter list

frmGraph.crvReport.ReportSource = AccountRPT
'Set my report document as a report source for viewing

4. The Problem.

a. The connection of my Report Document "AccountRPT" does not change from "D:\Account.mdb" to "F:\Business\Grocerry\Account.mdb".

If anybody can help please do...

Sincerely...Check with this link :

http://support.businessobjects.com/library/kbase/articles/c2010371.asp

It may help you to solve your problem.

Thanks,
Vidu.