License Key Conflict with Myself

[zach20]

Hello,

This morning I went to remotely open a FileMaker database from our server and got the following message upon trying to open the database itself...

"The maximum number of licensed users are currently using this copy of FileMaker Pro....

License Key conflict occurrued with user "Myself".

I don't know how, but it looks like I'm causing licensing conflicts with myself. Say for example my machine was named "Zach HD", any changes I make to the name also reflect in the license key conflict line of the message I'm getting. We're also supposed to have an unlimited license for FileMaker Pro. Any suggestions? Thanks!

[AudioFreak]

I assume the file is being hosted by FM Server. If so check the admin console it will still show you logged in.

This usually happens if you disconnect your computer from the network while connected to a hosted file or if you are wireless and you lose the wireless connection. Not sure why it would keep you logged in all night though. In my experience it usually sees that you dropped connection after about 2 min and removes you from the logged in status.

Michael

[Ender]

License key conflicts can also be caused by accessing a file from different IP/domain name references. For example, if you log in using the domain name, but the file references from other files use IP addresses.

We're also supposed to have an unlimited license for FileMaker Pro.

I'm not familiar with this. Is this that site license I've seen in their price list?

[zach20]

I assume the file is being hosted by FM Server. If so check the admin console it will still show you logged in.

This usually happens if you disconnect your computer from the network while connected to a hosted file or if you are wireless and you lose the wireless connection. Not sure why it would keep you logged in all night though. In my experience it usually sees that you dropped connection after about 2 min and removes you from the logged in status.

Michael

Doesn't say I'm logged in. The timeout is set to 15 minutes on ours, but even after restarting the FileMaker Server today I still receive the message.

License key conflicts can also be caused by accessing a file from different IP/domain name references. For example, if you log in using the domain name, but the file references from other files use IP addresses.

Nope that's not the case either. Strangely enough, the only machines affected are mine and my boss's, everyone else's works perfectly.

Is this that site license I've seen in their price list?

No I don't believe the price is actually listed, we were forwarded by a salesperson to a licensing agent who handled occasions where customers wanted to buy more than 10 copies. As to the exact price, I have no idea what it was.

[fmpwnerer]

I've also seen this false license key error caused by file references.

Especially converting from pre 7 version.

I would double check that you don't have duplicate file references, and that they point to the correct locations.

Just clean up the file references in general.

Make sure you have a copy of your files though. Deleting the wrong file reference can break relationships and cause headaches.

back ups are mans best friend ;)

[Vaughan]

I'd say the same non-VLA license code was used for multiple installs of FMP.

The install code can be checked in the About box.

[Steven H. Blackwell]

I'd say the same non-VLA license code was used for multiple installs of FMP.

Precisely.

Steven

[zach20]

The file references looked ok but I changed them anyway. The weird thing though is that before I changed them, I was able to successfully open the database remotely without any problems at all. I have no idea why, but everything has been working fine from yesterday at around 2:30PM EST up through 8AM EST now. I hope it stays this way...

I'd say the same non-VLA license code was used for multiple installs of FMP.

I thought this may have been the case as well, but all of the license keys seemed alright when I checked them.

Also when I was able to remotely access files, the same people were connected to the FileMaker Server, no more, no different, and no less.

Edited July 20, 2007 by Guest

[Ender]

The file references looked ok but I changed them anyway.

What specifically did you change?

[zach20]

...Well I feel dumb, I just had a talk with my boss and it looks like we only have 1 copy of FMP 8 Advanced (which both of us were using), everyone else just has FMP 8, which explains why everyone but the two of us could log on....I'm very sorry for the confusion everyone.

[Vaughan]

... which means the error message you got from FMP was spot-on.

Hey, but now you know your file references are OK!

[Brian S]

This is precisely the problem I am having with 8.0/8.5 access the FM Server. I just wrote this letter to FM Tech Support...

------------

Highly irritating erroneous license conflict issue with FM Server 8:

Single user license of FileMaker Pro Advanced 8.5. If it crashes or needs to be force quit, while connected to a FM Server, the app will NO LONGER LAUNCH when trying to access files on that server. It yields a license conflict error, to which there is none. The fix is... we have to SHUT THE SERVER down and restart it. My guess is to reset the license access list.

Other info:

• We have 3 other licenses, all do the same thing.

• It occurs on 2 different servers and the problem sticks with the server (whichever was being accessed at the time)

• It happens with FM Adv 8.0 and 8.5.

Is there anything that can be done about this?? It really slows things down, not to mention the inconvenience to our clients for repeatedly having to restart their servers.

[Ender]

It's not clear what advice (if any) from this thread you have tried.

If you have two servers who's files interact, it's probably the IP/domain thing I talked about before.

[Genx]

To revisit this - do not restart your server.

Because the app crashed, it was not given a chance to inform fm server of its desire to disconnect... i.e fmserver still thinks its connected. If you wait 2-3 minutes I think FM polls the client, but it will disconnect itself and you will be able to open FM up again. Option 2 is log-in to the fms admin console and manually disconnect the client - do not restart the server.

[FionaRM]

We had this problem with a PC in the office and also with my own PC connecting remotely from home.

From home, if Filemaker crashed (my PC has issues) and I tried to restart Filemaker it came up with the clash message. To solve it I restarted the PC and the problem was solved.

At the office we never got to the bottom of it. We were due an upgrade, explained the ongoing issue and bought new license keys as part of a deal.

That may not help other than to point out that there was an unresolved issue of this nature.

Fiona ;)