Visual studio license file problem regarding to Spread 2.5

Posted by: kufelixjpn on 7 October 2018, 2:05 pm EST

    • Post Options:
    • Link

    Posted 7 October 2018, 2:05 pm EST - Updated 11 January 2024, 5:40 am EST

    Hello there,

    I was originally using Win7 32bit and spread 2.5 with visual studio 2015. The spread 2.5 installation file can run successfully on Win7 32bit and therefore I can view and edit the source code of my vb.net program in which some of the applications were scripted with Spread 2.5.

    The problem occurs when I try open the vb.net project on Win10 64bit with VS2015, visual studio pops out warning stating that```

    “SS32X25.OCX License file for custom control not found. You do not have an appropriate license to use this custom control in the design environment. Call FarPoint at:x-xxx-xxx-xxxx”

    
    I have tried moving the ss32x25.ocx and ss32d25.dll from Win7 32bit to Win10 64bit and register, the ss32x25.ocx can be registered successfully but the MSVCRT40.dll cannot be found in both system32 and syswow64 folder even after successful registration (Not sure if this is the cause of my problem).
    
    Is there 32bit installer for Spread 2.5 available or where can I shift my license file to Win10?
    
    Please kindly advice me how can i view and edit my vb.net source code with applications scripted with Spread 2.5 on Windows10 64bit. Thank you very much! [img]https://gccontent.blob.core.windows.net/forum-uploads/file-2c798cb6-8276-49a9-93cc-5467ad1615aa.jpg[/img]
  • Posted 7 October 2018, 5:25 pm EST

    Hello,

    The error message clearly states that you are trying to use the custom control created using Spread 2.5 in the design environment. It requires the control to be installed on the machine where it is used and licensed.

    This is the correct behavior.

    Thanks,

    Deepak Sharma

  • Posted 7 October 2018, 5:45 pm EST - Updated 29 September 2022, 4:58 am EST

    Thank you for your prompt respond. As Spread 2.5 cannot be installed on Windows 10 64bit, is there a way to transfer the license files from my Win7 to Win10?

    Thanks

  • Posted 8 October 2018, 12:24 pm EST

    It’s ok I have solved the issue.

    Thank you for your reply.

    Best

  • Posted 8 October 2018, 3:49 pm EST

    We are happy to know that you got your issue resolved.

    In case you need help with any other issue, please feel free to get back to us.

    Regards,

    Deepak Sharma

  • Posted 30 July 2023, 7:44 am EST

    kufelixjpn - How did you resolve this issue? I’m having the same issue. I ported an old VB6 dev environment from VMWare to Azure, and XP didn’t play well with Azure (wouldn’t boot up because it wanted to be activated due to significant hardware changes but since you can only RDP to the machine, you couldn’t do anything to get past the prompt on bootup). So we started with a fresh Win 10 machine and installed VB6 and the references the project needed. The system has ss32x25.ocx in the system32 and sysWoW64, and we used the 32 bit and 64 bit methods to register the ocx in both locations. The project loads fine and can run in debug mode, but when you compile or load the form that has the FarPoint grid on it, it fails. When you go to compile, it throws the same error you reported (“SS32X25.OCX License file for custom control not found. You do not have an appropriate license to use this custom control in the design environment. Call FarPoint at: 1-919-460-1887”. If you open the form, it adds this to the log file for that form:

    Line 130: Property OleObjectBlob in sprConfirmImport could not be set.

    Line 130: Cannot load control sprConfirmImport; license not found.

    Any insight would be appreciated. I’d love to get this resolved. We’re converting this project to browser-based, but they’re using the old code as a reference as they build its replacement.

  • Posted 31 July 2023, 4:25 am EST

    Hi Steve,

    It seems that you are using very old version of ActiveX control. We do not provide support for the ActiveX controls now. We request you update your control to the latest version in order to avail latest updates and support.

    However, we can provide you some hints regarding this issue. Please make sure that you have correctly licensed your custom control. Also, check whether the controls are properly registered in the windows registry or not. Sometimes, the issue occurs when the OCX used during development is different from the one installed on the test machine or if the registration process fails to locate the correct OCX.

    > I ported an old VB6 dev environment from VMWare to Azure, and XP didn’t play well with Azure (wouldn’t boot up because it wanted to be activated due to significant hardware changes but since you can only RDP to the machine, you couldn’t do anything to get past the prompt on bootup).

    Could you please let us know what steps you followed to port your project from VM to Azure? We are not sure whether Azure will support this much outdated version of the control. Please provide us the details required so that we can understand your use-case scenario and assist you, if it is possible.

    In addition to this please share the details regarding your .ocx file.

    Thanks & Regards,

    Aastha

Need extra support?

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

Learn More

Forum Channels