Showing posts with label business. Show all posts
Showing posts with label business. 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

Friday, February 24, 2012

Connection cannot be made to http://localhost/ReportServer

I have developed a reports in Business Intelligence Development studio and when I am tring to deploy it.
It says that
Connection cannot be made to http://localhost/ReportServer
What does it really mean.Is SSRS service running ?|||

Do you have Reporting Services install on Localhost?

Has it been configured?

Is IIS running?

That's a start.

BobP

|||Yess, it is runnning .|||IIS install - > start, control panel, add remove progs, add/remove windows components ->
tick IIS, click next etc...

Think you need to be running XP pro to do this, don't think you can do it from Home edition

Shurely you need to do this before you install RS, no? I can't remember the install process of RS....|||

It wont let you install SSRS without IIS.

BobP

|||If IIS is running then it must be user permissions on the IIS folder.