Post reply

Error :t" property not set correctly, parameters not set correctly, or connection not established correctly.

  • October 31, 2012 at 7:45 am

    #283849

    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,

  • October 31, 2012 at 7:54 am

    #1554602

    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.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • October 31, 2012 at 8:02 am

    #1554608

    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

  • October 31, 2012 at 10:58 am

    #1554708

    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.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply