July 5, 2012 at 4:39 am
We have a job that works most of the time but has been throwing the below error for the past two days. We've seen this error popup on other jobs, but only occasionally, and have yet to figure out what the heck it means.
The error will just randomly stop too, without us having changed anything.
SQL Job Log
Error: 2012-07-04 19:30:16.93Code: 0x00000001
Source: Move files to archive folders
Description: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.DirectoryNotFoundException: Could not find a part of the path.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Move(String sourceFileName, String destFileName)
at ScriptTask_a3933498a8f3487ab11584b394010694.vbproj.ScriptMain.Main()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTATaskScriptingEngine.ExecuteScript()
End Error
Any thoughts on what this is or means? We're running SQL 2008 SP2. We have an application server which runs the package. The package has only 2 ForEach Loop containers, which each contain a script task to move files from one folder to another folder on our NAS share. It's nothing fancy.
It does seem this error pops up only on jobs that touch our NAS, but I can't seem to convince anyone that we might be having a connectivity issue because no one sees the NAS go down. And it's possible I'm wrong.
Thoughts?
July 5, 2012 at 4:50 am
at first look, seems like
the source/destination path issue.
or
the permission issue on folder for the account which is running the job.
----------
Ashish
July 5, 2012 at 6:50 am
Oh good grief. Nevermind.
We're getting a new type of file that hasn't been accounted for. DOH.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply