locked
Value cannot be null. SCSM SDK RRS feed

  • Question

  • Aplicativo: System Center Service Manager
    Versão do Aplicativo: 7.5.3079.607
    Severidade: Erro
    Mensagem: Value cannot be null.
    Parameter name: type

    System.ArgumentNullException: Value cannot be null.
    Parameter name: type
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task, List`1 parameterList)
       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task)
       at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobRecord.ExecuteBackgroundJob(Object sender, ConsoleJobEventArgs eventargs)
       at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

    The application works on the client console plus displays error on the server console

    Monday, July 3, 2017 6:02 PM

Answers

  • Then you need to debug your console task. Just attach the debugger to the console process and check where it breaks.
    • Proposed as answer by Yan Li_ Monday, July 31, 2017 5:45 AM
    • Marked as answer by Dayvson Lucas Monday, July 31, 2017 5:25 PM
    Friday, July 7, 2017 3:11 PM

All replies

  • Hello,

    Do you mean that only the console on your management server have this issue? When do you receive this error, when you open the console, or when you open some items in the console? 

    Please look into the operations manager event log to check is there any related error or warning there. 

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 4, 2017 2:21 AM
  • Yes. The error happens with a custom task created via visual studio sdk
    Thursday, July 6, 2017 3:19 PM
  • Then you need to debug your console task. Just attach the debugger to the console process and check where it breaks.
    • Proposed as answer by Yan Li_ Monday, July 31, 2017 5:45 AM
    • Marked as answer by Dayvson Lucas Monday, July 31, 2017 5:25 PM
    Friday, July 7, 2017 3:11 PM