Problem with latest version: "OpenNI library can't find any module!"

1,381 views
Skip to first unread message

sgroves

unread,
Apr 18, 2011, 11:40:05 AM4/18/11
to OpenNI
Hi all,

I'm having a problem getting the latest OpenNI/NITE release to work
with my Kinect (the previous version worked fine). I downloaded avin's
latest sensor release and followed the instructions in the readme
(installed OpenNI, the sensor package, and NITE), but when I try to
launch NiViewer.exe, I get the error "OpenNI library can't find any
module!".

Before installing the latest version, I uninstalled the previous
version of everything and all Kinect drivers, so I'm not sure what's
wrong. Can anyone help?

Siyfion

unread,
Apr 18, 2011, 11:51:59 AM4/18/11
to OpenNI
What OS are you running? Did you manually uninstall the drivers from
the Kinect Sensor? Did you unplug the device? Did you install in the
correct order OpenNI -> Sensor -> NITE? etc.

Siyfion.

Дериглазов Сергей

unread,
Apr 18, 2011, 12:00:15 PM4/18/11
to openn...@googlegroups.com
What is text in file "c:\Program Files (x86)\OpenNI\Data\modules.xml"?

-- 
Sergey Deriglazov
derig...@gmail.com



2011/4/18 Siyfion <siy...@gmail.com>

sgroves

unread,
Apr 18, 2011, 12:03:02 PM4/18/11
to OpenNI
Sorry, I'm running Windows 7. After manually uninstalling the old
drivers, I unplugged the Kinect, plugged it back in, then installed
the three packages in the right order. The previous version of OpenNI
worked just fine, so I'm really puzzled.

sgroves

unread,
Apr 18, 2011, 12:07:32 PM4/18/11
to OpenNI
Дериглазов - modules.xml contains:

<Modules>
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Features_1_3_0\Bin\XnVFeatures.dll" configDir="C:\Program Files
(x86)\PrimeSense\NITE\Features_1_3_0\Data" />
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Features_1_3_1\Bin\XnVFeatures_1_3_1.dll" configDir="C:\Program Files
(x86)\PrimeSense\NITE\Features_1_3_1\Data" />
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Hands_1_3_0\Bin\XnVHandGenerator.dll" configDir="C:\Program Files
(x86)\PrimeSense\NITE\Hands_1_3_0\Data" />
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Hands_1_3_1\Bin\XnVHandGenerator_1_3_1.dll" configDir="C:\Program
Files (x86)\PrimeSense\NITE\Hands_1_3_1\Data" />
<Module path="C:\Program Files (x86)\OpenNI\Bin\nimRecorder.dll" /
>
<Module path="C:\Program Files (x86)\OpenNI\Bin\nimMockNodes.dll" /
>
<Module path="C:\Program Files (x86)\OpenNI\Bin\nimCodecs.dll" />
<Module path="C:\Program Files (x86)\PrimeSense\SensorKinect\Bin
\XnDeviceFile.dll" />
<Module path="C:\Program Files (x86)\PrimeSense\SensorKinect\Bin
\XnDeviceSensorV2KM.dll" configDir="C:\Program Files (x86)\PrimeSense
\SensorKinect\Data" />
</Modules>



On Apr 18, 12:00 pm, Дериглазов Сергей <derigla...@gmail.com> wrote:
> What is text in file "c:\Program Files (x86)\OpenNI\Data\modules.xml"?
>
> --
> Sergey Deriglazov
> derigla...@gmail.com
>
> 2011/4/18 Siyfion <siyf...@gmail.com>

sgroves

unread,
Apr 18, 2011, 12:04:01 PM4/18/11
to OpenNI
Дериглазов - modules.xml contains:

<Modules>
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Features_1_3_0\Bin\XnVFeatures.dll" configDir="C:\Program Files
(x86)\PrimeSense\NITE\Features_1_3_0\Data" />
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Features_1_3_1\Bin\XnVFeatures_1_3_1.dll" configDir="C:\Program Files
(x86)\PrimeSense\NITE\Features_1_3_1\Data" />
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Hands_1_3_0\Bin\XnVHandGenerator.dll" configDir="C:\Program Files
(x86)\PrimeSense\NITE\Hands_1_3_0\Data" />
<Module path="C:\Program Files (x86)\PrimeSense\NITE
\Hands_1_3_1\Bin\XnVHandGenerator_1_3_1.dll" configDir="C:\Program
Files (x86)\PrimeSense\NITE\Hands_1_3_1\Data" />
<Module path="C:\Program Files (x86)\OpenNI\Bin\nimRecorder.dll" /
>
<Module path="C:\Program Files (x86)\OpenNI\Bin\nimMockNodes.dll" /
>
<Module path="C:\Program Files (x86)\OpenNI\Bin\nimCodecs.dll" />
<Module path="C:\Program Files (x86)\PrimeSense\SensorKinect\Bin
\XnDeviceFile.dll" />
<Module path="C:\Program Files (x86)\PrimeSense\SensorKinect\Bin
\XnDeviceSensorV2KM.dll" configDir="C:\Program Files (x86)\PrimeSense
\SensorKinect\Data" />
</Modules>



MichaelK

unread,
Apr 18, 2011, 12:30:01 PM4/18/11
to OpenNI
Same problem here. Installed the previous version just 2 days ago.
And today I just installed the two packages (first openni then nite),
and when running the samples now, the error message appears :-/

Tomorrow I will try to uninstall all again and do a fresh install...

deriglazov

unread,
Apr 18, 2011, 12:31:07 PM4/18/11
to OpenNI
It's correctly. A radical solution to the problem:
0) Unplug Kinect
1) remove NITE (use .msi-installer to remove)
2) remove Avin's drivers (use .msi-installer to remove)
3) remove OpenNI (use .msi-installer to remove)
3a) Check intallation in ControlPanel->Software and Components
4) remove folders C:\Program Files (x86)\PrimeSense + C:\Program Files
(x86)\OpenNI
5) reboot
6) check your installers
6a) Install OpenNI 1.1.0.41 x86
7) Install Avin's drivers
8) Test OpenNI samples
9) Install NITE 1.1.3.5 and add key to xml-files.

sgroves

unread,
Apr 18, 2011, 12:31:56 PM4/18/11
to OpenNI
I solved the problem -- in my system environment variables,
OPEN_NI_BIN was set to C:\Program Files (x86)\OpenNI\bin

It should be "Bin" with a capitalized B rather than "bin". All the
demos work fine now.

deriglazov

unread,
Apr 18, 2011, 12:37:04 PM4/18/11
to OpenNI
Very interesting. I checked it and found "OPEN_NI_BIN" = "C:\Program
Files (x86)\OpenNI\bin" but all samples work correctly.

msdark

unread,
Apr 19, 2011, 11:29:39 AM4/19/11
to OpenNI
(sorry for my english)
I have the same problem but using Mac OS X 10.6.7 (Snow Leopard)I try
to install OpenNI and failed with "Can't write to file" (this is the
niReg utility) so i build and install and this works, next i install
Sensor, and test the Samples but all Samples say Open failed: OpenNI
library can't find any module!

But the all files are where they have to be...

ANy idea??

Vangos Pterneas

unread,
Apr 19, 2011, 4:17:52 PM4/19/11
to OpenNI
Either change the environment variable or rebuild the projects adding
the references to OpenNI.dll and OpenNI.net.dll properly.

Matias Hernandez Arellano

unread,
Apr 19, 2011, 5:23:30 PM4/19/11
to openn...@googlegroups.com
What environment variables??? OpenNI.dll i work with Mac OS X .. not windows...

Any idea??

Somebody with the same problem???

Thanks in advance

> --
> You received this message because you are subscribed to the Google Groups "OpenNI" group.
> To post to this group, send email to openn...@googlegroups.com.
> To unsubscribe from this group, send email to openni-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/openni-dev?hl=en.
>

Matías Hernandez Arellano
Ingeniero de Software/Proyectos en VisionLabs S.A
CDA Archlinux-CL
www.msdark.archlinux.cl


Sunhawk

unread,
Apr 28, 2011, 7:27:43 AM4/28/11
to OpenNI
Same problem here, windows 7, latest unstable OpenNI, 64-bit
developer. It's quite frustrating.

* Environmental variables are correct.
* The drivers appear properly in the device manage (all three this
time).

Running a sample from OpenNI (NiUserTracker64.exe) I get
"Open failed: OpenNI library can't find any module!"

On Apr 19, 5:23 pm, Matias Hernandez Arellano <msd...@archlinux.cl>
wrote:
> What environment variables??? OpenNI.dll i work with Mac OS X .. not windows...
>
> Anyidea??
>
> Somebody with the same problem???
>
> Thanks in advance
> El 19-04-2011, a las 16:17, Vangos Pterneas escribió:
>
>
>
>
>
>
>
>
>
> > Either change the environment variable or rebuild the projects adding
> > the references to OpenNI.dll and OpenNI.net.dll properly.
>
> > On Apr 19, 6:29 pm, msdark <msdark...@gmail.com> wrote:
> >> (sorry for my english)
> >> I have the same problem but using Mac OS X 10.6.7 (Snow Leopard)I try
> >> to install OpenNI and failed with "Can'twrite to file" (this is the
> > For more options, visit this group athttp://groups.google.com/group/openni-dev?hl=en.

Ana Sousa

unread,
May 7, 2011, 2:36:50 PM5/7/11
to OpenNI
Problem solved. I solved the same problem with the environment
variables. you have to go to the "Path" environment variable and add -
at the end - all the "Open NI" values existent (check environment
variables named like "Open NI"). you may have to restart your pc to
changes to take effect.

Sam Muscroft

unread,
Jun 26, 2011, 11:57:23 AM6/26/11
to openn...@googlegroups.com
I can confirm that this was the same issue for me - using "Bin" instead of "bin" in the Binary env path solved the problem. I am beginning to wonder if any of these releases are actually fully tested - this has caused me a couple of hours of farting around...thanks sgroves for pinning down the problem.

Reply all
Reply to author
Forward
0 new messages