ESET Endpoint Protection Update Fails

[Richard Conram]

Issue seems related to the one described here

The Log does not give a lot of information.

2012-06-19 08:36:31 Update module Error creating temporary file name. NT AUTHORITY\SYSTEM

W7x64, new setup of Endpoint protection, updated has worked previously, but fails since two days back. There is a Temp folder, both for user profile and for Windows, no parameters changed, no access rights changed. I have cleared the update cache in Endpoint.

Any more suggestions?

(I am running a dual boot with XP, and have three partitions on the harddrive, but C: is of course still C: in the active OS)

[agoretsky]

Hello,

Have you tried deleting the contents of the %WINDIR%\TEMP directory and restarting the computer? If so, did that make any difference?

Regards,

Aryeh Goretsky

[Richard Conram]

Emptying %user% and %windir% temps was done prior to creating this thread.

[agoretsky]

Hello,

Perhaps a permissions problem on the %WINDIR%\TEMP directory itself? Try RMDIR'ing the actual directory and rebooting into the same operating system to allow the operating system to recreate the directory with proper permissions.

Regards,

Aryeh Goretsky

[Richard Conram]

Well, I always alter the envirnmental variables for %TMP% to a root:\Temp directory (often on another drive or partition). Have it on other PC's so should no be an issue. Easier to clean.

Have been without that comp a couple of days so my feedback is lacking a bit. Will try to look at it again tomorrow.

[Richard Conram]

Still same issue, I have to retract previous statement about altering environmental variables path to temp. It is unaltered in that computer.

Failed to create temporary file.

I looked for the AV def files to make an offline update, where are they?

The closest official KB for this is probably http://kb.eset.com/esetkb/index?page=content&id=SOLN39

[Geosoft]

Hi Richard,

When you are changing the system temp file directory in the system variables, you would also need to make sure that you are setting the proper security groups to use that new path. For example, C:\Windows\Temp isn't inheriting permissions completely and has a group called "TrustedInstallers" with List and Special NTFS Permissions. System also has Special NTFS Permissions as well. If you neglect to set these, you are going to see odd behaviour in general.

You are better off not changing the %temp% variable and pointing it into a new location but rather leaving it at the Windows Default.

[Richard Conram]

I did not. I know about that, but it tuns out I did not change it. Please read my posts.

[Richard Conram]

Just uninstalled, cleaned system and rebooted. And reinstalled Eset Endpoint Security. The installation goes well. I reboot. EES loads well, all is ok, but then I trigger an "update" and the same error appears again.
It tries to download "em_001_32_I0" something and some othe definitions,but fails with the same error specified above.

I am opening an official support case.

[agoretsky]

Hello,

Please be sure to include an ESET SysInspector log when submitting the ticket. That may help speed up the response from support.

Regards,

Aryeh Goretsky

[Richard Conram]

On it. Was told to do the manual removal and then to use the web installer. After that, SysInspector with logs.

However, the web installer cant find my license. Updated info to supporter (Andi Olsen), and requested advice.

[Marcos]

Deleting the content of the system temporary folder should fix the error mentioned in your initial post.

[Richard Conram]

Well, it did not.

[Geosoft]

Would manually deleting the contents inside C:\ProgramData\ESET\ESET Endpoint Antivirus\Updfiles fix anything?

[Marcos]

Should the problem persist, create a Process Monitor log from an attempt to update, compress it, upload it somewhere and PM me the download link.

[Richard Conram]

Sorry for tardy input.
We seem to have verified that the issue is caused by defining the system and/or user %temp% folder to other path with a folder name that EEP is unable to handle.

It is fine to allocate the paths to other folder or other folder on other drives, that is not the issue, however, do not name the folder using $ or % as first letter. For safety, use only alfanumerical characters in naming.

Case closed.

[agoretsky]

Hello,

Could you let me know the redefined paths you used which caused the problem?

Regards,

Aryeh Goretsky

[Richard Conram]

User: f:\%tmp%
System: f:\%tmp%

Edit:

In here: http://www.computerhope.com/issues/pictures/winpath.jpg

[agoretsky]

Hello,

Just to check, F:\ is a local, direct-attached (e.g., non-removable) disk volume?

Regards,

Aryeh Goretsky

[Richard Conram]

Yes. A secondary NTFS partition, in this case on the same physical hard drive.

[agoretsky]

Hello,

I have spoken with ESET's developers about this and the issue will be addressed at some point in the future, however, I do not have a timeframe for when that will be.

Regards,

Aryeh Goretsky