One computer can no longer access FMPro DB

Yes, trying to use Open Remote option. On a working machine, as soon as a user clicks on the favorite we've setup on all machines, they are presented with a user logon prompt. Once they successfully logon, the DB opens up. On the problem machine, when you click on the favorite, the error message I reported in the original message is what comes up instead. It appears that the machine just never gets to communicate or connect to the server on the other side. Can ping the server, and the same happens whether on their network or any other. I've been able to rule out a DNS issue, blocking, firewall, etc.

Attempted to install and use on a computer that has never been setup before, and get the same error. It has come to light that there was an event shortly before this started happening on the hosting side. I don't have details, but the term "crashed" was used, and "Rebuilding". We're starting to think that the issue is on the hosting site and a result of either the crash, a setting not being re-enabled, or something similar. We have our DB creator looking into this with them.

Unfortuately we no longer have any "Local" hosts to test from. We used to host this DB internally on our own "server", but since moved it offsite to the hosting facility. However, to answer the question, we get no error messages or unexpected behaviors when using the local option, or if I even manually enter the connection info (i.e. typing in fm://... etc).

However, you have sparked an idea for me that may allow me further testing to prove out if it's the host facility or not. I can bring up the old version of the DB on the "server" we have in house, and see if that yields the same results or not. May take a couple of days for me to get in there to test that out or walk them through it. I will update if I come up with any additional information.

I also have yet to contact our DB expert to see if he's made any progress working with the hosting site.

Update: I have since followed up with our DB manager and he did follow up with the hosting facility and they have come up empty handed. They reviewed all settings, options, etc. and everything is as it should be. All previously existing users are still functioning save the one listed above. We are now thinking this could be an issue between FMPro and the OS?

We have now three different machines with this error resulting. The original computer, which is a MacBook, Intel based computer, running OS 10.4.11 (Tiger). A "test" computer, which is another MacBook, Intel, but running 10.5.8 (Leopard), with the same client version of 8.0v2. Then our DB manager's Mac (don't know specific model) is running 10.6.x. (Snow Leopard).

Can someone offer any other thoughts, ideas, or suggestions as to where the problem might lie within FMPro, or what we may try next?

You rock TSGal! That did it. Thank you.

However, while this is good to know how to correct this, I'm more concerned about why we have to do this. I had a fresh install on another machine that was also fixed by doing your prescribed procedure. This is not something I ever had to do in the past. We never had to "seed" this file on installs previously, and as recently as several months ago when I did a new install on the very machine we ran into this issue with. Can you shed any light on why this may now be an issue as it is? Seems like something has changed to have brought this to the surface. They are currently at version 8 and are planning to either move to version 10 or at the very least version 9, so is it possible this issue will "go away" with the upgrade?

Thanks again for coming to the rescue.

TSGal:

Well I'm very happy we're working again, but I get nervous when the vendor doesn't know the why's for an issue? Yikes! I hate those more than anything, and I will now keep a backup copy of that file and treat it like gold. I do backups on their machines, so even if everyone had encountered the same issue at the same time, I could have retrieved this file from one of the backups. Just wonder what folks who run into this that don't have backups would do?

I can't help but think that the crash on the hosting facility side was definitely the event that brought this out into the open. Was odd though, as the one machine that did have the problem was not being used with the DB at all at that time, as the user was on vacation for a week, and upon getting back into things is when the error started on her machine. Do you know the interaction between the server/network/client for this file? Is it the network or actual server connections that interact with that file? Just curious, and maybe some of this could help you folks figure it out someday. Figure it can't hurt to give you as much info as we can about it.

I will definitely get back to you if this does continue with later updated versions as we move them forward. I think our developer might be wanting to wait until version 11 comes out before moving them forward. Is there another method of contacting you if that happens, or should I just put up another post if and when that happens and reach out to you that way? Let me know, and thanks again for the fix.

Michael Eagleson

MacMan Services

www.macmanservices.net

TSGal:

One more thing I'd like to add that I forgot to mention in previous postings, which might also be useful information.

Before I'd gotten your post about the "fix", our developer had wanted me to try out the 8.0v3 update. I installed it onto one of the non-working machines, and while it didn't resolve it I had an interesting change in how it was behaving. After installing the update, I noted that now when I would click on the favorite, instead of immediately being presented with the above mentioned error, the DB we were trying to connect to would very briefly flash up in the "Available Files" side of the window. Was never long enough to click on it, as it would disappear quickly, but even when I was able be very fast about it, and grabbed it before it disappeared again, it would then yield the original error message. Just thought it might be worth adding to the info bank.

Thanks again,