ginjo / rfm

FileMaker to Ruby adapter.
MIT License
45 stars 22 forks source link

Timeout Error #37

Open prashant7090 opened 8 years ago

prashant7090 commented 8 years ago

I am new to filemaker, I have installed filemaker server. I have install rfm gem,

Following is my config in config/rfm.yml :host: "192.168.1.20" :ssl: false :timeout: 10 :port: 16000 :account_name: "somename" :password: "somepass" :database: "dbname" :ssl_certificate: '/path/to/certificatefile/certificate.pem'

I have created user model & tried to fetch first record as follow, @user = User.find(1); puts "First User: " + @user.to_s

I am getting timeout error. (Net::ReadTimeout (Net::ReadTimeout):)

ginjo commented 8 years ago

Hi, I think the problem is the port. Should be whatever http port your Filemaker server is hosting the XML interface on. Probably 80 or 443. Port 16000 is for the FMS admin app only.

Looking at your config, you should be able to drop the :port and :ssl_certificate params. Give that a try, and let me know how it works.

prashant7090 commented 8 years ago

@ginjo Thanks for your time.

I have removed :ssl_certificate params as SSL is set to false.

For port no: 1600 It gives error as "No connection could be made because the target machine actively refused it. - connect(2) for "localhost" port 1600", may be because of HTTPS.

For port no: 80: It gives error as "UnableToOpenFileError occurred: (FileMaker Error\ #802**)" may be because of "filemaker licensed key generation issue" (I am using trial Filemaker Server 14)

For port no : _443 _ : Net::ReadTimeout error.

If I have removed :port params It gives filemaker error as "UnableToOpenFileError occurred: (FileMaker Error #802)"

I wonder If there is any demo project available for "ginjo/rfm" gem integration with rails.

Thanks.

ginjo commented 8 years ago

Ok, that's progress! On port 80, Rfm is communicating with FM server. The "UnableToOpenFileError" means Filemaker was unable to gain access to the Filemaker file "dbname". This usually means that either the username & password is incorrect, or the username & password is ok but the file permissions are not set to allow access. Check the Filemaker permissions for that user & group (in "dbname" file), and make sure the "xml" extended privilege is enabled.

prashant7090 commented 8 years ago

@ginjo Thanks again! username & password is correct because JDBC connectivity is working fine, I will look it into file permissions.

dsomar commented 8 years ago

I would clarify that by file permissions, it may actually be "extended privileges" and you have to ensure the XML privilege is enabled.