Error adding files to .pset

When I get a .pset file set up, I go to add the files by dragging them to into print organizer.  After it apparently loads all the files, I get the following error.  Any ideas?

 

"Exception encountered inside [WorkerMicroStationProxy.LoadDesignFile] "

Message details:

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."

 

 

Thanks for any help,

 

-Andy Wynn

Parents
  • I get this same error with the same message details but only when I attempt to add one specific file. With any other file I've attempted to add, it works great. In both scenarios I'm running all the same apps, even in the same exact session.

    When I try to add any other file:

    1. I click to Add Files to Set
    2. I specify input files (all of which refer to a common sheet border which has SHEET_PLOTTING_SHAPE surrounding the sheet.
    3. I set Print style name to PDF Prelim (Color Full Scale) -- I know this is workspace-based; this particular style fences around each shape on level SHEET_PLOTTING_SHAPE.
    4. Three entries from that file show up.

    When I try to add TSI-1.dgn:

    1. I click Add Files to Set
    2. I specify TSI-1.dgn (which also has this common sheet border reference)
    3. I set Print style name to PDF Prelim (Color Full Scale)
    4. This error shows up as described in the original post.

    On the other hand, if I try again but skipping step 3 and using the default style, TSI-1 does show up, but it doesn't match the border I want. Yes, I can set it to fence to fit master model and all reference models (and this does work), but the reference is a tad larger than the sheet, so the fence boundary overextends SHEET_PLOTTING_SHAPE. I've also tried to define from cell (because the SHEET_PLOTTING_SHAPE element is also included in a cell) and fit to element range using only SHEET_PLOTTING_SHAPE. None of these work.

    So what remains is that I have to specify fence points.

    Using Microstation SS3 8.11.09.608 and Geopak SS3 .722.

Reply
  • I get this same error with the same message details but only when I attempt to add one specific file. With any other file I've attempted to add, it works great. In both scenarios I'm running all the same apps, even in the same exact session.

    When I try to add any other file:

    1. I click to Add Files to Set
    2. I specify input files (all of which refer to a common sheet border which has SHEET_PLOTTING_SHAPE surrounding the sheet.
    3. I set Print style name to PDF Prelim (Color Full Scale) -- I know this is workspace-based; this particular style fences around each shape on level SHEET_PLOTTING_SHAPE.
    4. Three entries from that file show up.

    When I try to add TSI-1.dgn:

    1. I click Add Files to Set
    2. I specify TSI-1.dgn (which also has this common sheet border reference)
    3. I set Print style name to PDF Prelim (Color Full Scale)
    4. This error shows up as described in the original post.

    On the other hand, if I try again but skipping step 3 and using the default style, TSI-1 does show up, but it doesn't match the border I want. Yes, I can set it to fence to fit master model and all reference models (and this does work), but the reference is a tad larger than the sheet, so the fence boundary overextends SHEET_PLOTTING_SHAPE. I've also tried to define from cell (because the SHEET_PLOTTING_SHAPE element is also included in a cell) and fit to element range using only SHEET_PLOTTING_SHAPE. None of these work.

    So what remains is that I have to specify fence points.

    Using Microstation SS3 8.11.09.608 and Geopak SS3 .722.

Children
  • Derek,

    Can you upload the TSI-1.dgn dataset and dgnlib containing the PDF Prelim Print Style? Please include the .pltcfg and pen table. Send them in a private message if you prefer.



  • Thanks for your interest in this issue. I'm in the process of uploading it now, and it will be done within a couple minutes I think. Look for 319455 dataset.zip as a secure file upload.

    By the way, I've also included TSI-2 which does work well for me.

  • Derek,

    The zip file does not contain TSI-1.dgn. Please hover over my name and send a private message. We’ll work the problem off the forum and then post our findings.



  • FIXED. Sort of.

    I was mistaken; the Style 6 is what the print style was looking for (not level SHEET_PLOTTING_SHAPE) in all models and references. Since it behaves if I keep "Master model" and "Reference files" selected--as long as I limit the references to simply the one where the plot border is--I conclude that it was another reference that was corrupted. However, this leads me to believe that the sheet border reference wasn't corrupted. (I narrowed down the offending reference; I'm not sure what about that was offensive.)

    So the next question becomes: Why wasn't it able to find the shape in this (apparently) uncorrupted reference even if it can't handle the corruption in any other reference?

    The workaround for setting the fence range is that I needed to limit the search to a reference specified by logical name. This solution is only valid after the file has a print definition, which means you'll need to make sure of all the settings in the desired print style so you can match those settings after you add the sheet without a print style. Also, if you have multiple sheets in a file such as this, you'll need to find a way to establish several entries in that file.

    The more permanent workaround for this very unlikely condition is to use a modified print style that looks at a specific reference. I don't think there's an established go-to logical name for sheet border attachments, this is a rather isolated solution. Another option is to narrow down the offending attachments or perhaps even disable all attachments, set up the print definitions, and then turn each one on as your sheet requires.

  • Verifydgn repairing topo_signal.dgn does not resolve the problem. Searching all references for a style 6 plot shape causes the failure and it appears to be related to the topo reference file. Send your contact information, I'll open a Service request and then file a Trouble Report. The suggested workaround is to refine the plot shape search specifically to the "sheet" reference file. If the logical name is inconsistent, the .dgn file name can be used or multiple .dgn file names if multiple borders are used.

    If possible, try detaching and reattaching the topo reference file.