GP SoftwareTwitter
Opus FAQsManualCommandsObjects

Copying Workstation files to NAS Drive (UAC) issue


#10

Hey Leo,

Can you point me in the right direction where these settings are.

Cheers,


#11

#12

[quote="jon"][quote](i.e. turn off all but one of the rightmost icons on its toolbar)[/quote][/quote] Got it.

I have saved both .CSV & .PML files which one is best and what email should I send it too.

BTW thank you for your help guys.

Cheers,
Gino


#13

PML is best. The CSV won't have the stack data.

Put it in a zip & send it to me via the forum's private message facility.


#14

[quote="leo"]PML is best. The CSV won't have the stack data.

Put it in a zip & send it to me via the forum's private message facility.[/quote] See your PM thank you.


#15

Hi Gino,

The log only has profiling events turned on. This is the toolbar icon that needs to be turned on in Process Monitor:


It matters which one is on as they all control different things. Sorry if my instructions before were a bit vague.


#16

I've spent several hours analysing the log file you sent and looking into some ideas. It's impossible to say if any of these theories are definitely the answer but they all seem worth a try:

[ol][li]After seeing the problem, run Process Explorer (run it as Administrator, i.e. via UAC), push Ctrl+F and then paste the name of the file in. Does it list any processes as having the file open?

[/li]
[li]In Opus, turn off Preferences / File Operations / Copy Attributes / Copy metadata (comments, keywords, etc), then fully exit & restart Opus.

(Don't just close all the Opus windows, that isn't enough to exit the program by default. Make sure you select the Exit option, and that dopus.exe is no longer listed in the task manager Process list if you are unsure. Reboot if you are really not sure.)

[/li]
[li]The Tabbles software you have seems suspect to me, since it installs a shell extension written in .Net (which is a bad idea), and that extension is loaded near a possibly (though not definitely) suspect part of the log.

Get the latest version of ShellExView and use it to disable anything to do with Tabbles, then fully exit & restart Opus and try again.

[/li]
[li]If it still happens, go back to ShellExView, scroll right until you see the "Microsoft" column, then click so the list is sorted by that column. Select all of the non-Microsoft extensions, and disable them all -- except for the Directory Opus ones -- then fully exit & restart Opus and try again.

[/li]
[li]Go back to ShellExView and re-enable everything so things are back how they started.

[/li]
[li] You've got all three of MalwareBytes, LavaSoft Ad-Aware, and SuperAntiSpyware installed. Did you disable all three of them when you tried before? It still seems very suspicious that this is happening on two filetypes that malware scanners will often spend a long time inspecting for large-sized files.

[/li]
[li] The Acronis disk monitor / snapshot tool may be related. Just a hunch, though. If it's easy to disable it, give it a try. If not, don't worry about it.

[/li]
[li]From the log, it looks like Windows may be "prefetching" the file. Before Opus even opens it, the special "System" process appears to have the file open. As Opus reads the file, the System process is as well, via code to do with prefetching. It never seems to close the file, either.

This could be normal, and a red herring. Perhaps Windows Vista always does this when buffering large files and I just haven't noticed it before. It seems odd to me, though, and AFAIK the OS buffering a file on behalf of dopus.exe would still generate log entries that only show dopus.exe reading the file, not the System process reading it...

If it is prefetching then Windows has decided this .exe file is one you are likely to use and is preemptively loading the whole thing into memory (or trying to), which may be locking the file.

If you want to try disabling prefetching to test this theory, you'll need to use RegEdit. Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters

and change EnablePrefetcher from 3 (three) to 0 (zero), then reboot.

Remember to change it back to 3 and reboot again after testing, as disabling prefetching may reduce performance.

[/li]
[li]If you've got anything setup to automatically sync to/from network drives (e.g. Offline Folders), or anything weird like you've setup symbolic links from a directory on your C:\ drive to point to a network share, then that is worth mentioning.[/li][/ol]

If none of that helps then I'm a bit stumped, to be honest.


#17

Just to add to the long list above, it would also make sense to test the same thing in Explorer every so often, just to make sure that it really is only Opus that is having the problem. Since the problem is intermittent it may affect both programs.


#18

[quote="leo"]I've spent several hours analysing the log file you sent and looking into some ideas. It's impossible to say if any of these theories are definitely the answer but they all seem worth a try:[/quote] First thought was wow and then WOW thank you very much for giving your time to look into this.

[quote="leo"]After seeing the problem, run Process Explorer (run it as Administrator, i.e. via UAC), push Ctrl+F and then paste the name of the file in. Does it list any processes as having the file open?[/quote] I already have Process Explorer running when windows boots up replacing Windows Task Manager so do I still run it as Administrator or turn it on while its running.

[quote="leo"]In Opus, turn off Preferences / File Operations / Copy Attributes / Copy metadata (comments, keywords, etc), then fully exit & restart Opus.

(Don't just close all the Opus windows, that isn't enough to exit the program by default. Make sure you select the Exit option, and that dopus.exe is no longer listed in the task manager Process list if you are unsure. Reboot if you are really not sure.)[/quote]

No problem that should be straight forward and I can still kill the process via Process Explorer. Should I leave this setting in DOpus or adjust it back once I have finished testing the file again.

[quote="leo"]The Tabbles software you have seems suspect to me, since it installs a shell extension written in .Net (which is a bad idea), and that extension is loaded near a possibly (though not definitely) suspect part of the log.[/quote] I can remove this software for this purpose then install it later on.

[quote="leo"]Get the latest version of ShellExView and use it to disable anything to do with Tabbles, then fully exit & restart Opus and try again.[/quote] Will do.

[quote="leo"]If it still happens, go back to ShellExView, scroll right until you see the "Microsoft" column, then click so the list is sorted by that column. Select all of the non-Microsoft extensions, and disable them all -- except for the Directory Opus ones -- then fully exit & restart Opus and try again.[/quote] Ok.

[quote="leo"]Go back to ShellExView and re-enable everything so things are back how they started.[/quote] No problems.

[quote="leo"]ou've got all three of MalwareBytes, LavaSoft Ad-Aware, and SuperAntiSpyware installed. Did you disable all three of them when you tried before? It still seems very suspicious that this is happening on two filetypes that malware scanners will often spend a long time inspecting for large-sized files.

The Acronis disk monitor / snapshot tool may be related. Just a hunch, though. If it's easy to disable it, give it a try. If not, don't worry about it.[/quote]
I can remove all of these then reinstall them later on.

[quote="leo"]From the log, it looks like Windows may be "prefetching" the file. Before Opus even opens it, the special "System" process appears to have the file open. As Opus reads the file, the System process is as well, via code to do with prefetching. It never seems to close the file, either.

This could be normal, and a red herring. Perhaps Windows Vista always does this when buffering large files and I just haven't noticed it before. It seems odd to me, though, and AFAIK the OS buffering a file on behalf of dopus.exe would still generate log entries that only show dopus.exe reading the file, not the System process reading it...

If it is prefetching then Windows has decided this .exe file is one you are likely to use and is preemptively loading the whole thing into memory (or trying to), which may be locking the file.

If you want to try disabling prefetching to test this theory, you'll need to use RegEdit. Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters

and change EnablePrefetcher from 3 (three) to 0 (zero), then reboot.

Remember to change it back to 3 and reboot again after testing, as disabling prefetching may reduce performance.[/quote] I don't really like touching registry But leave this as a last option.

I don't have anything sync the only thing I has setup is a custom folder in DOpus from the toolbar but only in the last few days I have done this.

Cheers,

Gino :slight_smile:


#19

[quote="leo"]Just to add to the long list above, it would also make sense to test the same thing in Explorer every so often, just to make sure that it really is only Opus that is having the problem. Since the problem is intermittent it may affect both programs.[/quote] Will do also I have test the same thing with small files under 20mb and the same error but not on all of them.

Cheers,


#20

Exit Process Explorer, then start it again as Admin. If it isn't running as Admin then it won't be able to provide information about the System process, which looks like it may be involved.

No problem that should be straight forward and I can still kill the process via Process Explorer.[/quote]

There's no need to kill dopus.exe; just tell it to exit as per the FAQ I linked. But it is worth then checking in Process Explorer that it really has exited. dopus.exe should go away. Don't worry about dopusrt.exe, though; that can stay running.

You might as well leave Copy metadata turned off for all the tests. Once you are done testing you can turn it on (if you want).


#21

Hey Leo,

I will give it a go and report back but should I remove MalwareBytes, LavaSoft Ad-Aware, SuperAntiSpyware and Tabbles from the computer system or is it best to leave them alone as they are now.

Cheers,

Gino :slight_smile:


#22

Try removing them, but only if the things I mentioned earlier in the list don't seem to help.

As a general note, it's usually not a good idea to have multiple real-time malware scanners installed (except maybe the built-in Windows Defender + a third party scanner).

(I don't know about ones you are using in detail, though. It's possible they coexist with each other just fine, and/or that they don't install real-time scanners at all and only do on-demand scanning.)


#23

Hey Leo,

I tried the things you mentioned but no luck yet.

[quote="leo"]After seeing the problem, run Process Explorer (run it as Administrator, i.e. via UAC), push Ctrl+F and then paste the name of the file in. Does it list any processes as having the file open?[/quote] I tried it with .exe and without at the end of the file name nothing showed up at all.

[quote="leo"]In Opus, turn off Preferences / File Operations / Copy Attributes / Copy metadata (comments, keywords, etc), then fully exit & restart Opus.[/quote] Did this and left it on for the purpose of testing so I could resolve the issue.

[quote="leo"](Don't just close all the Opus windows, that isn't enough to exit the program by default. Make sure you select the Exit option, and that dopus.exe is no longer listed in the task manager Process list if you are unsure. Reboot if you are really not sure.)[/quote] I also made sure nothing was running in process explorer for thsi purpose.

[quote="leo"]The Tabbles software you have seems suspect to me, since it installs a shell extension written in .Net (which is a bad idea), and that extension is loaded near a possibly (though not definitely) suspect part of the log.

Get the latest version of ShellExView and use it to disable anything to do with Tabbles, then fully exit & restart Opus and try again.[/quote] I downloded it, ran it as Administrator mode and tried it as you suggested and also killed it in Process Explorer no luck as well.

[quote="leo"]If it still happens, go back to ShellExView, scroll right until you see the "Microsoft" column, then click so the list is sorted by that column. Select all of the non-Microsoft extensions, and disable them all -- except for the Directory Opus ones -- then fully exit & restart Opus and try again.
[/quote] No luck here either when trying this out as well.

On the other hand I could start removing other software as mentioned by yourself leo from the previous post and see what happens but will they leave some kind of information in the registry that will not help us solving this.

At the moment I can use tera copy or window explorer as they seem to work without a giltch.

I really appreciate your time leo and anyone else who has helped along the way any other thought let me know.

Cheers, :slight_smile:


#24

[quote="Gino"]Hey Guys,

I have a issue at times when copy or cut to move files from my workstation desktop to my Nas drive I get a error as shown in the screen shot. I have tried to also allow UAC on for 5 minutes still the same error occurs.

[attachment=0]Copy _ Directory Opus Moving files 15082011.jpg[/attachment]

This doesn't aways happen from time to time any thoughts? BTW even when using the cut command from opus the file remains in the original location as well as the new location.

Cheers, :slight_smile:[/quote]

Just a update I transferred this file today and it worked nothing has changed on the computer other than installed a couple of programs. I did move a file today as well from the workstation to the nas drive which was the latest DOpus .exe file and the problem re-occurred strange.

Cheers,


#25

What is the NAS drive model? Have you searched online for similar issues with this model? Have you contacted the manufacturer for their input to this?

Your NAS drive may have a log file or an option to run one. If so, I would see what it logs when this happens.

NAS drives can be particularly quirky in their communication, especially via shell replacement tools. If you can configure it to run without using an ip as a normal drive, you might have better luck. I've experienced similar issues with these and stopped using them.

If low form factor (i.e. small footprint) isn’t a requirement, old computers work great for this: They run much faster, provide higher compatibility, experience less communication issues and provide better configuration options.


#26

[quote="kgibbs"]What is the NAS drive model? Have you searched online for similar issues with this model? Have you contacted the manufacturer for their input to this?[/quote]n Have searched online and didn't find much help.

[quote]Your NAS drive may have a log file or an option to run one. If so, I would see what it logs when this happens.[/quote] I will look into this and see if it helps.

[quote]NAS drives can be particularly quirky in their communication, especially via shell replacement tools. If you can configure it to run without using an ip as a normal drive, you might have better luck. I've experienced similar issues with these and stopped using them.[/quote] Same thing need to look into this more.

[quote]If low form factor (i.e. small footprint) isn’t a requirement, old computers work great for this: They run much faster, provide higher compatibility, experience less communication issues and provide better configuration options.[/quote] I have 8tb on the nas system so I don't want to switch over to anything in a hurry yet.

Little update

I just moved a file from my downloads file folder to a external usb pen drive using DOpus and the same thing happened on the .exe file but some others moved ok. BTW I tested it with windows explorer or teracopy no problems. But I also noticed even though the error has occurred the file was moved and left behind in the original location using the cut and move form.

Gino :frowning:


#27

Hi I have the same problem. I want to back up files to the NAS. Win 10 File explorer does this, including creating new folders and deleting them. Opus noes not, at least it may sometimes!!. It strikes me that Opus should inherit all the permissions that File Explorer has, and do the same things. So there are 2 choices

  1. It should inherit the same permissions, and can be fixed to do so.
  2. It cannot do the same things and you have to use File Explorer instead.

I would like to think the choice is no 1, but at the moment it seems i'm stuck with choice no 2.

Donovan


#28

You'd need to work out where things are failing to know what's going on. We need more detail to do that.

The questions in my first reply are a good place to start.

Process Monitor logs may reveal what's happening, too, but only in addition to those questions so we know what to look for.


#29

Hi
Latest Fall Creators Update version 10.0.16299 seems to have solved this issue