This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- Data Platform
- :
- Data Platform Forum
- :
- SCCM Normalization Error: task_id cannot be NULL, please provide valid task_id @l_sub
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 26, 2018
10:57 AM
SCCM Normalization Error: task_id cannot be NULL, please provide valid task_id @l_sub
When we try to run a normalization on our SCCM data we get the following error:
task_id cannot be NULL, please provide valid task_id @l_subscription_id2578 Create NC_UNSUB_MAP table(PUBLISH
Which then stops the normalization. The product is ultimately useless if this normalization fails.
task_id cannot be NULL, please provide valid task_id @l_subscription_id2578 Create NC_UNSUB_MAP table(PUBLISH
Which then stops the normalization. The product is ultimately useless if this normalization fails.
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
4 Replies
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 04, 2018
02:15 AM
Hi Brian,
Are you still facing this issue?
-Vinod
Are you still facing this issue?
-Vinod
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 08, 2018
10:14 AM
vinodvenkatiah wrote:
Hi Brian,
Are you still facing this issue?
-Vinod
Hello,
I was able to apply a FlexDP update which seems to have fixed the issue. However, now I'm having difficulty getting FlexDP to work as expected with FNMS 2018 R1. The import from FlexDP to FNMS dumps the data into "Unrecognized Evidence" versus anywhere meaningful. Is this expected behavior?
Brian
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 09, 2018
03:37 AM
brianmcelraft wrote:
Hello,
I was able to apply a FlexDP update which seems to have fixed the issue. However, now I'm having difficulty getting FlexDP to work as expected with FNMS 2018 R1. The import from FlexDP to FNMS dumps the data into "Unrecognized Evidence" versus anywhere meaningful. Is this expected behavior?
Brian
Are you seeing a message like this(attached screenshot) in the System Health Dashboard?
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 22, 2018
05:29 PM
he process of normalization transforms all this data into actionable information which can be used for license management. It also creates consistency
