FMP URL protocol message
Posted: Wed Jun 27, 2018 9:39 am
Hello -
Upon starting my modified DayBack I sometimes see the message, "It appears that the FMP URL protocol is not working...(etc.)."
However, once I've dismissed the message DayBack most often works fine. Very occasionally it initially displays no events, but simply refreshing it results in normal functioning.
- I believe this started happening AFTER a recent DayBack update (a month ago?) designed to improve detection of FMP URL functioning.
- The message is more likely to appear when my internet connection is bogged down/things are running more slowly, including starting DayBack.
- It is also more likely to occur when I open my solution using FMP 15 Advanced rather than FMP 16. (These are installed on different partitions so they don't confuse URL access). Most often I don't see the message upon opening my solution with FMP 16. (FMP 16 has always started DayBack more quickly than FMP 15 when accessed from a remote location, especially repeated startups. I think 16 does more caching.)
- I've taken all the steps previously posted here vis testing and setting up FMP URL access.
- My solution is hosted remotely by Datatrium. I develop using MacOS Sierra and High Sierra, but IIRC I see the message under Windows 10 too.
Again, particularly with FMP 16, I often don't encounter the message at all.
Any thoughts?
Upon starting my modified DayBack I sometimes see the message, "It appears that the FMP URL protocol is not working...(etc.)."
However, once I've dismissed the message DayBack most often works fine. Very occasionally it initially displays no events, but simply refreshing it results in normal functioning.
- I believe this started happening AFTER a recent DayBack update (a month ago?) designed to improve detection of FMP URL functioning.
- The message is more likely to appear when my internet connection is bogged down/things are running more slowly, including starting DayBack.
- It is also more likely to occur when I open my solution using FMP 15 Advanced rather than FMP 16. (These are installed on different partitions so they don't confuse URL access). Most often I don't see the message upon opening my solution with FMP 16. (FMP 16 has always started DayBack more quickly than FMP 15 when accessed from a remote location, especially repeated startups. I think 16 does more caching.)
- I've taken all the steps previously posted here vis testing and setting up FMP URL access.
- My solution is hosted remotely by Datatrium. I develop using MacOS Sierra and High Sierra, but IIRC I see the message under Windows 10 too.
Again, particularly with FMP 16, I often don't encounter the message at all.
Any thoughts?