How to fix Google Drive error c24e where the sync button does not work or do anything

I upgraded one of my computers to Windows 8 today, and when I installed Google Drive and chose a custom setup configuration to only sync some of my folders, I got some weird behavior from Google Drive.

After selecting all the configuration options (leaving the default folder as it is), clicking the Start Sync (or Sync) button wouldn’t do anything at all. No feedback, no error message, no alert, no event viewer message, nothing. I waited for a few minutes, tried again, nothing. I uninstalled Google Drive, tried again, nothing.

After a few minutes, I got an alert box that just mentioned error c24e, and a few more tries gave a different error: An unknown issue occurred and Google Drive needs to quit. Error: Invalid root_inodes set.

A few minutes of google searches, and found a very long Google Products Forum post about a lot of people having this very same error.

Apparently, one of the possible causes of this error is having two accounts with the same username (one local, one domain), which I had. The error has to do with folder permissions, more specifically, the account the user is logged on not having access to the created Google Drive folder by the installer, which is weird, since I installed with that user. I even tried to give my account full access to the folder, but that did not work.

Anyways, the fix is simple:

  1. Uninstall Google Drive
  2. Manually delete the Google Drive folder from your computer.
  3. Manually create a folder with the same name (after creating, confirm your logged in account has full access to the folder).
  4. Install Google Drive
  5. Success.

It worked for me. Another possible solution could be to just to use a different folder from the default one.

Hope it helps.

Windows 8 Pro Box

Hace un par de dias lei un blog post donde anuncian que la gente puede pre-ordenar Windows 8 Pro por $69.99, desde Amazon. Incluso al visitar la pagina de Amazon de preventa de Windows 8, se menciona una promocion en la que regresan $30 dolares en credito de la tienda online (si se ordena antes de Octubre 20), lo cual dejaria el costo de Windows 8 Pro en $40 dolares.

La muy notable reduccion en el precio a comparacion de ediciones anteriores de Windows (no recuerdo precios exactos, pero Windows XP y Windows 7 solian costar arriba de $200 dolares por una edicion comparable a la Pro) me hizo pensar que ahora es cuando varias empresas, oficinas y profesionistas independientes mexicanos pueden cambiarse al lado legal y quitarte de algunos problemas y riesgos.

$70 dolares. No es nada descabellado para un profesionista y mucho menos para una empresa, incluso micro empresas.

Los dos principales riesgos que se me ocurren de instalar ediciones piratas o crackeadas de Windows son:

  1. Pueden tener virus o backdoors integrados desde antes de que lo instales, para hacer tu computadora parte de una Botnet, o simplemente poder robarse informacion (hasta financiera) de la computadora en que se instale el Windows pirata. Una version legal de Windows te permite descargar tambien el antivirus gratis de Microsoft.
  2. Riesgos legales, auditorias, etc. Que necesidad de arriesgarse a multas o cosas por el estilo cuando se puede pagar $70 dolares por una edicion legal de Windows, cuyo gasto hasta se puede deducir de impuestos.
Espero que esta reduccion de precio que Microsoft hizo realmente impacte de manera positiva a las empresas y profesionistas mexicanos.

Como asignar numeros al azar (random) a un campo en SQL Server

Ayer, para probar un code fix, tuve que actualizar el valor de una columna numerica en una tabla de SQL a valores random. No recordaba haber generado numeros al azar en SQL antes, asi que tuve que buscar como hacerlo. Encontre la siguiente manera, por si a alguien le sirve:

UPDATE TableName SET Field1 = ROUND(RAND(CHECKSUM(NEWID())) * (85 - 17), 2) + 17

Donde 17 es el limite inferior, 85 es el limite superior, y 2 el numero de decimales que se desean.

La formula la encontre en la siguiente pregunta de SQL Server: fill a column with random decimal numbers

How to automate GMVault in OSX with Cron

Having just made the switch to OSX, I was clueless about how to trigger GMVault to make a quick daily backup of my GMail account. Fast forward a few google searches and I’ve got it working, but 100% the way I want it to work. In Windows, it would’ve been easy. Open Task Scheduler, find the executable you want to call, set the frequency of the task, and you’re done. Windows also provides logging for each task that you schedule, which is great.

In OSX, you apparently have a few different ways of doing it, none which I found easy or intuitive.

Automator was not helpful. GMVault is not a .app per se, so using the “Launch Application” option of a workflow wouldn’t let me select the GMVault binary. I gave up on that. I read that Launchd replaced Cron. But, Launchd appears to be XML based. I hate manually editing XML files, so Launchd is out of the question. Then there’s cron. Syntax seems fairly simple. I had trouble with Vim being the default editor for crontab. I hate Vim. So after a lot of googling, here are the steps I used.

1. crontab -l > mycron (to create a text filed called “mycron” which contains existing cron jobs)
2. echo “30 22 * * * path/to/gmvault sync -t quick > ~/gmvault.log 2> ~/gmvault-error.log” >> mycron (this added this new cron job to the mycron file, which contained pre-existing tasks, if any).
3. crontab -r (to delete all existing crontab jobs, since they will be added when adding the mycron file)
4. crontab mycron (load the previously existing cron jobs, plus the new GMVault one).
5. rm mycron

That’s it. The things I didn’t like about cron is that it doesn’t provide any job-specific logging by default. Not even when there were errors when executing the job. The other thing was that even though one logfile is for success and the other one for error (at least that’s what I got from the articles I read), running the crob job creates both files, regardless of if the job was run successfully or not. Other than that, the syntax is fairly simple. Another thing I did not like is that I have no easy way of knowing if a job executed a given day. I tried modifying the bash command to make the log filename be date-based, but haven’t been able to get it there. I’ve tried a couple of variations of the $date function but haven’t been able to get it working yet.

These are all the pages I used in reference:

Anyways. Hope this helps someone.

1 2 3 4 31  Scroll to top