This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided "as is" with no warranties.

Issue

When using the Broker Management tool, you receive an unhandled exception error when attempting to run the tool.

Unhandled exception has occurred in your application…..
Method not found: ‘System.String Sourcecode.smartobjects.servicebrokerstore.store.getservices()
If you click on the details of the error you will see the following:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

Symptoms

The full error can be seen below:

Unhandled exception has occurred in your application….. Method not found: ‘System.String Sourcecode.smartobjects.servicebrokerstore.store.getservices() If you click on the details of the error you will see the following: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.MissingMethodException: Method not found: 'System.String SourceCode.SmartObjects.ServiceBrokerStore.Store.GetServices()'. at BrokerManagement.BrokerConsole.PopulateServices() at BrokerManagement.BrokerConsole.PopulateConsole() at BrokerManagement.BrokerConsole.SBConsoleLoad(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

This issue was originally fixed in 5.2, however after upgrading to 5.3 the issue has reappeared.

Resolution

This issue has been resolved within Fixpack 4 for 5.3. The link for this can be viewed here: http://help.k2.com/kb003179