Local Data Access companion weirdness -
08-09-2005
, 11:29 AM
HI all,
I have a .Net windows service that i developed to communicate with a
running instance of Filemaker 6.
In development, testing and a temporary production server, the service
was fine.
When moved to its final home however, the service can no longer connect
to the database with the LDAC. It worked the first few minutes, then
stopped. The error I got was Connect Failed. FM 6 Unlimited is
running, the table is open and sharing through LDAC is enabled.
There are only a few differences i can think of.
1. The username running filemaker on the final production box is only
a User. But if this was the problem, why did it work for a few
minutes?
2. I enabled RDAC as well... I don't think this would intefere. I'm
going to try disabling it (since we don't need it), but I'm pretty sure
it was disabled to begin with..
3. There is another table open with a script that's always running.
But during my development, i tested this scenario and FM can do updates
to another table while a script is actively running or paused.
The service is working for the moment using the RDAC, but I saw a few
errors logged; two indicated that the service couldn't find the right
rows to update (but they DO exist) and the other two said that a
certain field didn't exist (which it does.. and if it didn't, NOTHING
should be getting processed, but many other orders have been).
Any ideas whats going on? I don't think I can trust the RDAC, but I
can't get the LDAC working again.
Help!
Andy |