User forced to close connection.

[Anatoli]

User "Username" [192.168.128.35] forced to close connection.

Why is this in log?

Why the user was disconnected?

[Kurt Knippel]

Automatic logout after a period of time?

Force-Quit/Crashed application on the client machine?

User kicked out by developer?

"Username" sounds like an install which did not have the Filemaker machine name set, or possibly an OS install where the machine name was set as "Username" for default login purposes.

Is the IP address a valid one in this case? If so what machine does it point to?

[Anatoli]

RE: Automatic logout after a period of time?

I never used that. That was the first thing I've checked

RE: Force-Quit/Crashed application on the client machine?

Nope. The machine was working overnight and I checked that several times. Nobody has access to that room.

But it is possible, that FM just crashed by itself. But there is nothing in log! (W2k)

RE: User kicked out by developer?

Unlikely. The only other developer is on holiday

RE: "Username" sounds like an install which did not have the Filemaker machine name set, or possibly an OS install where the machine name was set as "Username" for default login purposes.

There is valid user name and that machine is working OK for 2-3 weeks. I've just used the "Username" to give it some meaning in post. Sorry

RE: Is the IP address a valid one in this case? If so what machine does it point to?

Yes, it is working OK 2-3 weeks.

Thank you.

It is still mystery to anyone...

[CyberSport]

was it prefaced by another user wanting exclusive access?

and the passwords for this individual don't have "disconnect when idle" checked?

bevin

[Anatoli]

Nope.

It is the Script Machine, which is running the scripts every night.

AFAIK it just happened because the Jupiter was at too close to Saturn.

Still this is better explanation, than FM techsupport will give me, so I am OK with that.

Today it was running fine...

[Kurt Knippel]

I've seen Filemaker Server do some goofy things with users that didn't exist and this may be what happened here. Usually a restart of the server fix the problems. This was under FMS 3 though.