New installation of FM Server

[Neil]

After reading through lots of documentation I am hoping someone here can help...

I am trying to successfully make a large upgrade jump from FM 3 to FM 6 in an office of about 12 users.

We have been sharing databases over our network via FM 3, running in MAC OS 9, until now.

As we have moved everything over to OS X, FM is the next thing to bring up to speed.

All the new bells & whistles in FM 6 and FMS are making the transition a bit more confusing than I had expected.

I have installed FM Server 5.5v2 on an iMac. It's not a workstation and will only be used to serve FM databases. I can start the server running using the FileMaker Server Config application. I have placed some test databases (opened and saved in FM 6) in a sub-folder to the Server Config app.

To test things out, I have installed FM 6 on my machine.

I am trying to open the hosted files, on the FM Server machine, but I am getting nothing.

This is what I am doing: File -> Open... -> [Hosts] button in the Open dialog box

I can see the FM Server computer listed, but no files appear below it. The FM Server machine is the only thing appearing in the Hosts window. Selecting and opening it brings up an admin. type window. (Trying to use the "Open File" button there doesn't work.)

So, I find myself dead in the water.

FM 3 would list open & hosted databases. FMS doesn't not. I have looked around for options to open or share the db's but I find nothing.

I am usually quite good at figuring things like this out, but this one has me stumped.

Any advice??

[Anatoli]

Are the dbs set to Multiuser and not Hidden?

[-Queue-]

It sounds as if your dbs may be set to Multi-User [Hidden] in their sharing properties. If you type in your password into the admin window, you can see all dbs that are being served, regardless of their sharing settings. You can close these files from the remote admin, open them on the server, and change them (File->Sharing) to regular Multi-User, if you need to see them in Hosts. I much prefer to hide all but the main file and any that don't automatically open when the system is started. This prevents curious users from entering a file the incorrect way and possibly (or probably) screwing things up for you.

[Neil]

Anatoli, Queue, thanks for the tips... but...

I have logged into the FM Server remotely and none of the db's appear under the tabs, or in any other areas I can view. Since I can't see them there, I can't close them.

Directly on the FM Server computer I have tried to close the db's, but they aren't even open. Actually, they can't be open (in FM6) because FM6 isn't on that machine, only the Server is. (When I dbl-click each db, it does the Mac's "I'm expanding" animation, but they don't actually appear)

I brought the db's over to my machine, which has FM6, opened them and checked File -> Sharing... They are all visible Multi-User.

What might you suggest next?

As for opening files the "incorrect way", what is the incorrect way? Everyone here is used to FM3 and are accustomed to going to File -> Open -> [Hosts] -> file.

[ernst]

Hey Neil,

You mentioned the files are in a subfolder.

I think they should be in the -same- folder as the Server Application and -not- in a subfolder.

Then you can open them via the 'admin. type window' or have them opened automatically by (re) starting the server via the Server Config app.

Hope this helps,

Ernst.

[-Queue-]

Personally, I would use opener files and never even teach users how to access 'Hosts'. A nice 'incorrect' example would be File C, that is usually opened by File A and has relationships to File D on its default layout, being opened before/instead of File A by a curious/confused user. File C's relationship to File D causes it to open without performing any on open steps, possibly resulting in the user being stuck in a layout that says 'No Access' or failing to perform steps that are vital when the file opens, or (even better) being stuck in an 'All fields' layout where they can play with fields to which they should not have access, all day long, before you realize anything odd is happening. This is why I would strongly encourage using an opener file with Open [ ] script steps mapped to the server's ip.

When you click on 'Open' in the remote admin, you should see any dbs that are not currently being hosted by the server. If you see none, my guess is that your solution is in the wrong folder.

[Neil]

Ernst, thanks for the tip. I wish it did help, however...

I moved the files up and out of the sub-folder. They are now residing in the same folder as the FM Server Config app.

(For what it's worth, there is no FM Server app in that folder.)

I have restarted the Server (via the FM Server Config window) but I the files still don't appear in the admin-type window in any way.

:(

[Neil]

Queue,

Unfortunately, it will be next to impossible to get these folks to -not- use the Hosts route since that is what they are used to. (I'm also not quite sure what an "Opener" file is.) Whatever the case though, I'm not too worried about that aspect of things, since everyone here behaves. Also, the db's we use are dead simple... a contact directory, a log of transmittals, etc. Nothing so complex that it would need to do anything special when opening or closing (or maybe I am missing the boat completely... I'm afraid I don't know FM & db's well enough to understand your last post. :S)

As for clicking Open in the remote login, I don't see any db's whatsoever.

Should I install a copy of FM6 on the Server machine, in addition to the FM Server that is already there? Or is that just asking for trouble?

[Vaughan]

Firstly, set the machine up so FMS starts itself up at system boot:

http://www.filemaker.com/ti/107911.html

Also consider installing the FMS 5.5v4 patch for MacOS X.

Check that FMS is set to network through the same protocol as your clients are using (either TCP/IP or AppleTalk, as you prefer). Then re-boot the computer.

As for getting folks to use opener files instead of the Hosts button... when you show them they can access the remote files by just double-clicking on an icon and typing their password, they'll change over very quickly.

Search the Forum for "opener file" and you'll learn very quickly about them.

[Neil]

Vaughan,

I set the machine up so FMS started itself at System Boot, as per the instructions on the page you listed. (Upon restart of the FMS machine, the boot screen listed "FileMaker Server")

However, when I run FM6 on my machine and go to File -> Open... -> [Hosts], the FM Server machine is now not visible, making me think the startup script didn't work.

(I had to run FMS Config manually and <start the Server>, and then it appeared under Hosts.)

I've download the patches and will update a.s.a.p... (Is an update needed to get this thing to work properly. Setting all this up seems MUCH harder than it needs to be.)

As for the "opener files", yes... Telling my gang they can just double click a (local) file and type a password will get them to switch in a second. I will search the Forum for more info on them once I get this FMS thing to work for me at least.

Still very much open to suggestions, and appreciating all the advice,

-Neil

[dkemme]

Is the network protocol FM6 on your machine set for TCP/IP? Double check by looking at Filemake Pro->Preferences->Application. If not, set for TCP/IP, restart FM6 and try clicking on Host.

If that doesn't make your files appear, and you are sure your computer networks are functioning well, I would try to make sure the files are open in the FMServer. Make sure you have clicked on start serving on the server machine. Although on OSX you cannot see what files are open, if you choose File->Open and the file you wish to serve is not an option to open, you know FMServer is serving that file.

[Vaughan]

FMS *is* relatively easy to get up and running. Some setting is not right, either at the server end or the client end.

Create a lettle test database (make sure it's sharing is set to multi-user) and put it into the FileMaker Server 5.5 folder. Then use the FMServer Config application to stop and start the server. Now check from a client copy of FMP for the test file.

If it isn't there then something is really wrong.

You haven't specified which version of MacOS X you are using.

[Neil]

(...and a response to Vaughan too.)

Good morning folks... Another day begins battling the FileMaker Server beast.

To catch up on the posts from last night...

Updates: I have tried to update from FMS 5.5v2 to v3 but an error "prevents the update from completing." The same happens when I try to run the v4 updater. In fact, trying to update seems to have damaged something, as FMS Config runs forever (30mins+) now and still the Server doesn't show as running. I will reinstall it.

Might this have something to do with the fact that I can't see any app called "Filemaker Server" on the machine?

Current Mac OS: 10.2.6 plain, not Server.

Network Protocol: TCP/IP on my machine. I am not sure what FM Server Config is set up as, since I can't find a place to select the Networking Protocol. There doesn't seem to be any spot to select either TCP/IP or Appletalk in the FMS Config preferences.

(Also, my local netowrk is functioning well, as people are sharing files, email & the net is up, printing is happening, etc.)

dkemme,

About making sure the db files are open in FM Server: I have manually opened the db files (by going to File -> open) and they appear to do the "expanding" things that Macs do, but that is it. I would assume that the db's are now being served, but when I go back to File -> Open they are still visible as open-able (which makes it seem like they weren't opened when I did it the first time.)

Vaughan,

I'm glad to hear that FMS *should* be easy to set up, because I have been wondering if I have been ripped off. I'm also glad to hear that you concur on the fact there must be a setting wrong somewhere. This has been my hunch too, I have just been stumped as to what setting it is.

I have created a brand new db file, made sure it is Multi-User, and put it next FM Server Config. I have stopped and started the FM Server, and again, only the Server machine shows up under Hosts, with no files being served.

I guess this means that something is really wrong.

I'm going to delete all traces of FMS from the server machine and begin AGAIN. argh.

As I do this, I just want to confirm something with all of you...

After I install FMS again, there won't be an actual FileMaker Server application I can double click on, correct? The only way to "run" FMS is by starting it up using the FMS Config app, right?

And this is because FMS runs as a daemon on the machine...?

-N.

[Neil]

I am pleased to be able report some *limited* success!

I completely reinstalled FMS on the server machine. I ran FMS Config, started the server with the button, and checked the status of things via FM Pro on another machine...

The brand new db file, that Vaughan suggested making above, was being served!

So it seems the old db files I have are "broken" in some way, even though I have opened, checked and saved them in FM Pro 6 on my own machine. (Note: Those "old" db's are basically just updated versions of ones we are still using with FM3 until I get this new FM working. So, "old" is really only a relative term, they are still healthy in another incarnation of FM.) I also triple checked that the old db's are multi-user.

Any suggestions as to how to update the "old" multi-user db's so they are shared by FM Server?

Also, I am still not able to get FMS to run and serve files automatically when the server computer starts up. I have follwed the instructions at:

http://www.filemaker.com/ti/107911.html

and do I get FMS Startup confirmation on the Mac's startup screen, but FMP cannot see the FMS machine as a host. I still must manually run FMS Config and start the FM Server in order to have it appear as a host.

Because I have reinstalled FMS since first doing the instructions listed on the above page, must I re-do all the instructions? (I installed FMS in the same place as it was last time.)

And... trying to update to FMS 5.5v3 or v4 completely buggers FMS, so I am going to avoid updating it for now. Hemce, for the record, I am still running FMS 5.5v2

Finally seeing light at the end of this tunnel...

-N.

[AudioFreak]

It's a stab in the dark but do the old files have .fp5 on them also?

[Neil]

AudioFreak, it was a decent stab. The "old" files do already have .fp5 at the end of their filenames. Their icons also appear, like the fresh new db, as a blank page icon.

-N.

[Neil]

Success!

I have managed to get the db files to be shared!

(thought I still can't get the auto startup tweak to work.)

Given my limited knowedge of FM, I suppose I shouldn't be embaressed, but I am.

Upon reading about the backup abilities of FMS, and how it temprarily closes file to back them up, it occured to me that I may have made copies of my "old" db's while FM3 was running. I went back to the original db files, quit FM3, and started again with *closed* db files. That must have been the problem, since, after updating them in FM6, they are visible through the FM Server.

Thank you to everyone for your help.

Still on my to-do list are:

- Get FMS to run and serve when the machine starts up.

- learn about and implement Opener files.

...so I will keep checking back here, as well as elsewhere in the forums, for info on those. If you have any tips, please do post them.

Thank you again!

-N.

[Neil]

For the record, I have just found Vaughan's post about opener files. I thought I would post the link to it, as it took me a while to find it. In case anyone else is in need of it...

http://www.fmforums.com/threads/showflat.php?Cat=&Number=1433&page=2&view=collapsed&sb=5&o=all&fpart=1

[Vaughan]

Firstly, document everthing that you do as you do it, so you can quickly and accurately set up another computer as a FMS later.

I'd be very tempted to reformat the iMac's disk, do a clean, standard install of 10.2 (save almost 1 GB of disk space by opting not to install the extra languages, fonts, and printer drivers) and install all the MacOS X updates. When done, make sure all unnecessary services are turned off like file sharing, web sharing etc. Set the Energy Saver not to put the CPU or hard disk to sleep, and set the screen saver to the most basic, cpu-efficient option there is. Document every option you choose, every button you click on.

Now do a standard install of FM Server 5.5 and install all the updates. Don't do the modifications outlined in TechInfo Article 107911 until much later when you know it's all working correctly.

Take the time to read the FMS Best Practices white paper (on the FMI web site) and go through all of FM Server's preferences and set them accordingly. FM Server's preferences are set with the FMServer Config program: in MacOS X choose "Preferences..." from the "FMServer Config" menu. Document everything.

Set up some Schedules to backup the hosted databases. I backup up the files every hour to a different folder on the local hard disk, plus once a day (or night really) to a remote volume or removeable disk. Document everything.

Then -- ideally on another computer -- I'd start cleaning up the database files with FMP. Convert them, then save them as compressed copies (this cleans out a lot of junk) then check their multiuser sharing status. Then copy them to the FMS machine and restart the FMS daemon. Any files that do not show up in the hosted list are damaged and will need recovering in FMP. Keep going until they all show up. (I worked on a project recently where it took two days to get them converted and cleaned up, so don't give up.)

When it's done you'll have a very stable system indeed, and with your documentation you'll be able to set up another server in less than an hour.

[Vaughan]

I just saw your post above, it looks like you don't need to do much more. Well done.

Do get the scheduled backup working asap though.

[Neil]

Vaughan,

I must have read your mind in advance, because I have done most of what you suggest above.

The machine FMS is on (a 600 Mhz iMac) had been totally scrubbed and a raw 10.2(.6) was installed.

Energy Saver has been set up to keep the machine awake and other settings have been adjusted to their most basic/efficient options.

The fresh install of FMS 5.5v2 has been working so far, but the updates just won't work no matter what, and they do seem to be damaging FMS in the process. I have tried to update twice now with consistent(ly bad) results.

I will hold off on the auto-start tweaking for now.

I have read some of the Best Practice white paper as it came with our FM package.

Setting up Backup Schedules is at the top of my list (and one of the main reasons I opted for FMS) so I will be dealing with that a.s.a.p.

I will be checking out the "compressing" of db files as it sounds interesting and a good idea.

As for documentation, you read my mind. I always do this when I tackle something new and have been keeping notes since I began this journey.

You have been absolutely amazing at providing assistance here. I simply cannot thank you enough.

-N.

[Neil]

... unless I did something wrong, I seem to have converted and compressed the db files with great ease in about 5 mins. I moved them to the FMS folder on the Server machine and they all opened (for me, coming from FMP on my machine) just fine.

Mind you, I only had 7 files to do, the largest being 2.5 MB and the smallest being 44k.

On to the Backup Schedule...

[Vaughan]

Make sure you are logged in as the same user for the update as was used for the install.

Do try very hard to get the FMS 5.5v4 update on asap, it fixes a nasty bug that corrupts your files when the FMS server deamon is shut down.

[Neil]

ok, I was FINALLY able to get the updater to work...

I had told the FMS installer originally to put FMS into Applications, with all the other applications (made sense to me at least.)

Evidently the finicky updater wanted FMS to be at the top level of the drive, so (after the updater damaged my poorly placed FMS) I reinstalled FMS where it wanted to go.

After that, the updater ran without a hitch.

As an amusing side note, the folks here in the office are dying to not have to startup Classic to run our old FM3. They keeping tossing comments around about how anxious they are... So I keep telling them that I can do it as soon as they can give me about one free hour to transfer files over and set things up, at which point they say "Noooo! You can't do that!" That, of course, makes them realize that the hold up isn't technical really, it's due to their FileMaker "addiction". It's awfully fun to convince people that the technology is fine, it's they who are the problem.

Mind you, they don't know about all the troubleshooting I've been doing here with you guys, but that's beside the point.

[Charles Delfs]

Use the FMS administration tool, (open hosts, then click FMS server first item) and then (after entering your PW) click the open button (in the admin tool that is) if your db's are 'seeable' by fms the they will list, if the are corrupt (unlikly all of them would be) then you will get an error stating they can't be opened. If they can't be seen then you've got 'em in the wrond dir.

Charles