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

BE0066: ResolveReferenceLinksComponent: [...] Member ID URL resolver service failed. #1040

Closed
koszeggy opened this issue Jan 23, 2024 · 5 comments

Comments

@koszeggy
Copy link

When I try to build a help project using the latest release I get the following warning:

BE0066: ResolveReferenceLinksComponent: [T:MyNamespace.MyType] Member ID URL resolver service failed.  No further look ups will be performed for this build.
Reason: The remote server returned an error: (403) Forbidden.

As a result, none of the MS references are resolved in the documentation (though the mentioned type in the warning is mine). I found the already closed #762, which seems to be a similar issue but I think this must be some different change in the service as this was working recently.

@EWSoftware
Copy link
Owner

The resolver service is down for some reason. I've already replaced it with a method that no longer requires it due to the removal of the binary formatter used to store the URL cache (#1035). I'm going to try and publish the update this weekend.

@koszeggy
Copy link
Author

Ah, I see, and thank you for the quick fix.

Btw, if you need an alternative solution for BinaryFormatter that is mainly compatible with it, I can offer mine.

@EWSoftware
Copy link
Owner

The links are generated locally in code now so the service and the need to cache the URLs has gone away.

@EWSoftware
Copy link
Owner

It's official. The resolver service is being shutdown. It says on March 8th but as we know, it stopped working a couple of weeks ago. I've got the changes made that no longer need it and they are checked in. It's just a matter of finding the time to publish the update. Most people probably won't notice unless the local cache file is deleted or it tries to resolve something that isn't in the cache and tries to use the service.

@EWSoftware
Copy link
Owner

Version 2024.2.18.0 is now available. It contains the new resolver that no longer needs the service.

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

No branches or pull requests

2 participants