Workflow Soluiton

 View Only

  • 1.  Error Calling Workflow as a Web Service

    Posted Jan 23, 2014 04:46 PM

    I have a workflow setup as follows:

    Web form (feeder) -> Workflow published as a web service with two invocation targets (Model 1, Model 2) and an integration library with the web service call to the workflow. I'm able to call the web service call to Model 1 from the web form without issues but as soon as I put the Model 2 web service component on the form and try to run the project it throws this error. Why is it throwing an error on the Model 2 web service call and not the Model 1? Both have the same input data passed through the models. This is for WF 7.1 SP1.

    Exception Component Class Name: LogicBase.Components.Default.Process.LinkedModelComponent
     
    Exception Component Name: Linked Model - Extension Request
     
    Exception Trigger Component ID: abf4c20a-ded4-41dd-bcc4-4e8387deaaa3
     
    Exception Trigger Exception Class Name: System.Exception
     
    Exception Trigger Message: Could not read in object 
     
    Exception Trigger Stack Trace: System.Exception: Could not read in object ---> System.InvalidOperationException: There is an error in XML document (19830, 45). ---> System.Xml.XmlException: '', hexadecimal value 0x07, is an invalid character. Line 19830, position 45. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar) at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType) at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType) at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos) at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr) at System.Xml.XmlTextReaderImpl.ParseAttributes() at System.Xml.XmlTextReaderImpl.ParseElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlReader.ReadStartElement() at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderObjectStorageContainer.Read4_ObjectStorageObjectData(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderObjectStorageContainer.Read5_ObjectStorageContainer(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderObjectStorageContainer.Read6_ObjectStorageContainer() --- End of inner exception stack trace --- at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader) at LogicBase.Framework.ObjectStorage.Deserialize(FileInfo fromFile) --- End of inner exception stack trace --- at LogicBase.Framework.ObjectStorage.Deserialize(FileInfo fromFile) at LogicBase.Core.AbstractOrchestrationProject.GetComponentModelPrivate(Model model, Type componentModelType) at LogicBase.Core.AbstractOrchestrationProject.GetComponentModel(String name) at LogicBase.Components.Default.Process.LinkedModelComponent.GetTargetComponentModel(IData data) at LogicBase.Components.Default.Process.AbstractLinkedModelComponent.GetStartInstructions(IData parentData) at LogicBase.Core.ExecutionEngine.LinkedModelExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context) at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)

     



  • 2.  RE: Error Calling Workflow as a Web Service

    Posted Mar 27, 2014 10:16 AM

    Just to be sure:

    You set both as invocable? 
    Do they have outputs?
    If so did you set the return types?
    Published the webservice after?
    Updated your webservice integration library and tested each service when prompted?
    Recompiled and Closed?
    No special security on the webservice?
    The webservice runs clean when run manually?

     

    Sounds to me like the webservice is throwing an error and the forms don't know how to handle a 'Symantec Error Page' the same way they handle the normal xml.

     

    Other then that, open a new project and create all the models with inputs and outputs as needed. Don't build out the logic. Create a new integration library and test and then embed in your forms. Test again. Then add the logic to the webservice and republish. 

    Sometimes gremlins get stuck and workflows get corrupted.