4 Replies Latest reply: Oct 2, 2014 6:54 AM by Nisha Nangalia RSS

    Trigger task not found

    Nisha Nangalia

      Hello All,

       

      The scheduled trigger task runs at times and sometimes does not trigger at all. Also the scheduled on event trigger reload job does not run at all even on completion of the job. Sometimes even manually starting the job does not seem to work.

       

      Has somebody encountered issue like this before. Please provide the solution which worked.

       

       

      Error in QMC.log

       

      10/1/2014 04:15:13.9233153 Error System.ServiceModel.CommunicationException: QDS did not respond to request.

      Last exception (for http://fihel1-s5262:4720/QDS/Service): The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://ws.qliktech.com/QDS/11/:GetTaskLogResult. The InnerException message was 'There was an error deserializing the object of type System.Collections.Generic.List`1[[SolutionGlobal.Logging.LogfileEntry, SolutionGlobal, Version=11.20.12354.0, Culture=neutral, PublicKeyToken=null]]. The 'maximum bytes per Read operation' quota (4096) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 39275.'.  Please see InnerException for more details. ---> System.ServiceModel.Dispatcher.NetDispatcherFaultException: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://ws.qliktech.com/QDS/11/:GetTaskLogResult. The InnerException message was 'There was an error deserializing the object of type System.Collections.Generic.List`1[[SolutionGlobal.Logging.LogfileEntry, SolutionGlobal, Version=11.20.12354.0, Culture=neutral, PublicKeyToken=null]]. The 'maximum bytes per Read operation' quota (4096) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 39275.'.  Please see InnerException for more details. ---> System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type System.Collections.Generic.List`1[[SolutionGlobal.Logging.LogfileEntry, SolutionGlobal, Version=11.20.12354.0, Culture=neutral, PublicKeyToken=null]]. The 'maximum bytes per Read operation' quota (4096) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 39275. ---> System.Xml.XmlException: The 'maximum bytes per Read operation' quota (4096) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 39275.

         at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)

         at System.Xml.XmlExceptionHelper.ThrowMaxBytesPerReadExceeded(XmlDictionaryReader reader, Int32 maxBytesPerRead)

         at System.Xml.XmlUTF8TextReader.ReadAttributes()

         at System.Xml.XmlUTF8TextReader.ReadStartElement()

         at System.Xml.XmlUTF8TextReader.Read()

         at System.Xml.XmlReader.ReadToFollowing(String name)

         at SolutionGlobal.Logging.LogfileEntry.ReadXml(XmlReader reader)

         at System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadIXmlSerializable(XmlSerializableReader xmlSerializableReader, XmlReaderDelegator xmlReader, XmlDataContract xmlDataContract, Boolean isMemberType)

         at System.Runtime.Serialization.XmlDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)

         at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)

         at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)

         at ReadArrayOfLogfileEntryFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString , XmlDictionaryString , CollectionDataContract )

         at System.Runtime.Serialization.CollectionDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)

         at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)

         at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)

         at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

         at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

         --- End of inner exception stack trace ---

         at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

         at System.Runtime.Serialization.DataContractSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)

         at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part, Boolean isRequest)

         --- End of inner exception stack trace ---

       

      Regards,
      Nisha

        • Re: Trigger task not found
          Peter Cammaert

          Seems like an internal QDS error. This text explains the error message you posted.

           

          The 'maximum bytes per Read operation' quota (4096) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader.

           

          However QlikView Server is very verbose and in the end the novels we get to read may have nothing to do with the actual problem. Do the tasks pass a lot of parameters to the QlikView models to be reloaded? Is there a document log for the failed reloads?

           

          Best,

           

          Peter

            • Re: Trigger task not found
              Nisha Nangalia

              Hello Peter,

               

              Thanks  for the reply.

               

              No task does not pass parameters. There is no trace of the jobs which are not triggered as per the schedule.

              Its sporadic sometimes they trigger sometimes we see the error the trigger task not found( task id - some alphnumeric string)

               

              Some times even manually starting the task do not work. We are currently on Qlikview 11 -SR6 planning to upgrade it to SR8 to see if that helps.

               

              I was doubtful if the configuration file could be messed up/corrupted due to some reason.

              We have even opened this case with qlik support still torubleshooting.

               

              Also is there any limitation on number of task in QMC ?

               

              Regards,

              Nisha

                • Re: Trigger task not found
                  Peter Cammaert

                  No there is no limit on the number of tasks you can define. However, only a limited set of reload engines can be launched in parallel. See QMC->System->Distribution Service->Advanced->QlikView Engine (assuming you have a Publisher) Any more will be queued until a Reload engine becomes available.

                   

                  Best,

                   

                  Peter

                    • Re: Trigger task not found
                      Nisha Nangalia

                      Hello Peter,

                       

                      I meant the total number of jobs which can be hosted on publisher. Some where is in the community some one has stated 70. But we might have even more to it.

                       

                      Yes we have a publisher and has set this limit to 12 - we have a clustered environment.

                       

                      Regards,
                      Nish