Workflow Soluiton

Dear All,

I am using a Workflow to read a file (\\DEVSERVER\Import$\FileImport.csv) and I am getting an error in debug (which is as far as I have got):

Execute Time (ms): 8934
System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Execution Engine Exception  ---> System.Exception: Execution Exception ---> System.Exception: exception component created:  ---> LogicBase.Framework.BusinessRuleException: The critical error failed execution on component Read File : Error reading file: \DEVSERVER\Import$\FileImport.csv. : at LogicBase.Components.Default.IO.ReadFile.Run(IData data) at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context) at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.ExceptionComponentDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.ExecuteComponent(IData data, IOrchestrationComponent component)
   at LogicBase.Core.Models.Workflow.WorkflowExecutionEngine.StartInternalWithProcessIDReturn(IData data, String modelName, IData globalData, String testRunId, TestingScenario testingScenario)
   at LogicBase.Core.Models.Workflow.WorkflowExecutionEngine.Start(IData data, String modelName)
   at Default.DeploySoftware.DeploySoftwareExecute()
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at DeploySoftware.DeploySoftwareExecute()
   --- End of inner exception stack trace ---
   at LogicBase.Framework.DynamicProxy.InvokeMethod(String MethodName, Object[] parameters)
   at LogicBase.Tool.UI.Debugging.DebugEngine.ExecuteMethodThreadStart(Object parameter)

I have set the security to Everyone Read permission on Share and Security. I am using a File Exists component beforehand, so it exists and I am not using the file anywhere else:

Kindest regards,

QuietLeni

Do you get similar results when you browse using the IP of BUILDSERVER (i.e \\xxx.xxx.xxx.xxx\Import$\FileImport.csv)?

Try mapping that path to a drive and navigating to it via the mapped drive.

Just some things to try.

reecardo,

Yes, I get the same result:

Execute Time (ms): 23223
System.Exception: exception invoking method ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Execution Engine Exception  ---> System.Exception: Execution Exception ---> System.Exception: exception component created:  ---> LogicBase.Framework.BusinessRuleException: The critical error failed execution on component Read File : Error reading file: \192.168.115.245\Import$\FileImport.csv. : at LogicBase.Components.Default.IO.ReadFile.Run(IData data) at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context) at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.ExceptionComponentDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)
   --- End of inner exception stack trace ---
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)
   at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.ExecuteComponent(IData data, IOrchestrationComponent component)
   at LogicBase.Core.Models.Workflow.WorkflowExecutionEngine.StartInternalWithProcessIDReturn(IData data, String modelName, IData globalData, String testRunId, TestingScenario testingScenario)
   at LogicBase.Core.Models.Workflow.WorkflowExecutionEngine.Start(IData data, String modelName)
   at Default.DeploySoftware.DeploySoftwareExecute()
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at DeploySoftware.DeploySoftwareExecute()
   --- End of inner exception stack trace ---
   at LogicBase.Framework.DynamicProxy.InvokeMethod(String MethodName, Object[] parameters)
   at LogicBase.Tool.UI.Debugging.DebugEngine.ExecuteMethodThreadStart(Object parameter)

Note, however, that the error message says \192.168.115.245\Import$\FileImport.csv and seems to omit the first slash in the UNC path. Is that a bug?

Kindest regards,

QuietLeni

Ugh, this looks like a wierd bug...

try putting 3 slashes at the front of the path vs. 2  i.e. \\\BUILDSERVER\...

reecardo,

I tried using C:\Import$\FileImport.csv and it worked, but I need to use UNCs...

I also tried using  \\\192.168.115.245\Import$\FileImport.csv and this seems to work as well!

That is weird. Using WF 7.1 SP2. I think that this is a bug.

Kindest regards,

QuietLeni

You're right, it is. I've fixed it in our trunk in the past few minutes. Thanks for finding this.

It seems to have been this way for quite a while (stripping off a leading \ if it begins with 2 slashes)... for whatever reason.

reecardo,

So, what I did was to look at the first character in the UNC and and if it is a \, then put another one on, otherwise, do not touch it. A little fudge.

Kindest regards,

QuietLeni