Ixiguis
December 13, 2018, 12:34am
1
I get the error below when packaging a project.
It’s a project that I’ve been working on since 4.19 I think. It was imported using Datasmith 4.19.
It used to package without problems on UE 4.20.3. Now this is my first attempt to package this project after updating to 4.21.1, and I got this error.
Full log attached.
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: begin: stack for UAT
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: === Handled ensure: ===
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error:
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: Ensure condition failed: It->Value [File:D:\Build\++UE4\Sync\Engine\Plugins\Enterprise\DatasmithContent\Source\DatasmithContent\Private\DatasmithAssetUserData.cpp] [Line: 25]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: Stack:
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff869d116e6 UE4Editor-DatasmithContent.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff87817d25a UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff87826d7f5 UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff878288a24 UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff878287c19 UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff875c4620f UE4Editor-Engine.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff87337d511 UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8733830b9 UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8733a2200 UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff87320516b UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff87323722f UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff77412ed22 UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff774125783 UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff7741259ea UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff7741348da UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff77413584e UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8c6113034 KERNEL32.DLL!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8c8893691 ntdll.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: end: stack for UAT
I’ve got the exact issue and exact same circumstances.
Any luck fixing yet?
I don’t believe that we have a prior awareness of this issue. In order for us to properly investigate, you may need to report this issue at the linked form , and provide your project so that we may reproduce.
Thank you.
Ixiguis
December 14, 2018, 4:49pm
4
I have filed the bug report as Stephen suggested and will update here when I have news.
spazfirem
December 14, 2018, 4:49pm
5
I ran into packaging issues last night with a 4.21 project as well. WIndows and Android platforms were fine, but iOS gave me a similar, but slightly different issue relating to Datasmith.
To get past it, I opened up the .uproject file with a text editor and removed the “enterprise: true” line near the top and removed the datasmith plugins from the project settings. It worked, but now I have cert issues which should be completely unrelated, but who knows.
There’s a few answerhub posts about the enterprise: true thing, maybe give that shot. (backup the .uproject file though to be safe)
Ixiguis
December 14, 2018, 5:34pm
6
spazfirem:
I ran into packaging issues last night with a 4.21 project as well. WIndows and Android platforms were fine, but iOS gave me a similar, but slightly different issue relating to Datasmith.
To get past it, I opened up the .uproject file with a text editor and removed the “enterprise: true” line near the top and removed the datasmith plugins from the project settings. It worked, but now I have cert issues which should be completely unrelated, but who knows.
There’s a few answerhub posts about the enterprise: true thing, maybe give that shot. (backup the .uproject file though to be safe)
I tried that and unfortunately didn’t work for me, thanks for the suggestion though.
I’m getting the same error. It was imported using Datasmith 4.19.
It used to package without problems. Attempt to package this project after updating to 4.21.1
LogOutputDevice: Error: === Handled ensure: ===
LogOutputDevice: Error: Ensure condition failed: It->Value [File:D:\Build\++UE4\Sync\Engine\Plugins\Enterprise\DatasmithContent\Source\DatasmithContent\Private\DatasmithAssetUserData.cpp] [Line: 25]
LogOutputDevice: Error: Stack:
LogOutputDevice: Error: [Callstack] 0x00007ffa4d5a16e6 UE4Editor-DatasmithContent.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa6479d25a UE4Editor-CoreUObject.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa6479d1ad UE4Editor-CoreUObject.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa6488d7f5 UE4Editor-CoreUObject.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa648a8a24 UE4Editor-CoreUObject.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa648a7c19 UE4Editor-CoreUObject.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa55d770b8 UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa55d66965 UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa55d4a54f UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa56650a03 UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa56125cac UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa56125a93 UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa56669505 UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffa5664f203 UE4Editor-UnrealEd.dll!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ff6bc4d584f UE4Editor.exe!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ff6bc4d59ea UE4Editor.exe!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ff6bc4e48da UE4Editor.exe!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ff6bc4e659a UE4Editor.exe!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffab9de3034 KERNEL32.DLL!UnknownFunction ]
LogOutputDevice: Error: [Callstack] 0x00007ffaba093691 ntdll.dll!UnknownFunction ]
I know this error has been submitted as a bug report but does it have an UE-[00000] issue number yet?
Ixiguis
December 20, 2018, 3:51pm
9
I don’t know about that, but I got a reply from the studio team, they could reproduce the issue and are currently investigating it.
Even now I’m still getting this build error. Has anyone made progress with a solve or workaround?
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: begin: stack for UAT
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: === Handled ensure: ===
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error:
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: Ensure condition failed: It->Value [File:D:\Build\++UE4\Sync\Engine\Plugins\Enterprise\DatasmithContent\Source\DatasmithContent\Private\DatasmithAssetUserData.cpp] [Line: 25]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: Stack:
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe89a816e6 UE4Editor-DatasmithContent.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe9de1d25a UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe9df0d7f5 UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe9df28a24 UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe9df27c19 UE4Editor-CoreUObject.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe7ce9620f UE4Editor-Engine.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe8fbc7871 UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe8fbcd4ea UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe8fbeca0b UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe8fa4a79b UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffe8fa7d0bf UE4Editor-UnrealEd.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff61afced22 UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff61afc5783 UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff61afc59ea UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff61afd48da UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff61afd584e UE4Editor-Cmd.exe!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffecc203034 KERNEL32.DLL!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ffece933691 ntdll.dll!UnknownFunction ]
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: LogOutputDevice: Error: end: stack for UAT
Ixiguis
January 6, 2019, 11:59pm
11
Nope, still waiting for news from the studio team.
There were delays over the holiday, but our team has confirmed the issue and logged it here for further review and resolution - Unreal Engine Issues and Bug Tracker (UE-68059)
Ixiguis
January 14, 2019, 9:00pm
13
Umm, I received an email today saying the issue was resolved, but looking at the above link, it still shows Unresolved. So what’s the status?
Hi Jefferson.
The email you received was about your support ticket being closed, but the issue itself has not been fixed yet. Support tickets for bug reports are typically closed when we confirm the issue and log an internal bug report for it. You can then follow the internal bug report to track the status. Your support ticket had been kept open for longer than normal, which I’m sure led to the confusion.
Depending on the issues that get reported to us, it may sometimes take months for a bug to get fixed. We avoid unnecessarily keeping the support tickets open for that duration.
Cheers
Ixiguis
January 17, 2019, 1:22am
15
I found a workaround!
Open the project, and disable all Unreal Studio-related plugins.
Close the editor, edit the uproject file, set Enterprise to false
Open the editor and check the message log. If any BP uses any function that depends on Datasmith, disable (remove / unpin) these functions
Open the levels you want to package. Re-save any asset that shows up with errors in the message log. Or simply ight-click the Content folder (in Content browser) and select Resave All
Package
However, you’ll lose all metadata from your meshes (permanently I guess), and functions that rely on Datasmith won’t work.
PS. I am not completely sure step 4 is necessary. Try skipping it at first.
Open the project, and disable all Unreal Studio-related plugins.
Close the editor, edit the uproject file, set Enterprise to false
Open the editor and check the message log. If any BP uses any function that depends on Datasmith, disable (remove / unpin) these functions
Open the levels you want to package. Re-save any asset that shows up with errors in the message log. Or simply ight-click the Content folder (in Content browser) and select Resave All
Package
Thanks, Ill try this today and see if it makes a change.
Ixiguis:
I found a workaround!
Open the project, and disable all Unreal Studio-related plugins.
Close the editor, edit the uproject file, set Enterprise to false
Open the editor and check the message log. If any BP uses any function that depends on Datasmith, disable (remove / unpin) these functions
Open the levels you want to package. Re-save any asset that shows up with errors in the message log. Or simply ight-click the Content folder (in Content browser) and select Resave All
Package
However, you’ll lose all metadata from your meshes (permanently I guess), and functions that rely on Datasmith won’t work.
PS. I am not completely sure step 4 is necessary. Try skipping it at first.
This worked! Thank you so much for sharing. Guess ill have to find another non-datasmith import workflow for now. My deadline was the 20th so this came right when I needed it. Ill stay to see when the proper fix comes though.