cancel
Showing results for 
Search instead for 
Did you mean: 

Temp folder is full

hi all
i m having problem in some servers
it's having hundreds of folders named like "unz8CB.tmp"
they are containing the installation files of CMA agent
they are having about 20 GB of space
i m trying to delete them but they can't be deleted because "agentres.dll" is in use
the log "FrmInst_servername.log" is having hundreds of the message

---------------------------------------------------------
20071122093609 I #5148 Stub Pkg
20071122093609 I #5148 Stub Pkg START ["C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\EPOAGENT3000\Install\0409\FramePkg.exe" /Install=Agent /Silent /ResetLanguage]
20071122093609 I #5148 Common Pkg CreateDirectory (C:\WINDOWS\TEMP\unz2EC.tmp)
20071122093609 I #5148 Stub Pkg System=1
20071122093624 I #5148 Common Pkg CreateProcess (C:\WINDOWS\TEMP\unz2EC.tmp\FrmInst.exe, /Install=Agent /Silent /ResetLanguage /FramePkg /Cleanup="C:\WINDOWS\TEMP\unz2EC.tmp" /LOGDIR="C:\WINDOWS\TEMP\NAILogs")
20071122093624 I #5148 Common Pkg WaitForSingleObject (C:\WINDOWS\TEMP\unz2EC.tmp\FrmInst.exe, -1)
20071122093625 I #6112 naCmnLib Ins Random seed = 0xbd46****
20071122093625 I #6112 Setup Ins START [/Install=Agent /Silent /ResetLanguage /FramePkg /Cleanup="C:\WINDOWS\TEMP\unz2EC.tmp" /LOGDIR="C:\WINDOWS\TEMP\NAILogs"]
20071122093625 I #6112 Setup Ins Windows 5.2.3790 Service Pack 1
20071122093625 I #6112 Setup Ins Attempting to perform a setup operation
20071122093803 I #5076 Stub Pkg
20071122093803 I #5076 Stub Pkg START ["C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\EPOAGENT3000\Install\0409\FramePkg.exe" /Install=Agent /Silent /ResetLanguage]
20071122093803 I #5076 Common Pkg CreateDirectory (C:\WINDOWS\TEMP\unz2F0.tmp)
20071122093804 I #5076 Stub Pkg System=1
20071122093819 I #5076 Common Pkg CreateProcess (C:\WINDOWS\TEMP\unz2F0.tmp\FrmInst.exe, /Install=Agent /Silent /ResetLanguage /FramePkg /Cleanup="C:\WINDOWS\TEMP\unz2F0.tmp" /LOGDIR="C:\WINDOWS\TEMP\NAILogs")
20071122093819 I #5076 Common Pkg WaitForSingleObject (C:\WINDOWS\TEMP\unz2F0.tmp\FrmInst.exe, -1)
20071122093819 I #816 naCmnLib Ins Random seed = 0xcad9****
20071122093819 I #816 Setup Ins START [/Install=Agent /Silent /ResetLanguage /FramePkg /Cleanup="C:\WINDOWS\TEMP\unz2F0.tmp" /LOGDIR="C:\WINDOWS\TEMP\NAILogs"]
20071122093819 I #816 Setup Ins Windows 5.2.3790 Service Pack 1
20071122093819 I #816 Setup Ins Attempting to perform a setup operation
20071122094106 I #5652 Stub Pkg
----------------------------------------------------------

i need help URGENTLY
thanks alot
3 Replies
tonyb99
Level 13
Report Inappropriate Content
Message 2 of 4

RE: Temp folder is full

You could do the actions below but you will probably need to reboot the server during this.

*Do you have upgrade agent in a deployment task or install agent from an RSS sensor that applies to the servers, if so disable this.
*Remove VSE
*KIll any frminst or framework sessions in memory (across all users)
*Try agent removal from server (logged in as admin users using RDP with /console switch) you can use the frminst.exe /forceuninstall command.
*IF this doesnt work hack it out of the registry
*Reboot
*Clear down any surviving files
*reinstall latest agent
*reinstall VSE

RE: Temp folder is full



thanks very much
finally i have removed these files
but i need to know what's wrong with my deployment task
i have assigned install action to CMA and applied on the whole directory
what is the best practice to avoid sending these temp files to servers and clients without real need to them
again thanks for your quick help and support
tonyb99
Level 13
Report Inappropriate Content
Message 4 of 4

RE: Temp folder is full

Servers suck at upgrading CMA agents, I usually get around 10-15% failure when an agent upgrade rolls out to servers, in these cases you end up having to remove and readd.

This could be due to the fact that they dont get rebooted every often and so may have locked uninstall files from an old version or patch, or may be due to lots of sessions in use locking files. In your case its tried to upgrade but failed again and again and just kept trying at every interval creating a new set of temp files.

I keep servers on their own deployment task (change inheritance for the task for server grouping) by moving them manually in and out of an upgrade group and only upgrade when I can monitor the results on each server, (yeah I know its a pain)