Skip to main content
Solved

Infrastructure Manager instance has not checked in with the JSS

  • October 23, 2023
  • 5 replies
  • 230 views
R
Forum|alt.badge.img+5

Hello,

I received this message from Jamf Pro Server :


jamfim.lfz.ch Infrastructure Manager instance has not checked in with the JSS.

 

What does this mean? Is it critical? Can you help me with any action I need to take?

 

Thanks !

Best answer by RBaZ

Hello,

Thanks for the answers
We found the problem
The connection with the LDAP server was broken (we tested the connection on JAMF Pro)
It was a VMWare update on our server that had disconnected a virtual card

Now we can reach the LDAP server and the message has disappeared
Problem solved! 👍

    5 replies

    Jason33
    Forum|alt.badge.img+13
    • Jason33
    • Honored Contributor
    • October 23, 2023

    Sometimes a simple reboot of the system hosting the JIM will suffice, and restore communication; that is what I would try first. Failing that, you may need to reinstall the Infrastructure Manager on the server. I believe I saw a thread not too long ago stating that a certificate may have expired, and the user needed to reinstall the JIM, per direction from Jamf.

    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • October 23, 2023

    @RBaZ I'd echo @Jason33 's suggestion of restarting your JIM instance, but if that doesn't work re-install shouldn't be necessary as just re-running the enroll command should re-generate the certificate used to secure communications.

    mm2270
    Forum|alt.badge.img+24
    • mm2270
    • Legendary Contributor
    • October 23, 2023

    I have this same error on our JIM, despite the fact that lookups continue to work. I pointed this out to a Jamf engineer I've been working with, and he has no idea how that can be the case. I haven't rebooted the system running JIM yet, but I'm going to do that to see if the error clears up, at least temporarily.

    R
    Forum|alt.badge.img+5
    • RBaZ
    • Author
    • New Contributor
    • Answer
    • October 24, 2023

    Hello,

    Thanks for the answers
    We found the problem
    The connection with the LDAP server was broken (we tested the connection on JAMF Pro)
    It was a VMWare update on our server that had disconnected a virtual card

    Now we can reach the LDAP server and the message has disappeared
    Problem solved! 👍

    Jason33
    DanTaylor
    Forum|alt.badge.img+3
    • DanTaylor
    • New Contributor
    • May 2, 2024

    I have this same error on our JIM, despite the fact that lookups continue to work. I pointed this out to a Jamf engineer I've been working with, and he has no idea how that can be the case. I haven't rebooted the system running JIM yet, but I'm going to do that to see if the error clears up, at least temporarily.


    Curious if you ever were told a solve on this? Our org is in a similar situation. 

    Terms & ConditionsCookie settingsAccessibility statement