noob to SSIS package configure and deploy

Hi there

I am fairly new to SSIS, I got my package running fine in my development environment with the connection managers (connecting to 3 databases on the same server, with username and password, not Integrated security) and all.

The problem comes in when i want to deploy my package or execute it outside of the development environment.

When I execute the .dtsx file in my project it brings up the Execute Package Utility and I just click Execute, thinking it should work, but not, any ideas?

So I read some of the forums and got looking into the configuration file, suppose that it does not carry the connection manager settings thru, but dam that still doesn't work for me?

The whole idea is that I will be executing the package from my C# code, so does my package have to be just on the server in a folder or does it have to be installed in the db? which is best?

Hope anyone can help me!!

Thanks
Jamie

If the error you are getting is a failure to connect to the database, the problem is in the password not being stored in the package. If you search the forum for connection strings and configurations, you'll see a number of different solutions to this.

If that's not the problem, please include the error message that you are receiving.

None-Domain server cannot access SQL2005 data on Windows 2003 domain server

I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.

- I have try following the KB265808 - no success.

- Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.

Error Message:

TITLE: Connect to Server

Cannot connect to ardsqldatawh.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

Question: Could Windows 2003 security be blocking access? I'm using sa account to access.

Also, sa account does not seems to work for remote access. It is ok when accessing locally.

Any help would be appreciated.

949jc

Hi 959jc,

Have you configured the Windows firewall on your server machine to allow remote connections? If you're intending to use Named Pipes, then you will need to enable the "File and Print sharing" exception. Also, please take a look at this topic in the BOL for additional info regarding configuring firewalls: http://msdn2.microsoft.com/en-us/library/ms175043.aspx.

Another consideration is whether you've restarted your instance after enabling remote protocols.

Otherwise, please provide your connection string and the contents of your error log after you've restarted the service.

Thanks,
Il-Sung.