No log of known format is detected

[ianrego]

Can you write some debug output to be able to debug issues like these when trying to opening files?

The following file works in some machines but not in others among different peers I have:

app_process32.msrtc-0-s2696500524.blog.zip

[sergey-su]

Try using debug logging into lj-debug.log by adding the following to logjoint.exe.config that resides next to the logjoint.exe

<configuration>
  <system.diagnostics>
    <sharedListeners>
      <add name="file" type="LogJoint.TraceListener, logjoint.model" initializeData="lj-debug.log;membuf=1" traceOutputOptions="DateTime, ThreadId"></add>
    </sharedListeners>
...

I suspect the difference between machines is in the list of recent log types that have been open on a machine. When auto-detecting log format logjoint tries most recently used formats first. Try deleting the recent factories cache that may look like that
c:\Users<username>\AppData\Roaming\LogJoint\e-E7FFECFD5A7308D0-global\x-2E24B3FA9320E2B3-recent-factories.

Also verify that the definition for the desired format is present in Formats folder, that also resides next to the executable.

[ianrego]

[lj-debug.zip](https://github.com/sergey-su/logjoint/files/7060369/lj-debug.zip) Hi Sergey-Su/Logjoint Thanks for looking into this. Here are the logs. It looks like I'm missing some plugins. I did try to reinstall and found that there is some problem getting the repository of dlls from blob.db3prdstr11a.store.core.windows.net. I'm not sure if its a connectivity or a repository issue. I've had someone else try the install from a different site and PC non-domain and they have the same issue. Could you check the repository and logs?

…

On Sat, Aug 21, 2021 at 3:16 PM SergeyS ***@***.***> wrote: Try using debug logging into lj-debug.log by adding the following to logjoint.exe.config that resides next to the logjoint.exe <configuration> <system.diagnostics> <sharedListeners> <add name="file" type="LogJoint.TraceListener, logjoint.model" initializeData="lj-debug.log;membuf=1" traceOutputOptions="DateTime, ThreadId"></add> </sharedListeners> ... I suspect the difference between machines is in the list of recent log types that have been open on a machine. When auto-detecting log format logjoint tries most recently used formats first. Try deleting the recent factories cache that may look like that c:\Users<username>\AppData\Roaming\LogJoint\e-E7FFECFD5A7308D0-global\x-2E24B3FA9320E2B3-recent-factories. Also verify that the definition for the desired format is present in Formats folder, that also resides next to the executable. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATZUNIFWBKWGX5K5FVDBXBDT573R3ANCNFSM5CKQAN2A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[sergey-su]

Your installation lacks required plugins indeed. I guess you installed it from the homepage https://github.com/sergey-su/logjoint, but you probably want to install a private MSFT build. MSFT has a fork of logjoint that adds a private plugin. As I no longer work in MSFT, I can not give you up to date instructions. You can probably copy the folder with the binaries (where logjoint.exe resides) as is from a colleague who has the right version capable of opening your blog file. Logjoint supports x-copy installation, and will be able to update itself even if installed by copying from someone else. Maybe you can ask for installation instruction from David Zhao who was the one whom I transferred the knowledge before leaving MSFT 3yrs ago.

[ianrego]

Thank you for the clarification! There are many David Zhaos' in the community, could you specify his alias?

[sergey-su]

https://www.linkedin.com/in/drdavidzhao/. Sorry, don't remember the alias.