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
I have the env var AZURITE_DB set to (something similar to) mssql://user:password@localhost/azurite, but no help if I remove that. Can't seem to find any other configuration. Several of my colleagues have the same issue, but we have no idea how to start to diagnose without the debug log working.
Assistance appreciated :)
Which service(blob, file, queue, table) does this issue concern?
All
Which version of the Azurite was used?
3.26.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Visual Studio 2022 bundled
What's the Node.js version?
21.6.1
What problem was encountered?
Fails to start - please see above
Steps to reproduce the issue?
Nothing is written to the debug log - seems to fail very early
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered:
When attempting to run the azurite executable bundled with Visual Studio 2022 Professional 17.8.6 (and earlier versions). It fails to start with:
The same applies when running outside of VS:
I have the env var
AZURITE_DB
set to (something similar to)mssql://user:password@localhost/azurite
, but no help if I remove that. Can't seem to find any other configuration. Several of my colleagues have the same issue, but we have no idea how to start to diagnose without the debug log working.Assistance appreciated :)
Which service(blob, file, queue, table) does this issue concern?
All
Which version of the Azurite was used?
3.26.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Visual Studio 2022 bundled
What's the Node.js version?
21.6.1
What problem was encountered?
Fails to start - please see above
Steps to reproduce the issue?
Nothing is written to the debug log - seems to fail very early
Have you found a mitigation/solution?
No
The text was updated successfully, but these errors were encountered: