I am Trying to update my Filemaker Server 7 to v2 and it stops at item 104 (pretty close to the start). Any ideas why, the server was off at the time.

Here is a console log of what happens when I try to update

===== Mon Nov 15 2004 ===== 14:32:37 US/Eastern =====

cp: symlink: ./A: File exists

cp: cannot overwrite directory ./FileMaker Server Admin.app/Contents/Frameworks/ABCFoundation.framework/Versions/Current with non-directory ../FileMaker Server Admin.app/Contents/Frameworks/ABCFoundation.framework/Versions/Current

cp: cannot overwrite directory ./FileMaker Server Admin.app/Contents/Frameworks/ABCFoundation.framework/Resources with non-directory ../FileMaker Server Admin.app/Contents/Frameworks/ABCFoundation.framework/Resources

cp: symlink: ./A: File exists

cp: cannot overwrite directory ./FileMaker Server Admin.app/Contents/Frameworks/ABCApplication.framework/Versions/Current with non-directory ../FileMaker Server Admin.app/Contents/Frameworks/ABCApplication.framework/Versions/Current

cp: cannot overwrite directory ./FileMaker Server Admin.app/Contents/Frameworks/ABCApplication.framework/Resources with non-directory ../FileMaker Server Admin.app/Contents/Frameworks/ABCApplication.framework/Resources

  

This looks like a UNIX permissions problem. Are you logged in as root?

You don't need root per se, but you need to run the updater with the same account you used to install FMS.

If you are, try running 'repair permissions'. If that fails, uninstall FMS, install it again and before running it immediately install the updater.

Repairing permissions didn't help and I tried root user yesterday, but a clean install fixed it.

When I ran into this problem, I trashed the old files and found some that were still running, even though I used FMS Admin to stop the server. I wonder if this is why some have had success installing the update after restarting their machine or updating just after reinstalling?

Had the same problem. Just tossed everything, repaired persmission and reinstalled. Finally worked.