In this guide, we will learn about some of the possible causes that can cause error 2360 0x938, and then we will give you several ways to solve the problem.


  • 1. Download ASR Pro
  • 2. Open the program and select "Scan your computer"
  • 3. Click "Repair" to start the repair process
  • The software to fix your PC is just a click away - download it now.



    Notes / Domino 8 Forum


    readabilitydatatable = “0”>

    < img alt = "" src = "/ ldd / nd8forum.nsf / back.GIF? OpenImageResource"> Previous Size = “1”> Next
    Object: Process face = “Arial” D: Lotus Domino nRnRMgr.EXE (2360 / 0x938) has an abnormal

    Face = “Arial” Return type: Face = “Arial “ Face =” Arial “ Problem

    Product line:
    Domino alt = “” src = “/ ldd / nd8forum.nsf / 4ea80140e7239dfc85256647004dc7d0 /% 24Body / 0.46C0? OpenElement & FieldElemFormat = gif”>
    Technical area: Functionality
    Platform: Windows 2003- Server
    Publication: 8.0
    Reproducible: Not reproducible < / td>

    The server connected to the member server had mail routing issues, it also accepts and distributes, but emails that do not go beyond that may route outgoing emails to the website url rather than through them. Redirect to the notified SMTP host.

    After restarting the change, the engineering issue was resolved.

    A new error message may be noted at the bottom of this log file “
    Process D: Lotus Domino nRnRMgr.EXE (2360 / 0x938) crashed “

    An idea of ​​what it is


    error 2360 0x938

    Review number WEBB7G8CDQ created ~ Yentl Zekboosiberggon on 04/07/2008

    Back to top

    D: Lotus Domino nRnRMgr.EXE … (~ Yentl Zekbusi … July 4, 2008)
    … ** cr ** ** cr ** RnRMgr.exe (~ Nita Catreber … July 4, 2008)
    … … -. Thank you (~ Yentl Zekbusi … July 7, 2008)

    href = “/ ldd / nd8forum.nsf / Feedback + Print? OpenForm & ParentUNID = 268E323A30A11CB18525747C003096C5″> Print version

    Search This Forum


    Tools For Members


    readabilitydatatable = “0”>

    RSS Feed

    < / tr>

    all RSS articles

    All major RSS topics

    This news forum is closed to innovative content andAnswers. Names of people who have been changed for data protection purposes. The information on this website is for informational purposes only and should not be construed as a customer support forum. All support requests should probably be directed through the official HCL customer support channels listed below:

    HCL Software Customer Support Portal for US Federal Customers
    Government HCL Software Customer Support Portal

    Notes / Domino 8 Forum

    Member Tools


    Readability table = “0”>

    RSS Feed

    all RSS articles
    error 2360 0x938

    All major RSS topics

    In Which Forum To Search

    • About HCL
    • Data protection
    • Contact

    I understand that if there is no account on the Accounts tab of the client push installation properties, SCCM will take full advantage of the site server computer account to install the ConfigMgr client. It only fails in the following scenario:

    I need a global group called SMSAdmins. This group contains the site Web server computer account (WCAS131). This global mass resides in the local admin community on all of my client computers. In this case, installation of the push cartridge will fail. The ccm.log displays:

    —> ERROR: Could not connect to all shares \XPFIVE admin $ with account “Machine $$

    —> ERROR: Target computer for request: “BLAGDSAD”, tool name: “XPFIVE”, code: error 5 not available $$ < Thread = 2360 (0x938)>

    If I add the device account for WCAS131 to the surrounding Client Computer Administrators group, the installation is successful.

    Am I doing something wrong or is this a bug?


    The ASR Pro repair tool is the solution for a Windows PC that's running slowly, has registry issues, or is infected with malware. This powerful and easy-to-use tool can quickly diagnose and fix your PC, increasing performance, optimizing memory, and improving security in the process. Don't suffer from a sluggish computer any longer - try ASR Pro today!

    If I add the task_sms_client account, which is a set of SMSAdmins, to the list of accounts for client push installation, the installation will certainly succeed.

    I was able to reproduce this behavior in two different SCCM 2007 configurations. Am I working something wrong, or is this a better bug?



    The software to fix your PC is just a click away - download it now.