Error: Cannot open/create file / The process cannot access the file because it is being used by another process

[paul666root]

Hello.

 

I tried generating LODs for SSE and I'm getting this at the end of the process and doesn't create the DynDOLOD.esp...

 

[00:31:14.641] Waiting for LODGenx64.exe to finish ...

[00:31:19.645] Waiting for LODGenx64.exe to finish ...

[00:31:24.650] Waiting for LODGenx64.exe to finish ...

[00:31:29.656]

[00:31:29.656] Exception in unit functions line 379: Cannot open file "E:\Games Instalate\Skyrim Special Edition Mods\SSEEdit 3.2-164-3-2\Logs\LODGen_SSE_Tamriel_log.txt". The process cannot access the file because it is being used by another process

 

the thing is that LODGenx64.exe is not finishing yet and DynDOLOD is trying to read the log that is used by LODGenx64.exe... what can i do to delay reading the log until it finishes generating lods?

 

thanks.

[dzee349]

Hi Sheson!

When attempting to run DynDOLOD 3 Alpha 73, I received the below error message:

Quote

Cannot create file "F:\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Grass_Map_Tamriel.txt". The process cannot access the file because it is being used by another process

Error: Cannot create file "F:\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Grass_Map_Tamriel.txt". The process cannot access the file because it is being used by another process.

I'm running No Grass In Objects with Seasons of Skyrim, and in the Grass Config file for NGIO I have OnlyLoadFromCache = False.  Might the above error message be caused by anything in particular?

 

Edited February 20, 2022 by dzee349

[sheson]

1 hour ago, dzee349 said:

Hi Sheson!

When attempting to run DynDOLOD 3 Alpha 73, I received the below error message:

I'm running No Grass In Objects with Seasons of Skyrim, and in the Grass Config file for NGIO I have OnlyLoadFromCache = False.  Might the above error message be caused by anything in particular?

 

Read the first post which log and debug log to upload when making posts.

The error message "The process cannot access the file because it is being used by another process" is self explanatory. 

End the other process before running DynDOLOD. It is possible that the other process is only visible in task manager and needs to be ended there. If all else fails, rebooting typically clears that up.

[PhxFuryKnight]

"The process cannot access the file because it is being used by another process" error when running on Wizard Mode - High Settings. 
I do not have any other programs open besides Mod Organizer 2 to launch DynDOLOD.

DynDOLOD_SSE_log.txt

[PhxFuryKnight]

 

1 hour ago, PhxFuryKnight said:

"The process cannot access the file because it is being used by another process" error when running on Wizard Mode - High Settings. 
I do not have any other programs open besides Mod Organizer 2 to launch DynDOLOD.

DynDOLOD_SSE_log.txt 1.45 MB · 0 downloads

Nevermind, I had tried 3 times, restarting my PC after the first encounter, and then again after the 3rd encounter with this same error message. On the 4th try, 2 computer restarts in total, it finished flawlessly?? xD 
Thanks man!

Edited February 9, 2023 by PhxFuryKnight

[sheson]

On 2/9/2023 at 7:15 PM, PhxFuryKnight said:

"The process cannot access the file because it is being used by another process" error when running on Wizard Mode - High Settings. 
I do not have any other programs open besides Mod Organizer 2 to launch DynDOLOD.

DynDOLOD_SSE_log.txt 1.45 MB · 0 downloads

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log and bugreport.txt (if it exists) to also upload when making posts.

[megablackk1d]

All these years I have been avoiding dyndolod because it looked way to hard to install, but I finally decide to try it. No matter what I do the process hangs and gets stuck close to 3 minutes in. This is the most frustrating mod I have ever had to deal with. Here is the log:

 

[sheson]

On 8/4/2023 at 1:20 PM, megablackk1d said:

All these years I have been avoiding dyndolod because it looked way to hard to install, but I finally decide to try it. No matter what I do the process hangs and gets stuck close to 3 minutes in. This is the most frustrating mod I have ever had to deal with. Here is the log:

Moved to the appropriate thread for the error message. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which logs and debug logs to upload when making posts. 

I will list the things that worked for people in the past. Try one at time until it hopefully works:

Make sure UAC and antivirus are not interfering. Add exceptions for all executables, also for in ..\Edit Scripts\Texconvx64.exe for example.

Update the graphics driver to the latest version. Install the driver only without the crapware or terminate the crapware before using the tools.

Check the task manager for stuck Texconvx64.exe that TexGen might be waiting for. If you terminate all Texconvx64.exe TexGen should have a related error message and stop.

Add LockTexconv=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI to see if that changes anything.

If not, test if adding RenderSingle=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI lets it run through.

If not, test if adding RenderTexturesSingleThread=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.IN changes anything.

If not, test if instructing Texconv to not use the GPU by adding TexconvAdapterIndex=-1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.IN changes anything.

If it still gets stuck, upload both the log and the debug log.

[megablackk1d]

16 hours ago, vektor9999 said:

Reverted back to 1.7.5.2 and worked like a charm, as always you are the GOAT

Thanks a lot

 

16 hours ago, z929669 said:

Please do not post your logs as text

Also, please do not double post identical topics.

I'm not sure why you are posting this in this particular forum, when the DynDOLOD application and Nexus mod pages all point clearly to the official support forum elswhere on this site. If you had read the basic info provided to everyone that obtains the application, you likely wouldn't have an issue or would have enough information to properly request support for your issue.

Moved to the DynDOLOD support forums for further input/investigation.

Sorry didn't mean to double post, and this is my first time using the site, and I thought my first post didn't go through. I'm learning how this works.

[megablackk1d]

On 8/4/2023 at 8:01 PM, sheson said:

Moved to the appropriate thread for the error message. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which logs and debug logs to upload when making posts.

I will list the things that worked for people in the past. Try one at time until it hopefully works:

Make sure UAC and antivirus are not interfering. Add exceptions for all executables, also for in ..\Edit Scripts\Texconvx64.exe for example.

Update the graphics driver to the latest version. Install the driver only without the crapware or terminate the crapware before using the tools.

Check the task manager for stuck Texconvx64.exe that TexGen might be waiting for. If you terminate all Texconvx64.exe TexGen should have a related error message and stop.

Add LockTexconv=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI to see if that changes anything.

If not, test if adding RenderSingle=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI lets it run through.

If not, test if adding RenderTexturesSingleThread=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.IN changes anything.

If not, test if instructing Texconv to not use the GPU by adding TexconvAdapterIndex=-1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.IN changes anything.

If it still gets stuck, upload both the log and the debug log.

Ok thank you. Sorry if I sounded frustrated because I was haha. I been trying to get it to finish running for days. Anyways I finally got textgen to finish, but now when trying to run Dyndolod it makes it about 16 minutes in and spits out this error message "C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds". The process cannot access the file because it is being used by another process [C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds]. I don't get it nothing else was running except Mo2, and antivirus has been shut down.

DynDOLOD_SSE_log.txt bugreport.txt

[sheson]

On 8/5/2023 at 11:16 AM, megablackk1d said:

Ok thank you. Sorry if I sounded frustrated because I was haha. I been trying to get it to finish running for days. Anyways I finally got textgen to finish, but now when trying to run Dyndolod it makes it about 16 minutes in and spits out this error message "C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds". The process cannot access the file because it is being used by another process [C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds]. I don't get it nothing else was running except Mo2, and antivirus has been shut down.

DynDOLOD_SSE_log.txt 815.94 kB · 0 downloads bugreport.txt 254.85 kB · 0 downloads

For future references, read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log to upload as well.

The program (process) tries to read/write the file C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds using OS functions. 
The OS tells the program that it is not possible because: The process cannot access the file because it is being used by another process.

Such messages state a fact.

You could try to check the the manager for all current processes (including hidden ones and services) in order to determine which one it might be and terminate it.
Otherwise a reboot typically clears that up.

[megablackk1d]

11 minutes ago, sheson said:

For future references, read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log to upload as well.

The program (process) tries to read/write the file C:\Mod Tools\dyndolod\DynDOLOD\DynDOLOD_Output\textures\landscape\reachmoss01noalpha.dds using OS functions. 
The OS tells the program that it is not possible because: The process cannot access the file because it is being used by another process.

Such messages state a fact.

You could try to check the the manager for all current processes (including hidden ones and services) in order to determine which one it might be and terminate it.
Otherwise a reboot typically clears that up.

Ok thanks, but even if I reboot I still get the same error. I'll try and see what I can do.

[sheson]

35 minutes ago, megablackk1d said:

Ok thanks, but even if I reboot I still get the same error. I'll try and see what I can do.

Are you able to delete the incomplete output before trying again?

If that is the case, try with this test version of DynDOLODx64.exe https://mega.nz/file/4BQk3C7Z#cHinjlNTRVcUyG4jL5zhFz32bf4eCbsk7IE_E612cEI

If problem persists upload new log, debug and bugreport.txt.

[megablackk1d]

8 hours ago, sheson said:

Are you able to delete the incomplete output before trying again?

If that is the case, try with this test version of DynDOLODx64.exe https://mega.nz/file/4BQk3C7Z#cHinjlNTRVcUyG4jL5zhFz32bf4eCbsk7IE_E612cEI

If problem persists upload new log, debug and bugreport.txt.

Ok I tried the new exe, and it never got past 6 minutes before it would hang, and do nothing for hours. So I reverted back and once again I get the same error message no matter what. I just want to say thanks for the help, but I have been at this for a week now haha. I think I may just continue to play without it like I have been for all these years. You made a great program by the way, I don't think it's meant to be. For me at least. Here are the files you asked for anyway. The debug file was 300mb so I couldn't upload it here. Here is the link to the debug file https://www.mediafire.com/file/8ewcfg0077vgmzg/DynDOLOD_SSE_Debug_log.txt/file. Again thanks for the help!

bugreport.txt DynDOLOD_SSE_log.txt

 

Well I unticked beyond reach from creation lod's and it worked. I was able to complete it.

[sheson]

15 hours ago, megablackk1d said:

Ok I tried the new exe, and it never got past 6 minutes before it would hang, and do nothing for hours. So I reverted back and once again I get the same error message no matter what. I just want to say thanks for the help, but I have been at this for a week now haha. I think I may just continue to play without it like I have been for all these years. You made a great program by the way, I don't think it's meant to be. For me at least. Here are the files you asked for anyway. The debug file was 300mb so I couldn't upload it here. Here is the link to the debug file https://www.mediafire.com/file/8ewcfg0077vgmzg/DynDOLOD_SSE_Debug_log.txt/file. Again thanks for the help!

bugreport.txt 511.68 kB · 1 download DynDOLOD_SSE_log.txt 830.03 kB · 1 download

 

Well I unticked beyond reach from creation lod's and it worked. I was able to complete it.

For future reference, do not post screenshots of message, use the 'Copy message to clipboard' link instead and post the text. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

See if you have more luck with this test version https://mega.nz/file/oUZi2JDA#e0mpNTqTcSaZQRpL1U0CrxkN-4W0rvSUhf---qUqycA
Upload new log, debug log, bugereport.txt in case it has an error. If it stalls, check task manager for stuck texconv processors and kill them top get it to have an error.

It is normal that when something that has an error is not done, the error is not happening. Kind of like staying in bed to not have accidents outside.

[megablackk1d]

14 hours ago, sheson said:

For future reference, do not post screenshots of message, use the 'Copy message to clipboard' link instead and post the text. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

See if you have more luck with this test version https://mega.nz/file/oUZi2JDA#e0mpNTqTcSaZQRpL1U0CrxkN-4W0rvSUhf---qUqycA
Upload new log, debug log, bugereport.txt in case it has an error. If it stalls, check task manager for stuck texconv processors and kill them top get it to have an error.

It is normal that when something that has an error is not done, the error is not happening. Kind of like staying in bed to not have accidents outside.

Sorry I didn't know. I'm very new here. But Dyndolod finally finished when I ticked everything except for beyond reach.