-
Notifications
You must be signed in to change notification settings - Fork 55
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
trace_logging_minimal_win.cc(23) Provider resistration failure #3687
Comments
Hi @mmaciejo sorry you are running into this. Do you have the event log on Azure machine? It may provide more information about the error. |
It indicates that a call to EventRegister failed. Does this error prevent WebView2 from working? |
I'm not sure if this error prevent WebView from working. I have forwarded exception to console and I have got: |
"Invalid window handle" error doesn't make much sense from CoreWebView2Environment.CreateAsync. At that time, the parent hwnd for the webview controller has not been provided yet and the trace_logging_minimal_win.cc error has nothing to do with any hwnd. Since the error message stated invalid window handle, and you stated that "WebView2 component used inside class without form", are you providing HWND_MESSAGE as the parent hwnd when creating WebView controller? If the trace_logging_minimal_win.cc error could cause some trouble, it would be it crashed the webview browser process, could you check whether there is any dump files under the EBWebView\Crashpad\reports subfolder of the specified userDataFolder in CoreWebView2Environment.CreateAsync? If there are dump files, the stack in those dump files would give us some clues. |
Hello
I'm using WebView2 inside Windows Forms App project in specific scenario:
Everything it seems to be prepared for using this app inside Azure Web App App Service.
On my local testing environment application works fine, but on Azure I have got error:
ERROR: trace_logging_minimal_win.cc(23) Provider resistration failure.
I have checked it using App Service Console, but also inside WebAPI call.
Can someone help me how to get around this problem? Any tip will be appreciated.
Regards,
Maciej
The text was updated successfully, but these errors were encountered: