Page 1 of 1

4148 File sharing violation

Posted: Tue May 22, 2012 10:11 am
by rvancura
Greetings everyone,

I'm having issues with an open statement, it's indicating that it has a file sharing violation. The end-user receives the error code on line 310. It doesn't happen all the time though. Does anyone have an idea why they might be receiving this error? I thought the “SHR” command would prevent this error from occurring. Could it be that the end-user has the file open and it is being locked by Windows? I'm running version 3.90 and I can run tests on 4.17 too.

Thanks,
Ryan

00260 open #1: "NAME=DATA\customer,KFNAME=KEYS\customer.KEY,SHR",internal,input,keyed
00270 open #2: "NAME=DATA\RECOSTRC,KFNAME=KEYS\RECOSTRC.KEY,SHR",internal,input,keyed
00280 open #3: "NAME=DATA\INGREDS,KFNAME=KEYS\INGREDS.KEY,SHR",internal,input,keyed
00290 open #4: "NAME=DATA\RECOSTRM,KFNAME=KEYS\RECOSTRM.key,SHR",internal,input,keyed
00300 open #6: "NAME=DATA\nprice,KFNAME=KEYS\nprice.key,SHR",internal,input,keyed
00310 open #9: "name=y:\general\prichist\diffcost.XLS,replace,recl=150,shr",external,output

Error Code Info:

4148 File sharing violation
Cause
Violation of file sharing rules.
Attempt to access a file that is in use and cannot be shared
Some other computer has the file open without sharing it.
OR you need non-shared access to a file and another computer has it opened.
OR the operating system has locked the file.
Remedy
Check to see that the correct SHR parameters were specified in the OPEN
statement. If so, change the program so that it does not violate the file-sharing
rules or wait for release of the file in use. Also, be sure that your IBMNET or
Business Rules Programmer's Manual
Chapter 20 Error Codes 53
NOVELL specification (in the BRConfig.sys file) is correct
OR Ask other users to exit the file and/or reboot the file server

Nevermind

Posted: Wed May 23, 2012 2:54 pm
by rvancura
It appears this error is related to Novell server and Windows 7 OS. I upgraded the client to the latest service pack for Novell and now I can't replicate this error.

Thanks,

Ryan