Video Screencast Help

pcAnywhere sharing violation on .CHF file - on two machines accessing separate .CHF's

Created: 19 Apr 2012 | 5 comments

Hi all,

Just investigating an issue with Anywhere whereby two users recieved a sharing viloation prompt whilst accessing different CHF files. I tried to replicate the error by opening the same file at the same time, this did not bring the error up and just set one of the users as host busy. Also tried accessing two files from the same pool at the same time, again the error did not re occur.

Can anyone advise on how this error occurs and how to prevent it happening again? 


Comments 5 CommentsJump to latest comment

MacBrinky's picture

What version (build number) of pcAnywhere is it? (SP4?)
The platform of the host and remote could be also from interest.

MacBrinky's picture

Since SP4 the CIF files are encrypted and unique for the host.
So you cannot copy these CIF files around.

AJWild's picture


where on 11.0.0 build 730
the machines that got the violation are both on win7 


AJWild's picture

what do you mean copy them around?

the files where on a shared server folder

ICHCB's picture

11.0 isn't compatible with win 7

Mac's comments are that the newest 12.5 sp4 locks the files to the system that launches them so you would need to copy the master list to each 12.5 sp4 system before launching them and then the copy when ran they will then lock to that 12.5 sp4 install.  

but if you are working with 11.0 that isn't the issue.  Unless some one opened one of these with 12.5 sp4 they will be upgraded and no one except that one can use them.    There is a utility that can then unlock them awFileMgr.exe.  If you identify who locked them you can run the awFileMgr.exe unlock utility .

Importing and exporting configuration files

By default, host and remote configuration files will be encrypted. If you wish to move one of these files to another computer, you must first remove the encryption using awFileMgr.exe.

After you remove the encryption, you can move the file to a new system and import it using the same tool. The import process encrypts the file with the key of the new computer.


If you find this post helpful please give it a thumbs up!
If you find that this solves your problem please mark it as the solution!