Jump to content
Welcome to our new Citrix community!
  • 0

App layering 19.11 error with vsphere / offload compositing


Tyler Dickey1709161241

Question

We're having some errors with publising our Win10 images after the update to 19.11. It seems like there is something in some of our layers that are causing an issue, as we can publish a plain vanilla OS layer without any issues. Our Server 2016 (with all app layers included) also works fine.

 

The error we see in the console is: <value missing>.

 

 

 

On the ELM logs, maservice.log we see:

 

2019-12-06 07:08:50,183 INFO   [220]        Shell: EXEC: /dev/nbd30 disconnected
2019-12-06 07:08:50,184 INFO   [237]        Shell: EXEC: Done - Exit Code:  0
2019-12-06 07:08:50,184 INFO   [237]        DiskAttachService: Checking to see if the process managing /dev/nbd30 is still active.
2019-12-06 07:08:50,185 INFO   [237]        DiskAttachService: Deleting differencing disk '/mnt/repository/tmp/568767ce_e0be_41a9_918e_05f9e5326006.qcow2'.
2019-12-06 07:08:50,223 INFO   [237]        PlatformConnectorS: TeardownCompositingEngine(Uni.Appliance.Services.PlatformConnectorServices.Model.VirtualMachineInfo)
2019-12-06 07:08:50,261 INFO   [237]        PlatformConnectorS: TeardownCompositingEngine(Uni.Appliance.Services.PlatformConnectorServices.Model.VirtualMachineInfo) => id: 8b8e3560-1829-11ea-b1a7-dbd8fb7e5557
2019-12-06 07:08:50,315 INFO   [237]        JobStatusUpdater: Updating Status of '[WorkItem Id: 22347778, WorkTicket Id: 22315009,  ItemId: 22216704, ItemType: Image, ItemName: R_W10_OEA_IMG_R098, State: Running]' with State 'Running' and Resource 'ConnectorStatusMessage' Args: Connecting to the vCenter server.
2019-12-06 07:09:00,352 INFO    [22]        JobStatusUpdater: Updating Status of '[WorkItem Id: 22347778, WorkTicket Id: 22315009,  ItemId: 22216704, ItemType: Image, ItemName: R_W10_OEA_IMG_R098, State: Running]' with State 'Running' and Resource 'ConnectorStatusMessage' Args: Detaching required disks from the virtual machine.
2019-12-06 07:09:10,391 INFO   [242]        PlatformConnectorT: TeardownCompositingEngineRequests RequestId 8b8e3560-1829-11ea-b1a7-dbd8fb7e5557 state: Done status: The compositing engine machine 'R_W10_OEA_IMG_R098-2019-12-06_06-55-36.507' has been deleted.
2019-12-06 07:09:10,391 INFO   [242]        PlatformConnectorS: Delete(8b8e3560-1829-11ea-b1a7-dbd8fb7e5557, TeardownCompositingEngineRequests)
2019-12-06 07:09:10,405 INFO   [242]        PlatformConnectorS: Delete(8b8e3560-1829-11ea-b1a7-dbd8fb7e5557, TeardownCompositingEngineRequests) => Done
2019-12-06 07:09:10,454 ERROR  [242]        AsyncWorkItemManag: WorkItem with id 22347778 finished with an exception: Uni.Core.Handlers.Exceptions.LocalizedErrorException`1[Uni.Core.Contract.Results.MmfErrorCategory]: <value missing>
  at Uni.Core.Contract.Results.ApplicationError.Throw () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Uni.Core\Contract\Results\ApplicationError.cs:396 
  at Unidesk.Ma.MaService.Services.CompositingEngine.CompositingEngineService.UpdateStatus (System.Int64 itemId, System.String address, System.Guid jobId, Unidesk.Ma.MaService.RegisteredTasks.RegisteredCancellation rc, Unidesk.Ma.Web.Contract.PeCal.Job& job) [0x00100] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\Services\CompositingEngine\CompositingEngineService.cs:249 
  at Unidesk.Ma.MaService.Services.CompositingEngine.CompositingEngineService+<RunJobToCompletion>d__24.MoveNext () [0x0010a] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\Services\CompositingEngine\CompositingEngineService.cs:173 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.ThrowIfCompletedUnsuccessfully () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:97 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.InternalWait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00022] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:63 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:53 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:38 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTask`1[T].get_Result () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTask.cs:34 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskAwaiter`1[T].GetResult () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskAwaiter.cs:43 
  at Unidesk.Ma.MaService.Services.CompositingEngine.CompositingEngineService+<RunJob>d__20.MoveNext () [0x0003e] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\Services\CompositingEngine\CompositingEngineService.cs:141 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.ThrowIfCompletedUnsuccessfully () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:97 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.InternalWait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00022] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:63 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:53 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:38 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskAwaiter.GetResult () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskAwaiter.cs:30 
  at Unidesk.Ma.MaService.Services.AsyncWorkItemHandlers.ExportImageWorkItemHandler+<Handle>d__12.MoveNext () [0x00572] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\Services\AsyncWorkItemHandlers\ExportImageWorkItemHandler.cs:103 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151 
  at Unidesk.Ma.MaService.Services.AsyncWorkItemHandlers.ExportImageWorkItemHandler+<Handle>d__12.MoveNext () [0x0098b] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\Services\AsyncWorkItemHandlers\ExportImageWorkItemHandler.cs:141 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.ThrowIfCompletedUnsuccessfully () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:97 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.InternalWait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00022] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:63 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:53 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:38 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTask`1[T].get_Result () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTask.cs:34 
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskAwaiter`1[T].GetResult () [0x00001] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskAwaiter.cs:43 
  at Unidesk.Ma.MaService.Services.AsyncWorkItemManager+<RunHandler>d__19.MoveNext () [0x00077] in d:\builds\R4OUTCOME-WSW-JOB1\source\Unidesk.Ma\MaService\Services\AsyncWorkItemManager.cs:187 
2019-12-06 07:09:10,460 INFO   [242]        WorkItem: Setting State of [WorkItem Id: 22347778, WorkTicket Id: 22315009,  ItemId: 22216704, ItemType: Image, ItemName: R_W10_OEA_IMG_R098, State: Running] to 'Failed'

 

Any insight to what other logs to look into or where to go from here would be helpful. This was working fine before offload compositing with the same layers, so I'm not sure why enabling offload compositing is now causing an issue.

Link to comment

9 answers to this question

Recommended Posts

  • 0

Scratch that, this is not figured out quite yet. It seems there are certain layers that are conflicting somehow in the compositing process. It works no problem without the compositing, but with compositing there are issues. 

 

It happens right after compositing is done and the machine, I guess reboots. RIght before the registry starts assembling. I'm not sure if there is some kind of conflict between the layers, but I'm not sure how to get logs off the machine that is created and booted up in windows pe mode.

Link to comment
  • 0

Hello,

 

I'm having exactly the same issue on App Layering 2001 with Offload Compositing enabled on my connectors. The issue ceases to exist when I exclude Application Layers that were created using a connector with Offload Compositing.

 

Any update on this issue? You may find the stack trace down below;

 

2020-02-13 11:19:29,584 INFO   [232]        PlatformConnectorT: TeardownCompositingEngineRequests RequestId 823623b0-4e39-11ea-87c0-bfb61a2f114c state: Done status: The compositing engine machine 'W10_1903 - BT - İstemci Yönetimi-2020-02-13_11-08-18.465' has been deleted.
2020-02-13 11:19:29,584 INFO   [232]        PlatformConnectorS: Delete(823623b0-4e39-11ea-87c0-bfb61a2f114c, TeardownCompositingEngineRequests)
2020-02-13 11:19:29,601 INFO   [232]        PlatformConnectorS: Delete(823623b0-4e39-11ea-87c0-bfb61a2f114c, TeardownCompositingEngineRequests) => Done
2020-02-13 11:19:29,690 ERROR  [232]        AsyncWorkItemManag: WorkItem with id 23691267 finished with an exception: Uni.Core.Handlers.Exceptions.LocalizedErrorException`1[Uni.Core.Contract.Results.MmfErrorCategory]: <value missing>
  at Uni.Core.Contract.Results.ApplicationError.Throw () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Uni.Core\Contract\Results\ApplicationError.cs:396
  at Unidesk.Ma.MaService.Services.CompositingEngine.CompositingEngineService.UpdateStatus (System.Int64 itemId, System.String address, System.Guid jobId, Unidesk.Ma.MaService.RegisteredTasks.RegisteredCancellation rc, Unidesk.Ma.Web.Contract.PeCal.Job& job) [0x00100] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\Services\CompositingEngine\CompositingEngineService.cs:249
  at Unidesk.Ma.MaService.Services.CompositingEngine.CompositingEngineService+<RunJobToCompletion>d__24.MoveNext () [0x0010a] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\Services\CompositingEngine\CompositingEngineService.cs:173
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.ThrowIfCompletedUnsuccessfully () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:97
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.InternalWait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00022] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:63
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:53
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:38
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTask`1[T].get_Result () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTask.cs:34
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskAwaiter`1[T].GetResult () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskAwaiter.cs:43
  at Unidesk.Ma.MaService.Services.CompositingEngine.CompositingEngineService+<RunJob>d__20.MoveNext () [0x0003e] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\Services\CompositingEngine\CompositingEngineService.cs:141
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.ThrowIfCompletedUnsuccessfully () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:97
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.InternalWait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00022] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:63
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:53
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:38
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskAwaiter.GetResult () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskAwaiter.cs:30
  at Unidesk.Ma.MaService.Services.AsyncWorkItemHandlers.ExportImageWorkItemHandler+<Handle>d__12.MoveNext () [0x00572] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\Services\AsyncWorkItemHandlers\ExportImageWorkItemHandler.cs:103
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151
  at Unidesk.Ma.MaService.Services.AsyncWorkItemHandlers.ExportImageWorkItemHandler+<Handle>d__12.MoveNext () [0x0098b] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\Services\AsyncWorkItemHandlers\ExportImageWorkItemHandler.cs:141
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /builddir/build/BUILD/mono-5.2.0.224/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:151
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.ThrowIfCompletedUnsuccessfully () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:97
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.InternalWait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00022] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:63
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait (System.TimeSpan timeout, System.Threading.CancellationToken cancellationToken) [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:53
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskBase.Wait () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskBase.cs:38
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTask`1[T].get_Result () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTask.cs:34
  at Unidesk.Ma.MaService.RegisteredTasks.RegisteredTaskAwaiter`1[T].GetResult () [0x00001] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\RegisteredTasks\RegisteredTaskAwaiter.cs:43
  at Unidesk.Ma.MaService.Services.AsyncWorkItemManager+<RunHandler>d__19.MoveNext () [0x00077] in d:\builds\R4EMERALDLAKE-WSW-JOB1\source\Unidesk.Ma\MaService\Services\AsyncWorkItemManager.cs:187

Link to comment
  • 0

I know it's not the best answer but to fix the <value missing> error we ended up re-creating the layer causing issues, after narrowing it down to a specific layer or 2. But we also ended up giving up on the offload compositing until a proper fix is released to make office work with the offload compositing change (separate, but possibly related issue).

 

I'm not sure if it's related, but for the office issue, support was able to determine that it is a known bug related to 8.3 shortnames. They said this was expected to be fixed in March, but no guarantees... :(.

 

Like I said, we ended up simply disabling the offload compositing engine as it seemed it wasn't ready for production at this point in time. It really sucks to have to wait to use it because it helps publishing times so much, but that was our end result. Hopefully that helps.

Link to comment
  • 0

Hello everybody,

 

I have nearly the same error.

 

First of all it started with the Office 2016 prof plus layer not working anymore on the published Image (compositing offloading enabled).

 

On the packaging machine Office is working properly. But after publication it Ends up in Errors.

 

After testing all possible Scenarios with older versions of the layers I assume that the Problem have to be the compositing engine. As deploying wihtout this Feature, Office is working on the Image.

 

Running on Windows Server 2019 and ELM 2001

 

Hope Citrix will fix this soon

 

BR,

Marcel

Link to comment
  • 0

tdickey77 - i am seeing an issue with offload compositing in v2003 still. It just sits there when pubishing and never sends any layers to vsphere to composite. If i turn it off and composite on the ELM appliance, it works fine (albeit slower). 

 

Did you say that you had to update some of the app layers since upgrade to get OC to work? We have some layers that were there from a few versions ago and never needed to be touched. I need to figure out which ones may be causing the issue first, but i'm hoping it's just a case of spinning up a new version and sealing again

Link to comment
  • 0
3 hours ago, Olly Thompson1709156630 said:

tdickey77 - i am seeing an issue with offload compositing in v2003 still. It just sits there when pubishing and never sends any layers to vsphere to composite. If i turn it off and composite on the ELM appliance, it works fine (albeit slower). 

 

Did you say that you had to update some of the app layers since upgrade to get OC to work? We have some layers that were there from a few versions ago and never needed to be touched. I need to figure out which ones may be causing the issue first, but i'm hoping it's just a case of spinning up a new version and sealing again

Yeah, that's exactly what we did. We just created a new version for every layer (hopefully not too many) and then finalized the version without making any changes to the layer. We did this for every layer in the image.

 

If that doesn't work, try narrowing it down layer by layer until you find the one that isn't working and then re-create that layer. Hopefully that helps!

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...