IV96616: Exporting graphic floor map to PDF hangs on Xref layer 0

We can’t export the graphic floor map to PDF from TRIRIGA. The system is “hanging” and not exporting. This is only happening with some drawings and only occurs when using Layer 0 from the Xref file ( xrefdwg | 0 ). If all other layers are off and a layer zero from any Xref is displayed on the graphics section, even if empty, the export will fail to complete.

The export graphic was throwing a malformed XML exception. The root cause was that there was a “1 = 1” element that got pulled in from the layout of an attached Xref onto layer 0 on that Xref. It turns out that, for any text element that contains any equals sign, the process of sending the SVG from the client to server using a Dojo API to post via a hidden input element, resulted in extra double quotes getting sent, and causing the SVG XML to be malformed.

We resolved this by pre-processing the SVG sent to the server to remove these extra double quotes, before sending it to the SVG converter. Moving forward, the export graphic will now successfully export a graphics section that includes text that contains any equals sign. Text that contains both double quotes and equals in it, will get the double quotes removed for technical reasons.

[Admin: To see other related posts, use the Xref tag or SVG tag.]

Continue reading

IV96408: Xref layers do not maintain their display state

When publishing a drawing with Xrefs, the display state of the Xref layers is not carried over to the graphics section. Meanwhile, the base drawing layers do maintain their state when published. A couple related things:

  • 1. If there are no existing or active layer configurations, the default behavior seems to be that the base layers will be displayed as they were in the drawing at the time of publishing. Meanwhile, the Xref layers will all be displayed regardless of their display state at the time of publishing. Is this the intended functionality?
  • 2. There does not seem to be a way to save the graphics section display of layers. When you open the graphics section, it is displayed based on the state of the last publishing. (I’ll be looking into this further and will likely open a separate L3 request. There should be a way to save the graphics section display.)

We resolved this issue by removing the code that removes the Xref layers. Now, the Xref layer states and colors, based on the main drawing, are retained when publishing a drawing. Moving forward, the Xref layer display states and colors are correctly retained when publishing to the graphics section.

[Admin: To see other related posts, use the Xref tag.]

Continue reading

Having an issue with drawings reprocessed during upgrade

When a client attempts to view the graphics for which a CAD drawing has been applied to a given record, the client sees an error in the lower-right side of the screen (Error 2, for example). Clicking on it shows the MID number that references an entry in the server.log file. An error appears on the screen and the following error appears in the log:

2016-03-19 02:02:36,710 WARN [com.tririga.platform.graphics.vector.drawing.XRefResolver](Default Executor-thread-4) Problem resolving XRef "DrawingFileName" for drawing: Drawing ID=5291 ContentID=319130 Path='DirectoryPath' Updated=2016-03-19 02:02:36.0 PV=174792. Error: com.tririga.platform.persistence.PersistenceException: Error executing sql: Sql[SQL=select * from DRAWING_DATA where DWG_ID=4142 and DWG_OBJ_TYPE=2,DB transaction ID=(None)][MID-1222218782]

Multiple issues may result in this problem during the upgrade process, so there is no single cause that can be identified, other than the problem occurs during the upgrade process. During the upgrade process, drawings are reprocessed. As mentioned, a large number of issues can be the source of this issue, but the common thread is that they failed during the reprocessing portion of the upgrade.

To see the problem, review the initial server.log file from the initial startup after an upgrade has been performed. If you see a warning regarding the reprocessing of a drawing, you are likely running into this issue. To resolve the problem, go to the Admin Console, navigate to Database Manager and choose the “Reprocess Published Drawings” action. This should resolve the majority, if not all, of the drawings that failed to reprocess properly during the upgrade process.

Continue reading

Why does a “ghost” floor plan show in TRIRIGA but not AutoCAD?

To the left of my TRIRIGA floor plan, there is a “ghost” mirror image of the window mullions (bars). They show up in the building layer only, and they are not on my AutoCAD 13 drawing. Any idea how to delete the window mullions (bars) or “ghost” floor plan and not have it happen again?

If these are showing up in TRIRIGA, then they are actually on the drawing somewhere, as the DXF spec outputs the data on the drawing, and we use the DXF data to publish the graphic in TRIRIGA. Possibly, what happened is that these items are on the drawing, but there was a transform problem where those entities were supposed to line up with your drawing but got flipped or moved incorrectly for some reason. Alternatively, they could actually exist in the drawing, but are hidden for some reason in AutoCAD, but getting exposed in TRIRIGA. I would also check your Xrefs for this data…

Continue reading

Getting a failure when publishing in CAD Integrator

When I perform a Smart Attach, I get the following error:

2015-11-02 18:04:32,201 ERROR [com.tririga.ci.service.PublishServiceImpl](pool-1-thread-4) Publish drawing response: FAIL - Error processing DXF - last line read: 1118. Error: com.tririga.platform.persistence.PersistenceException: Error executing sql: Sql[SQL=insert into DRAWING_LAYER (DWG_ID, HANDLE, NAME, ATTACHED, DISPLAYED, FROZEN, LOCKED, XREF, PLOT, ENTITY_COUNT, T_LEVEL, INST_DATA)values (1541,-101,'==LabelsLayer',false,false,false,false,false,true,0,-1,org.springframework.jdbc.core.support.SqlLobValue@dafbe9b4),DB transaction ID=(None)] Caused by: PreparedStatementCallback; uncategorized SQLException for SQL [insert into DRAWING_LAYER (DWG_ID, HANDLE, NAME, ATTACHED, DISPLAYED, FROZEN, LOCKED, XREF, PLOT, ENTITY_COUNT, T_LEVEL, INST_DATA)values (?,?,?,?,?,?,?,?,?,?,?,?)]; SQL state [72000]; error code [1653]; ORA-01653: unable to extend table TRIDATA.DRAWING_LAYER by 128 in tablespace TRIDATA_DATA; nested exception is java.sql.SQLException: ORA-01653: unable to extend table TRIDATA.DRAWING_LAYER by 128 in tablespace TRIDATA_DATA [MID-406679000]

What is the problem?

The key bit of information from the error message is in regard to the tablespace. Show this error message to your DBA. The application will normally attempt to increase the amount of allocated tablespace, but that assumes that the DBA allowed that in the configuration of the user account associated with the application. In your case, it appears that the DBA does not permit the application to automatically allocate more space when the application will run out of need tablespace. If that is the policy of the DBA team, then they should have warnings when tablespace is nearly full to prevent the issue from impacting the application. I suspect you will find additional errors in the server.log file for other actions.

Continue reading

Having an issue with duplication of Xref in web graphics

Using AutoCAD 2014, CI, Platform 3.3.2: I have a TRIRIGA CAD drawing with just the tri## layers. This references two files as overlays: Base build and Furniture. The Furniture drawing also references the base build as an overlay. In AutoCAD, an overlay means it only provides data from the file you Xref and NOT any files that the Xref references. When I publish the drawing, I get the base build drawing twice, once directly and one through the Furniture Xref. For example:

  • Base build | Walls
  • Furniture | Base build | Walls

Where the base build drawing is large, it is causing the Web Graphic to fail through a time out. When it does work, users are confused by having two layers with the same data.

Continue reading 

Missing AutoCAD layers from Web Graphics view

When using AutoCAD 2013 and CAD Integrator 12.1, many of our drawings with Xrefs work perfectly; all layers show up in the web graphics view on the attached floor plan record – however a few drawings behave differently. All of the floor, drawings and layer naming conventions are the same as other drawings, however on some of these floors only 15 of the 98 layers in the AutoCAD drawing show up in the web graphics view. Any ideas what may be going on?

Continue reading