Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9104

Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      Windows XP, Windows 7 using MSBuild or devenv.exe to build MS Visual Studio Projects
    • Similar Issues:
      Show 5 results

      Description

      I run into errors when using a customized build system which uses Visual Studio's devenv.exe under the hood to compile VisualStudio 2005 projects (with VC++ compiler). When starting two parallel builds with Jenkins (on different code base) the second job will always fail with "Fatal error C1090: PDB API call failed, error code '23' : '(" in exactly the same second the first job finishes processing. Running both jobs outside Jenkins does not produce the error.
      This has also been reported for builds executed by MSBuild on the Jenkins user mailing list [1].

      I analysed this issue thoroughly and can track the problem down to the usage of mspdbsrv.exe. This program is automatically spawned when building a VisualStudio project. All Visual Studio instances normally share one common pdb-server which shutdown itself after a idle period (standard is 10 minutes). "It ensures access to .pdb files is properly serialized in parallel builds when multiple instances of the compiler try to access the same .pdb file" [2].
      I assume that Jenkins does a clean up of its build environment when a automatically started job finishes (like as described at http://wiki.jenkins-ci.org/display/JENKINS/Aborting+a+build). I checked mspbsrv.exe with ProcessExplorer and the process indeed has a variable JENKINS_COOKIE/HUDSON_COOKIE set in its environment if started through Jenkins. Killing mspdbsrv.exe while projects are still connected will break compilation.

      Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual Studio project at the same time.


      [1] http://jenkins.361315.n4.nabble.com/MSBuild-fatal-errors-when-build-triggered-by-timer-td385181.html
      [2] http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/b1d1bceb-06b6-47ef-a0ea-23ea752e0c4f/

        Issue Links

          Activity

          Hide
          ostojan Aleksander Stojanowski added a comment -

          When do you publish new version of plugin with fix? It's been month since you released version with(out) fix...

          Show
          ostojan Aleksander Stojanowski added a comment - When do you publish new version of plugin with fix? It's been month since you released version with(out) fix...
          Hide
          jxramos Jaime Ramos added a comment - - edited

          I'm in need of a fix for this too, it's consistently failing numerous jobs for me. Is there an old version of Jenkins to revert to that avoids this particular problem? I'm willing to go that route as a workaround.
          So far this has been a cause of a pretty bad first impressions for a team I setup a CI build setup for who had never seen Jenkins before.
          I'm using VS2010 devenv.exe to build the solution files.

          Show
          jxramos Jaime Ramos added a comment - - edited I'm in need of a fix for this too, it's consistently failing numerous jobs for me. Is there an old version of Jenkins to revert to that avoids this particular problem? I'm willing to go that route as a workaround. So far this has been a cause of a pretty bad first impressions for a team I setup a CI build setup for who had never seen Jenkins before. I'm using VS2010 devenv.exe to build the solution files.
          Hide
          olexandr_maltsev Olexandr Maltsev added a comment - - edited

          Hello Jaime,
          I found a solution.
          I think it is a workaround, but it works for me.
          I set for every project the addition String parameter.
          Go to the Jenkins Project and set "This build is parameterized", “Name” – “BUILD_ID”, “Default Value” – “DoNotKillMe”.

          Show
          olexandr_maltsev Olexandr Maltsev added a comment - - edited Hello Jaime, I found a solution. I think it is a workaround, but it works for me. I set for every project the addition String parameter. Go to the Jenkins Project and set "This build is parameterized", “Name” – “BUILD_ID”, “Default Value” – “DoNotKillMe”.
          Hide
          olexandr_maltsev Olexandr Maltsev added a comment -

          Show
          olexandr_maltsev Olexandr Maltsev added a comment -
          Hide
          gl1koz3 Edgars B. added a comment - - edited

          Stumbled upon this issue immediately after trying parallel builds. Been open for 5 years now, so I guess you can simply check for 'mspdbsrv.exe' and leave it alone? Please free us of our pain.

          Show
          gl1koz3 Edgars B. added a comment - - edited Stumbled upon this issue immediately after trying parallel builds. Been open for 5 years now, so I guess you can simply check for 'mspdbsrv.exe' and leave it alone? Please free us of our pain.

            People

            • Assignee:
              danielweber Daniel Weber
              Reporter:
              gordin Christoph Vogtländer
            • Votes:
              58 Vote for this issue
              Watchers:
              72 Start watching this issue

              Dates

              • Created:
                Updated: