Unhandled exception message when opening a pset

I hope you can see this. and this is what shown in the details - I am guessing something to do with the PDF driver

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at PrintOrganizer.DocumentManager.DoFileSpecValidityCheck(IList`1 printSetItems)
at PrintOrganizer.DocumentManager.OpenDocument(FileSpec fileSpec, Boolean openAsReadOnly)
at PrintOrganizer.DocumentManager.OnFileOpen()
at PrintOrganizer.AppForm.ToolbarItemClicked(Object sender, ToolStripItemClickedEventArgs e)
at System.Windows.Forms.ToolStrip.OnItemClicked(ToolStripItemClickedEventArgs e)
at System.Windows.Forms.ToolStrip.HandleItemClick(ToolStripItem dismissingItem)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
MicroStation
Assembly Version: 0.0.0.0
Win32 Version: 10.11.00.36
CodeBase: file:///C:/Program%20Files/Bentley/MicroStation%20CONNECT%20Edition/MicroStation/microstation.exe
----------------------------------------

Hi Mohammed,

Mohammed Bahada said:

I hope you can see this.

Yes, it's better now ;-) ... even when the dialog itself is pretty useless, because it always displays only a fraction of exception details (and is not resizable).

Mohammed Bahada said:

and this is what shown in the details

I recommended to attach it as text file, not to insert it. When you prefer to paste such text to your post, please use Insert > Insert code tool to ensure it will be formatted properly, not as plain text.

What you posted is not complete I guess, the list of loaded assemblies is much longer typically. But the exception text is the most important part (even when the loaded assemblies list provides also valuable information in some situations).

Mohammed Bahada said:

I am guessing something to do with the PDF driver

Technically (at code level) it's clear why the exception was created. But it does not tell anything about in what file. It can be PDF driver, but also the problem can be directly in pset file. In my opinion this option is more probable.

I think there is not simple solution available, also some more information is still missing:

• MicroStation you use is quite old (1.5 year). Is it possible to test the same pset with the current Update 14 to ensure the problem is not caused by some internal bug?
• Where pset file comes from? Was it created in the same MicroStation version or in some older one?
• Where PDF driver (because you mentioned it, I assume it's used in your pset file) comes from? Is it the standard one delivered with MicroStation CE U11 installation or is it some older one or customized?
• Does it happen with any pset file or only with this specific one?

With regards,

  Jan

Hi Mohammed,

Mohammed Bahada said:

I hope you can see this.

Yes, it's better now ;-) ... even when the dialog itself is pretty useless, because it always displays only a fraction of exception details (and is not resizable).

Mohammed Bahada said:

and this is what shown in the details

I recommended to attach it as text file, not to insert it. When you prefer to paste such text to your post, please use Insert > Insert code tool to ensure it will be formatted properly, not as plain text.

What you posted is not complete I guess, the list of loaded assemblies is much longer typically. But the exception text is the most important part (even when the loaded assemblies list provides also valuable information in some situations).

Mohammed Bahada said:

I am guessing something to do with the PDF driver

Technically (at code level) it's clear why the exception was created. But it does not tell anything about in what file. It can be PDF driver, but also the problem can be directly in pset file. In my opinion this option is more probable.

I think there is not simple solution available, also some more information is still missing:

• MicroStation you use is quite old (1.5 year). Is it possible to test the same pset with the current Update 14 to ensure the problem is not caused by some internal bug?
• Where pset file comes from? Was it created in the same MicroStation version or in some older one?
• Where PDF driver (because you mentioned it, I assume it's used in your pset file) comes from? Is it the standard one delivered with MicroStation CE U11 installation or is it some older one or customized?
• Does it happen with any pset file or only with this specific one?

With regards,

  Jan