SSIS job fails intermittently only on production.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • HiGu
    New Member
    • Feb 2012
    • 99

    SSIS job fails intermittently only on production.

    OnError,__SEQ Insert ETL Logic Here,{795D68BF-C348-4D7E-87BC-756EC7552FBB},{ D3AF4786-E01E-43CC-B57D-BD3D05491B5D},1 5/05/2012 13:25:13,15/05/2012 13:25:13,-1073450952,0x,S SIS Error Code DTS_E_PRIMEOUTP UTFAILED. The PrimeOutput method on component "SCR_SRC Get Equipment" (1) returned error code 0x80004003. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

    OnError,{C5BFEA 73-95D1-4FF2-9CF6-B7A3421D2A89},{ 7EA81E6C-D917-4DA5-B86C-77005C89E5F8},1 5/05/2012 13:30:06,15/05/2012 13:30:06,-1073450910,0x,S ystem.NullRefer enceException: Object reference not set to an instance of an object

    This package fails intermittently on Productionn server while it runs successfully on other environments.It s sql server 2005. __SEQ Insert ETL Logic Here is the name of the container.There are no webservices used for the package.However , there is a reference of OSISOFT PI in one of the scripts.
  • Rabbit
    Recognized Expert MVP
    • Jan 2007
    • 12517

    #2
    It would help to know what the package does. And specifically, which task failed and what that does.

    Comment

    • HiGu
      New Member
      • Feb 2012
      • 99

      #3
      Originally posted by Rabbit
      It would help to know what the package does. And specifically, which task failed and what that does.
      Let me attach a file that would give you more info.

      Comment

      • Rabbit
        Recognized Expert MVP
        • Jan 2007
        • 12517

        #4
        I don't have office 2007. I can't open that. Just put the relevant information in the post.

        Comment

        • HiGu
          New Member
          • Feb 2012
          • 99

          #5
          This package performs the following:
          1. Synchronises NotificationCom mentStore DB with AF2 for keeping NotificationCom mentStore (a sql server 2005 DataBase) up to date. This Package fetches all the wells and equipments from AF2 (i.e. PI Asset framework) and stores the well data in WellFilter table, equipment data in EquipmentFilter s table. This tables are then used to relate wells belonging to respective Area and fields in order to display alerts for wells.

          Comment

          • Rabbit
            Recognized Expert MVP
            • Jan 2007
            • 12517

            #6
            What are the rest of the error messages? The one you posted is a generic message and is usually accompanied by other more detailed messages.

            Comment

            • HiGu
              New Member
              • Feb 2012
              • 99

              #7
              There are other similar errors.

              Comment

              • HiGu
                New Member
                • Feb 2012
                • 99

                #8
                I found this warning (not an error) in the package. Can this create a problem in running the job?

                Warning 1 Warning loading AfToNotificatio nCommentStore.d tsx: The configuration environment variable was not found. The environment variable was: "ETLFramework.C onnectionManage r.NotificationC ommentStore". This occurs when a package specifies an environment variable for a configuration setting but it cannot be found. Check the configurations collection in the package and verify that the specified environment variable is available and valid

                Comment

                • Rabbit
                  Recognized Expert MVP
                  • Jan 2007
                  • 12517

                  #9
                  None of those messages are very helpful and there's too much code to look through. Try setting up break points and stepping through the code to find the line that's causing the error.

                  Comment

                  • HiGu
                    New Member
                    • Feb 2012
                    • 99

                    #10
                    Hey.I got the problem. The source has some new data in it which is null and the destination table does not allow any null value.
                    The issue is now resolved.

                    Comment

                    Working...