| Re: [statet-users] Compatibility problems with rj_4.0.1-4 / rj.gd_4.0.1-3 and R-3.6.2 |
|
Hi, Stephan: I followed all your instructions; I even update my eclipse to a fresh version of eclipse (2019-12), but results are the same: all work fine with R-4.0.2, but it does not work with R version 3.6.x or 3.5.x; find enclosed the obtained trace below. Some ideas about what to do? Best Regards, FGS. An error occurred while running R-3.5.1 [R Console]. R-3.5.1 / RJ (29 jun. 2020 21:14:49) terminates unexpected. The R engine could not be started. Process Error Log: jun 29, 2020 9:14:49 PM org.eclipse.statet.rj.server.srv.RMIServerControl initServer INFORMACIÓN: [Control:rjs-local-1593458089149] Initializing R engine server... jun 29, 2020 9:14:50 PM org.eclipse.statet.rj.server.srv.RMIServerControl publishServer INFORMACIÓN: [Control:rjs-local-1593458089149] server is added to registry - ready. jun 29, 2020 9:14:53 PM org.eclipse.statet.rj.server.srvext.ServerAuthMethod createLogin INFORMACIÓN: [Auth:none] creating new login (127.0.0.1). jun 29, 2020 9:14:53 PM org.eclipse.statet.rj.server.srvext.ServerAuthMethod performLogin INFORMACIÓN: [Auth:none] performing login completed successfull: - (127.0.0.1). jun 29, 2020 9:14:53 PM de.walware.rj.internal.server.gr.jri.GRSrvEngine start GRAVE: Could not start the R engine java.lang.UnsatisfiedLinkError: C:\Program Files\R\R-3.5.1\library\rj\jri\x64\jri.dll: No se encontró el proceso especificado at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(Unknown Source) at java.lang.ClassLoader.loadLibrary(Unknown Source) at java.lang.Runtime.loadLibrary0(Unknown Source) at java.lang.System.loadLibrary(Unknown Source) at org.rosuda.JRI.Rengine.<clinit>(Rengine.java:30) at de.walware.rj.internal.server.gr.jri.GRSrvEngine.start(GRSrvEngine.java:479) at de.walware.rj.internal.server.gr.jri.GRSrvEngine.start(GRSrvEngine.java:1) at org.eclipse.statet.rj.server.srv.engine.SrvEngineServer.execute(SrvEngineServer.java:194) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -----Mensaje original----- Hi Fernando, [28.06.2020 10:59] Fernando García Sedano wrote: > Hi, > > I am using eclipse 2018-12 with statET 4.0.2 and R-4.0.2 and > R-3.6.2; with R-4.0.2 all works fine, but when I try to launch R-3.6.2 > I obtain the error shown below: Are there any compatibility problem > using the new statET & RJ version with old R versions? No, StatET 4.0 and 4.1 usually works fine with R 3.6. Did you try to reinstall the R packages (make sure no StatET console is running during the update!) and double check the R home path setting? Regards, Stephan > Could you help me to fix this problem? By the moment, I have to use > the ‘old’ R version…. > > Thank you very much for your help, and best regards, > > Fernando. _______________________________________________ statet-users mailing list To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/statet-users |