Connection to the server

[milanm]

Hi,

EasySync looks to me as a great solution and i am tr(d)ying hard to get it to work for my client but unfortynatilly not getting it right yet.
here is my latest frustration, i am wondering did anybody experience this yet and what could be the cause.

 

DESCRIPTION:

 

I downloaded and installed the demo files, placed them correctly on the server (Windows 2012) and on the iPad (iOS 8), setup the external data source, tested - and it WORKED just fine.

 

Than i went over all the steps suggested to prepare the real working database. I obviously got something wrong as it was taking ages to do something and didnt work at the end.

I got stuck on various kind of messages that gave more or less hope that it will almost work with some fixes but finally i got stuck with the message like: "Unable to connect to server".

 

ISSUE:

 

Message "Unable to connect to server" is showing SUDDENLY after a few times i have tested the files with the similar setup and it worked. I can reach and open the hosted files using the same IP and file path from the same unit (iPad and PC) so the path to the hosted file should not be an issue.

 

Does anyone have an idea what could be happening here?

[timdietrich]

Milan --

 

In your mobile database, what does the external data source's "file path" look like?

 

-- Tim

[milanm]

Hi Tim,

thank you for responding really appreciate it, i could imagine how bussy you are and i can see how much effort you already made building this excellent solution, i could only say thank you and WOW.

 

My file path goes like this:

fmnet:/31.209.186.202/FM_Surveys_Hosted_v1r3

 

This is a public IP and i managed to get it connected at the first.

When i wanted to test "Wipe" and "Reset" it removed all the data from the mobile file and from there on is refusing to connect to the server.

When i run the script in debugger - it shows this error message "Unable to connect to the server" on the segment of the script "Ping Server" from the mobile file under the comment line reading "# If there was a problem with the ping..." somewhere close to the bottom of that segment.

 

I will repeat that i am able to connect to the Hosted database directly from my iPad or PC using the same path and it also worked for the sync at some point before i executed "Wipe" and "Reset".

[timdietrich]

Hi Milan.

 

I did a ping test on that IP, and it came back with 0% packet loss after 100 pings. So the server's connection seems reliable.

 

You might want to double-check the "Ping Server" script. At around lines 13 and 17 (just after the comments that read "*** Remote Script: Respond to Client Ping") you should see "Perform Script on Server" and "Perform Script" steps. Both of those should be referencing a script in the hosted database named "Respond to Client Ping." It could be that those steps aren't set properly, in which case the response from the server would be something that the ping test isn't expecting. (It would throw the "Unable to connect to the server" result that you're receiving.)

 

Thanks, and good luck.

 

-- Tim

[milanm]

Hi,

yes, it seams to be a problem with these scripts. When i open the script "Ping Server" and set the script availability dropdown in the bottom left corner to "Server", i can see that these scripts (together with some others) are grayed out, which should indicate that they are not working on the server i assume (i got my certification for FM 13 but i am still trying to fully figure out the "Perform script on the server" feature).

I am working on this system in a team with another FM developer and a Windows Server specialist - could it be that something is done on the server which would gray out these scripts and prevent them from being executed? This happened really suddenly, at one point it was working and than suddenly it stoped working, might be that the other developers did something to prevent the scripts from being executed on the server.

I will test the whole process on my testing server now to see if this might be what is happening.

[timdietrich]

Milan --

 

The grayed out scripts sound like the problem, although I've never seen this before.

 

Have you tried doing a sync with the PSOS options ($$use_psos_during_ping, $$use_psos_during_push, etc) disabled? Could it be a permissions problem, where the account that you are syncing with doesn't have permission to even run the EasySync scripts?

 

-- Tim 

[milanm]

It seams to be the server issue of some kind.

I now loaded the same demo files you provided to my testing server and everything works fine in regards to the connection.

It is giving me error 6 though (the attempt to push data to the server...) but that kind of error i will be able to deal with i hope.

The scripts are still grayed out but they seem to be working.

I guess now i have to go to the Server 13 documentation to get into detail about PSoS feature and in which cases would it be disabled on the server.

Sorry Tim, it appears that i was pullling you arround for reasons that are not directly related to EasySync, i hope at least the readers will find this helpfull as an information on what could happen.

Thanks a million.