The call resulted in multiple return values....

Tina_Sams

Hello,

I have just started getting the attached message when trying to submit a Change Request in our test system. Can someone point me in the direction of what is going wrong please? I can't see anything that has changed on the offering.

Thank you

joivan_hedrick

I tracked this one down. Enabling ALL logging in web.config, 

...

2020-09-02 00:20:58,445, DEBUG [ 32]: SCSM command invokation completed dust\jhedrick

2020-09-02 00:20:58,446, ERROR [ 32]: Commit new threw an exception

2020-09-02 00:20:58,458, ERROR [ 32]: Microsoft.EnterpriseManagement.Common.ObjectNotUniqueException: The call resulted in multiple return values, where one was expected. Use an appropriate method for further specializing the request.

  at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObjectBaseWithProperties.TryGetProperty(ManagementPackType type, String name, EnterpriseManagementSimpleObject& simpleObject)

  at Cireson.ServiceManager.Library.Extensions.SystemCenterExtensions.TrySetValue[T](EnterpriseManagementObject emo, String propertyName, T value)

  at Cireson.ServiceManager.DAL.ObjectProperties.<UpdateObjectPropertiesAsync>d__7.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

...

Ignoring the spelling of invocation, the stacktrace says that the process failed to get a unique property value when attempting to call TryGetProperty(). In my rather suspect lab envionrment, the SR class had multiple SR extensions, and two of them had the same internal name, "SR_ext01". SCSM allows this, but it's terrible practice, and most custom fields should be prefixed, such as "Dust_ext01". 

Deleting one of the MPs that contained one of the class extensions immediately fixed the issue. This also of course permanently deleted all data contained by that class extension. 

Tina_Sams

Here is the error from the logs....

2020-06-22 10:05:32,936, ERROR [ 91]: Commit new threw an exception2020-06-22 10:05:32,937, ERROR [ 91]: Microsoft.EnterpriseManagement.Common.ObjectNotUniqueException: The call resulted in multiple return values, where one was expected. Use an appropriate method for further specializing the request.

   at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObjectBaseWithProperties.TryGetProperty(ManagementPackType type, String name, EnterpriseManagementSimpleObject& simpleObject)

   at Cireson.ServiceManager.Library.Extensions.SystemCenterExtensions.TrySetValue[T](EnterpriseManagementObject emo, String propertyName, T value)

   at Cireson.ServiceManager.DAL.ObjectProperties.<UpdateObjectPropertiesAsync>d__7.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Cireson.ServiceManager.DAL.RelatedObjects.<UpdateObjectsAsync>d__21.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Cireson.ServiceManager.Services.Projection.<UpdateNewProjectionAsync>d__13.MoveNext()

2020-06-22 10:05:32,938, ERROR [ 91]: WorkItem Save call failed with error: The call resulted in multiple return values, where one was expected. Use an appropriate method for further specializing the request.

Peter_Miklian

@Tina_Sams I noticed something like this while ago in our lab environment, too. I don't remember how it went away, maybe upgrade to newer portal version. @Gabriel_Lences don't you have any information about this? Thanks.

Gabriel_Lences

Think this was happening to us as well on v 9.9.4 or so but went away after upgrading our env. Not sure what it caused though.

joivan_hedrick

I tracked this one down. Enabling ALL logging in web.config, 

...

2020-09-02 00:20:58,445, DEBUG [ 32]: SCSM command invokation completed dust\jhedrick

2020-09-02 00:20:58,446, ERROR [ 32]: Commit new threw an exception

2020-09-02 00:20:58,458, ERROR [ 32]: Microsoft.EnterpriseManagement.Common.ObjectNotUniqueException: The call resulted in multiple return values, where one was expected. Use an appropriate method for further specializing the request.

  at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObjectBaseWithProperties.TryGetProperty(ManagementPackType type, String name, EnterpriseManagementSimpleObject& simpleObject)

  at Cireson.ServiceManager.Library.Extensions.SystemCenterExtensions.TrySetValue[T](EnterpriseManagementObject emo, String propertyName, T value)

  at Cireson.ServiceManager.DAL.ObjectProperties.<UpdateObjectPropertiesAsync>d__7.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

...

Ignoring the spelling of invocation, the stacktrace says that the process failed to get a unique property value when attempting to call TryGetProperty(). In my rather suspect lab envionrment, the SR class had multiple SR extensions, and two of them had the same internal name, "SR_ext01". SCSM allows this, but it's terrible practice, and most custom fields should be prefixed, such as "Dust_ext01". 

Deleting one of the MPs that contained one of the class extensions immediately fixed the issue. This also of course permanently deleted all data contained by that class extension.