none
Problems with the Kinect

    Question

  • I've been having some issues trying to use the Kinect with the DSS command prompt in Microsoft RDS4. 

    For example, if I type "KinectUI", it fails setting up the service and gives me the exception and error pasted below. It seems it can't find the proper service even though I already downloaded the Kinect SDK and everything else. Any idea what the problem might be?

    Here's what I got at the command line:

    C:\Users\Mark\Microsoft Robotics Dev Studio 4 Beta 2>KinectUI
    
    C:\Users\Mark\Microsoft Robotics Dev Studio 4 Beta 2>REM Run the KinectUI Sample
    
    
    C:\Users\Mark\Microsoft Robotics Dev Studio 4 Beta 2>"C:\Users\Mark\Microsoft Ro
    botics Dev Studio 4 Beta 2\bin\\dsshost32" /p:50000 /t:50001 /m:"C:\Users\Mark\M
    icrosoft Robotics Dev Studio 4 Beta 2\bin\..\Samples\Config\KinectUI.manifest.xm
    l"
    *   Service started [02/19/2012 06:24:30][http://mark-think:50000/directory]
    *   Service started [02/19/2012 06:24:30][http://mark-think:50000/constructor]
    *   Service started [02/19/2012 06:24:30][http://mark-think:50000/console/output
    ]
    *   Service started [02/19/2012 06:24:30][http://mark-think:50000/console/output
    ]
    *   Rebuilding contract directory cache. This will take a few moments ... [02/19
    /2012 06:24:30][]
    *** Service creation failure most common reasons:
        - Service contract identifier in manifest or Create request does not match C
    ontract.Identifier
        - Service references a different version of runtime assemblies
        - Failure to load referenced assemblies (not found in binary folder or unabl
    e to load types)
        Additional information can be found in the system debugger log.
     [02/19/2012 06:24:30][http://mark-think:50000/manifestloader/fb80131e-6513-41b1
    -8d33-64673a6d87fc]
    **  Common Create Handler ExceptionSystem.InvalidOperationException: Service not
     found: http://schemas.microsoft.com/robotics/2011/08/kinect.html
       at Microsoft.Dss.Services.Serializer.DataCache.LoadServiceAssemblies(ServiceI
    nfoType createRequest)
       at Microsoft.Dss.Services.Constructor.ConstructorService.CommonCreateHandler(
    DsspOperation create) [02/19/2012 06:24:30][http://mark-think:50000/constructor]
    
    *   Contract directory cache refresh complete [02/19/2012 06:24:32][]
    **  Common Create Handler ExceptionSystem.InvalidOperationException: Service not
     found: http://schemas.microsoft.com/robotics/2011/08/kinect.html
       at Microsoft.Dss.Services.Serializer.DataCache.LoadServiceAssemblies(ServiceI
    nfoType createRequest)
       at Microsoft.Dss.Services.Constructor.ConstructorService.CommonCreateHandler(
    DsspOperation create) [02/19/2012 06:24:32][http://mark-think:50000/constructor]
    
    *** Service creation failure most common reasons:
        - Service contract identifier in manifest or Create request does not match C
    ontract.Identifier
        - Service references a different version of runtime assemblies
        Additional information can be found in the system debugger log.
     [02/19/2012 06:24:32][http://mark-think:50000/manifestloader/fb80131e-6513-41b1
    -8d33-64673a6d87fc]
    *** Error creating service. Service type:http://schemas.microsoft.com/2008/08/ki
    nectui.html [02/19/2012 06:24:32][http://mark-think:50000/constructor]
    *** Error creating service. Service type:http://schemas.microsoft.com/robotics/2
    011/08/kinect.html [02/19/2012 06:24:32][http://mark-think:50000/constructor]

    dimanche 19 février 2012 06:28

Réponses

  • My apologies, I glossed over the dsshost32 part - you're right, it was already launching in x86 mode.

    Next troubleshooting tip, what version of Kinect runtimes are you running?  If you're not using the K4W Beta that the RDS service was designed for, then that might be the problem.  Note, RDS 4 Beta nor RDS 4 Beta 2 are compatible with the Kinect for Windows SDK version 1.

    • Marqué comme réponse Mark_3 mardi 21 février 2012 22:36
    lundi 20 février 2012 23:32
  • I uninstalled K4W 1.0 and installed the Beta, launched with the x64 command prompt, and its working now. Thanks!
    mardi 21 février 2012 22:35

Toutes les réponses

  • Looks like you're running an x64 machine.  Try launching your manifest with dsshost32, this will force it into x86 compatibility mode.
    lundi 20 février 2012 06:39
  • Thanks for the reply. Didn't it automatically launch with dsshost32 though? At least that's what it looks like from this line:

    C:\Users\Mark\Microsoft Robotics Dev Studio 4 Beta 2>"C:\Users\Mark\Microsoft Ro
    botics Dev Studio 4 Beta 2\bin\\dsshost32" /p:50000 /t:50001 /m:"C:\Users\Mark\M
    icrosoft Robotics Dev Studio 4 Beta 2\bin\..\Samples\Config\KinectUI.manifest.xm
    l"

    If not, then how would I go about launching my manifest with dsshost32? Thanks.

    lundi 20 février 2012 07:33
  • My apologies, I glossed over the dsshost32 part - you're right, it was already launching in x86 mode.

    Next troubleshooting tip, what version of Kinect runtimes are you running?  If you're not using the K4W Beta that the RDS service was designed for, then that might be the problem.  Note, RDS 4 Beta nor RDS 4 Beta 2 are compatible with the Kinect for Windows SDK version 1.

    • Marqué comme réponse Mark_3 mardi 21 février 2012 22:36
    lundi 20 février 2012 23:32
  • Hmm that might be my problem. I downloaded this: http://www.microsoft.com/en-us/kinectforwindows/develop/overview.aspx. But you are saying I actually want the K4W Beta, not K4W 1.0? Should I just delete all the K4W 1.0 files and install the Beta? Thanks.
    mardi 21 février 2012 21:56
  • I uninstalled K4W 1.0 and installed the Beta, launched with the x64 command prompt, and its working now. Thanks!
    mardi 21 février 2012 22:35