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.

Hi Maneeshb,

it could be just an intermittent lost of connection when accessing file on the network. if you're using sql job, you can go to the steps advanced setting, and set the job to retry 1 more time, with interval 5 minutes... so it will try to run the job again in another 5 minutes without failing the job.

• Proposed as answer by drkusnadi Friday, August 15, 2014 12:28 AM
• Unproposed as answer by Maneeshb Monday, August 18, 2014 1:26 AM

Hello Maneesh,

This could be because of the server unavailability when the job tried accessing it. As @drkusnadi mentioned, you can change the setting to re-run with different interval.

thank you both for the inputs.

As per my analysis ,server has been totally with all continuos pings running to it and no RTOs..that shows network connectivity was there.Also, the sql  job is configured and being run on the same server i.e \\NAMSQLML02..so even if network connectivity is lost it should be able to browse locally on the server and it negates the network part..

Hi ManeeshB,

you can still try to use the retry on the SQL job. or, if you can try change the unc to point directly to the local disk if it's on the same server. d:\SSIStore\BIN\ADataImport.dtsx. or store the package in the SSIS.

thanks drkusnadi,this does work with local disk..but the issue is occuirng when using the unc path...The packages with local disk do not have any issues...Also,,there is a dependey to keep the server name in the path due to which it is being refernced.

can someone please help on this case.

Also,,have noticed..during the issue if connect the server locally via UNC path ..it takes around 30-40 sec for shares to open..but this is the weird thing happening on only this server though if we try to browse from other server(2k8,win7) all seem to open the share hosted on problematic server immediately...

Any idea why locally it might take time to oepn the shares

it again seem to be due to the SMb patch issue on server ..once applied havent seen any issues with shares

Would you mind to elaborate on what was "SMb patch issue"  and how you resolved it? Was there a hot fix or you backed out particulatr MS patch? We have the same problem - random failure of UNC share path access...

Hi Gene,

The issues got fixed after applying following 2 hotfixes..Not sure if these woul be applicable in your case.

http://support.microsoft.com/en-us/kb/2582112
https://support.microsoft.com/en-us/kb/2831154?wa=wsignin1.0