Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Environment Reference Id is null Expand / Collapse
Author
Message
Posted Thursday, January 3, 2013 7:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 14, 2014 5:00 AM
Points: 5, Visits: 39
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
Post #1402388
Posted Thursday, January 3, 2013 8:58 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, January 8, 2014 2:44 PM
Points: 18, Visits: 104
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.
Post #1402427
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse