Filemaker Server File will not open on network:
I have been using filemaker server for some years with approx 15 solutions currently working. We use the HOST method to connect to these files.
Recently I placed a new database that will NOT OPEN, using the host or direct click to open.
I have gone through the usual:
-stop start service
-check tcp/ip selected
-Configured the required number of clients in Filemaker Server 5.5 app.
-Increased memory allocation in Filemaker Server 5.5 app.
- Checked windows permissions
I am working largely on PC some MAC. On win 2003 server. This file will open locally on my own laptop PC. So it is something to do with the network/server environment. Could recent changes in win security be blocking the opening of this file.
The error states it cannot find the file to open.
Recently I placed a new database that will NOT OPEN, using the host or direct click to open.
I have gone through the usual:
-stop start service
-check tcp/ip selected
-Configured the required number of clients in Filemaker Server 5.5 app.
-Increased memory allocation in Filemaker Server 5.5 app.
- Checked windows permissions
I am working largely on PC some MAC. On win 2003 server. This file will open locally on my own laptop PC. So it is something to do with the network/server environment. Could recent changes in win security be blocking the opening of this file.
The error states it cannot find the file to open.
ASKER
Thanks lesouef
It was set as a multi-user database so I will check the other possibilities, events log etc
It was set as a multi-user database so I will check the other possibilities, events log etc
slight correction, the file won't be open by server if not shared; since you're saying it is shared, then it may be shared "hidden".
(this feature is to avoid users to open it directly), in this case, after you've checked eventvwr log for "file opened", try to open it with a script from within another FM file: when you define a script to open another table, you can see all filed in the host files selection dialog boxes, uncluding hiddens ones, while normal file open let you only see visible files.
(this feature is to avoid users to open it directly), in this case, after you've checked eventvwr log for "file opened", try to open it with a script from within another FM file: when you define a script to open another table, you can see all filed in the host files selection dialog boxes, uncluding hiddens ones, while normal file open let you only see visible files.
ASKER
Thanks again lesouef
I didn't use the multi-user (Hidden) option just muti-user. So back to the drawing board. I have a network system admin man having a look today! The file doesn't even open if you use a direct click on the server. Yet if you copy the same file locally it works.
I didn't use the multi-user (Hidden) option just muti-user. So back to the drawing board. I have a network system admin man having a look today! The file doesn't even open if you use a direct click on the server. Yet if you copy the same file locally it works.
ASKER
Incidently I am using filemaker server version 5 on a windows 2003 network.
ASKER
I found the solution. Can you beleive after 2 weeks of soul searching all I had to do is rename the file using less characters. My origonal name was "Careers Job Seeker Information". I changed this to simply "careers" and all is OK.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for attempting to answer even though I found the solution myself. The fact that someone was prepared to give it a try is greatly appreciated. Incidently it had the xtension I just thought we had left the dos world of limitations to file names.
If you had the extension on yr name, you were exceeding the os9 limit by 3 characters (31 max) since yr name=30char. long, so that explains...
If shared, it is shared visible or hidden?
Check events log in management console to see if the file is open by the server at launch, there is a msg for every file open or closed. If it is open, then you are mainly left with the sharing stuff.
Of course this file must be system access enabled, since the filemaker service has system rights.
If you come across a weird rights pb, try to start the filemaker service with the admin account.