Error 1172 .net COM exception

[EMehl]

I was wondering if anyone would be able to help me out with this:

Error 1172 occurred at Error creating instance of Runtime in assembly Microsoft.Research.Kinect.Nui.Runtime, Microsoft.Research.Kinect, Version=1.0.0.45, Culture=neutral, PublicKeyToken=31bf3856ad364e35, (System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x83010585)

Possible reason(s): LabVIEW: A .NET exception occurred in an external assembly. For information about correcting this error, copy the following exception (in bold), and search the Microsoft Developer Network (MSDN) Web site or the Web for a possible explanation. System.Runtime.InteropServices.COMException in Kinect_API.lvlib:Initialize Kinect.vi->Kinect_API.lvlib:Kinect Test Program.vi

I've done everything from Googling the issue to emailing LabVIEW, including uninstalling software and reinstalling it, and I always seem to get the same error, and nowhere closer to fixing it. I'm getting the error inside of a VI that I downloaded from the developer zone; the link to it is: http://zone.ni.com/devzone/cda/epd/p/id/6504

If anyone has ANY suggestions or hints as to how I can fix this, it would be greatly appreciated, as it's getting insanely frustrating. If it helps, I'm running LabVIEW via Windows 7 in Parallels Desktop 7 for Mac. Please let me know if you need any additional information, and thanks!

[KyleP]

Have you tried your code on something other than a Parallels machine? Being a virtual machine, Parallels can cause unexpected issues when trying to communicate over COM ports. A different environment may alleviate some headaches.

[EMehl]

Unfortunately, the only way I can run the program is through LabVIEW running in Parallels. I don't believe it's a COM port error, though. Even if I don't have the Kinect plugged in when I run the program, I still get the same exact error. Also, I uninstalled Visual Studio and tried to run the program, and I got a different error, telling me it couldn't an NUI runtime dll. This leads me to believe that the error has something to do with the .NET library and dll files.

[KyleP]

Which .dll files are you referring to? Are these .dll files that were coded in LabVIEW, are they something you wrote, or are these third party files? Tell us a little more about the environment you're working in. Have you been able to successfully communicate with the Kinect and how are you doing so?

If you believe that the issue may be related to Kinect .dll files, Microsoft's resources may be more helpful.

KyleP

[EMehl]

The .dll file I'm referring to is Microsoft.Research.Kinect.dll, and I don't believe it was coded in LabVIEW. It's part of a SDK that you can download from Microsoft in order to write programs for the Kinect in Visual Studio. The VI that I downloaded from the Developer Zone (http://zone.ni.com/devzone/cda/epd/p/id/6504) pulls the interface into LabVIEW, but I'm pretty sure it's still linked with Visual Studio somehow, though Visual Studio does not need to be running to run the VI. It may just need some files that are part of the Visual Studio download package. I have not been able to get the Kinect to work properly in the Visual Studio program either. I've also been through the troubleshooting steps listed on the VI download site, as well as some on the MSDN site, but none have really been helpful.

Basically, what the VI does is allow you see both a color image and a depth image from the Kinect sensor, and then using the depth camera it allows you calculate the distance from the Kinect to the object. My project partner has been able to get both the Visual Studio and LabVIEW VI working on his computer, and he is not running a virtual machine, so that may yet be the case. I read somewhere that .NET files don't like being stored and recalled from shared network folders, which is essentially where my files are since I'm running a virtual machine, but I can't find a way around that. I've tried reinstalling Visual Studio, reinstalling the .NET framework, trying to increase the trust properties of the .net files, and moving around the various key files to different locations to see if it would make any difference, but nothing has worked.

If it helps, the Kinect SDK can be downloaded here, along with more information regarding Kinect for Windows: http://www.microsoft.com/en-us/kinectforwindows/

I've also attached a few screenshots of the problem area with some notes. It seems to be localized to a subVI within the main VI called "Initialize Kinect".

Thanks!

[KyleP]

Since your partner has been able to successfully run Visual Studio and the LabVIEW VI, I would start searching for documentation from other users who have worked in a similar environment as you. A quick Google search of ".NET development on Parallels" netted me a few blog posts, but I'm not sure which ones will be useful to you since I'm not as familiar with the setup as you are. 

[EMehl]

Thanks! I'll give that a try and post any useful information I find here.

[lunabot]

How were you able to resolve this issue? I am having the exact same issue

[EMehl]

As of yet, I haven't been able to resolve it. I'm still working on it, though, and when/if I have any sucess I'll post exactly what I did on here. In the mean time, good luck!

[Greg-H]

Hi,

The DLL referenced above uses .NET framework 4 and LabVIEW defaults to .NET framework 3.5.  Try following these steps and see if it helps:

http://ae.natinst.com/public.nsf/web/searchinternal/567f6effc5669c348625739b003739cd?OpenDocument

Regards,

Greg H.