Announcement

Collapse
No announcement yet.

Protee interface error messages

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Protee interface error messages

    My old computer was failing so I had to build a new on about 4 to 5 months ago. (I712700K, RX6700XT, Z690, 32G DDR5 standard clocks) I installed windows 11 pro as well as the protee interface and TGC. Things worked well until a few days ago. I noticed the vertical camera was not recognized by the software at times and sometimes flickered. I had not install any new software of late except for windows and driver updates, but decided to role back the system to an earlier date. Unfortunately, I had a power failure during the role back process and the windows installation did not functioning correctly. I ended up reinstalling windows.

    During the installation I kept my files. When I reinstalled the protee interface I got a 339 error message. That is "Component' MSWINSCK.OCX or one of its dependencies not correctly registered: a file is missing or invalid". I'm fairly knowable about computers. I've built over a dozen and know how to run admin scans and load and register software. So, I downloaded software and went about fixing the issues. Well, I would fix one and another would pop up. Got to the point were I could find no software to fix the issues. I tried to run the interface as administrator and it would start and even communicate with TGC (no ball flights though), but then I would get errors trying to use the cameras. Firecap does recognize and display the cameras. The errors I get are still 339 errors. These include but are not limited to icimagingcontrol.ocx or MSVCP100.dll.

    I ended up reformating the hard drive and doing a fresh install of windows. I did not allow the newest updates of windows and used an older version of AMDs drivers. I still have the interface issues.

    Anyway, it would seem that no amount of scanning, downloading, registering or permissions will get the interface working. Protee is great by the way.
    Anyone else have this type of issue and if so, did you resolve it?
    Last edited by Stonebattle; 02-21-2023, 02:08 PM. Reason: Made more complete

  • #2
    Originally posted by Stonebattle View Post
    My old computer was failing so I had to build a new on about 4 to 5 months ago. (I712700K, RX6700XT, Z690, 32G DDR5 standard clocks) I installed windows 11 pro as well as the protee interface and TGC. Things worked well until a few days ago. I noticed the vertical camera was not recognized by the software at times and sometimes flickered. I had not install any new software of late except for windows and driver updates, but decided to role back the system to an earlier date. Unfortunately, I had a power failure during the role back process and the windows installation did not functioning correctly. I ended up reinstalling windows.

    During the installation I kept my files. When I reinstalled the protee interface I got a 339 error message. That is "Component' MSWINSCK.OCX or one of its dependencies not correctly registered: a file is missing or invalid". I'm fairly knowable about computers. I've built over a dozen and know how to run admin scans and load and register software. So, I downloaded software and went about fixing the issues. Well, I would fix one and another would pop up. Got to the point were I could find no software to fix the issues. I tried to run the interface as administrator and it would start and even communicate with TGC (no ball flights though), but then I would get errors trying to use the cameras. Firecap does recognize and display the cameras. The errors I get are still 339 errors. These include but are not limited to icimagingcontrol.ocx or MSVCP100.dll.

    I ended up reformating the hard drive and doing a fresh install of windows. I did not allow the newest updates of windows and used an older version of AMDs drivers. I still have the interface issues.

    Anyway, it would seem that no amount of scanning, downloading, registering or permissions will get the interface working. Protee is great by the way.
    Anyone else have this type of issue and if so, did you resolve it?
    Hi,

    Could you verify that you installed the correct drivers for the cameras : https://download.protee-united.com/drivers/firefly.exe

    The MSVCP errors are from missing C++ runtimes; try running : https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

    Please do reach out if you keep running into issues and what issues you notice


    Thank you

    Comment


    • #3
      Yes, I am running the Firefly.exe driver from your sight. Still, I downloaded a new copy and ran the repair option. Firecap2 does recognized both the vertical and horizontal cameras. I can see the image they display in the software.

      I downloaded and performed the install all in one C redistribution package you show above. After installation, if I start the interface without admin I get the MSWINSCK.OCX error. I got this error before when I down loaded Visual Basic from Microsoft's sight, that is before I did a fresh windows install.

      If I run the interface as admin, it displays. I then set the com port and save. Exit and then restart. I now find I can bring the V cam and H cam windows up but the cameras are not recognized. Not bad, that's further than I got.

      I have to note, that the first time I tried admin, port set and restart of the interface I got the same issues as I did before the fresh windows install. But, I uninstalled the interface and restarted the computer. As it turns out another windows update installed at that time. When I restarted, I reinstalled the interface and got the results noted above. Coincidence?

      Comment


      • #4
        My guess is you know this but the links for download fixes for above errors are broken on the Protee support site. That tends to leave folks on their own looking for fixes.

        Comment


        • #5
          I decided to have a remote session with Protee support. As usual they did a great job and got the interface functioning.

          There was not an obvious solution and they spent quite a bit of time resolving them. It's interesting, I know I did all of the same things the Protee folks did, but not quite in the same sequence. The ultimate solution was to completely uninstall the firefly software, reinstall it and check the register DLLs box during installation.

          Comment

          Working...
          X