LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (January 2007, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Mon, 22 Jan 2007 05:56:25 -0800
Reply-To:   Anita <aheckenbach@GMAIL.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Anita <aheckenbach@GMAIL.COM>
Organization:   http://groups.google.com
Subject:   Re: Close Lock error / McAfee??
Comments:   To: sas-l@uga.edu
In-Reply-To:   <45B297BE.2040600@csulb.edu>
Content-Type:   text/plain; charset="iso-8859-1"

Hi all,

SAS just sent me this. I have passed on the info to the network guys.

anita

<=== Page: 1 === SAS Consultant === emailed w/answer === 22Jan2007 08:10:07 ===>

Hi Anita,

I found this out on the web and it definitely seems to be effecting alot of McAfee customers with different products. Here is the link for you to reference:

http://forums.mcafeehelp.com/viewtopic.php?p=428157&sid=a649078f8f1fe4faaad9524be994e051

Thank you, sandy

On Jan 20, 4:29 pm, dfis...@CSULB.EDU ("Dennis G. Fisher, Ph.D.") wrote: > Anita, > I do not know if this is related to your problem or not. We use a data > entry program that recently > stopped working and we needed to upgrade it to a new version. The > company said that it was > either a problem with a windows update or a problem with an antivirus > program that updated. We have > upgraded to the new version on one test machine that seems to be working > with the new version. > One of my staff said that she has McAfee AV on her home machine and that > it caused problems > recently with one of her programs. I am not sure what is going on, but > your description and the > timing and the program that you suspect are all too similar to some of > our problems. Let us know what > you ultimately find out. If I were in your shoes I would ask SAS if > there is a patch for this. > Dennis Fisher > > Anita wrote: > > This week, my company updated our McAfee to 3.6.0.453. I don't know if > > it is a coincidence or not, but ever since, I've been getting errors > > like this : > > > 97 data misc8.tcert;length key $100;set misc8.tcert(obs=0);run; > > > NOTE: There were 0 observations read from the data set MISC8.TCERT. > > NOTE: The data set MISC8.TCERT has 0 observations and 43 variables. > > ERROR: Close lock is not available for MISC8.TCERT.DATA, lock held by > > another process. > > ERROR: Close lock is not available for MISC8.TCERT.DATA, lock held by > > another process. > > ERROR: Close lock is not available for MISC8.TCERT.DATA, lock held by > > another process. > > NOTE: SAS set option OBS=0 and will continue to check statements. This > > may cause NOTE: No observations in data set. > > NOTE: DATA statement used (Total process time): > > > This has been on numerous different files. I've gone in and copied the > > data from misc6.tcert to misc6.tcert1 (for example) and changed the > > code to look at tcert1. It ran fine the next time - stopping at yet > > another file because of a locking problem. After re-creating the new > > file, the program is run again...and it stops at yet another file. > > > This program is on a scheduled task and runs hourly. What is the > > problem and is there a solution? > > > Thank you in advance, > > anita


Back to: Top of message | Previous page | Main SAS-L page