Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Issue C1 20.0.2 and Open With plugin

pgrat
Hi,
installed last evening, version 20.0.2 brings a issue with the Open With plugin which cannot initialize and is declared disabled. This issue prohibits the use of the "Open with" and "Edit with" functions.
A reinstall did not change anything.
I send a request to the support currently without response (it was not the usual).
Win 10 Home 1909.
0

Comments

81 comments

Date Votes
  • pgrat
    • Edited

    Hi Patrick,
    no change! The plugin remains inactive from 20.0.2 to 20.0.4 ... and I'm back to 20.0.0 !
    I slowly come back to LR + Iridient N-transformer ... with a good dcp profile (not from Adobe), it works fine !

    I've just seen that my request has been considered resolved!
    That's showing a bit of flippancy since the issue persists and no information has reached me from the development team!

    2
  • pgrat

    Hi there,
    the version 20.0.3 has just been released but unfortunately, the bug "open with" plugin is still present!
    What was the use of reporting this bug to the support when the version 20.0.2 was released  more than a month ago?
    For information, the support sent me an email 20 days after my bug report to tell me that it was transmitting to the development team !! A joke !
    I am still forced to stay at version 20.0.0 and no matter what new cameras are supported.
    I'm starting to be really disappointed with Capture One.

    1
  • Samoreen

    > @SFA, you are lucky !

    Lucky ? Not half ! SFA is a happiness spitting machine. Never hit by a bug, always happy with whatever version of C1 he gets, always finding good excuses for P1 not doing the job... I'm envious :--)) .

    1
  • Epipactis
    • Edited

    > For me :

    20.0.2 does not work,

    20.0.3 does not work

    only 20.0.0 works fine.

     

    Same for me. It's a SHAME that they did not address this major bug ! Will they ever take it into account ?

    1
  • Epipactis

    Grant

    Thank you for trying to help but the problem is not as you say in your post : it is not a matter of program icon not found.

    It is a problem of cast, as you can see in pgrat's log in page 1 of this thread. I reproduce hereunder the end of the log :

    [2020-01-28 09:07:13.059][051][ID:001, ]{PLUG } | Discovery OK
    [2020-01-28 09:07:13.060][000][ID:001, ]{PLUG } | Creating a new instance...
    [2020-01-28 09:07:13.626][566][ID:001, ]{PLUG } | Exception of Type : System.Reflection.TargetInvocationException
    **| Message : Une exception a été levée par la cible d'un appel.
    [2020-01-28 09:07:13.626][000][ID:001, ]{PLUG } | Exception of Type : System.InvalidCastException
    **| Message : Impossible d'effectuer un cast d'un objet de type 'System.String[]' en type 'System.String'.
    [2020-01-28 09:07:13.626][000][ID:001, ]{PLUG } | Plugin exiting

    I have the same exceptions (with both V20.0.2 and V20.0.3) and it's up to Phase One to fix this problem !

    1
  • Samoreen

    > I have the same exceptions (with both V20.0.2 and V20.0.3) and it's up to Phase One to fix this problem !

    Correct. As I have already stated, this a programming error. A bug.

     

    1
  • NNN634411414117438868

    I have the same proble with version 20.0.2 and 20.0.3

    [2020-03-02 21:56:03.747][000][ID:001, ]{APPL } | Application started, version PluginHost 1.0 - Located at: C:\Program Files\Phase One\Capture One 20.0.3\P1.C1.PluginHostProcess.exe
    [2020-03-02 21:56:03.747][000][ID:001, ]{APPL } | Running on Microsoft Windows NT 6.2.9200.0
    [2020-03-02 21:56:03.756][008][ID:001, ]{PLUG } | InitializationStarting
    [2020-03-02 21:56:03.759][003][ID:001, ]{LOG } | Log file initialized.
    [2020-03-02 21:56:03.759][000][ID:001, ]{PLUG } | Parameters: C:\Program Files\Phase One\Capture One 20.0.3\Plugins\OpenWith BuiltInOpenWithPlugin com.phaseone.openwith
    [2020-03-02 21:56:03.763][003][ID:001, ]{PLUG } | Discovering...
    [2020-03-02 21:56:03.764][000][ID:001, ]{PLUG } | Discovering from path: C:\Program Files\Phase One\Capture One 20.0.3\Plugins\OpenWith with entry point: BuiltInOpenWithPlugin
    [2020-03-02 21:56:03.764][000][ID:001, ]{PLUG } | Dlls discovered: C:\Program Files\Phase One\Capture One 20.0.3\Plugins\OpenWith\OpenWithPlugin.dll C:\Program Files\Phase One\Capture One 20.0.3\Plugins\OpenWith\P1.C1.Localization.dll
    [2020-03-02 21:56:03.779][015][ID:001, ]{PLUG } | Discovery OK
    [2020-03-02 21:56:03.779][000][ID:001, ]{PLUG } | Creating a new instance...
    [2020-03-02 21:56:04.157][377][ID:001, ]{PLUG } | Exception of Type : System.Reflection.TargetInvocationException
    **| Message : Se produjo una excepción en el destino de la invocación.
    [2020-03-02 21:56:04.157][000][ID:001, ]{PLUG } | Exception of Type : System.InvalidCastException
    **| Message : No se puede convertir un objeto de tipo 'System.String[]' al tipo 'System.String'.
    [2020-03-02 21:56:04.157][000][ID:001, ]{PLUG } | Plugin exiting

    1
  • Mike Watson

    Hi,

    Decided to give 20.0.3 a go and save the log files.  As others it failed again.

    Plugin log file for working 20.0.0

    Application started, version PluginHost 1.0 - Located at: C:\Program Files\Phase One\Capture One 20\P1.C1.PluginHostProcess.exe
    Running on Microsoft Windows NT 6.2.9200.0
    InitializationStarting
    Log file initialized.
    Parameters: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith BuiltInOpenWithPlugin com.phaseone.openwith
    Discovering...
    Discovering from path: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith with entry point: BuiltInOpenWithPlugin
    Dlls discovered: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\OpenWithPlugin.dll C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\P1.C1.Localization.dll
    Discovery OK
    Creating a new instance...
    Starting service...
    Adding host at: net.pipe://localhost/PhaseOne/Plugins/com.phaseone.openwith/P1.C1.Plugins.Common.Wcf.IPluginHostOpenWith
    Adding host at: net.pipe://localhost/PhaseOne/Plugins/com.phaseone.openwith/P1.C1.Plugins.Common.Wcf.IPluginHostSettings
    Service started...
    Plugin initialization completed

     

     

    and for the failing 20.0.3

    } | Application started, version PluginHost 1.0 - Located at: C:\Program Files\Phase One\Capture One 20\P1.C1.PluginHostProcess.exe
    } | Running on Microsoft Windows NT 6.2.9200.0
    } | InitializationStarting
    } | Log file initialized.
    } | Parameters: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith BuiltInOpenWithPlugin com.phaseone.openwith
    } | Discovering...
    } | Discovering from path: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith with entry point: BuiltInOpenWithPlugin
    } | Dlls discovered: C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\OpenWithPlugin.dll C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\P1.C1.Localization.dll
    } | Discovery OK
    } | Creating a new instance...
    } | Exception of Type : System.Reflection.TargetInvocationException
    **| Message : Exception has been thrown by the target of an invocation.
    } | Exception of Type : System.InvalidCastException
    **| Message : Unable to cast object of type 'System.String[]' to type 'System.String'.
    } | Plugin exiting

     

    ---------------------------------

    This appears to be the same failure that was logged (in Spanish) on a previous post that during the creating of a new instance of the service a change has been made to cause the

    Unable to cast object of type 'System.String[]' to type 'System.String'.

    failure.

     

     

    Continuing investiagtion...!

     

     

     

     

    1
  • Samoreen

    } | Exception of Type : System.InvalidCastException
    **| Message : Unable to cast object of type 'System.String[]' to type 'System.String'.

    There's nothing that anyone of us can do about this. This kind of message clearly denotes a programming error, in that case a confusion between a string (array of characters) and a string table (a table of arrays of characters). Something like confusing an apple with a crate of apples.

    1
  • Epipactis

    @Samoreen

    Please note the differences in the log files : you can see messages in english (Exception has been thrown... and Unable to cast...) or in spanish (Se produjo una excepción... and No se puede convertir...) or in french (Une exception a été levée... and Impossible d'effectuer un cast...).

    @Mike & Samoreen

    Thanks for your replies.

    @pgrat

    Congratulations, you discovered why it works with V20.0.0 and why it began to bug with V20.0.2.

    I wonder why they made this "fix", I didn't see anyone complain on the forum about a problem with V20.0.0 and the OpenWith plugin.

    Did anyone have a problem in V20.0.0 with OpenWith plugin ?

    1
  • pgrat

    The collection of software in the plugin list gives strange or even incoherent results, but there is always a way to work around it.
    I guess someone at Phase One wanted to fix that and had to break something else...

    What I don't understand is why since January 27th when I reported this bug to the support, nothing has happened yet.

    1
  • Samoreen

    Hi,

    I just discovered something rather strange with the OpenWith plugin.

    In order to display localized strings, the main program uses C:\Program Files\Phase One\Capture One 20\P1.C1.Localization.dll in english and C:\Program Files\Phase One\Capture One 20\xx\P1.C1.Localization.resources.dll for other languages, xx being the language identifier.

    I see that when the OpenWith plugin is loaded it also loads a copy of P1.C1.Localization.dll but this copy is located in C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\P1.C1.Localization.dll (EN) or C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\xx\P1.C1.Localization.resources.dll.

    Both versions of P1.C1.Localization.resources.dll for a given language are strictly identical binaries.

    This doesn't make sense. Since the localization DLL is already loaded by the main process and since the plugin is also a DLL loaded by the main process, there's absolutely no need to load it again. This localization DLL can be accessed simultaneously by both the main program and the plugin DLL.

    Moreover, this localization DLL contains all the translations needed by the main program while the plugin only needs to translate a few strings.

    Duplicate copies of the same binaries, duplicate instances of the same DLL... There's something strange in this programming practice.

    I don't know if this was working the same way in v12.

    1
  • Samoreen

    Hi,

    Was the "plugin not initialized" problem fixed for anyone with version 2.0.4 ?
    Thanks.

    1
  • NNN634411414117438868
    I have the same problem.
    0
  • pgrat
    I feel less alone 😉
    0
  • Samoreen
    Hi,

    I do not have this problem (running Windows 10 Pro 1909). A fellow photographer of mine on a french forum is affected, though. She switched back to a previous version and the plugin now works normally. Could one of you please share the offending DLL (C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith\OpenWithPlugin.dll) so that I can compare it with mine which is working normally ? Just to see whether yours was corrupted.
    0
  • pgrat
    Hi Patrick,
    I didn't want to install this problematic update on my desktop computer running Win 10 Pro 1909 ...
    I send this to your contact email.

    Thanks
    0
  • Samoreen
    Hi Pascal,

    Thanks for the files.

    The DLL dated 01-17-2020 that you sent me is strictly identical to mine. This doesn't mean that the bug is elsewhere. Just, the problem doesn't appear on my system.

    The DLL dated 11-27-2019 from the previous C1 version is not identical to the one above. There are slight differences. However, they do have the same internal assembly version number and product version number which is bad programming practice and can only generate confusion for the installers.

    I guess you'll have to wait for a fix. Another example of lack of regression testing.
    0
  • pgrat
    Hi Patrick,

    Thank you very much ! It's indeed curious that the same code works on the Pro version of the OS and does not work properly on its Home version!
    We will therefore wait for the support to respond positively to this issue.
    The regression tests seem to be incomplete ...
    0
  • Adam Tidswell
    I`ve got the same problem .. I don`t need the plug in, just want the irritating display box to go away ...... Windows 8.1 here
    0
  • Samoreen
    pgrat wrote:
    It's indeed curious that the same code works on the Pro version of the OS and does not work properly on its Home version!


    Actually, the plugin appears to also fail on a Windows 10 Pro system. Not on mine, however.
    0
  • Samoreen
    Adam52 wrote:
    I`ve got the same problem .. I don`t need the plug in, just want the irritating display box to go away


    By the way, I don't see any way to disable the plugin. Maybe you could try to move the C:\Program Files\Phase One\Capture One 20\Plugins\OpenWith folder out of C:\Program Files\Phase One\Capture One 20\Plugins ? C1 should no longer try to open it.
    0
  • Paul Steunebrink
    The issue - like many issues - does not seem to affect all users. I have no issues with 20.0.2 on both Win8.1 and Win10 (1909) and the Open With plugin.

    Please do report to support, it needs attention.
    0
  • pgrat
    Paul_Steunebrink wrote:

    Please do report to support, it needs attention.


    The report was sent on Monday (20998) and remains unanswered to this time.
    0
  • pgrat
    Samoreen wrote:

    By the way, I don't see any way to disable the plugin.


    I think this plugin can't be disabled since it contributes to the functionality of C1. And that's what's really annoying ...
    0
  • Samoreen
    pgrat wrote:
    The report was sent on Monday (20998) and remains unanswered to this time.


    Don't hold your breath. Here is what I received this morning :

    Since the launch of Capture One 20 our Support department has been flooded with tickets, and we are still trying to get to the bottom of the pile. We can see that your request is one of the ones that have waited the longest, and we are trying to give those tickets the attention that they need, and will prioritize it, if your issue still needs handling.

    A lot of the issues that users wrote to us about have already been addressed, either by an actual fix or with an article in our Help Center (https://support.captureone.com/hc/en-us), so you might not need our assistance anymore.
    We haven't read each and every support request, but if you still need help with this, please just let us know by replying to this message - we don't need details just a word to indicate that we need to respond.
    If we don't hear from you within a week, we will assume that you found an answer to your request.

    We apologize for the prolonged reply time, and assure you that we are doing our best to learn from this.

    This appears to confirm that regression testing has not be done seriously before releasing version 20. When a maintenance release adds new bugs (like this one) instead of stabilizing the software, this is an obvious sign of a lack of testing. It also seems that the "new" (downgraded) support organization for those users who are only C1 customers and didn't purchase Phase One hardware is too weak.

    Also, I understand that if we do not reactivate within one week the support requests that have not been handled yet, we have no chance to get a fix within a reasonable amount of time.
    0
  • IanS
    Samoreen wrote:
    pgrat wrote:
    The report was sent on Monday (20998) and remains unanswered to this time.


    Don't hold your breath. Here is what I received this morning :

    Since the launch of Capture One 20 our Support department has been flooded with tickets, and we are still trying to get to the bottom of the pile. We can see that your request is one of the ones that have waited the longest, and we are trying to give those tickets the attention that they need, and will prioritize it, if your issue still needs handling.

    A lot of the issues that users wrote to us about have already been addressed, either by an actual fix or with an article in our Help Center (https://support.captureone.com/hc/en-us), so you might not need our assistance anymore.
    We haven't read each and every support request, but if you still need help with this, please just let us know by replying to this message - we don't need details just a word to indicate that we need to respond.
    If we don't hear from you within a week, we will assume that you found an answer to your request.

    We apologize for the prolonged reply time, and assure you that we are doing our best to learn from this.

    This appears to confirm that regression testing has not be done seriously before releasing version 20. When a maintenance release adds new bugs (like this one) instead of stabilizing the software, this is an obvious sign of a lack of testing. It also seems that the "new" (downgraded) support organization for those users who are only C1 customers and didn't purchase Phase One hardware is too weak.

    Also, I understand that if we do not reactivate within one week the support requests that have not been handled yet, we have no chance to get a fix within a reasonable amount of time.


    Yes, I had one of those emails which also said I was receiving it because mine was one of the oldest requests, I have been waiting for weeks ☹️

    Capture One A/S is now a separate business unit which is why they have a new support team.

    Capture One management must be aware that they have serious issues with support and hopefully they will address them urgently. Operating as a new business unit should focus management minds on such issues but we will just have to wait and see if reality matches aspiration. 😊
    0
  • pgrat
    IanS wrote:

    Capture One management must be aware that they have serious issues with support and hopefully they will address them urgently. Operating as a new business unit should focus management minds on such issues but we will just have to wait and see if reality matches aspiration. 😊


    There is indeed a problem with the quality of the support that requires energetic action from C1.
    During the installation of the new v20, I had the surprise to see that the activation was done on the serial key of the beta. I indicated my surprise to the support which systematically answered outside to the problem, as if it was a bot programmed to answer "pre command" when it was not the case!
    The programmer(s) may not have seen this as an anomaly or even not seen at all, but it's perfectly illogical and a misunderstood problem due to the generalization of licenses for all products, even free ones.
    Operating simultaneously a new functional organization and a new major version of the software is certainly not a good idea.
    0
  • Paul Steunebrink
    pgrat wrote:
    ...
    During the installation of the new v20, I had the surprise to see that the activation was done on the serial key of the beta.

    If you participated in the Capture One 20 beta program, then you are aware that the beta ran with a serial key as well, provided to you. Using this key was part of the beta testing, as activation rules has changed from earlier versions.

    This 'beta key' remained active a week after the release, which gave beta testers some extra time to make the switch to the new version.

    Once the beta key expired, you could activate the program again with a license key you bought, or a 30-day trial key, or stop using Capture One 20.

    I do not see any issue in this, other than that it may be misunderstood by some users. Or as we say, not a bug, just a feature. 😉
    0
  • Samoreen
    Hi,

    I further investigated the case and there's something that those Windows users who have the problem could try :

    - Exit C1.
    - Go to C:\Users\<user>\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn (the actual name may vary).
    - You'll possibly find there several subfolders, each one corresponding to a different release of C1 20. Open the one corresponding to version 20.0.0.2 : 13.0.2.13.
    - Open the file named user.config in Notepad.
    - Look for the PluginsDictionary section. The entry corresponding to the OpenWith plugin has a tag named <IsEnabled>. It should be set to true. If it is set to false, set it to true, save user.config and relaunch C1.

    I'm not sure that this will directly solve the problem but this will force C1 to re-evaluate its environment and possibly enable the plugin.

    NB : This is not a way to disable the plugin (if it is working correctly on your system). If the IsEnabled tag is set to true, setting it to false will force C1 to do some checking operations but the value will eventually be reset to true and the plugin will be enabled anyway.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post