Hi,

I'm trying to use the OpenNETCF.Desktop.Communication dll. I'm using Windows mobile 5.0, VS 2008, .Net 2.0

When I try to create a new instance of RAPI it throws the following error.

"Unable to load DLL 'rapi.dll': A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A)"

 

Any and all help is appreciated.

Thanks,

D

I digged a little further and found out that its actually failing when creating a new instance of DccMan() in ActiveSync.cs. Throws the following error:

"Unable to create ActiveSync object. Make sure ActiveSync is installed"

 I've ActiveSync 4.5 installed and it connects and all nicely.

Any ideas why its doing that?

Where are you running the code: on a device or on the desktop? The Desktop Communication library cannot be used in a device application.

On the desktop from my web application (vb.net, asp.net).

Is the issue with Visual Studio 2008 or something?

I created a small web app which uses RAPI to copy files from the desktop to device. And it ran fine in the Development Server. But when I switched it to run with IIS it failed (the same error as mentioned in the above posts).

I hope this helps you in helping me :)

So I think I've the same problem as mentioned in this thread: http://community.opennetcf.com/forums/t/5150.aspx

Frankly I've tried granting access and all but nothing worked so far.

If anybody has a solution/suggestion I'd really appreciate.

Thanks,

D

Can somebody please look into this. Its kinda urgent.

I'm unclear what you want us to look into.  While we provide the Communication library, we do so for free we don't guarantee any form of support for it - that's why we also give you the full source code to extend and/or fix it as you see fit. 

We do offer consulting services and if you wanted us to look into it we certainly could follow that path, but otherwise it's unlikely that we're internally going to look at how to make this scenario work in the near future.

Hello,

I appreciate the service that you are extending for all of us. I really appreciate.

What I need to know is why would my web app fail while instantiating a new dccMan instance? Is it a access rights issue? If just somebody would point me in right direction that would be very helpful.

I'm sure you understand that if this doesn't work then I've to look into finding another solution which works for me asap.

I truly appreciate you guys taking time off and looking into this.

Thanks,

D

I suspect that the ASP process needs the ability to interact with the desktop and needs the right to run as a specific user.  IIRC there's a checkbox for the service to give it that permission.

 
 

Using the Desktop Communication library (and more importantly, RAPI) through a web app is not a supported scenario.