Getting "System IOException" for Opkey on-premise setup

Issue:


Getting System.IO.IOException in local Opkey environment while executing.


Solution:


To address a System.IO.IOException when executing a test case in Opkey from a local machine, you can follow these steps:

  1. Check Disk Space:

    • Ensure that there is sufficient disk space on your local machine.
    • Clear unnecessary files if needed to free up space.
  2. Verify File Access Permissions:

    • Ensure that you have the necessary read/write permissions for the directories and files involved in the test execution.
    • Right-click on the file or folder in your system, go to Properties and then check the Security tab to modify permissions if needed.
  3. Close Conflicting Applications:

    • Make sure that no other applications are using the files or directories required by Opkey.
    • Use the Task Manager to identify and close any conflicting processes.
  4. Check File Path Length:

    • Windows has a maximum path length limitation (260 characters). Ensure that the path to your test files does not exceed this limit.
    • Try moving your project to a directory with a shorter path if necessary.
  5. Update Opkey and Dependencies:

    • Ensure that you are using the latest version of Opkey and that all dependencies are up to date.
    • Check for updates and apply them if available.
  6. Run as Administrator:

    • Try running Opkey with administrative privileges. Right-click on the Opkey application and select "Run as administrator."
  7. Check Network Drives:

    • Users may face issues in Opkey's local environment because it needs to access a shared drive for logs and reports. If "Remember Me" isn't checked on the access authentication page, Opkey might fail to connect, causing test case failures and System.IO.IOException. 
  8. Temporary Files and Cache:

    • Clear the temporary files and cache on your local machine.
    • Use tools like Disk Cleanup or manually delete temporary files from the Temp folder.
  9. Review Log Files:

    • Check the Opkey log files by downloading them from the execution result section for more detailed error messages.
    • The logs can provide specific information about what caused the System.IO.IOException.
  10. Antivirus/Firewall Settings:

    • Ensure that your antivirus or firewall is not blocking Opkey or the test files.
    • Add exceptions if necessary.
  11. Contact Support:

    • If the issue persists, reach out to Opkey support for further assistance. Provide them with detailed information about the error and the steps you have already taken.


 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article