/build/static/layout/Breadcrumb_cap_w.png
05/17/2018 480 views
Noticing that uninstalling KBOX agent (7.2 or 8.1) we are unable to create SharePoint documents. Can reproduce easily, install client, infopath form works, uninstall client, infopath form immediately breaks.

I do not understand it, if I din't see it with my own eyes. Uninstall KBOX client, bam, InfoPath broken.

Have a case open with Quest, have a case open with Microsoft.

Sending an SOS in a bottle...

Image of InfoPath error:

5 Comments   [ + ] Show comments

Comments

  • Impossible....

    Those are not related at all.... Unless..... You are pushing some script with the KACE agent to mess around or update the hosts file... or something related to that... a Registry key maybe?

    Infopath and the KACE agent are 100% not related, removing a KACE agent should not affect an Online based tools, like I said unless the agent is pushing something vital... but that would not make any sense either... since push and scripts are normally one time job.

    Is this happening to one or multiple machines?

    Go to IMGUR and upload a screenshot please (remove any sensitive data)
    • Impossible? No. Improbable. Yes. However...please read my notes.."Can reproduce easily, install client, infopath form works, uninstall client, infopath form immediately breaks...I do not understand it, if I din't see it with my own eyes. Uninstall KBOX client, bam, InfoPath broken."
      • Ok Ok, a very odd anomaly,

        I will subscribe to see what the outcome is...

        Amount of computers affected?

        Could you please let us know what exactly happens to InfoPath?
  • Agreed. "A very odd anomaly". Really, If I wasn't reproducing the error each and every time, I wouldn't(still don't) believe it. Quest has been very silent even though the ticket is set to critical.
    • I saw your screenshot, honestly I haven't used infopath ever in my life, so probably I'll add more questions to the thread...

      But Maybe the microsoft guys could help us to determine what application or add-ins, or processes are involved... to make that error message pop-up.
  • Update: Quest technicians have acknowledged the error occurs during the uninstall. A video was created. I am getting "our developers are working on this, no status at this time" responses.
  • Update: Channeler, yes, Microsoft has identified the two DLLs that are called at this event, files look good (they don't change during uninstall), possibly registry related. We have informed Quest of MS findings.
    • Apologies for the delay. The case came to my attention yesterday (I'm a dev), and I'm still piecing together the details. We don't have any note about the two DLLs you discussed with Microsoft in our ticket anywhere, so I'll be reaching out to you shortly.
  • Quest technician has acknowledged the error and is currently working the issue.

All Answers

1
At first I would do the following:
1. export the registry when all works
2. do the problematic step (uninstall the agent)
3. export the registry when it is broken
4. compare the registries

I assume a Winlogin Hook is set and needed and when the KACE agend uninstalls itself the Winlogin is set to the default value:
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows NT > Current Version > Winlogin
Answered 05/19/2018 by: Nico_K
Red Belt

  • Nico will test, any suggestions on a reg compare tool?