N-central Troubleshooting

Error: Attempting to set a non-NULL-able column's value to NULL

Last Modified

Mon Jan 09 18:36 GMT 2023

Description

This article explains what to do if RM Logs are showing the message: "Attempting to set a non-NULL-able column's value to NULL" in ETL process.

Environment

RM 4.x
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012

Solution

There is a known issue with SQL Server 2008, 2008 R2 or SQL Server 2012, that will cause the ETL to fail with the following error: Attempting to set a non-NULL-able column's value to NULL.
Apply the following cumulative update of SQL Server.
- Cumulative Update 10 for SQL Server 2008 R2 SP2
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server
- Latest cumulative update for SQL Server 2008 R2 SP2
Cumulative update package 1 for SQL Server 2012 Service Pack
- The fix for this issue was first released in Cumulative Update 1.
- For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
  - Cumulative update package 1 for SQL Server 2012 Service Pack 1
- Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
- We recommend that you consider applying the most recent fix release that contains this hotfix.
- For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  - The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
SQL Server 2008 R2 Service Pack 1
- The fix for this issue was first released in Cumulative Update 8.
- For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
  - Cumulative update package 8 for SQL Server 2008 R2 SP1
- Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release.
- We recommend that you consider applying the most recent fix release that contains this hotfix.
- For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  - The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released
SQL Server 2012
- The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012.
- For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
  - Cumulative update package 3 for SQL Server 2012
- Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
- Microsoft recommends that you consider applying the most recent fix release that contains this hotfix.
- For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  - The SQL Server 2012 builds that were released after SQL Server 2012 was released
- You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
SQL Server 2008 Service Pack 3
- The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 3.
- For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
  - Cumulative update package 6 for SQL Server 2008 Service Pack 3
- Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
- Microsoft recommends that you consider applying the most recent fix release that contains this hotfix.
- For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  - The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
- Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs.
- You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3.
- By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 R2
- The fix for this issue was first released in Cumulative Update 14.
- For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
  - Cumulative Update package 14 for SQL Server 2008 R2
- Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
- We recommend that you consider applying the most recent fix release that contains this hotfix.
- For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  - The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
SQL Server 2008 Service Pack 2
- The fix for this issue was first released in Cumulative Update 9 for SQL Server 2008 Service Pack 2.
- For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
  - Cumulative update package 9 for SQL Server 2008 Service Pack 2
- Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
- We recommend that you consider applying the most recent fix release that contains this hotfix.
- For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  - The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Reference: https://support.microsoft.com/en-us/kb/2671078
NOTE: Microsoft has confirmed that this is a problem in the Microsoft products:
- SQL Server 2008
- SQL Server 2008 R2
- SQL Server 2012
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the N-able software or documentation that you purchased from N-central, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.