FM 6 server on win 2k os (not win 2k server)

[Jen Kennedy]

My file is not allowing the creation of new records on the server.

The more investigation I do, the more I'm convinced its a server

issue.

I shut down FM Server, put the files on cd, bring the cd home and

create 1000 records just fine except for one thing: My file has a

serial number that was normally 24669 and has jumped to 1866000,

however there are only 24669 records in the db.

Anyone ever seen this? Any clues?

In this investigation process I've also learned that the server room

a/c isn't on most of the time, that the server is never rebooted, and

theres someone there making changes without turning off FM Server

each time.

Are these relevant to this specific issue?

Thanks in advance!!!

Jen

[QuinTech]

Hi, Jen, and welcome to FM Forums.

My file is not allowing the creation of new records on the server.

What happens when you hit Ctrl-N?

theres someone there making changes without turning off FM Server

each time.

What type of changes? Do you mean changes in the FM Server configuration? I can't imagine that any of these settings would result in the behavior you're describing. The server should not need to be rebooted very often, unless it is also being used as a workstation, which is, of course, a bad idea. As for the AC, if it's really hot in the server room, this may cause issues, although if this record-creation issue is caused by an excessive heat malfuncion, i would think you would see other problems with your server also.

HTH,

Jerry

[Jen Kennedy]

What happens when you hit Ctrl-N?

The coffee cup comes up and doesn't let you do anything else, it just hangs.

So you know what server settings might affect this? The server isn't being used as a workstation except for when I am there and FMserver service is stopped.

Thanks!! Jen

[QuinTech]

After you try creating a record remotely, go back to the server and see if the serial number has changed.

What if you have the file open locally on the server--are you able to create a record then?

Do you see this behavior from any other client machines?

Try copying the file locally to the machine that is giving you problems, turning off the FM network protocol, and creating a new record then. Same problem?