Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
MSBUILD : Logger error MSB4104: Failed to write to log file Intermittent Issue RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Team,

    We are using Azure Devops for our CI pipelines .We are using the Ms Build task to build the solution file with Create log file enabled. recently we have noticed following ms build errors sporadically. the Agent has all the Required Administrative permissions on the build server.And also excluded the agent folders as part of the scanning also.

    

    Error Message:

    MS BUILD : Logger error MSB4104: Failed to write to log file "E:\VstsAgent01\_work\374\s\***.sln.log". The process cannot access the file 'E:\VstsAgent01\_work\374\s\***.sln.log' because it is being used by another process.
    ##[error]Process 'msbuild.exe' exited with code '1'.


    MSBuild Task Details:

    Task         : MSBuild
    Description  : Build with MSBuild
    Version      : 1.151.0

    Agent Version: 2.133.3

    Agent.OS: Windows_NT

    Could some one assist how to resolve such errors. 

    Thanks in Advance

    Ravi j

    Friday, May 17, 2019 7:49 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi friend,

    Thanks for posting here.

    This forum is about the MSBuild locally in VS(Discuss the Microsoft build engine aka MSBuild. Topics including: usage of MSBuild, build customization, and MSBuild extensibility via tasks, loggers and hosting). 

    As your issue is more related to the Devops, I suggest that you could open an new thread on the DeveloperCommunity or Stack OverFlow with Devops tag for better support.

    If you have some MSBuild questions, please feel free to contact us. We will try our best to give you a solution.

    Thanks for your understanding and cooperation. 

    Best Regards

    Lance

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, May 20, 2019 8:41 AM