mehronx Posted February 12, 2003 Posted February 12, 2003 I'm currently trying to update my server to 5.5v2 hoping that it will fix some of the problems I am having. Anyway, the updater never finishes running. I get "could not be updated because and error occured" What could cause this?
mehronx Posted February 12, 2003 Author Posted February 12, 2003 I'm also having a problem starting the server. It has been trying to start for the past hour. What could be going on here?
Newbies bartman Posted February 13, 2003 Newbies Posted February 13, 2003 Are you logged in as root in OSX? Were you logged in as root for the initial install. When I first installed OSX FMServer I was not logged in this way and had some issues. On the starting front, I had this problem after renaming FM DB files without changing the relationships to other files affected. If you have DB files in the Server folder try taking them out and starting up the server without it trying to start any files. After that try opening 1 file at a time (or folder of files) to find the conflict. Good luck. bartman
mehronx Posted February 13, 2003 Author Posted February 13, 2003 I logged in as root and reinstalled. It seems to have worked except now some of my relationships are seemingly broken. I can't find the problem, but the relationships don't seem to be working.
Newbies bartman Posted February 14, 2003 Newbies Posted February 14, 2003 Did you try to restore files from a recent backup to see if they are broken also? If you know they are correct, you could try and "restore" the culprits to see if that corrects the problem. You're losing me now....? Good luck. bartman
paulage77 Posted February 19, 2003 Posted February 19, 2003 I ran into a similiar problem with OS X and the relationships seemingly becoming broken. This happened to me when adding a new field to a database while it was being served on OS X. After adding the field, opening and closing the database, some relationships were broken. I went to a backed up version of the database, stopped the server, opened up the databases in FileMaker Pro, added the new fields, served them back up and the relationships remained in tact. Not sure if this has anything to do with what you are seeing, though.
Recommended Posts
This topic is 7947 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now