Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OneDrive is stuck in a loop of constant null references #323

Open
TuggyNE opened this issue Jan 6, 2022 · 4 comments
Open

OneDrive is stuck in a loop of constant null references #323

TuggyNE opened this issue Jan 6, 2022 · 4 comments
Labels

Comments

@TuggyNE
Copy link

TuggyNE commented Jan 6, 2022

When I try to synchronize or check the connection, I get .NET fallback exception handler messages with variations on "Object reference not set to an instance of an object". Unfortunately, even though running the OAuth cycle appears to work, it immediately forgets its auth token and the error messages appear again as soon as I try to do anything.

It doesn't matter which storage is chosen for auth details, either. Restarting and clearing the connection and creating a new one don't help.

Also, OAuth only works at all when elevated, since it expects to be able to listen on a privileged port (<1024). This is wrong.

@Kyrodan
Copy link
Owner

Kyrodan commented Apr 22, 2022

Hi @TuggyNE,

  • Forgetting the auth token: maybe you are right and this should be fixed. There are others reported issues relating to this.
  • Privileged ports: I don't use privileged ports in KeeAnywhere. Maybe you are still using Windows 7 which has a different behavior opening ports on Localhost-IP, than newer Windows Versions, which forces you to run KeePass elevated.

Regards,
Daniel

@Kyrodan Kyrodan added the bug label Apr 22, 2022
@TuggyNE
Copy link
Author

TuggyNE commented Apr 22, 2022

Thanks for getting back to me! I use Windows 8.1, which is still under extended support.

@bnosie
Copy link

bnosie commented Apr 23, 2022

Also experiencing this issue on multiple computers. All running Windows 10, KeePass 2.50, KeeAnywhere 2.0.3.

@LtlBear
Copy link

LtlBear commented May 17, 2022

I am seeing the same problem on multiple computers - Windows 10 and Windows 11. KeePass 2.51.1 / KeyAnywhere 2.0.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants