-
Notifications
You must be signed in to change notification settings - Fork 244
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
[Question]: PlaywrightException: Process exited #1649
Comments
To help you, we'll need a lot more details. Please consider filing a bug using the correct issue template, or add details:
|
Hi @avodovnik, the version of Playwright for .NET is: 1.13.0.0; the OS & Version is: Windows Server 2016 Datacenter; the deployment method is: The error occurred when the “Playwright.CreateAsync“ method was called; code snippets as follow: using (var playwright = await Playwright.CreateAsync())
the debug logs as follow: at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() |
Thanks. Do you ensure you run |
@avodovnik I'm a colleague of @johnnyhegagng, |
To clarify, you run the install command on the target server correct? Not copy/deploy the browsers folder over via WebDeploy? |
Both the Web Deploy process and the install command are run on the target server, by an Azure Pipelines agent running on the server. |
I managed to redirect the application process's stderr to a file, and got this output:
It looks like this is probably the same issue as nodejs/node-v0.x-archive#3977, the app pool user has permission to access the application directory, but not any of the ancestor directories. It's not directly related, but it would be nice if there was a better way to get the Playwright logs for non-console applications than writing stderr to a file. |
@JoelEinbinder could you have a look at this? |
It seems that just granting "Read Attributes" permission may not be enough if there are also Deny permissions in place, see nodejs/node#35853 and libuv/libuv#3267. |
We managed to fix this issue by removing the Deny Full Control permission for BUILTIN\IIS_IUSRS from the E: drive root and adding Allow Read Attributes permissions for the individual app pool identities to the ancestor directories (including the drive root), with inheritance disabled. The app pool identities don't have any other Allow permissions for the drive root, so they don't have any access except reading attributes. Even with the Deny permission in place, the Effective Access tab of the folder security settings showed that the app pool had Read Attributes permission for the folder; despite Node being blocked from reading the attributes. |
Awesome to hear. |
Closing this as it seems like it was answered. Feel free to open another issue, if you still have problems doing this. |
Your question
Hi,
I encountered a problem when deploying microsoft.playwright to the test server,it's called Playwright.CreateAsync() method, but my local working fine.
Microsoft.Playwright.PlaywrightException: Process exited
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Playwright.Transport.Connection.d__22`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Playwright.Playwright.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
The text was updated successfully, but these errors were encountered: