Hi when I install the Audio2Face 2022.1.0 , there are always error like this
Error occurred during installation of Audio2Face: [785ef2d3-b474-4b48-bcb7-a14deac59683] Cannot sign URL for download – FetchError: request to https://api.launcher.omniverse.nvidia.com/app/url?path=https%253A%252F%252Flauncher-prod.s3.us-east-2.amazonaws.com%252Faudio2face%252F2022.1.0%252Fwindows-x86_64%252F90af9be5c280a03ee647052b3591de9d.zip failed, reason: connect ETIMEDOUT 99.86.199.102:443
can you tell me what should I do, by the way I have installed version 2021.3.3 and no problem during use this version
THX
Hello @yu_phon! Could you attach a copy of your launcher log? It is usually found here: C:\Users\<USERNAME>\.nvidia-omniverse\logs\launcher
I am hoping this will indicate where the error is occurring.
I am also having trouble with 2022.1.2 I have tried to install it multiple times. It downloads the full file and then it downloads the SDK Launcher. errors out. Error occurred during installation of Audio2Face: EISDIR: illegal operation on a directory, symlink ‘X:\NvidiaOmniverse\pkg\deps\9eb9e2bfab1fb1d171ea6e5e894f8558’ → ‘X:\NvidiaOmniverse\pkg\audio2face-2022.1.2’
Here is my log:
launcher.log (62.0 KB)
Were you able to resolve it? I am facing the same issue
Hi @mitdave95
Does it fail if you use Audio2Face 2022.2.0? If yes, can you please share your launcher log which can be found here: C:\Users\(UserName)\.nvidia-omniverse\logs\launcher.log?
Yes, it happens with 2022.2.0
Error
Error occurred during installation of Audio2Face: The following file is used by another process: EBUSY: resource busy or locked, open ‘C:\Users\Mit\AppData\Local\ov\pkg\deps\3c0394c49a8bbd33ca645c854d30247f\exts\omni.kit.telemetry\omni.telemetry.transmitter\carb.tokens.plugin.dll’
Attached the logs below
launcher.log (214.6 KB)
Restarted the machine and it got installed
2 Likes
Restarted it here and it keeps installing “Forever”. I just saw the minimum aspect is RTX3070. I was using an rtx2060 on the last version. I guess I will have to give up os this new version.
@lucianodaluz It looks like there was an authenticationPlease try to log out from the launcher and authenticate again