File sharing lock count exceeded. (Error 305

[yunwang]

I am trying to synchronize a replica to the master project. I got this error:
File sharing lock count exceeded.  (Error 3052)

What is the cause of this error? How to fix it?

FYI: EA Program Version 4.10.738.


Thanks

[AshK]

Hi Hun,

It seems that this problem is related to a Jet 4 issue.  You may find this link of intereset - it contains a potential remedy:

http://support.microsoft.com/kb/q198633/

Ash

[yunwang]

Following the instruction in the linked page, I increased the MaxLocksPerFile setting. But I still get the same error. I have to use export/import to get my changes into the master project. Will do more frequent synchronizations.

Thanks

[thomaskilian]

What jet version do you use for the EA repository?

[yunwang]

I did not check "Use JET 4.0" in my EA. I am not sure what is in use for checking the file sharing lock count.

[AshK]

If "Use Jet 4.0" is not checked then EA will be using the Jet 3.5 interface.

As a result, I don't think that the 4.0 registry settings will be active.

You may try manipulating the keys relative to 3.5:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Jet 3.5

I hope this helps.

Ashley

[yunwang]

I have tried to increase both 3.x and 4.0 from 9500 to 299500. I still have the same error:(

I also tried to check the Use JET 4.0 in EA. Then I got the following error when trying to open the replica or synchronize the replica or uncheck the Use JET 4.0:

---------------------------
EA
---------------------------
DAO.Database [3703]

Operation not supported on replicable databases that have not been converted to the current version.
---------------------------
OK  
---------------------------



Yun

[thomaskilian]

  You're right. Replication does not work with Jet 4.0. Why

[nara_c]

Hi,

I experienced the same problem when trying to setup replication on a EAP file.

EA displayed the following error when I tried to create a Design Master:

"Operation not supported on replicable databases that have not been converted to the current database"

I am running EA ver 5.00.770.

I initially had Jet ver 4.0 turned on.  I thought this could be the issue and turned it off (going back to Jet 3.5) but the issue persisted.  

The following series of steps show how I got around this issue.

Resolution to Design Master error
Then I opened EAP file in Access 2000 and was prompted that the file was created in an older version of Access (Jet 3.5).  So I selected to upgrade the database version to Jet 4.0.

Creation of Replicas
Once this was completed I went back into EA and was able to create the Design master and replicas.  I tried synchronisation by making some sample changes and it worked fine.

So far so good.  I created 3 replicas for my team and want to see how it goes.  

Advice please!
Since this is a large model that is likely to grow exponentially, I am wondering if anyone has advise on this approach.  Earlier I was using the Import export option and this was getting tricky hence the shift in synchonisation approach.

I am a bit concerned from this post that some of you are facing problems as the size increases.  My current EAP file is around 15 MB.  

Is the replication solution reliable or should I stick to Import/Export of remote files?  Way I figured it, if replication falls over at some stage I can still use the Export/Import option.  Is this advisable?

Thanks
Nara

[sargasso]

Things may have improved in the last two years, but ....

IMO Jet replication is (was) a dog.  You'll end up spending more time jigging replication errors than you ever would trying to manually synch model copies in a small team.

There is a ton of stuff on the net about jet replication problems.  

sadly...

bruce