5 Replies Latest reply on Aug 21, 2018 10:37 AM by mpinkos

    Replicator Stops reporting

    mpinkos Apprentice

      We have random issues where the replicator stops reporting after so long.  Than it works other times.

       

      We have tried to reinstall agent on client no correct.  

       

       

      2018 10:11:33 Last status: Retrying in 1 seconds...

      Thu, 01 Feb 2018 10:11:54 Action SOAPAction: "http://tempuri.org/ResolveDeviceID" failed, socket error: 0, SOAPCLIENT_ERROR: 5.  Status code: 503, fault string:

      Thu, 01 Feb 2018 10:11:54 Disabling vulscan's & lddwnld.dll's use of proxyhost

      Thu, 01 Feb 2018 10:11:54 ERROR: function DisableProxyHost is no longer supported

      Thu, 01 Feb 2018 10:11:54   Retrying in 12 seconds...

      Thu, 01 Feb 2018 10:11:57 Last status: Retrying in 9 seconds...

      Thu, 01 Feb 2018 10:11:58 Last status: Retrying in 8 seconds...

      Thu, 01 Feb 2018 10:11:59 Last status: Retrying in 7 seconds...

      Thu, 01 Feb 2018 10:12:00 Last status: Retrying in 6 seconds...

      Thu, 01 Feb 2018 10:12:01 Last status: Retrying in 5 seconds...

      Thu, 01 Feb 2018 10:12:02 Last status: Retrying in 4 seconds...

      Thu, 01 Feb 2018 10:12:03 Last status: Retrying in 3 seconds...

      Thu, 01 Feb 2018 10:12:04 Last status: Retrying in 2 seconds...

      Thu, 01 Feb 2018 10:12:05 Last status: Retrying in 1 seconds...

      Thu, 01 Feb 2018 10:14:03 Action SOAPAction: "http://tempuri.org/ResolveDeviceID" failed, socket error: 10054, SOAPCLIENT_ERROR: 5.  Status code: -1, fault string:

      Thu, 01 Feb 2018 10:14:03 Disabling vulscan's & lddwnld.dll's use of proxyhost

      Thu, 01 Feb 2018 10:14:03 ERROR: function DisableProxyHost is no longer supported

      Thu, 01 Feb 2018 10:14:03 Handling case of core server not found.

      Thu, 01 Feb 2018 10:14:03 Last status: Failed: Core returned error

      Thu, 01 Feb 2018 10:14:03 GetComputerIdn {B717B54C-E7DF-2B41-AAF9-5DA53C6454DA} = -1

      Thu, 01 Feb 2018 10:14:03 Error:  Unable to resolve computer idn

        • 1. Re: Replicator Stops reporting
          phoffmann SupportEmployee

          So - first of all, what version are you on?

           

          Second - the fact that resolving device ID fails, seems to indicate that it's unable to talk to the IIS service(s) on the Core.

           

          Check the IIS logs on the Core, to see whether you see any kind of "poke" from that IP there (remember - IIS logs are always logged in GMT - so be wary of your time zone!).

           

          If it gets better if you run an "iisreset" (requires admin privileges) on the Core, this is down to an IIS load / configuration issue, which would need to be looked at seperately.

          • 2. Re: Replicator Stops reporting
            ggrassart Apprentice

            it's possible it's because your core server has been restarted.

             

            If you have a replicator runing you will have this message juste after the reboot of the core.

            • 3. Re: Replicator Stops reporting
              mpinkos Apprentice

              2017.3

               

              Any thoughts on what iis settings could be wrong?

              • 4. Re: Replicator Stops reporting
                ggrassart Apprentice

                i had just finish a communication with a customer about the same issue

                 

                when you run a replication,

                on replication settings on the core you can see the replication runing with the percent.

                you have it because your have a thread on landesk core listening what the replicator SEND to update what the replicator do ( create list download file....)

                So if your restart the core server there is no more thread listening the replicator.

                 

                Then the replictor faile to contact correctly the core server and we have this issue.

                 

                with the customer we have seen the issue appear at  4h AM it's time when it has restarted the core.

                 

                since 4h AM the replicator has the issue and the download of the wim was very long. (timeout,) 40% downloader and it stop to work every 10 minutes restart download and stop for 10 minutes stop.....

                 

                after restart of replication the replication of the wim has been finished on 3 minutes and we have the state in replication tools.

                 

                I don't know if you have undestand and if you have the same issue.

                 

                Regards,

                 

                Guillaume.

                • 5. Re: Replicator Stops reporting
                  mpinkos Apprentice

                  I get that..... But i am sure our core don't reboot..... Unless IIS is crashing.    We have logs to show it has long uptimes.