Skip to main content
Question

MBS Xojo Plugins Popup

  • August 22, 2018
  • 21 replies
  • 31 views
G
Forum|alt.badge.img+3

I am getting the following message when Running 10.6.2 on macOS Mojave Beta (18A314k)

MBS Xojo Plugins
This serial number is too old for this plugin version. Please update your license key. (None: Registration, Version 18.0 from Jan 22 2018, Process ID: 97599)

Separate Popup, same branding:

This application uses unregistered plugins from Monkeybread Software. Please inform the developer of this application that they need to purchase a license from Monkeybread Software to remove this message. Thank you. (Util: Process, Version 18.0 from Jan 20 2018, Process ID: 97599)

And then I get a JAMF Remote branded dialog box of

A Critcal Error has occured (-14999)

    21 replies

    A
    Forum|alt.badge.img+5
    • andy_granger
    • New Contributor
    • 14 replies
    • August 22, 2018

    The same is happening to me, too, on High Sierra 10.13.6 (17G2208).

    I've seen the identical errors from Jamf Remote and Jamf Admin, respectively.


    N
    Forum|alt.badge.img+13
    • npynenberg
    • Contributor
    • 35 replies
    • August 23, 2018

    Same here. Kinda of a day wrecker for me. This was on 10.13.6.

    S
    Forum|alt.badge.img
    • stremtan
    • New Contributor
    • 1 reply
    • August 23, 2018

    Same issues for us too. Need to get this fixed Jamf!

    bpavlov
    Forum|alt.badge.img+18
    • bpavlov
    • Esteemed Contributor
    • 1206 replies
    • August 23, 2018

    🤭🤫

    S
    Forum|alt.badge.img+6
    • Sims_
    • Contributor
    • 35 replies
    • August 23, 2018

    I am seeing the same thing.

    S
    Forum|alt.badge.img+7
    • stuffelse
    • New Contributor
    • 7 replies
    • August 23, 2018

    Same thing for me. All three technicians affected, only Remote seems to not work for us. Just opened a support case a minute ago.

    EDIT: posted too soon. I believe the three of us are all on 10.13.6, at least I confidently am.

    Did someone at Jamf forget to pay the Monkey Bread bill? :)

    S
    Forum|alt.badge.img+4
    • sggr57a
    • Contributor
    • 21 replies
    • August 23, 2018

    We were told to use Jamf Pro Remote 10.6.0 for the time being.

    A
    • Anonymous
    • 0 replies
    • August 23, 2018

    Having the same problem with a client. Trying 10.6.0 to see if that works.

    It does.

    bpavlov
    Forum|alt.badge.img+18
    • bpavlov
    • Esteemed Contributor
    • 1206 replies
    • August 23, 2018

    Wouldn't using 10.6.0 when your JSS is on 10.6.2 stop you from using it? I imagine it would tell you there's a version mismatch and tell you to use the appropriate version. The other thing it might do is downgrade/upgrade the jamf binary I think.

    S
    Forum|alt.badge.img+7
    • stuffelse
    • New Contributor
    • 7 replies
    • August 23, 2018

    Support said it's a listed product issue: PI-006187: Jamf Remote MBS Xojo Plugins fail on 10.6.2

    Aside from remote "Update Inventory" panicking about the binary version discrepancy, using Remote 10.6.0 seems to work.

    S
    Forum|alt.badge.img+1
    • seb-o2i
    • New Contributor
    • 1 reply
    • August 24, 2018

    Same problem for me...
    Using Jamf admin tool version 10.6.0 resolve the issue.
    Seems that Jamf dev team missed something when compiling last version of the admin tools.

    D
    Forum|alt.badge.img+14
    • djdavetrouble
    • Valued Contributor
    • 131 replies
    • August 24, 2018

    gonna hold off on this release thanks guys.

    R
    Forum|alt.badge.img+5
    • Raven_D
    • Contributor
    • 19 replies
    • August 28, 2018

    Following: Also getting the "MBS Xojo Plugins" error. Running 10.6.2 and OS 10.13.6

    R
    Forum|alt.badge.img+18
    • rcorbin
    • Valued Contributor
    • 278 replies
    • August 29, 2018

    I'm looking at upgrading to 10.6.2 and then using the 10.6.0 tools. But this does feel a little odd. It's strange that Jamf hasn't released a new set of the 10.6.2 tools with a fix for this. Seems like something that should be easy to do.

    J
    Forum|alt.badge.img+1
    • jose_gocobachi
    • New Contributor
    • 5 replies
    • September 2, 2018

    Same issues too. My solution was to install an older version of Jamf Remote 10.4.2. The rest of the 10.6.2 suite seems to be stable. No other issues to report.

    R
    Forum|alt.badge.img+5
    • Raven_D
    • Contributor
    • 19 replies
    • September 4, 2018

    I raised a ticket with JAMF about it. They are aware and working on a fix for the issue and recommended using the above solution if you have 10.6.2 installed use the 10.6.0 tools.

    L
    Forum|alt.badge.img+9
    • luke_reagor
    • Contributor
    • 79 replies
    • September 11, 2018

    This is still a problem. Got it today after upgrading jamf to 10.6.2.

    C
    Forum|alt.badge.img+4
    • cornwella
    • Contributor
    • 15 replies
    • September 14, 2018

    Same here, 10.13.6 with Jamf Pro 10.6.2. Using 10.6.0 works.

    K
    Forum|alt.badge.img+4
    • Kmartin
    • Contributor
    • 13 replies
    • September 14, 2018

    Jamf Pro 10.7 fixed the issue for me.

    roiegat
    Forum|alt.badge.img+16
    • roiegat
    • Valued Contributor
    • 412 replies
    • September 25, 2018

    Anyone find get a fix yet for JAMF Pro 10.6.2?

    R
    Forum|alt.badge.img+4
    • rcarey
    • Contributor
    • 15 replies
    • September 25, 2018

    I'm still on 10.6.2, but just using the 10.7 Remote. Working normally for me. Everything else seems to work normally on 10.6.2.


    Terms & ConditionsCookie settingsAccessibility statement