Hi,

I have run exactly into the same error but only after dowloading the recommended updated for the plugins via the notifications (after I upgraded to CU7, there was no error). See detailed log:

<SDLErrorDetails time="11.07.2020 12:32:58">
  <ErrorMessage>Method not found: 'Void NLog.Logger.Error(System.Exception, System.String)'.</ErrorMessage>
  <Exception>
    <Type>System.MissingMethodException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>AppStoreIntegration</Source>
    <HResult>-2146233069</HResult>
    <StackTrace><![CDATA[   at AppStoreIntegration.Service.LocalPlugins.PluginManagementService.GetPluginPackages(String[] pluginPath)
   at AppStoreIntegration.Service.LocalPlugins.PluginManagementService.GetInstalledPlugins(StudioVersion studioVersion)
   at AppStoreIntegration.AppStoreIntegrationInitializer.<OnStudioWindowCreated>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.7.2849</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser></LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName></ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16660708 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

[I have removed my machine and computer name for data protection purposes]

So before I manually do all these exercises with deleting contents of the various SDL directories over and over again, I rather wait for a proper fix for whichever of the plugins is not yet compatible with CU7...

Thanks,

Christine

Christine Bruckner said:

I rather wait for a proper fix for whichever of the plugins is not yet compatible with CU7...

They have all been updated as far as we are aware..

Hi Paul,

on my 2nd computer, I have now runany outstanding plugin updates BEFORE the CU7 upgrade, and got the error immediately after the CU7 installation. If I remember correctly, the outstanding updates affected the appNotifications, TransitPackage Handler and MT Comparision apps.

Thanks,

Christine

Hi Paul,

on my 2nd computer, I have now runany outstanding plugin updates BEFORE the CU7 upgrade, and got the error immediately after the CU7 installation. If I remember correctly, the outstanding updates affected the appNotifications, TransitPackage Handler and MT Comparision apps.

Thanks,

Christine

All of these have been updated Christine. They used to use their own NLog but this was outdated so they were updated to use the version that came with Studio. If you remove all your plugins, and make sure you do this properly from the installed folders too, andthen download and install the latest versions from the appstore you should not have any problems.

If you did then we would get them too... and we don't.

The entire plugin architecture badly needs the appstore integration that we now have with Trados 2021, and they also badly need the core Studio development to stop making changes to things that affect the public API.  So many improvements are going on under the hood it's getting very difficult to maintain so many plugins and have to change them each time we update.  But I'm hopeful these things are all getting better and certainly 2021 is a huge step forward.

Thanks, Paul. But it is not worth while for me to do all these exercises: I have dozens of apps, but hardly use Studio any more (and will therefore not invest in Studio 2021). And as I can make the error disappear with one click, this is the easier option for me. I just thought that if I could provide more details on this error, it might enable SDL to provide a more stable experience for translators who after an upgrade face the same issue, but are really under time-pressure, unlike me ;-)

Cheers,

Christine

Christine Bruckner said:

just thought that if I could provide more details on this error, it might enable SDL to provide a more stable experience for translators who after an upgrade face the same issue

ok - thank you.  The solution is to be using the up to date plugins with the upto date version of Studio.  Nothing specific for SDL to do here because we have already done it.  The problem is users don't get the notifications... and that is something we have changed.

My second Studio installation has now given me an error related to the MT Comparison plugin (which I updated via the appNotifications from my Studio CU7). But maybe it is related to the fact that I had used my usual C:\ProgramData folder for installing apps... Anyway, thanks - and have a nice rest of the weekend!

Cheers,

Christine

Christine Bruckner

Tank you... actually I think you found one we didn't get t yet.  I just saw the developer did this today, we'll test and release the updated version on Monday/Tuesday probably.  Like I said... this is a very long process for us as well so we really don't like having to make all these changes all the time :-(

Hi

I ran into the same problem today after installing CU 7.
Uninstalling the plugin "Appstore Notifications" solved the problem, so there might be an incompatibility between version 1.0.1.6 of this plugin and CU7. I guess this because all other installed plugins are up to date and the previous version of the plugin does not give this error..

I also noticed that since CU7 I do not see the shortcut to "Plugin Management" anymore in the Welcome view.

Walter Blaser

Or update the appnotifications plugin as well. On the plugin management missing... at a guess I'd say this was one of the changes Daniel Brockmann mentioned for CU7 in preparation for 2021... possibly unintentional?

This happened with the latest version of the appnotifications plugin and the problem disappears if one reinstalls the previous version.

Something else must be wrong here Walter.  We all have the latest one and have a lot of plugins installed. None of us are seeing this problem.  I suggest you remove all of your plugins from all locations (properly... so if you don't use the plugin manager make sure you remove the unpacked folders as well), then download and install the latest versions you need from the appstore.

I solved the problem by uninstalling the appnotifications plugin, updating all other plugins and reinstalling version 1.0.1.6 of the appnotifications plugin.