3 Replies Latest reply on Jun 19, 2018 5:28 AM by MarkusMichalski

    Checksum is not written into the database

    Sebastian Silaghi Apprentice

      Does anybody know where to search for, if all our new or revisioned packages will not refresh/create their checksum within the database?

       

      Our problem is:

      - We create a new package or a new revision

      - distribute it

      - checksum is ok within the depot files but not in the properties pane in the dsmc. it is also missing within the database

       

      Therefore all the packages will not be executed due to crc error.

       

      Inc is open at Ivanti.

       

      DSM 2016.2 R2

      Not working on all devices.

       

      Thx

      Lucky

        • 1. Re: Checksum is not written into the database
          MarkusMichalski Specialist

          Hi,

           

          I have seen this before, the message queue on the SQL DB was the culprit, because there were blocking jobs.

           

          Regards, Markus

          • 2. Re: Checksum is not written into the database
            Sebastian Silaghi Apprentice

            Hi Markus,

             

            thanks for your answer. In our case it is the same problem. We have about 200 000 - 350 000 messages in the que. Do you know how to find the probably blocking jobs? Incident at ivanti is since one week in dev but we didn't get a workaround or something like that. The que is sometimes shrinking than again growing, so the jobs are beeing processed but very slow.

             

            Regards,

            Lucky

            • 3. Re: Checksum is not written into the database
              MarkusMichalski Specialist

              Sebastian,

               

              The message queue is processed by the BLS Auxilary Service, please check the logs of this service, if there are any exceptions/error messages. Also check, if the process of the aux service is in a running state. The messages for the queue will be resent to the BLS by the clients (or in your case the Management Point Servers, sending the distribution messages) every 24hrs.

               

              So if the aux process is hanging or not running at all, the message queue will sum up pretty quickly. You should problably update the ticket with your findings, and/or escalate the issue to customer service.

               

              Markus

              1 of 1 people found this helpful