Author: mikegrok
Subject: solution to NAME COLLISION in temp folders
Posted: 13 June 2013 at 11:19pm
I work in IT for a company who has a number of vertical applications. The developer who wrote the application in this case sits about 20 feet from me, so I will not find solutions to my problems on the internet in general, because the applications only run on a single computer, so I have to get into the grit of things to find out the problems.
I keep seeing "path not found", "Name not found", and "NAME COLLISION" errors in procmon when I run it on her server.
Part two also applies to "NAME COLLISION" result when doing the CreateFile operation with Synchronize in the details.
This solution applies to "NAME COLLISION" errors during createfile in the folders:
C:\Users\ username goes here \Appdata\LocalLow - the location of the dummy file backing the disk cache
C:\Users\ username goes here \Appdata\Local\Temp
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows
The solution is to login via remote desktop to the user who the task is running.
Disable IE ESC
You can get there by pressing start, then typing, "Server Manager". "Configure IE ESC" is on the right hand side under "Security Information" section.
Launch Internet explorer.
Complete the internet explorer setup with default settings.
I am not sure if this is needed:
Go to Internet Options, click Connections, click Setup, choose "Browse the Internet", Click OK
Now the folder structure is there for the files to be created in, unlike manually creating this folder structure that gets purged on reboot, now the folder structure gets recreated every boot.
Since these are temp files, they don't actually exist anywhere until they are closed. These folders are used for dynamically compiled applications. For instance I have an application that has 8 worker processes. Each worker process gets compiled on the fly (C sharp thing), and the exe is located in this folder with only the DLLs it needs, to lower the ram footprint of the processes. However on launch, there are persistent errors, until it finally works. What happens is that as soon as the compiler closed the file, the antivirus scans the file. Once the antivirus application is complete, the worker process gets launched.
So you have two options, depending on your needs.
1, stay safe.
!!! WARNING Don't do this if you browse the web on this computer, SERVERS ONLY.
2, tell your antivirus to ignore these folders.
Best of luck,
-Michael
Please post if this was helpful to you, or if you have some insight to make a better solution. This reduced the runtime of my hourly process from 65 minutes (crashing every other run) to 45 minutes.
Subject: solution to NAME COLLISION in temp folders
Posted: 13 June 2013 at 11:19pm
I work in IT for a company who has a number of vertical applications. The developer who wrote the application in this case sits about 20 feet from me, so I will not find solutions to my problems on the internet in general, because the applications only run on a single computer, so I have to get into the grit of things to find out the problems.
I keep seeing "path not found", "Name not found", and "NAME COLLISION" errors in procmon when I run it on her server.
Part two also applies to "NAME COLLISION" result when doing the CreateFile operation with Synchronize in the details.
This solution applies to "NAME COLLISION" errors during createfile in the folders:
C:\Users\ username goes here \Appdata\LocalLow - the location of the dummy file backing the disk cache
C:\Users\ username goes here \Appdata\Local\Temp
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows
The solution is to login via remote desktop to the user who the task is running.
Disable IE ESC
You can get there by pressing start, then typing, "Server Manager". "Configure IE ESC" is on the right hand side under "Security Information" section.
Launch Internet explorer.
Complete the internet explorer setup with default settings.
I am not sure if this is needed:
Go to Internet Options, click Connections, click Setup, choose "Browse the Internet", Click OK
Now the folder structure is there for the files to be created in, unlike manually creating this folder structure that gets purged on reboot, now the folder structure gets recreated every boot.
Since these are temp files, they don't actually exist anywhere until they are closed. These folders are used for dynamically compiled applications. For instance I have an application that has 8 worker processes. Each worker process gets compiled on the fly (C sharp thing), and the exe is located in this folder with only the DLLs it needs, to lower the ram footprint of the processes. However on launch, there are persistent errors, until it finally works. What happens is that as soon as the compiler closed the file, the antivirus scans the file. Once the antivirus application is complete, the worker process gets launched.
So you have two options, depending on your needs.
1, stay safe.
!!! WARNING Don't do this if you browse the web on this computer, SERVERS ONLY.
2, tell your antivirus to ignore these folders.
Best of luck,
-Michael
Please post if this was helpful to you, or if you have some insight to make a better solution. This reduced the runtime of my hourly process from 65 minutes (crashing every other run) to 45 minutes.
Johnny Lee wrote:
