Unknown error: failed to write prefs file

Question

I continue to receive an error when performing functional tests using runner with the following parameters: -selenit 2.44 -Chrome driver -Windows Server 2008 R2 Enterprise

Error Description: Listening on 0.0.0.0:7000 Starting tunnel... UnknownError: [POST http://test.com/wd/hub/session / {"de siredCapabilities":{"browserName":"chrome","name":"tests/intern","idle-timeout": 60,"selenium-version":"2.44.0"}}] unknown error: failed to write prefs file (Driver info: chromedriver=2.12.301325 (962dea43ddd90e7e4224a03fa3c36a421281ab b7),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 1.06 seconds 

Has anyone encountered such a problem? How to fix it? Suggestions please

Answer 1

I had the same issue recently. The problem was caused by four-wheel drive C. Apparently for creating temporary profile files, etc. A chromodrover requires some space on the C drive (or on the drive where the chrome binary is located).

One solution might be to move the chrome installation to another drive. You can use the mklink command in a command prompt window.

Answer 2

you have different versions of chrome on the server and node

Answer 3

This may be caused by running ChromeDriver at the same time. In this case, other errors may occur, such as “failed to write the first run file” or “cannot create default profile directory”.

My solution was to specify the user-data-dir option. Two concurrent Chromedriver should not use the same user data directory.

 chromeOptions.AddArgument("--user-data-dir=C:\\tmp\\chromeprofiles\\profile" + someKindOfIdOrIndex); 

You can, of course, change the path to what you want :)

Answer 4

This problem occurs if the C drive is running out of space. The best solution for cleaning temporary files. This solution worked for me.

Open Run Team

2.Type% tmp%

3. Click OK.

4. Select all files. Delete all files permanently.