Zip Corrupted

0 views

Skip to first unread message

Wynellewe Gr

unread,

Aug 3, 2024, 10:21:43 AM8/3/24

to kyopekawin

I need help please with a corrupted folder. The other day, I saved a Word document in that folder on my desktop PC. It has not worked since and every time you click on the folder it says: "The file or directory is corrupted and unreadable."

I have already tried 'unlinking' the PC account via Dropbox.com. I have also tried (several times) un-installing/re-installing the Dropbox app on my PC, I have also cleared the Dropbox cache on the PC, and have also tried disabling Avast antivirus while doing this. Nothing works. The folder is also still fine, when accessing via Dropbox.com and via my iPad and iPhone. Currently, the desk tray icon has a blue circle, as if its synching but cannot finish synching. The folder itself has a red/white cross by it. I have also tried View Synching Issues, but again no joy. I even entirely deleted the folder from my Dropbox account and the corrupted 'empty' folder still came up when I re-installed the Desktop Dropbox app. So maybe this corrupted version is somehow stored in the PC, somewhere? I have also cleaned off any Malware. So that has been done. Also, I should add that I have managed to successfully add other Word files since this occured - so Dropbox itself, via the Desktop app, is working. Its just this folder that is corrupted.

Anyway, luckily it doesn't matter, as I managed to solve the problem myself. Something I'd already tried once before but this time it worked. I unlinked the PC account, deleted the entire folder from my Dropbox account, then cleared the cache, and then re-linked Dropbox app to my PC and then re-loaded the folder back into Dropbox by dragging and dropping the files online. That seemed to work fine. No more synching issues. I'd tried this before - and it wasn't working, but maybe I did something slightly differently then. Anyway, I've not stored the original Word document that caused the problem in Dropbox again in case it causes an issue again, but otherwise, all is working smoothly.

If this doesn't resolve the issue, please follow the steps again and instead click "Fix permissions". The app might need to sync for a while after doing this, so please just keep an eye out for any progress.

If the issue persists, can you let me know if there are any errors shown in the sync status of the desktop app? You can see this when you click the Dropbox icon along the bottom of the small pop up window.

Did this post help you? If so, please give it a Like below.
Still stuck? Ask me a question!
Tips & Tricks Find new ways to stay in flow or share your tips on how you work smarter with Dropbox.

Should I 'unlink' the account from here? That's one thing I have not done before (I did it previously by signing into dropbox over the internet, then clicking settings and then security and then 'unlink PC').

You may need to click on a blank space within the window before holding the Space bar if the option doesn't show up at first. It may take a second to appear so please keep the Space bar pressed for a short period.

Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join!

Generally speaking, it's a good idea to run a module from the Scheduler database instead of a local path unless that module is going to be updated frequently, and you want the module updates to be reflected when run from the Scheduler. If you do need to Schedule a module from a local path, however, there's several possible reasons why a module run can end up a "corrupted" state, but most likely the module isn't being found correctly by the Scheduler when it's time to execute.

When running module from a local location, it's critical that the path you choose is available to (and readable by) the Scheduler, otherwise the module will not be located and execution will fail. By default, the Scheduler will execute a module as the System account, but your Scheduler may be configured with a "Run As" user in the System Settings dialog:

Regardless of the user under which your Scheduler is running, the module path must be available to that user. If you schedule a module from your local account referring to a drive alias (for example, G:\my_modules\module.yxmd) or UNC path (for example, \\remote_drive\my_modules\module.yxmd), that same path must be available to the Scheduler.

If you have further questions or continue to have difficulty, feel free to follow up here. I would also encourage you to reach out to your support contact at Alteryx or to Client Services (clien...@alteryx.com) so we can resolve this matter quickly.

@ericy330 -- If @SteveA's suggestion did not work for you, you might want to try downloading the newest version of Alteryx (10.1, which was released yesterday). I was having a similar issue as the one you're seeing, and it's been fixed with 10.1.

The log is telling us that the Server does not have permissions to access those shared resources (the UNC paths). You need to ensure that the UNC paths accessed by the scheduled module are readable by the account used by the Server when processing workflows. By default, the Server will run workflows as a Service account, but that can be changed by specifying a "Run-As" user on the Server as described in this thread.

Make sure you open the workflow that you want to schedule from the network location before scheduling. So when you open the workflow initially, browse to the network location instead of the absolute location and then schedule. This worked for me.

It sounds like (and please correct me if I am missing anything) that you are out of space on your Disk Library, and that you have a corrupt store (likely the ddb that tracks the jobs using this same library. Checking the jobs for that store/storage policy, you are seeing several jobs showing BASIC CYCLES as their reason as not pruning.

The i have 3 sealed (status:offline) and 1 active DDB (status:ready), all of them have corrupted partitions as when i try to run data verification job, the error mentioned previously happens [62:2483].

I searched for DDB prune process, and i must wait for the data age to age out naturally the jobs from the DDB, but that will take at least 6 days OR another full backup to increase the cycle count, and in the meanwhile no backups are running, am I reading this situation right?

I could set the retention policy to 0 cycles so it gets pruned and the get back to 1 cycle?

A nice trick I use is to set the cycles to 0 (this works for any retention change you are considering), then run the Data Retention Forecast and Compliance report. If you like what you see as far as which jobs will age and which will remain, then go ahead and kick off data aging.

But if I set the cycles retention to 0, wont I lose full backups that are over 6 days of age?

I think they are stored in tapes by running auxiliary job, so i can probably restore if needed...

The process of freeing up disk space lags behind Data Aging because Commvault uses a distributed approach to identify deduplicated data to be physically pruned. The Job/Object Level Data Aging is done on the CommServe SQL Server DB, and the Commserve will communicate to the MediaAgent SIDBEngine regarding the status of aged deduplicated jobs/objects. Blocks held in the Primary (Single Instance) table that have been aged get picked up by the SIDBPrune process that moves them into the Zero Reference table. The SIDBPhysicalDeletes is the process that is used to physically delete the storage blocks.

The .PRUNABLE generally means something will be deleted in that folder if not the entire thing. I would suspend any jobs that are running to this library as well as running jobs will hog up the DDB related resources (things are FAR BETTER in v11).

That said if in the time since you adjusted retention that you are not seeing any data reclaimed on storage libraries, and your Data Forecast Report is shown that you should be reclaiming space then (if you are using Commvault Simpana and not just DDB that is V10), the log files that would be used to troubleshoot are SIDBEngine, SIDBPruning and CVMA. The CVMA log will inform you on the progress of physical deletes.

I've owned the MK63 mesh system (MR60 with two MS60 satellites) for over 1 year with no major issues. Recently upgraded the FW using the app to v1.1.6.122. The FW pushed through the MR and one of the MS satellites fine, but not to the 2nd MS. The impacted MS has a slow pulsing white light, which tells me the FW was corrupted during the update and never made it to the device. It seems the 2nd MS is not recognized anywhere in my network, but the app shows it with a purple dot. I even accessed the network via and the impacted satellite is not visible at all.