Bug report: mdbase connect could not start

[nhan000]

I got this notification when I run mdbase connect for the past 2-3 days

After clicking OK, the mdbase connect window opens and seems to work fine although there seems to be an error:

[LaikeSF]

I am running into the exact same issue

[callumalpass]

Thanks for reporting this and including both screenshots—they’re very helpful. Sorry for the trouble.

The screenshots show two errors: Windows is denying installation of Connect’s background task, and the running connector reports an invalid credential. The window opening doesn’t necessarily mean the connection is working, so we’ll investigate both.

Could you clarify:

• Did this start immediately after updating to beta.99?
• Have you ever installed or launched mdbase connect using Run as administrator, or installed it under a different Windows account?
• If you open Task Scheduler → Task Scheduler Library, is there an mdbase connect task? If so, does its configured user account match the Windows account you’re currently using?

Please don’t delete Connect’s settings or change the task’s permissions yet—we haven’t established the cause, and we’d like to preserve your existing configuration.

[nhan000]

Did this start immediately after updating to beta.99?

For this error:

I believe it happened with beta 96 or 97. Couldn't remember exactly which one.

For this error

it has happened for a few weeks. It seemed to work fine at the time (still synced between my laptop and TaskNotes app) so I didn't report it at the time. It still works fine right now but I think I should report it.

Have you ever installed or launched mdbase connect using Run as administrator, or installed it under a different Windows account?

No to both questions.

Is there an mdbase connect task?

No I don't think so. I attached a screenshot here.

Let me know if you need anything else.

[jemabaris]

The same is happening for me. I've not had any prior installations, installed 0.1.0-beta99 for the first time today after updating the TaskNotes Obsidian app and reading about the TaskNotes Android app and mdbase connect in the "What's New" release notes. I have tried running it elevated but to no avail.

EDIT: I manually ran this from an elevated powershell and that seems to have done the trick;

[callumalpass]

Thanks again for helping track this down. Beta101 is now available and includes a fix for the Windows startup error. Connect was trying to register its background task in a way that Windows rejected for standard users.

Could you update and let us know whether the startup error disappears? You shouldn’t need to run Connect as administrator.

The “Connector credential is invalid” message appears to be a separate issue and isn’t fixed by this release. I’m keeping that investigation open.

[nhan000]

I installed the Beta101. There seems to be new errors:

This window automatically opened:

Still seems to work fine (sync between the TaskNotes web and Android and my Obsidian)

[jemabaris]

I am still getting the same error as before "Access denied" with build 102. If I run the exe as admin I also get the same json parsing error as nhan000 but that was already the case with build 100, so basically nothing has changed for me. Despite the fact that I managed to get the mdbase-connect app up and running by registering the daemon manually (as shown in the screenshot earlier) I was never able to successfully sync between my collections (local Obsidian vault on my PC with TaskNotes 5.X and the TaskNotes Android app, it always gets stuck in some validation loops until it eventually times out or crashes). Overall the whole process seems extremely convoluted and unintuitive to me :/
I really hope things will get easier and more stable in the future because I really liked the idea of 'outsourcing' tasks to a specialized app (Obsidian on Android is not that fun imho) while still keeping everything part of my Obsidian vault. Fingers crossed 🤞🏻