CWDS "Error loading control" occurs after disk replacement

[JMW]

LabView 5.1; Win 2000 SP1; CW 2.1; C++ Builder 4.

System worked fine for nearly 4 years. Then the hard drive failed. Replaced drive and reinstalled all applications with Win2K SP4. Now the CWDS "Error loading control" msg appears (once for each socket?) when the C++ app loads. If I run an older version of the app (predates the one that has been running for 4 years), the msg does not appear. All the VI's run fine. The only known difference is SP4 vs SP1, but the fact that the older version works suggests that this is not likely the cause. What else is out of sync?" (The DS is the only control in the C++ app.)

[bilalD]

Hello

Thats a pretty old version of the CWDS control. Currently, we're at 4.2 for datasocket. Have you tried just removing and readding the activex control from the C++ app?
Also try to create a new app and see if you get the same message. It might be something particular with that project that re-adding and re-building the project might take care of


Hope this helps

Bilal Durrani
NI

[JMW]

Ooooh, wish I could. The development environment for this app is not available. I desperately need to recreate the operating environment that was working before the disk died. (Of course, it would have been nice if the customer had been making backups like they were supposed to....)

[Anonymous]

Ooooh, wish I could. The development environment for this app is not
available. I desperately need to recreate the operating environment
that was working before the disk died. (Of course, it would have been
nice if the customer had been making backups like they were supposed
to....)

[bilalD]

You might want to verify that the datasocket control has been correctly registered on the PC. You can do that by running regsvr32 on cwds.ocx. If the control was registered successfully, you will get a popup message indicating this.

You could also use a tool like Dependency Walker to make sure you have all the dependencies required by the application. You can profile the exe using dependency walker and see if the application is failing because of a missing dll or component.

Good luck

Bilal