none
cannot create a boundary in SCCM 2012

    Question

  • I am configuring SCCM 2012 for the first time.  All discovery methods work fine, however no boundaries are populated.  I can get a machine to PXE boot and begin the task sequence but fails with message  '...cannot be located on a distribution point'.  I assume that is because there are no boundaries.   When trying to create one manually, I get the error below.  Doesn't matter what type of boundary I try to add, they all come back with the same error.  Any ideas?

    I am running Server 2008R2 w/sp1,  SQL server 2008R2 (no CU's), SCCM 2012 (not sp1).  I have SCCM 2007 running,  ifferent site code, both as stand alone.  I am not planning on migrating any settings, wanting to start fresh.   Could that be related?  


    ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    {
    CauseInfo = "";
    Description = "SQL command failed: insert into vSMS_Boundary (BoundaryFlags, BoundaryType, DisplayName, Value, CreatedBy, CreatedOn, ModifiedBy, ModifiedOn) values (0, 1, N'Primary Boundary', N'Default-First-Site-Name', N'accountname', N'06/26/2013 18:36:20', N'accountname', N'06/26/2013 18:36:20')\n;\n select scope_identity()";
    ErrorCode = 2168851714;
    File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssputility.cpp";
    Line = 2123;
    ObjectInfo = "Please check SMS Provider log file for details of the SQL errors";
    Operation = "PutInstance";
    ParameterInfo = "";
    ProviderName = "ExtnProv";
    SQLMessage = "[42000][524][Microsoft][SQL Server Native Client 10.0][SQL Server]A trigger returned a resultset and the server option 'disallow results from triggers' is true. : vSMS_Boundary_iu";
    SQLSeverity = 16;
    SQLStatus = 524;
    StatusCode = 2147749889;
    };

    -------------------------------
    Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
    The SMS Provider reported an error.


    Stack Trace:
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
       at Microsoft.ConfigurationManagement.AdminConsole.SmsDialogData.Put(Boolean retainLock)
       at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.Put(ActionTrigger trigger)

    -------------------------------

    System.Management.ManagementException
    Generic failure 


    Stack Trace:
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
       at Microsoft.ConfigurationManagement.AdminConsole.SmsDialogData.Put(Boolean retainLock)
       at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.Put(ActionTrigger trigger)

    -------------------------------


    Wednesday, June 26, 2013 8:44 PM

All replies

  • Hi To start with check SMSPROV.log for errors. Regards, Manohar Pusala
    Wednesday, June 26, 2013 9:06 PM
  • The error is the same as what I included originally: A trigger returned a resultset and the server option 'disallow results from triggers' is true

    If my reading is correct, isn't this a required setting in SQL 2012? 

    *** insert into vSMS_Boundary (BoundaryFlags, BoundaryType, DisplayName, Value, CreatedBy, CreatedOn, ModifiedBy, ModifiedOn) values (0, 1, N'Primary Boundary', N'Default-First-Site-Name', N'accountname', N'06/27/2013 15:15:11', N'accountname', N'06/27/2013 15:15:11')~;~ select scope_identity() SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)
    *** [42000][524][Microsoft][SQL Server Native Client 10.0][SQL Server]A trigger returned a resultset and the server option 'disallow results from triggers' is true. : vSMS_Boundary_iu SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)
    *~*~[42000][524][Microsoft][SQL Server Native Client 10.0][SQL Server]A trigger returned a resultset and the server option 'disallow results from triggers' is true. : vSMS_Boundary_iu     ThreadID : 1556 , DbError: 524 , Sev: 16~*~* SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\ssputility.cpp(2123) : SQL command failed: insert into vSMS_Boundary (BoundaryFlags, BoundaryType, DisplayName, Value, CreatedBy, CreatedOn, ModifiedBy, ModifiedOn) values (0, 1, N'Primary Boundary', N'Default-First-Site-Name', N'accountname', N'06/27/2013 15:15:11', N'accountname', N'06/27/2013 15:15:11')~;~ select scope_identity()~ SQL Error: [42000][524][Microsoft][SQL Server Native Client 10.0][SQL Server]A trigger returned a resultset and the server option 'disallow results from triggers' is true. : vSMS_Boundary_iu~*~* SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)
    *~*~SQL command failed: insert into vSMS_Boundary (BoundaryFlags, BoundaryType, DisplayName, Value, CreatedBy, CreatedOn, ModifiedBy, ModifiedOn) values (0, 1, N'Primary Boundary', N'Default-First-Site-Name', N'accountname', N'06/27/2013 15:15:11', N'accountname', N'06/27/2013 15:15:11')~;~ select scope_identity() [42000][524][Microsoft][SQL Server Native Client 10.0][SQL Server]A trigger returned a resultset and the server option 'disallow results from triggers' is true. : vSMS_Boundary_iu~*~* SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)
    ERROR: SQL command failed: insert into vSMS_Boundary (BoundaryFlags, BoundaryType, DisplayName, Value, CreatedBy, CreatedOn, ModifiedBy, ModifiedOn) values (0, 1, N'Primary Boundary', N'Default-First-Site-Name', N'accountname', N'06/27/2013 15:15:11', N'accountname', N'06/27/2013 15:15:11')~;~ select scope_identity() SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=73203232 SMS Provider 1/1/1601 12:00:00 AM 1556 (0x0614)


    Thursday, June 27, 2013 3:20 PM
  • >I am running...SQL server 2008R2 (no CU's)



    For SQL Server 2008 R2, SCCM 2012 requires you to be running SP1 CU6 or SP2.

    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig


    • Edited by JeremySD Thursday, June 27, 2013 6:29 PM typo
    Thursday, June 27, 2013 6:28 PM
  • I apologize for leaving it out.  We are running SQL 2008R2 Standard w/sp2.
    Thursday, June 27, 2013 8:59 PM
  • Please check if Trustworthy is set to ON, you can do this by going in SQL Server Management Studio > Right click the ConfigMgr database> go to options> under Miscellaneous make sure that TRUSTWORTHY is set to True

    You can turn TRUSTWORTHY on by running:

    ALTER DATABASE <DB_NAME> SET TRUSTWORTHY ON 
    
    

    When the database is not configured with this setting ON, <ConfigMgr_Install>\bin\x64\CryptoUtility.dll fails to load into SQL and you get these type of errors in the SMS Provider

    http://technet.microsoft.com/en-us/library/ms187861(v=sql.105).aspx

    Thursday, June 27, 2013 10:13 PM
  • We have verified that trustworthy is set to 'on'.  Thanks for the suggestion.
    Friday, June 28, 2013 1:21 PM
  • Same problem here, seems to be a bug in SCCM 2012 SP1 CU2.

    Issue occurs when creating a boundary based on a ip adress range. Ip adress subnets work fine.

    Monday, July 15, 2013 3:27 PM
  • Same problem here, seems to be a bug in SCCM 2012 SP1 CU2.


    No. Just created a boundary based on an IP range and it did work without any issues at all.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, July 15, 2013 9:00 PM
    Moderator
  • Interesting. We are running SQL 2012 on Windows server 2008 r2, and you?
    Monday, July 15, 2013 9:09 PM
  • I can confirm I am also experiencing this issue,

    I am running SCCM 2012 SP1 (5.0.7804.1000) on Server 2008 R2 SP1, but I am not running CU2.

    However I just applied CU4 to SQL Server 2012 SP1 on Server 2008 R2 SP1 and the problem appears to have occurred after this update.

    I have a number of existing boundary groups utilizing IP address range but I can't add new IP address range groups, I get the same SQL errors as above.

    Tuesday, July 16, 2013 2:24 AM
  • We are running SQL 2012 on Windows server 2008 r2, and you?

    SQL 2012 on server 2012.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, July 16, 2013 7:17 AM
    Moderator
  • This issue has been caused for us by installing some .NET 4 security updates.

    The updates in question are KB2835393 KB280457 and KB2840628 (2008R2)

    I removed those 3 updates from my SCCM box, it didn't resolve the problem, but after also removing from my SQL box the issue is resolved. I can now add boundary groups again and a number of other SQL/SCCM issues have also disappeared.


    Cheers guy

    • Proposed as answer by Reserwar Thursday, July 25, 2013 6:24 PM
    Wednesday, July 17, 2013 2:59 AM
  • Hello Torsten,

    Did you find a solution for Windows Server 2012? We run SCCM 2012 SP1. Both our SCCM database server and SCCM server run on Windows Server 2012.

    Thanks.

    Friday, October 25, 2013 9:45 AM
  • My collegue searched a bit deeper into the backgroud of the error:

    Error: ** [42000][524][Microsoft][SQL Server Native Client 11.0][SQL Server]A trigger returned a resultset and the server option 'disallow results from triggers' is true. : vSMS_Boundary_iu  $$<SMS Provider><10-25-2013 12:52:27.991-120><thread=4032 (0xFC0)>

    So this happens when the SQL Advance Option "disallow results from triggers Server Configuration Option" is set to 1. After a check we found that all our recently installed SQL server 2012 SP1 installations have this option set to 1.

    This is what Microsoft states about this option:

    Important: This feature will be removed in the next version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible.

    We recommend that you set this value to 1. When set to 1, the disallow results from triggers option is set to ON. The default setting for this option is 0 (OFF).

    So the feature will be removed in the future and is recommended to be set to 1. So why does SCCM 2012 SP1 use this feature?

    To check if this feature is on, run the following query on the database:

    EXEC sp_configure 'Show Advanced Options'1;
    GO
    RECONFIGURE;
    GO
    EXEC sp_configure;

    Friday, October 25, 2013 2:06 PM