Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Random errors executing SSIS in SQL 2008 R2

$
0
0

hello All,

I have a issue occuring in one of my SQL boxes in which randomly we will get errors  while running the SSIS jobs.Mostly,the jobs would run fine but sometime it happens in couple of weeks or once a month.the job would fail with below error .

Our infra:

OS:windows 2008 r2 SP1

SQL:windows 2008 R2 SP2 Ent

Could not find any specific issues in eventlogs or server.The network connections are all good..Could someone please point me to correct direction where i can have this issue rectified.

Error Message:::---->

Message
Executed as user: NAM\sysglobalsqa1. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4000.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  13:32:00 PM  Error: 2014-08-12 13:33:03.66     Code: 0xC0011007     Source: {C9CA54E6-6247-484D-B25C-95B946931E51}      Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.  End Error  Error: 2014-08-12 13:33:03.66     Code: 0xC0011002     Source: {C9CA54E6-6247-484D-B25C-95B946931E51}      Description: Failed to open package file "\\NAMSQLML02\SSIStore\BIN\ADataImport.dtsx" due to error 0x80070040 "The specified network name is no longer available.".  This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.  End Error  Could not load package "\\NAMSQLML02\SSIStore\BIN\ADataImport.dtsx" because of error 0xC0011002.  Description: Failed to open package file "\\NAMSQLML02\SSIStore\BIN\ADataImport.dtsx" due to error 0x80070040 "The specified network name is no longer available.".  This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.  Source: {C9CA54E6-6247-484D-B25C-95B946931E51}  Started:  13:32:00 PM  Finished: 13:33:03 PM  Elapsed:  63.43 seconds.  The package could not be found.  The step failed.


ManeeshB


Viewing all articles
Browse latest Browse all 24688

Trending Articles