Error when Right Clicking on Job Number Open With (context menu item)

When I try to right click on Job Number (from any area) I get the error message:
Key already exists
Parameter name: Key

Below is the full detail:
Application Error

Exception caught in: Infragistics4.Shared.v12.2

Error Detail

Message: Key already exists
Parameter name: Key
Program: Infragistics4.Shared.v12.2.dll
Method: ValidateKeyDoesNotExist

Client Stack Trace

at Infragistics.Shared.KeyedSubObjectsCollectionBase.ValidateKeyDoesNotExist(String key, IKeyedSubObject ignoreObject)
at Infragistics.Win.UltraWinToolbars.ToolsCollectionBase.ValidateKeyIsntUsed(String key)
at Infragistics.Win.UltraWinToolbars.ToolsCollectionBase.AddHelper(ToolBase tool, Boolean honorReadOnlyStatus, Int32 insertAtIndex)
at Infragistics.Win.UltraWinToolbars.ToolsCollectionBase.Add(ToolBase tool)
at Infragistics.Win.UltraWinToolbars.RootToolsCollection.Add(ToolBase tool)
at Ice.Lib.Framework.PopupMenuBuilderBase.AddToolToPopupMenu(PopupMenuTool contextMenu, ToolBase tool)
at Ice.Lib.Framework.PopupMenuBuilderBase.AddToolToPopupMenuWithOverflow(ToolBase tool, PopupMenuTool contextMenu, PopupMenuTool& contextMoreMenu)
at Ice.Lib.Framework.StandardControlPopupMenuBuilderBase.BuildContextMenu(PopupMenuTool contextMenu, Control registeredControl, Control sourceControl)
at Ice.Lib.Framework.PopupMenuBuilderBase.BuildContextMenu(Control sourceControl)
at Ice.Lib.Framework.PopupMenuBuilderBase.ContextMenu_Opening(Object sender, CancelEventArgs e)
at System.Windows.Forms.ToolStripDropDown.OnOpening(CancelEventArgs e)
at System.Windows.Forms.ToolStripDropDown.SetVisibleCore(Boolean visible)
at System.Windows.Forms.ContextMenuStrip.SetVisibleCore(Boolean visible)
at System.Windows.Forms.ToolStripDropDown.Show(Control control, Point position)
at System.Windows.Forms.ContextMenuStrip.ShowInternal(Control source, Point location, Boolean isKeyboardActivated)
at System.Windows.Forms.Control.WmContextMenu(Message& m, Control sourceControl)
at System.Windows.Forms.Control.WmContextMenu(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
at System.Windows.Forms.TextBox.WndProc(Message& m)
at Infragistics.Win.EmbeddableTextBoxWithUIPermissions.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Fortunately, this is only happening to me and not other users, but I would like to figure out why?
Thanks for any suggestions.
Carol

You likely have a corrupt personalization. The first thing I would try is to close Epicor and delete your C:\ProgramData\Epicor forlder (if you are running this on your server, then delete the C:\ProgramData\Epicor*-808 folder). If that does not fix it, then use Personalization Purge to delete your context menus.

I tried all of the above and I still receive the error. Any other suggestions?
Thanks for the help!
Carol

Last idea: if you log into another person’s machine, does it still happen?

1 Like

Does it happen the instant you right click?

After hovering over the “Open with …” (causing the sub menu to fly out)?

Or only after actually selecting a program on the sub menu?

Also - Are there any custom contexts?

Here’s our Context menu Maint for OrderHed.OrderNum

image

The last three are custom. And if one of those had issues for just your user, that might affect your use of the Right Click

Are you opening the programs as a shortcut or from the main menu?

Try opening the program in the main menu and see if the problem persists.
If it’s a shortcut, delete the shortcut(s) and re-add.

It happens when I right click in the text box … but only for a Job search. Even if there is a Job listed in there and I want to right click and “copy” I get the error. I have to do a Control C to copy, but it is only for Jobs.

I always open from the main menu.

Check the Context Menu entries for JobHead.JobNum.

Are there any added ones?

Here’s what is built-in on 10.2.300 (Make sure you check the Customization Mode box before loading that context Menu ID)

image

Okay I am a bit confused. I must have a personalized context menu. I read through the application help, but it isn’t very clear.
To get rid of this personalized context menu, where can I look?

You said you already went through Personalization Purge?

(System Mangmnt -> Purge/Cleanup Routines -> Personalization Purge)

Yes I did.
It seems if I open up the context menu maintenance module and select JobHead.JobNum context menu ID, and leave that open then I can right click and open with from Job Tracker, Job Entry, etc.
As soon as I close the module, I cannot right click in the text box for Job number again.

That is what I show also.

Cleared your clients cache, via the main menu?

Hi all,
Any solution yet? I have the same problem in 10.2.700.19

Thanks,
John

I too am wondering if anyone found a solution. I am experiencing this in my Pilot cloud database that was recently upgraded to Kinetic 2021.2.1. My Context Menu Maintenance shows only the default entries shown in Calvin Krusen’s post above. I sent a ticket into Epicor but thought I would try here also.

Thanks,

Jill Schoedel

Metalworks

Our pilot DB has apparently also had this problem for a while, And now We are running 2021.2.3 in production and having the same issue.

Hey there, I know this is quite an outdated topic but in case anyone comes through looking for the answer to this I got it directly from support.
You must open the Context Menu Maintenance window, search for JobHead.JobNum,
when it opens you may see it says Current Status: Customization.
What you need to do is delete every item in the Menu Items menu from the bottom up including JobHead.Jobnum and this will trigger a warning saying it will be reset to base.
You can then uncheck the customize checkbox in the main window, you will visibly see the Current Status go to Base, save the window and close and reopen your epicor.

3 Likes

@daniel.didonato THIS IS DEFINITELY THE SOLUTION! THANKS FOR POSTING!

It’s funny, I literally just posted “the solution” on a different topic about a different issue which had no actual answer. Literally like an hour ago. That’s the way this community should work boys and girls. You pay it forward and trust me it comes back.

P.S. Take THAT necroposting :slight_smile:

1 Like