Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS Environment Reference Id is null


SSIS Environment Reference Id is null

Author
Message
apostolis.karayiannis
apostolis.karayiannis
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 43
Hello

I have created an SSIS package in visual studio 2010 and deployed it at SQL server 2012 by using Integration Services Catalogs. When i run the package at BIDS the package runs succesfully without any problems. When i scheduled the SSIS package to run using a job the execution of the job fails with the following message:

Environment reference Id: NULL. Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Source: .Net SqlClient Data Provider

The job runs for 37 seconds and then fails.

Another issue to mention is that because the job runs for a month now it does not fail all the time but at random intervals for example it may run succesfully from monday till thursday and then fails at friday.

Any clue what may be the cause of failure???

Thank you
Henrik Schütze
Henrik Schütze
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 113
apostolis.karayiannis (1/3/2013)
Hello

I have created an SSIS package in visual studio 2010 and deployed it at SQL server 2012 by using Integration Services Catalogs. When i run the package at BIDS the package runs succesfully without any problems. When i scheduled the SSIS package to run using a job the execution of the job fails with the following message:

Environment reference Id: NULL. Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Source: .Net SqlClient Data Provider

The job runs for 37 seconds and then fails.


Did You log anything? Did you take an trace?
What SSIS Elements you use?
Did the Account the Agent use to execute the Package all the needed rights?
Has the Account the correct drives mapped (if needed)
Did you use an User ODBC Datasource?


apostolis.karayiannis (1/3/2013)

Another issue to mention is that because the job runs for a month now it does not fail all the time but at random intervals for example it may run succesfully from monday till thursday and then fails at friday.

Any clue what may be the cause of failure???


We expect the same, but have no solution for them. Its very sporadic. Sorry.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search