App Connect

App Connect

Join this online user group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#Applicationintegration
#App Connect
#AppConnect
 View Only
Expand all | Collapse all

Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

  • 1.  Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

    Posted Fri October 20, 2023 10:20 AM
    Hi All,

    I am getting below error when tried to create a standalone integration server in ACE12.Could you please provide some inputs on how to resolve this issue?

    Error initializing event log file:
    BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'', '32', ''\\?\C:\Users\guntups\IBM\ACET12\FinSysWorkspace\TEST_SERVER\log\integration_server.TEST_SERVER.events.txt'', '3221225472', '4', '1', '32', ''The process cannot access the file because it is being used by another process.



  • 2.  RE: Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

    Posted Mon November 13, 2023 07:58 AM

    Hello!

    how did you try to create the server?

    Regards,

    Kjetil



    ------------------------------
    Kjetil Svihus
    ------------------------------



  • 3.  RE: Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

    Posted Wed January 03, 2024 06:41 PM

    Hi,

    Was there any resolution related to this? I am also getting the exact error and i created the integration sever through toolkit. I tried integrationServer command to start it and still no luck.



    ------------------------------
    satyam maurya
    ------------------------------



  • 4.  RE: Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

    Posted Wed September 11, 2024 10:35 AM

    Is this issue resolved now? I am facing same issue. 



    ------------------------------
    Vani Hegde
    ------------------------------



  • 5.  RE: Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

    Posted Wed September 18, 2024 12:40 AM

    Hi all

    If you create an SIS via the toolkit, not only does it create it, it will also start it.

    Without having more information such as: where did you get the error, how are you starting your SIS, ... the most logical thing is that your SIS is running and you are trying to start it again via command line or something. This would result is getting that error since the file  is being used by a running process.

    Check if you see an IntegrationServer process running, nested under your toolkit sessions



    ------------------------------
    Regards
    Matthias Blomme
    Integration Specialt
    Integration Designers
    Turnhout
    ------------------------------



  • 6.  RE: Getting "BIP2119E: IBM App Connect Enterprise internal error: diagnostic information ''The process cannot access the file because it is being used by another process.'' when tried to create standalone integration server

    Posted Thu September 12, 2024 08:18 AM

    Hi @sreenu rao

    Are you sure you are trying to start the IS from your user directory? if it is some other user directory, please make sure the file is not opened by other user session.



    ------------------------------
    uvaise odam
    ------------------------------