Running software: Microstation connect edition update 11_version 10.11.00.36
I keep receiving the message below every time I try to open a pset file and when I hit continue the files won't load
I would appreciate any help on this
Thanks
Hi Mohammed,
unfortunately your picture is resized to very low resolution, so nothing can be read. Can you please insert it in original 1:1 scale (use Insert > Insert image/video/file tool) ?
Also, please share complete text available in Details. It can be copied to clipboard and attached to your post as text (or zipped at first alternatively).
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
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----------------------------------------
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: