Skip to main content
Michael B. UK
Inspiring
July 7, 2025
Question

Elements 25. Strange log file entry, can someone please check their log file?

  • July 7, 2025
  • 0 replies
  • 111 views

Windows 11
Hello all, I'm seeing this entry in my log file. C:\Users\mickb\AppData\Roaming\Adobe\Elements Organizer\25.0\logs
I'm wondering if it's normal?

Log file created: 07/07/25 07:12:20
-------------------------------------
Ticks = 16      <17600> <NGL> <5> NGL and floodgate are running on prod
Ticks = 157      <17600> <NGL> <5> InitializeProfileUpdates returned mErrorCode = NglStatusCode:403 NGL Profile Unavailable
Ticks = 157      <17600> <NGL> <5> GetAMTData returned mErrorCode = NglStatusCode:403 NGL Profile Unavailable
Ticks = 3657      <17740> <DynamicLink> <5> Increase wait time to 2
Ticks = 3703      <17600> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 3703      <17600> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 3703      <17600> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 4344      <17600> <GPUFoundation> <0> Error initializing RED SDK (options: 3): 2
Ticks = 6750      <17600> <LUTManager> <5> Pre-Installed Lumetri LUTs path does not exist: C:\Program Files\Adobe\Elements 2025 Organizer\Lumetri
Ticks = 6750      <17600> <LUTManager> <5> Pre-Installed Lumetri LUTs path does not exist: C:\Program Files\Adobe\Elements 2025 Organizer\Lumetri
Ticks = 6766      <17600> <HighBeam> <5> No user ID while HL init
Ticks = 8078      <17740> <GPUFoundation> <5> Done loading modules, sec: 1.35329, device: CUDA(0)
Ticks = 41750      <17600 (main)> <assert> <5> Assertion Failed
{
expression: "paramData != NULL"
hash: "a4e040f8-8090-fed3-10ab-454400000036"
lastError: "183"
message: "CAUTION !!! The parameter was not found. There seems to be something really fishy out here !!!"
sourceFile: "E:\Adobe\workspace\PRE-X\PremiereElements\ContentAnalysis\ContentAnalysisData\Src\ClipData.cpp"
sourceFunction: "CAD::CAClipData::GetClipTagData"
sourceLine: "209"
timestamp: "2025-07-07T07:13:02.0Z"
}
Callstack: 
[
    dvacore::debug::DoSimpleAssert ( @ 0) (dvacore.dll+0x00000000000EEBEE)
    dvacore::debug::DoSimpleAssert ( @ 0) (ContentAnalysisData.dll+0x000000000000D3FE)
    CAD::GetCADataManager ( @ 0) (ContentAnalysisData.dll+0x000000000001A60B)
    CA::Utils::GetCATags ( @ 0) (ContentAnalysisHost.dll+0x00000000000340E1)
    imageUtil::PIEWrapper::getIsPIEInitialized ( @ 0) (Elements Auto Creations 2025.exe+0x0000000000503B38)
    imageUtil::PIEWrapper::getIsPIEInitialized ( @ 0) (Elements Auto Creations 2025.exe+0x00000000004F6690)
    dvacore::messaging::Broadcaster::BroadcastMessage ( @ 0) (dvacore.dll+0x00000000001671BB)
    dvacore::config::PurgeMemory ( @ 0) (dvacore.dll+0x00000000000AD347)
    dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler ( @ 0) (dvacore.dll+0x00000000000AB7B6)
    dvacore::config::ExecuteTopLevelFunction ( @ 0) (dvacore.dll+0x00000000000AD0D3)
    dvacore::messaging::Broadcaster::BroadcastMessage ( @ 0) (dvacore.dll+0x0000000000166F50)
    dvacore::messaging::BroadcastMessage ( @ 0) (dvacore.dll+0x000000000016CD2C)
    CA::CAManager::StartAnalysis ( @ 0) (ContentAnalysisHost.dll+0x000000000002B9A7)
    imageUtil::PIEWrapper::getIsPIEInitialized ( @ 0) (Elements Auto Creations 2025.exe+0x00000000004FBE27)
    dvacore::messaging::Broadcaster::BroadcastMessage ( @ 0) (dvacore.dll+0x00000000001671BB)
    dvacore::config::PurgeMemory ( @ 0) (dvacore.dll+0x00000000000AD347)
]
 
Ticks = 41750      <17600 (main)> <assert> <5> Assertion Failed
{
assertCount: "2"
expression: "paramData != NULL"
hash: "a4e040f8-8090-fed3-10ab-454400000036"
message: "CAUTION !!! The parameter was not found. There seems to be something really fishy out here !!!"
skippedCount: "1"
sourceFile: "E:\Adobe\workspace\PRE-X\PremiereElements\ContentAnalysis\ContentAnalysisData\Src\ClipData.cpp"
sourceFunction: "CAD::CAClipData::GetClipTagData"
sourceLine: "209"
timestamp: "2025-07-07T07:13:02.0Z"