Error while running bolt-any-llm

bolt.diy [bolt.diy] Issues and Troubleshooting
1

Hi there OTTomatar Community. Im a noob and want to try out boltanyllm however when i try to run it in coder editor after installing all the packages it shows this error on terminal

remix vite:dev

warn Data fetching is changing to a single fetch in React Router v7
┃ You can use the v3_singleFetch future flag to opt-in early.
┃ → Future Flags (v2.13.1) | Remix
┗
*** Received structured exception #0xc0000005: access violation; stack: 7ffc9fdf2f57 7ff63ce1251b 7ff63ce125e3 7ff63cdb3f9c 7ff63cdb3f47 7ff63c62bf5e 7ff63c62c26f 7ff63b411ed6 7ff63c755e3f 7ff63c75d0d6 7ff63c756343 7ff63c75d0d6
7ff63c753cdc 7ff63b401e66 7ff63df6572f 7ffcad8f7373 7ffcaee5cc90
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at Miniflare2.#assembleAndUpdateConfig (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241106.1\node_modules\miniflare\src\index.ts:1404:10)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Mutex.runWith (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241106.1\node_modules\miniflare\src\workers\shared\sync.ts:66:45)
at Miniflare2.#waitForReady (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241106.1\node_modules\miniflare\src\index.ts:1486:3)
at Miniflare2.getProxyClient (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241106.1\node_modules\miniflare\src\index.ts:1692:3)
at Miniflare2.getBindings (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241106.1\node_modules\miniflare\src\index.ts:1715:23)
at getPlatformProxy (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm\wrangler@3.91.0@cloudflare+workers-types@4.20241127.0\node_modules\wrangler\src\api\integrations\platform\index.ts:116:24)
at configureServer (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:55:11)
at createServer (file:///C:/Users/Aqib/bolt.new-any-llm/node_modules/.pnpm/vite@5.4.11@types+node@22.10.1_sass-embedded@1.81.0_sass@1.77.6/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:63080:20)
at configResolved (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\plugin.js:768:27)
at async Promise.all (index 3)
at resolveConfig (file:///C:/Users/Aqib/bolt.new-any-llm/node_modules/.pnpm/vite@5.4.11_@types+node@22.10.1_sass-embedded@1.81.0_sass@1.77.6/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:66404:3)
at createServer (file:///C:/Users/Aqib/bolt.new-any-llm/node_modules/.pnpm/vite@5.4.11@types+node@22.10.1_sass-embedded@1.81.0_sass@1.77.6/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:62758:18)
at dev (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\dev.js:39:16)
at Object.viteDev (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\cli\commands.js:221:3)
at Object.run (C:\Users\Aqib\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\cli\run.js:271:7) {
code: ‘ERR_RUNTIME_FAILURE’,
cause: undefined
}
ELIFECYCLE Command failed with exit code 1.

please suggest any fixes to this.

1 Like
2

Hey @nocode, thanks for posting your issue here!

This looks like a permission issue (access violation). Could you try making sure you are running your terminal as an administrator?

3

Hi everyone, I’m encountering the same error:

remix vite:dev

warn Route discovery/manifest behavior is changing in React Router v7
┃ You can use the v3_lazyRouteDiscovery future flag to opt-in early.
┃ → Future Flags (v2.13.1) | Remix
┗
warn Data fetching is changing to a single fetch in React Router v7
┃ You can use the v3_singleFetch future flag to opt-in early.
┃ → Future Flags (v2.13.1) | Remix
┗
*** Received structured exception #0xc0000005: access violation; stack: 7ffc3f462f57 7ff78427aa5a 7ff78427ab23 7ff78421c4ac 7ff78421c457 7ff783a8143e 7ff783a8174f 7ff782891ed6 7ff783babcef 7ff783bb2f86 7ff783bac1f3 7ff783bb2f86 7ff783ba9b8c 7ff782881e66 7ff7853e961f 7ffc44b7259c 7ffc459caf37
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at Miniflare2.#assembleAndUpdateConfig (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241205.0\node_modules\miniflare\src\index.ts:1404:10)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Mutex.runWith (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241205.0\node_modules\miniflare\src\workers\shared\sync.ts:66:45)
at Miniflare2.#waitForReady (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241205.0\node_modules\miniflare\src\index.ts:1486:3)
at Miniflare2.getProxyClient (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241205.0\node_modules\miniflare\src\index.ts:1692:3)
at Miniflare2.getBindings (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm\miniflare@3.20241205.0\node_modules\miniflare\src\index.ts:1715:23)
at getPlatformProxy (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm\wrangler@3.93.0@cloudflare+workers-types@4.20241205.0\node_modules\wrangler\wrangler-dist\cli.js:178278:20)
at configureServer (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_4g2boics2phbvdocisxkortxoa\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:55:11)
at createServer (file:///D:/11%20Coding%20Freelance%202024/bolt.new-any-llm/node_modules/.pnpm/vite@5.4.11@types+node@22.10.1_sass-embedded@1.82.0/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:63080:20)
at configResolved (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_4g2boics2phbvdocisxkortxoa\node_modules@remix-run\dev\dist\vite\plugin.js:768:27)
at async Promise.all (index 3)
at resolveConfig (file:///D:/11%20Coding%20Freelance%202024/bolt.new-any-llm/node_modules/.pnpm/vite@5.4.11_@types+node@22.10.1_sass-embedded@1.82.0/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:66404:3)
at createServer (file:///D:/11%20Coding%20Freelance%202024/bolt.new-any-llm/node_modules/.pnpm/vite@5.4.11@types+node@22.10.1_sass-embedded@1.82.0/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:62758:18)
at dev (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_4g2boics2phbvdocisxkortxoa\node_modules@remix-run\dev\dist\vite\dev.js:39:16)
at Object.viteDev (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_4g2boics2phbvdocisxkortxoa\node_modules@remix-run\dev\dist\cli\commands.js:221:3)
at Object.run (D:\11 Coding Freelance 2024\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0_@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_4g2boics2phbvdocisxkortxoa\node_modules@remix-run\dev\dist\cli\run.js:271:7) {
code: ‘ERR_RUNTIME_FAILURE’,
cause: undefined
}
ELIFECYCLE Command failed with exit code 1.

I tried running my terminal as an administrator, but the error persists. Has anyone else encountered this issue or found a solution? Any help would be appreciated!

4

Hi everyone. I’ve just managed to resolve this issue by upgrading the Visual Studio C++ to the latest version (got the info from 🐛 BUG: Received structured exception #0xc0000005: access violation; · Issue #6170 · cloudflare/workers-sdk · GitHub).

For my case I needed to install the VC Redistributable files Latest supported Visual C++ Redistributable downloads | Microsoft Learn

2 Likes
5

I was looking through to find another issue on this and was going to provide the same response. This is has come up a few times now.

@ColeMedin can we maybe add this to troubleshooting steps for Windows (seems exclusive to Win11 but not :100:%) in the README.md, or something? Thoughts?

1 Like
6

It might be a good idea to curate these common problems and put them on a troubleshooting md file in the docs folder

2 Likes
7

@aliasfox Yeah I will add this to the pinned troubleshooting post!

@thecodacus We have some troubleshooting steps in the docs already, but yeah maybe a dedicated section for it would be appropriate especially as we grow it for fixes for things like this!

1 Like