Hundreds of files stored in Dropbox, and now I get this "Unknown error occurred while accessing " message when I try to open any of them. Guess I'll have to start using my hard drive to backup my Dropbox files. [Profanity removed as per Community Guidelines]
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!
Accessing files on Dropbox over a stable secure WiFi connection, through Windows File Manager or through a hyperlink in an Excel spreadsheet. In File Manager, if the file shows a check mark in a green dot, the file opens properly. But if the file shows a cloud in a gray dot (which is by far the majority), I get an error message trying to open it. The error message is different depending on whether it is a PDF or JPG file.
Yesterday I tried opening files from my phone, and the files that gave me error messages on my laptop opened just fine from my phone. That tells me that the files themselves are not corrupted, and suggests there's something in the laptop setup. But those files used to open with my laptop. And I need them to open with my laptop, because all I can do with them on my phone is view them.
Well, I don't know what's going on. I spent most of the day working in those directories. The cloud icon was replaced with a gray "X", and none of those files would open (PDFs and jpegs). Not all the files were bad (had the gray "X" and gave errors when I tried to open them), but it was the majority of them, say two-thirds to three-fourths of them. Now, I was accessing (or attempting to access) the files through Windows File Manager or through my mail client, not through the Dropbox app (version 170.4.5895). I did start up the app, and saw File Manager doing what looked like a refresh, and now all the file icons are document previews or have green checkmarks and there are no gray "X" marks. I thought that when I accessed the files through the Dropbox folder in File Manager, that would use Dropbox to open the files. Is that not the case? I always had the Task Bar icon next to the WiFi icon, so I assumed Dropbox was running in the background. Not so? Do I need to run the app?
At any rate, at this moment everything looks good. I don't know why, and I have little faith that it won't revert to gray "X" marks and error messages later. And I don't know why I could view all those files from my phone even when I got error messages on the same files from my laptop. That does suggest the issue was with my laptop, and not with the files themselves. Unfortunately, I couldn't work with them on my phone, only view them.
i have an automation that was working fine, now when i try to test it, i can't get past the trigger. the trigger works, but when i try to evaluate the conditions for the first action group (or any other action group) i get an error instead of an "yes, matches conditions" or "no, doesn't match conditions". strangely, this automation worked until now. is the error possible related to airtable general maintenance or issues and not to my automation at all. or do you guys know what kind of conditions throw such an error instead of getting evaluated. very strange
If anyone runs into this: for me it's because I accidentally went over my automation run limit while building my database and running way too many tests. Word of caution, be more conservative about your tests!!
One of my conditions was checking if Completion < 1 where Completion is a formula field formatted that properly recognizes numerical formatting. I saw grumblings in another forum post which alluded to the fact that formulas referencing lookup fields can sneakily pass through an array rather than a number which can cause automations to fail.
I thought that the new feature in the lookup field configuration to "Limit the number of items shown to the first 1" would force the lookup to return a single value, but it still appeared to be passing an array with a single number. So I altered my formula field to explicitly cast the lookup field to a string and then a number. The resulting formula:
When you see errors like "II_Close" or "II_PushRecord", these are generally un-handled errors (hence the non-descript names) In some cases, I've found that while the error appears there, that's not always where the issue comes from/could be addressed. It's possible that something is wrong upstream, but was not caught until that tool and it didn't know what to do with that error besides give this non-descript message.
To test if the issue originates elsewhere, I recommend incremental testing using a tool container. Start by putting the tool that produces this error (and those downstream) in a disabled tool container. One by one, add one more tool to the disabled container, working backwards up the string of tools. Sometimes a tool will produce an error that was not displayed before and resolvin this error will help downstream.
In your image, there appears to be an error in the Dynamic Input tool. I recommend addressing this error first as it may resolve unhandled errors downstream. If you can share more information on this error, I'm sure the Community will help.
Just ran into this issue as well and found that our database was holding onto quite a bit of memory. With some small adjustments we freed up a little RAM and Alteryx once again ran without issue. So if you have Alteryx installed on a machine that also has SQL on it, and you are using Alteryx to read to and from that database from time to time, check the memory usage and make sure there is enough to go around. Hope that helps.
Off late I have started to get "An unknown error occurred in II_PushRecord." while outputting even excel file. I am using Alteryx Designer 2020.3.5. I even ensured there is select tool before each Output tool and the field width is not more than 10000, Still I am getting the error when executing the 2020 designed workflow in Alteryx 2021 designer.
Incidently there is a Knowledge Base article of a known issue in 2020.3 -Designer-Knowledge-Base/After-upgrading-to-2020-3-receive-e... for this error message, but it was happening when writing to SQL tables. Are you in a position to upgrade Alteryx at all as support ends for the version you're on by the 29th March 2022
@DavidSkaife Thanks for your reply. After all the investigation it turns out that it was an issue with access to writing out to the output path. It didn't had read/write access hence workflows where throwing errors. Doesn't seems to be the issue with field size or need to have auto filed tool before output tool.
Currently, I am trying to train a tf model with Vertex AI Custom Training Service. The training seems working smoothly, but after about 72 hours, I get an error saying, "Internal error occurred for the current attempt," and the job restarts the training application. I have confirmed that it does train and saves a model (i put a code that saves a model if an accuracy goes up from the previous epoch).
Previously, I was using a dedicated VM instance, and the training application ran with no issues. However, i decided to move onto Vertex AI Training and changed the code to save artifacts to GCS instead of a local VM.
Since you moved from a local VM to GCS, please check your Cloud Storage logs for any errors around the time the training job fails, look for entries related to "upload failure" or an "access denied" as they are most likely the ones that's causing the issue.
Aside from access concerns, resource limitations might also be the culprit, consider tracking your training metrics like losses, accuracy and utilization for any spikes or dips as it indicates resource limitations or code issues.
c80f0f1006