Jump to content
  • 0

You require permission from NETWORK SERVICE, Can't delete P:\5cc6ba767698f5504f4a776ed0


JazJon

Question

I've had a rouge folder I can't delete for a few years now.  I've been meaning to post about it for a while.   I've reinstalled Windows 10 and upgraded motherboards/CPU's since it's first been around.  It seems to follow the pool though forever stuck.   Suggestions?

 

image.png.9126688980a5faa8736de265b67b5b05.png

image.png.6eea48bb7f4f872aea48a59e8031e8ce.png

 

Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 0

Glad to hear it! 

And yeah, it's not a bad idea, on a new installation.

Also, my recommendation:  Use the built in groups for permissions.  This way, even on a reinstall, you won't run into this issue.
Built in accounts and groups ALWAYS use the same "SID", so it's the same between systems, every time.  Which makes things a lot more "portable".  

Only use local accounts when you HAVE to. 

Link to comment
Share on other sites

  • 0

I have a follow up question.   I reset permissions for the WHOLE pool as I said I was going to do.

When ever I try to save a PDF file to the pool I get this:
(yes my dropbox folder is on the pool, but that folder is set not to duplicate) 
image.png.10866871d59f2779a8fca275feb635fc.png

I have to save it to my desktop (which isn't part of the pool)

When I try to MOVE the .pdf file to a folder on the pool I then get:
image.png.7e7fb7f337cb8cb0787ff53b3d15b949.png

When I click Continue it works.

I have this type of similar behavior trying to save a file from a app to the pool.   

Suggestions?

Here are the properties of another folder I tried to save a different PDF to tonight

image.png.400ac1b41258e16e350ef2116b7dfd7f.pngimage.png.c067feae055b986bb354f87d58120ad7.pngimage.png.21632502e20ff357dfba323ca56b28e2.png

image.png.68507eb20cd1650f847775c7a26fb164.png

 

 

Link to comment
Share on other sites

  • 0

Uh oh, it seems that resetting permissions on my whole drive pool made EVERY single file I have appear to be totally new for CrashPlan.     Shouldn't they be smart enough to know not to re-upload the whole file again?   If I were to open a support ticket with crashplan what should I ask or tell them exactly to learn more or submit a feature request?   It took a year to complete the backup last time. :(

 

 

image.png.ec1f35f1bf92490babaf070717948403.png

Link to comment
Share on other sites

  • 0

As above, trying to emulate a new drive.

But I've added a note to the guide about this. 

 

20 hours ago, JazJon said:

Uh oh, it seems that resetting permissions on my whole drive pool made EVERY single file I have appear to be totally new for CrashPlan.     Shouldn't they be smart enough to know not to re-upload the whole file again?   If I were to open a support ticket with crashplan what should I ask or tell them exactly to learn more or submit a feature request?   It took a year to complete the backup last time. :(

Oh no!  :(

And what to tell them?  You changed the NTFS permissions, and it's re-uploading EVERYTHING. 

 

Likely, this changed the modify date, and it's uploading everything that changed, without running a hash check to see if stuff ACTUALLY changed. 

Link to comment
Share on other sites

  • 0

I received a response from CrashPlan:

 

"Hello Jon,

Thank you for contacting our Champion Support Team.

It looks like the CrashPlan app is restarting your backup unexpectedly, it is actually running a file verification scan. The scan puts ALL of your data in the To Do list. Then as the backup after the scan runs, its analyzes your files to determine if it has been backed up before and can be skipped, or if its new/changed and needs to be backed up. The percentage complete that you see is CrashPlan's progress through the current To Do list, not the overall backup.

The scan is an important and normal part of CrashPlan's scheduled activities, but it can also be triggered by several events. To read more, click on the link below:

The explanation for the lengthy time estimation relates to how CrashPlan prioritizes files for backup. CrashPlan backs up your most recent changes first. When the scan finds new files for backup, these files go straight to the top of CrashPlan's “to do” list. This impacts the estimated time to complete backup because the estimate is based on the type of files the scan is reviewing (i.e., new or existing) and your current network speed.

If you have any further CrashPlan questions or concerns, or need clarification please do not hesitate to reach out.

Best Regards,
Champion Support Specialist"

 

This seems to be the case.  The number of files sent match up but the total percentage is still off even after a FULL manual file scan. (that normally only happens every 30 days)

Things should sort themselves out over time after the complete verification "To Do" list is done.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...