Good morning!
Mcafee decided to change the way that is decompresses its SDAT update files. It used to be performed in the Mcafee folder under program files. Now it is in the windows temp directory. However, this was in March when the change was made. The file SDStbRes.dll is a temp file and is only on the drive for as long as the Dat update is going on. If it can't be accessed in the temp folder, this error will occur.
We were running fortres grand on our workstations (desktop security program) and had everything set up correctly to allow the updates on our workstations. As soon as Mcafee changed the format, this error came up on all 600 of our workstations. After two weeks of looking at fortres log files and file traces we entered in a line item into fortres to allow write access to the temp directory and it quickly fixed the problem. However, this is security risk, but tough to know where to exploit it to the average user. Here is the email I recieved from Fortres Grand:
Unfortunately, this will cause a potentially serious security risk. You
will have to enter the following as a Privileged Application:
C:\WINDOWS\TEMPFiles not to Protect:
The directory that they are going to copy files into.
Eric
This is the message I originally sent to Fortres Grand Tech support:
I have an interesting problem.
Mcafee decided to change the way their SDAT file uses the windows temp
directory.
We are getting this error: SDSTbres.dll. One of the library files needed to
run this application can not be found.
Fortres is causing this because it is blocking the file.
My question is this. The SDAT file is downloaded into the windows temp
directory and extracted there. The temp directory path and file name is
variable
c:\windows\temp\1e211fg.tmp\sdat4256.exe ( file name will be different next
week, SDAT4258.exe i.e)
How do I enter a privilaged application with variable paths and filenames ?
You can thank Mcafee for this one. I think it used to be extracted in the Mcafee folder.
If you have this error and do not have Fortres, I have heard that some people have rights issues to the windows temp folder on NT boxes that can cause the same thing(install rights).
If I can be of any further assistance, please let me know.
Hope this helps.
