After updating odrive logs such error and exiting immediately:
[ERROR] 2020-11-10 08:13:00,019: Got UnicodeEncodeError exception 'ascii' codec can't encode characters in position 9-13: ordinal not in range(128)
[ERROR] 2020-11-10 08:13:00,019: Traceback (most recent call last):
File "<string>", line 177, in main
File "C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts\build\odrive\WinOdrive\out00-PYZ.pyz\src.odrive_app.Launcher", line 167, in launch
File "C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts\build\odrive\WinOdrive\out00-PYZ.pyz\src.odrive_app.Launcher", line 121, in _launch_app
File "C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts\build\odrive\WinOdrive\out00-PYZ.pyz\subprocess", line 394, in __init__
File "C:\hudson\workspace\Odrive_Win_Master_Launcher\deploy\output\artifacts\build\odrive\WinOdrive\out00-PYZ.pyz\subprocess", line 644, in _execute_child
UnicodeEncodeError: 'ascii' codec can't encode characters in position 9-13: ordinal not in range(128)
Once the command prompt is open, copy and paste the following command in (all one line) and hit enter: powershell -command " & {Stop-Process -erroraction silentlycontinue -Force -processname odriveapp; Stop-Process -erroraction silentlycontinue -Force -processname odrive; Stop-Process -erroraction silentlycontinue -Force -processname odrive; sleep 5; ren \"$HOME\.odrive\bin\" \"$HOME\.odrive\bin_bak\";del \"$HOME\.odrive\version\";Start-Process -NoNewWindow \"$env:programfiles\odrive\odrive.exe\";sleep 20;cd \"$HOME\.odrive\"; del -recurse -Force \"bin_bak\"}"
This is going to delete the C:\Users\[your user name here]\.odrive\bin folder and the C:\Users\[your user name here]\.odrive\version file and then re-run the launcher. I have a feeling that the C:\Users\[your user name here]\.odrive\bin folder is incomplete somehow and a re-install will not correct this particular error, unfortunately.
Instead of running the above command you can also just manually remove those two items (and only those two items) and then try running odrive again:
The folder C:\Users\[your user name here]\.odrive\bin
The file C:\Users\[your user name here]\.odrive\version
Hi @kzh55,
This is definitely odd. What if you run this command from a command prompt: powershell -command "&{$bin=$(ls \"$HOME\.odrive\bin\" | sort Name -desc | select -f 1).FullName; Start-Process \"$($bin)\odriveapp.exe\";}"
The odrive.exe app actually ends up launching odriveapp.exe in the C:\Users\[your user name here]\.odrive\bin\[latest version]\ folder. The above command will run it directly. Maybe the odriveapp.exe app is erroring out in some way?
When you try to launch it directly, what happens?
Can you also send me the log file so I can take a look at it?
I am having a new version built based on the previous version that was working for you. That will hopefully get you back up and running until we figure out why this broke in this release.
Can you also post the username here so we can make sure we are testing with the same characters?
Hi @kzh55,
Sorry, I didn’t see your message before I signed-off.
I’m still working through this, but can you try this one-line script from a standard cmd prompt in the meantime? powershell -command "&{$bin=$(ls \"$HOME\.odrive\bin\" | sort Name -desc | select -f 1).FullName; Start-Process \"$((New-Object -ComObject Scripting.FileSystemObject).GetFolder($bin).ShortPath)\odriveapp.exe\";}"
This attempts to use the “shortpath” to bypass any non-standard character issues.
Another way to do this is to perform the following steps (also from a standard cmd prompt):
perform a dir /x on your C:\Users folder to get the “shortpath” of your profile directory
Use that “shortpath” version to run the odriveapp.exe command
For example, on my system running dir /x will show a shortpath for my user’s profile directory as 5A62~1. I then run C:\Users\5A62~1\.odrive\bin\6769\odriveapp.exe
I have the same problem.
Tried the powershell command powershell -command “&{$bin=$(ls “$HOME.odrive\bin” | sort Name -desc | select -f 1).FullName; Start-Process “$((New-Object -ComObject Scripting.FileSystemObject).GetFolder($bin).ShortPath)\odriveapp.exe”;}”
it didn’t work.
With the C:\Users\5A62~1.odrive\bin\6769\odriveapp.exe odrive started working. When I closed the command prompt it stopped responding.
