Multiple warnings about "spGetIpRangeDataByTaskGuid" stored procedure

Products

• IT Management Suite
• Deployment Solution

Issue/Introduction

You recently upgraded to ITMS 8.7.2 release and while looking at the NS logs on your SMP Server, you noticed the following warning message:

Attempt to execute procedure 'spGetIpRangeDataByTaskGuid' that does not exist in the white list

This message appears in SMP log during the execution of the "Apply System Configuration" task.

Environment

ITMS 8.7.2

Cause

Known issue. This "spGetIpRangeDataByTaskGuid" stored procedure is introduced by Deployment Solution. This warning is not a reflection of something wrong. It usually means at the Deployment Solution install/upgrade setup time about this procedure, it was not added it into 'white list', that we use for SP's that are possible to run from tasks.

"spGetIpRangeDataByTaskGuid" is created by this config file:

C:\Program Files\Altiris\Deployment\Config\Altiris.Deployment_PostInstallSQL.config 

 

<sqlObject name="spGetIpRangeDataByTaskGuid">
        <sqlStatement exists="true"><![CDATA[
        drop proc dbo.spGetIpRangeDataByTaskGuid
      ]]></sqlStatement>
        <sqlStatement exists="both"><![CDATA[
        -- =============================================
        -- Author:        <Author, Mark>
        -- Desc: 
        -- =============================================

        create proc dbo.spGetIpRangeDataByTaskGuid
        @taskGuid uniqueidentifier
        as 
        begin
                SET TRANSACTION ISOLATION LEVEL READ COMMITTED
                BEGIN TRANSACTION
                  update IpRangeData
                    set NextIpAddress = c.NextIpAddress+1
                    from dbo.IpRangeData c
                    where Task =@taskGuid
                 
                  select Task, NICNumber, Network, NextIpAddress-1 as NextIpAddress, WildcardMask
                  from dbo.IpRangeData where Task = @taskGuid
                COMMIT
        end
      ]]></sqlStatement>
    </sqlObject>

Resolution

This issue has been fixed in our ITMS 8.8 release.

This warning can be ignored at the moment for those with 8.7.2 and 8.7.3 versions.