Forum Discussion

AmolGawali's avatar
AmolGawali
Occasional Contributor
3 months ago

Pipelines are getting completed after the Access voilation error on windows server 2025

Hello experts,
getting below error in after running the test complete15.75 tests via azure pipelines

Access violation at address 00007FF848165642 in module 'mso20win32client.dll'. Read of address 0000000000000000

2025-07-14T18:49:59.1151714Z The test run has stopped because your test project is configured to stop on errors.

2025-07-14T18:49:59.1151922Z 'Nodes.item(...)' is null or not an object

5 Replies

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3

    The Dynamic Link Library (DLL) file mso20win32client.dll, relates to Microsoft/Office 365. If you search the internet for this DLL, there will be plenty of information on how to resolve this, i.e. repair Microsoft/Office 365 or Windows Update

  • scot1967's avatar
    scot1967
    Icon for Champion Level 2 rankChampion Level 2

    I have seen recommendations to "Avoid Office automation in DevOps pipelines and use server-safe libraries instead".  Is MS Office installed on your build machine? Does the build machine have a GUI or is it headless?  Office needs a GUI.  rraghvani​ has you on the right track.  These are just  few things I know to cause problems like this.  

    • AmolGawali's avatar
      AmolGawali
      Occasional Contributor

      Thank you, scot1967​  & @rraghrraghvani​ for your inputs.

      MS Office is not installed on my machine, but i have installed Access Database engine 2016 by using which we can use the Excel, and i am using excel only for Data driven testing. 
      it is a non-interactive session i am using though pipelines and not getting error when running the same test scrpts locally on same machine.

  • scot1967's avatar
    scot1967
    Icon for Champion Level 2 rankChampion Level 2

    The DevOps pipeline environment will need the same setup as your local pc.  Maybe the dll is missing or a different version on the server?  I would check the pipeline server.  We use Excel in TestComplete with a pipeline here and it works well.  Our pipeline server needed to have the correct files to make it work however.  Ensure you have  "Access Database engine 2016" setup correctly on you pipeline server as you have locally.

    We use the Excel object in scripts as shown in this link...

    https://support.smartbear.com/testcomplete/docs/testing-with/working-with-external-data-sources/excel/index.html