Windows 7 to Windows 10 Update - License Issue (Evaluation Message Displaying)

Posted by: dpotts on 4 December 2018, 5:50 pm EST

    • Post Options:
    • Link

    Posted 4 December 2018, 5:50 pm EST

    I have a situation where I have compiled and built my .net application on my Windows 10 machine (Enviroment A), and have released the the dlls to another Windows 10 environment (Environment B). Environment B has recently been upgraded from Windows 7 to Windows 10. The application worked perfectly, with no evaluation pop ups on Windows 7. However, now that Environment B has been upgraded to Windows 10, in which the same version of the application is installed, the Evaluation Pop Up displays within the application, as if the application is not licensed. Is there a compatibility issue with the licensing identification between Windows 7 and Windows 10? Has anyone else experienced this issue? If so, what was the cause and how was the issue resolved?

    NOTE: The app works fine on my Windows 10 machine, outside of my dev environment, and a few other Windows 10 machines.

  • Posted 5 December 2018, 6:26 am EST

    Hello,

    It seems that the Win10 machine (with issues) was already having a ComponentOne version installed. Could you please check that the version referenced in the deployed application and the version installed in that machine are same/not? Also, could you please check whether the version mentioned in nag screen is the one referenced by your application or the version present in your machine.

    Thanks,

    Ruchir

  • Posted 5 December 2018, 1:07 pm EST

    Thank you for your feedback Ruchir.

    The applicable dlls within the deployed application and the version mentioned on the nag screen, are all the same version. Additionally, the versions listed within the license files are the same versions that are listed within the dlls, and on the nag screen. The Win10 machine (with issues) does not have ComponentOne installed, and the same machine did not have it installed when it was running on Win7. We’ve never installed ComponentOne directly on the machines, if that is what you are referring to. Also, the issue is occurring on multiple machines that have been upgraded from Win7 to Win10. Please, let me know if I can provide additional information.

    NOTE: The application is installed on a Windows Server 2012+ environment and being accessed by a client workstation (Win7 - works, Win10 - does not work)

  • Posted 5 December 2018, 1:07 pm EST

    Thank you for your feedback Ruchir.

    The applicable dlls within the deployed application and the version mentioned on the nag screen, are all the same version. Additionally, the versions listed within the license files are the same versions that are listed within the dlls, and on the nag screen. The Win10 machine (with issues) does not have ComponentOne installed, and the same machine did not have it installed when it was running on Win7. We’ve never installed ComponentOne directly on the machines, if that is what you are referring to. Also, the issue is occurring on multiple machines that have been upgraded from Win7 to Win10. Please, let me know if I can provide additional information.

    NOTE: The application is installed on a Windows Server 2012+ environment and being accessed by a client workstation (Win7 - works, Win10 - does not work)

  • Posted 6 December 2018, 5:47 am EST

    In your initial message you mentioned that you released the dlls (by release we are assuming you have installed) on Environment B which is Win10. However, in your last response you have mentioned that you have installed the dlls on Win12 Server. So, could you please clarify whether the application is installed on Win12 Server machine or on Win10 machine.

    Also, could you please elaborate on how you are accessing the application, is it through Remote Desktop Connection or RD Web Access?

    Thanks,

    Ruchir

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels