Lakebridge SetUp Issue

[Chandana_Ramesh]

Hi,

I'm getting the below error upon executing databricks labs lakebridge analyze command. All the dependencies have been installed before execution of the command. Can someone please give a solution, or suggest if anything is missing? Below attached is the error.

17:11:56 ERROR [d.l.bladespector.analyzer] Analysis failed
Traceback (most recent call last):
File "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\analyzer.py", line 87, in _run_binary
with subprocess.Popen(
File "C:\Users\chandana.r\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 971, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\chandana.r\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1456, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
17:11:56 ERROR [src/databricks/labs/lakebridge.analyze] RuntimeError: Analysis failed

[aleksandra_ch]

Hi Chandana_Ramesh,

Please rerun the command with a --debug flag and share the command and the whole output.

From the message that you shared, it looks like the Analyzer.exe binary is not accessible:

• Verify the binary exists and is accessible: C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe. If it’s missing, reinstall Lakebridge via the Databricks CLI. If it’s present, ensure it’s not quarantined or blocked.
• Check Windows Defender quarantine and add an exclusion for the C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\Lib\site-packages\databricks\labs\bladespector\Analyzer\Windows directory, then restore the analyzer.exe if quarantined.

Hope this helps.

[Chandana_Ramesh]

Hi @aleksandra_ch ,

Please find the below attached complete output of command databricks labs lakebridge analyze --debug, as requested by you.

Also, the file C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe is missing, and I couldn't find it even after re installing lake bridge through databricks cli.

10:58:31    DEBUG [d.l.bladespector.analyzer] Using underlying analyzer: $C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe
10:58:31    DEBUG [d.l.bladespector.analyzer] Running command: C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe -d C:\Users\chandana.r\OneDrive - Fractal Analytics Limited\Documents\Chandana_docs\Lakebridge_poc\SSMS_SCRIPTS_2 -r C:\Users\chandana.r\AppData\Local\Temp\tmpj1eikafo\lakebridge_analyzer_result2.xlsx -t SQL -v
10:58:31    ERROR [d.l.bladespector.analyzer] Analysis failed
Traceback (most recent call last):
File "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\analyzer.py", line 87, in _run_binary
   with subprocess.Popen(
File "C:\Users\chandana.r\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 971, in __init__
   self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\chandana.r\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1456, in _execute_child
   hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
10:58:31    DEBUG [d.l.l.contexts.application] Added User-Agent extra analyzer_error=RuntimeError
10:58:31    DEBUG [d.l.l.contexts.application] Added User-Agent extra cmd=analyze
10:58:31    DEBUG [databricks.sdk] GET /api/2.0/preview/scim/v2/Me
< 200 OK
< {
<   "active": true,
<   "displayName": "chandana.r@fractal.ai",
<   "emails": [
<     {
<       "primary": true,
<       "type": "work",
<       "value": "**REDACTED**"
<     }
<   ],
<   "externalId": "306b3347-5968-4277-b8e5-1fe27b037fa8",
<   "groups": [
<     {
<       "$ref": "Groups/153089339549513",
<       "display": "users",
<       "type": "direct",
<       "value": "**REDACTED**"
<     },
<     "... (2 additional elements)"
<   ],
<   "id": "501874446901877",
<   "name": {
<     "givenName": "chandana.r@fractal.ai"
<   },
<   "schemas": [
<     "urn:ietf:params:scim:schemas:core:2.0:User",
<     "... (1 additional elements)"
<   ],
<   "userName": "chandana.r@fractal.ai"
< }
10:58:31    ERROR [src/databricks/labs/lakebridge.analyze] Failed to call analyze
Traceback (most recent call last):
File "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\analyzer.py", line 87, in _run_binary
   with subprocess.Popen(
File "C:\Users\chandana.r\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 971, in __init__
   self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\chandana.r\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1456, in _execute_child
   hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\blueprint\cli.py", line 118, in _route
   cmd.fn(**kwargs)
File "C:\Users\chandana.r\.databricks\labs\lakebridge\lib\src\databricks\labs\lakebridge\cli.py", line 822, in analyze
   result = ctx.analyzer.run_analyzer(source_directory, report_file, source_tech)
File "C:\Users\chandana.r\.databricks\labs\lakebridge\lib\src\databricks\labs\lakebridge\analyzer\lakebridge_analyzer.py", line 111, in run_analyzer
   return self._runner.run(source_dir, results_dir, platform)
File "C:\Users\chandana.r\.databricks\labs\lakebridge\lib\src\databricks\labs\lakebridge\analyzer\lakebridge_analyzer.py", line 76, in run
   self._runnable(source_dir, tmp_dir, platform, self._is_debug)
File "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\analyzer.py", line 61, in analyze
   analyzer._run_binary(directory, result, technology, is_debug)
File "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\analyzer.py", line 104, in _run_binary
   raise RuntimeError("Analysis failed") from e
RuntimeError: Analysis failed
10:58:32 Info: completed execution pid=8484 exit_code=0
10:58:32 Debug: no telemetry logs to upload pid=8484

[aleksandra_ch]

Hi @Chandana_Ramesh , 

Please check if the binary was not quarantined by Windows Defender or any other security solution on your PC. 

[Advika]

Hello @Chandana_Ramesh!

Did the suggestions shared above help resolve your issue? If so, please consider marking the response as the accepted solution.
If you found a different approach that worked, sharing it here would be helpful for others in the community.

[pradeep_singh]

As @Advika suggested can you confirm if you can locate analyzer.exe . Seems like it doesn't exist which means some background process might have removed it if it was installed initially . 

[SteveOstrowski]

Hi @Chandana_Ramesh,

The FileNotFoundError you are seeing means the analyzer.exe binary is not present on disk at the expected path:

C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe

Since reinstalling Lakebridge via the Databricks CLI did not restore the file, the most likely cause is that Windows Defender (or another antivirus/endpoint protection tool) is quarantining or deleting the binary immediately after installation. This is a documented scenario in the Lakebridge project (GitHub issue #1811).

STEPS TO RESOLVE

1. Check Windows Defender quarantine history:
- Open Windows Security > Virus and threat protection > Protection history
- Look for any entries that show analyzer.exe being quarantined or removed
- If found, restore the file from quarantine

2. Add an exclusion for the Lakebridge directory:
- Open Windows Security > Virus and threat protection > Manage settings
- Scroll to Exclusions > Add or remove exclusions
- Add a folder exclusion for:
C:\Users\chandana.r\.databricks\labs\lakebridge\

3. If your organization uses a centralized endpoint protection solution (CrowdStrike, Carbon Black, Symantec, etc.), you may need to request your IT/security team to whitelist that directory or the analyzer.exe binary specifically.

4. After adding the exclusion, reinstall Lakebridge:

databricks labs install lakebridge

5. Verify the binary is now present:

dir "C:\Users\chandana.r\.databricks\labs\lakebridge\state\venv\lib\site-packages\databricks\labs\bladespector\Analyzer\Windows\analyzer.exe"

6. Run the analyze command again:

databricks labs lakebridge analyze --debug

ADDITIONAL NOTES

- The analyzer binary is bundled inside the bladespector Python package. When you install Lakebridge, pip downloads the package and extracts the binary. If antivirus scans the extraction in real-time, the file can be removed before the process completes, which is why reinstalling alone does not fix it.
- Make sure you are running Python 3.10.1 through 3.13.x, as required by Lakebridge.
- The Lakebridge documentation and latest releases are available at:
https://databrickslabs.github.io/lakebridge/
https://github.com/databrickslabs/lakebridge

If none of the above resolves the issue, consider opening a GitHub issue at https://github.com/databrickslabs/lakebridge/issues with the full --debug output so the maintainers can assist further.

* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.

If this answer resolves your question, could you mark it as "Accept as Solution"? That helps other users quickly find the correct fix.