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

Error :t" property not set correctly, parameters not set correctly, or connection not established correctly. Expand / Collapse
Author
Message
Posted Wednesday, October 31, 2012 7:45 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, November 5, 2012 7:17 AM
Points: 54, Visits: 136
I have an SSIS job running in production.The job failed today with an error message

Executed as user: Test\SQLService. t" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:00:00 AM Finished: 7:07:10 AM Elapsed: 429.875 seconds. The package execution failed. The step failed.

No changes have been made to the package .Please help what could be the reason for the failure


Thanks,
Post #1379309
Posted Wednesday, October 31, 2012 7:54 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 4:51 AM
Points: 5,097, Visits: 11,896
Pink123 (10/31/2012)
I have an SSIS job running in production.The job failed today with an error message

Executed as user: Test\SQLService. t" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:00:00 AM Finished: 7:07:10 AM Elapsed: 429.875 seconds. The package execution failed. The step failed.

No changes have been made to the package .Please help what could be the reason for the failure


Thanks,


Strange error. Has anything changed in the enviroment? New server, decommissioned server, o/s upgrade, SQL Server upgrade etc etc?

Does the job contain only one step? I'm just wondering why it took seven minutes to fail if it is the only thing in the package.

Have you tried running the package again since (if you can)? Would be interesting to know whether it is a transient error.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1379318
Posted Wednesday, October 31, 2012 8:02 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, November 5, 2012 7:17 AM
Points: 54, Visits: 136
nothing has changed .Its not just one step but job executes around 40 queries .
I have not tried to rerun since its production,it runs everyday at 7 am so will have to wait
is that there is some parameter t" is passed which should not have ?
There are other jobs which run on the same server and ran sucessfully
Post #1379324
Posted Wednesday, October 31, 2012 10:58 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, June 27, 2014 2:05 PM
Points: 287, Visits: 810
I'd look at the job step carefully as maybe someone accidentally made a change to T.

You also might consider running it via command line. Sometimes just looking at what it is trying to execute can give you the answer, and if not, maybe you'll get a more exact description of the problem.
Post #1379442
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse