none
SSIS Package Load Error 0xC00160AC

    Question

  • I have an SSIS Package that was running last Friday, Monday it is failing with this error code  0xC00160AC. 

    The sever is 2008 R2 64x and Sql server is Microsoft SQL Server 2008 (SP1) - 10.0.2573.0 (X64)   

    After research, the error appears to be related running 2005 package in 2008, but it was running in 2008 when it was working.  

    I have not been able to find much on this error, any suggestions would be greatly appreciated.

    Thanks

    Tim

     

    Here is the error:

    Executed as user: ATLAS\mas500Admin. Microsoft (R) SQL Server Execute Package Utility  Version 10.0.5500.0 for 32-bit  

    Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    

    Started:  2:16:30 PM  

    Could not load package "\MSDB\Sage MAS 500\Sage MAS 500 mas500_app_FAST Fast_Imp_CADXL" because of error 0xC00160AC.  

    Description: No description found  

     

    Source:   Started:  2:16:30 PM  Finished: 2:16:30 PM  Elapsed:  0.031 seconds.  The package could not be loaded.

    Monday, February 6, 2012 10:05 PM

Answers

  • Solved at last!


    Should anyone run into this problem, the resolution is to reinstall SSIS.  Not being the dba, I was not in a position to do this, but once done, all was well.  


    Thanks for all the responses.  

    Tim

    • Marked as answer by tconway Tuesday, February 14, 2012 3:52 PM
    Tuesday, February 14, 2012 3:52 PM

All replies

  • Did something change over the weekend? Permissions that were altered?

    Does the ATLAS\mas500Admin have access to the MSDB database?


    MCTS, MCITP - Please mark posts as answered where appropriate.
    Answer #1: Have you tried turning it off and on again?
    Answer #2: It depends...

    Tuesday, February 7, 2012 8:31 AM
  • Thanks for responding Koen.  

    I checked with IT and some MS Updates ran over the weekend and he rolled them back, I'm about to test again now.  

    On the second question, Mas500Admin always has for the past year or so.  But did something change on that over the weekend, I'll check that too.

    The thing is, none of the SSIS Packages run now, all have the same error.  

    I'll see what I find out.  

    Thanks

    Tim  

    Tuesday, February 7, 2012 3:06 PM
  • Hi Tim,

    According to the error code, 0xC00160AC error could be DTS_E_CONNECTTOSERVERFAILED_NOTREGISTERED . I am not sure if you had applied those workarounds mentioned by http://support.microsoft.com/kb/2466166 before. Please check it first.

    Please feel free to ask if you have any question.

    Thanks,
    Eileen
    • Edited by Eileen Zhao Thursday, February 9, 2012 2:31 PM
    Thursday, February 9, 2012 2:26 PM
  • Thanks for the response Eileen.  I tried workaroun 2, but 1, istalling 2005 SSIS has to wait for the IT dept.  

    Still not working, but what is puzzling is the error points to 2005 / 2008 conflict, yet it has run all along, then suddenly everything stopped working.  It has always been 2008 and has worked for about a year.  Still stuck

    Thanks

    Tim

    Thursday, February 9, 2012 7:21 PM
  • Tim, how about you just upgrade the package to SSIS 2008 offline.

    Then remove the existing one, and place the new in?


    Arthur My Blog

    Thursday, February 9, 2012 8:29 PM
    Moderator
  • Solved at last!


    Should anyone run into this problem, the resolution is to reinstall SSIS.  Not being the dba, I was not in a position to do this, but once done, all was well.  


    Thanks for all the responses.  

    Tim

    • Marked as answer by tconway Tuesday, February 14, 2012 3:52 PM
    Tuesday, February 14, 2012 3:52 PM