The Welkin Suite Forum

Opening a log file, error: Can not parse 'CODE_UNIT_STARTED' with 6 arguments



Opening a log file, error: Can not parse 'CODE_UNIT_STARTED' with 6 arguments

  • Please log in to reply

#1
windows version welkinsuite

gtasker

    Posted 05 Jun 2018 and edited 07 Jun 2018

    After running a test, and having it fail, I try to open the log file to view it in TWS.  I get a popup message telling me an exception has been encountered, check the log file. Here are the three entries in the log file that were recorded:

     NOTE: This was with Bloom R17.  Apparently the updater did not detect a newer version when you released R18.  Installing that now, will re-test

    <entry>
    <record>369</record>
    <time>2018/06/05 11:20:09.281</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Entering function CVsPackageInfo::HrInstantiatePackage</description>
    <guid>{87569308-4813-40A0-9CD0-D7A30838CA3F}</guid>
    </entry>
    <entry>
    <record>370</record>
    <time>2018/06/05 11:20:09.282</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Begin package load [Visual Studio XML Editor Package]</description>
    <guid>{87569308-4813-40A0-9CD0-D7A30838CA3F}</guid>
    </entry>
    <entry>
    <record>371</record>
    <time>2018/06/05 11:20:11.447</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>End package load [Visual Studio XML Editor Package]</description>
    <guid>{87569308-4813-40A0-9CD0-D7A30838CA3F}</guid>
    </entry>
    <entry>
    <record>372</record>
    <time>2018/06/05 11:20:22.741</time>
    <type>Error</type>
    <source>Editor or Editor Extension</source>
    <description>WelkinSuite.Common.Extensions.NotParsedLogEventTypeException: Can not parse &apos;CODE_UNIT_STARTED&apos; with 6 arguments. Log event parameters: &apos;01qb00000006LHN|nisvc_Opportunity on Opportunity trigger event BeforeInsert|__sfdc_trigger/nisvc_Opportunity&apos;&#x000A;Original message: &apos;Value does not fall within the expected range.&apos;&#x000D;&#x000A; at WelkinSuite.ApexLogParser.Implementation.LogEntryFactory.CreateLogEntry(String rawText, Int32 logLineNumber)&#x000D;&#x000A; at WelkinSuite.ApexLogParser.Implementation.ApexLogParser.ParseLogEntry(String logEntryText, Int32 logLineNumber)&#x000D;&#x000A; at WelkinSuite.EditorExtensions.ApexLogs.Classifier.ApexLogsClassifier.GetClassificationSpans(SnapshotSpan span)&#x000D;&#x000A; at Microsoft.VisualStudio.Text.Classification.Implementation.ClassifierTagger.&lt;GetTags&gt;d__0.MoveNext()&#x000D;&#x000A; at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.&lt;GetTagsForBuffer&gt;d__5.MoveNext()</description>
    </entry>



    2 replies to this topic

    #2

    gtasker

      Posted 05 Jun 2018

      With R18, this error no longer occurs.  Log opens correctly



      #3

      kate.dulko

        Posted 07 Jun 2018

        Hi George,


        Thank you for your post and for the update.


        The issue was caused by some changes from the latest Summer'18 Salesforce version - for example, there is an updated structure of log files and the list of variables.

        As you could see, we have implemented the necessary changes in the Bloom R18 version of the IDE so that you could work with new logs as well with log files from an environment which are not moved to the Summer'18 Salesforce version.


        If you would have any other questions, please let us know.


        Regards,

        Kate


        Kate Dulko
        Customer Relations

        The Welkin Suite

        twitter: @KateDulko
        skype id: d_katerina
        e-mail: kate.dulko@welkinsuite.com

         

          





        Boost Your Productivity. Get Started Today

        Try Free Trial