I ended up getting around this issue by running installstatconnDCOM() - not
the exact name, but something very similar to that in RStudio instead of
downloading from their site. This resolved the 80040013 error. I
subsequently ran into a few issues regarding an 800706BE error. I resolved
this by deleting the registry and environment variables and running
RSetReg.exe. I can now successfully test the statconn server test; however,
my code still throws an 800706BE error at .Init("R"). I'm testing the
codeplex project .NET R integration now, but am running into some silly
errors there as well.

On Thu, Apr 26, 2012 at 8:43 AM, Jonathan Shore <jonathan.shore@gmail.com>wrote:

> I cleaner alternative would be to use Rserve.  You can use IKVM to compile
> the Rserve java API to a .NET assembly.   Alternatively you can implement
> the protocol in C# (as I did).
>
> On Wed, Apr 25, 2012 at 6:50 AM, Joel <j.nybeck@gmail.com> wrote:
>
>> Jeff Abrams <jeffab <at> microsoft.com> writes:
>>
>> >
>> > I have a C# program that requires the run of a logistic regression.  I
>> have
>> downloaded the R 2.11 package, and
>> > have added the following references to my code:
>> >
>> > STATCONNECTORCLNTLib;
>> > StatConnectorCommonLib;
>> > STATCONNECTORSRVLib;
>> >
>> > In my code I have:
>> > StatConnector scs = new STATCONNECTORSRVLib.StatConnectorClass();
>> > scs.Init("R");
>> >
>> > The init step returns the below error which seems to indicate a
>> connection
>> failure.
>> >
>> > System.Runtime.InteropServices.COMException was unhandled
>> >   Message="Exception from HRESULT: 0x80040013"
>> >   Source="Interop.STATCONNECTORSRVLib"
>> >   ErrorCode=-2147221485
>> >
>> > Any ideas?
>> >
>> > Jeff Abrams
>> > Research Engineer
>> > Auction Analytics, Microsoft
>> >
>> >       [[alternative HTML version deleted]]
>> >
>> >
>>
>>
>> For those who say this is not an R issue, it is... I believe this is a
>> issue
>> with the R registration within Windows. I have all the requisite .dll's
>> in the R
>> install file, and have the R_USER and R_HOME environment variables, yet I
>> am
>> still seeing this issue. I can use other .dll's in this way, so this is
>> NOT a
>> COM issue. It is an R problem. Any thoughts would be helpful.
>>
>> ______________________________________________
>> R-devel@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>
>
>
>
> --
> Jonathan Shore
> http://tr8dr.wordpress.com/
>

	[[alternative HTML version deleted]]

