You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TROUBLESHOOTING.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,6 +198,29 @@ The api-version '...' is invalid
198
198
199
199
2. Check for newer API versions in the Bicep templates
200
200
201
+
### Invalid Win32 application
202
+
203
+
This is a bit cryptic. It's helpful to execute the `az` command from the error separately in the terminal and supply the `--debug` flag. You might then see errors such as this one:
204
+
205
+
**Error Message:**
206
+
```
207
+
cli.azure.cli.core.azclierror: [WinError 193] %1 is not a valid Win32 application
208
+
az_command_data_logger: [WinError 193] %1 is not a valid Win32 application
209
+
```
210
+
211
+
Scroll up to see what is executed.
212
+
213
+
**Solution:**
214
+
215
+
#### Bicep
216
+
217
+
In one case, `%USERPROFILE%\.azure\bin` contained a `bicep.exe` file but with a zero-length. The CLI would recognize that the file is there but fail on execution.
218
+
219
+
1. Verify that bicep is indeed failing: `az bicep version`
0 commit comments