Statconn basic server test fails to connect with R 3.0

[terrya]

Sorry no. What was the exact error message? Also, did you try the XOPEN command in EViews? Maybe that would provide a better error message.

1. Error message: Method '~'of object '~' failed

2. Eviews failed to initialise

[Phreeze]

*up* no answer for this ?

we get the same Method ~ error.

It must be known by the eviews team i guess ?
os is win7 x64 enterprise with eviews8 and R 3.0 + latest statconn plugin

[EViews Steve]

terrya:

That "Method '~'of object '~' failed" error you’re getting is a problem with how statconnDCOM is setup on your machine. It has nothing to do with EViews. Given that, I would try the following:

1. Re-install 32-bit R and make sure that the option to "save the path and version information" in the registry is selected.

2. When you run R, make sure you are running R 32-bit. When you launch R, look for the title in the main window. It should say “RGui (32-bit)”. Or look for the “Platform” line (usually this is the 3rd line from the top) in the “R Console” window. It looks something like this:

Code: Select all

R version 3.1.0 (2014-04-10) -- "Spring Dance" Copyright (C) 2014 The R Foundation for Statistical Computing Platform: i386-w64-mingw32/i386 [b](32-bit)[/b]

3. Make sure you installed the “rscproxy” library properly inside of R. You can check for the existence of “rscproxy” by typing in:

Code: Select all

require(“rscproxy”)

and make sure it returns something like this:

Code: Select all

Loading required package: rscproxy

Assuming that steps 2 & 3 are ok, you may need to reinstall the statconnDCOM package by re-running their installer.

Finally, try their test program again.

Beyond this, I'm not sure what to tell you except to try a different machine. I've done these steps on Windows 7 & 8 and their test program works fine for me (as does EViews).

Steve

[terrya]

Thanks for the reply.

I've already carried out these steps in the past and they didn't work. But I'll try again soon. I don't use anything than 32-bit software so that is unlikely to be where the problem is located.