Soft Motion Runtime Error

[Banjo_B]

Hi All.

Iv'e come accross a problem when opening any communication with Solidworks from my Labview project environment.

For example, when i try to connect to a Solidworks assembly as in the first attached image, I get the  runtime error message as seen in the second image.

The strange thing is that it worked for me a couple of months ago on a separate project. Im running labview 2010 sp1 and I have soft motion 2010 installed. I tried reinstalling the soft motion module but Im still getting the same error. 

Has anyone come accross this problem and if so could you suggest a solution.

Thanks for your time

.

[Banjo_B]

I have tried everything at this stage it seems but I continually have the same problem. One issue that I think may have caused it was that I downloaded an evaluation lab view 2011 and softmotion 2011 but have since uninstalled both from my machine.

Would the fact that I had these newer versions affect my 2010 functionality. It really is a pain since it would be great to use this on my current project.

[AndyNash]

Hi Banjo_B,

The Microsoft Visual C++ Runtime Library error is a fairly generic error that may occur for a number of reasons (Installing the 2011 version then uninstalling is the most likely cause however).  As such I believe the quickest way to resolve this will be to uninstall and reinstall LabVIEW your drivers and SoftMotion. When reinstalling, install LabVIEW, then the drivers, then SoftMotion.

Kind regards,

[Banjo_B]

Thanks for your reply but unfortunately I have tried this and I still have the error.
Is there somewhere I can log this fault??.

[IRERI]

I HAVE THE SAME ERROR... WHAT DO YOU DO TO SOLVE IT???

[chiara.a]

Hi IRERI and Banjo_B,

I'm Chiara, an Applications Engineer here at NI.  As Andrew said above, in the past this issue can have been caused by errors in the installation process, so it'd be helpful if you could completely uninstall and reinstall LabVIEW, your drivers, and SoftMotion, before reinstalling in that order.  If this doesn't fix the error, it'd be helpful if you could try your program on a secondary machine if you have one, just in case it is a hardware issue.

I'll keep researching to try and find more information for you; please do get back to me and tell me how you get on with these suggestions, so I can see what else I may be able to do to help you further.

Regards,