Error SSIS 1

[Schewns]

Hello,
i'm kind of new to the SSIS programming, and i'm having some problems deploying a SSIS package.i'm a bit desperate...
So this package runs correctly in my pc, does everything it needs to do... but when i deploys it doenst even find the connections strings.
Here is the error:

Code: 0xC001000E
Source:
Description: The connection "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" is not found.
This error is thrown by Connections collection when the specific connection element is not found.
End Error

Error: 2012-08-09 00:21:06.25
Code: 0xC001000E
Source: Package
Description: The connection "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" is not found.
This error is thrown by Connections collection when the specific connection element is not found.
End Error

Error: 2012-08-09 00:21:06.25
Code: 0xC001000E
Source: Package
Description: The connection "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" is not found.
This error is thrown by Connections collection when the specific connection element is not found.
End Error

Error: 2012-08-09 00:21:06.25
Code: 0xC00291EB
Source: Execute SQL Task Execute SQL Task
Description: Connection manager "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" does not exist.
End Error

Error: 2012-08-09 00:21:06.25
Code: 0xC0024107
Source: Execute SQL Task
Description: There were errors during task validation.
End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 00:21:04 Finished: 00:21:06 Elapsed: 1.888 seconds.
The package execution failed. The step failed.

Can anyone help me? i would be forever grateful.
thanks in advance

 

[SQLBill]

Some things to check:

1. does the account the package is running under have access?
2. are you using SSIS Configuration to set the connections? If so, where is that table located at - the server where you deployed it or is it still on your local computer?

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[Schewns]

Hi Bill,

For what i checked, the account has the permissions.

now the SSIS Configuration, i'm sorry if it's a stupid question, i red a lot about the config file, but i don't have any, all the configurations i used where or in the package itself, or in the command line in the "Job"->"Step" window.

if it's not this can u enlighten me on what i have to do?
thanks in advance

 

[Schewns]

now the SSIS Configuration, i'm sorry if it's a stupid question, i read a lot about the config file, but i don't have any, all the configurations i am using are or in the package itself, or in the command line in the "Job"->"Step" window.

if it's not this can u enlighten me on what i have to do?
thanks in advance"

correcting my english sorry for that

 

[SQLBill]

I don't do much with SSIS myself. But to use SSIS Configurations, you would create a table in an existing database or a separate database. The table would be called SSISConfigurations or something similar to that.

You create the package, click in the package window, then on the menu bar select SSIS>Package Configurations Organizer. Check the box for Enable package configuration. Then click Add and follow the prompts.

I would check your current configurations and test the connections from the server the package is really running on. Also, double check that the login running it has the appropriate permissions.

First, remote into the server, open the package in BIDS and run it manually. Do you get the errors?
If not, then the error is coming from the job. Jobs are set up with the ability to change 'who' they run as. Normally, the default is to run under the service account that SQL Server Agent service uses. Check the job step that runs the SSIS package....what account is listed as Run as:? That account needs to have access to all the folders, files, databases, tables, that the package is using.

-SQLBill


The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[Schewns]

SQLBill thanks a lot for the help, it was crucial!
i solved the problem, it was a problem first with the premissions i had in the machine.
after having the necessary permissions i also noticed that i couldn't change the name of the connection string like i was doing; so i installed a new instance of sql server pointing to the (local) and compiled the ssis package with this new connection and it worked.
thanks a lot for your help it was awesome