JTB Sheet Set Creator 2.4 released

JTB Sheet Set Creator 2.4 for AutoCAD is released with these new features and fixes.

• Upgraded Excel reader: the app no more requires Microsoft Excel installed.
• Fixed keywords in Excel to non case sensitive.
• Error messages are collected to 1 place
• Fixed bug when sets up "Template" and "Template Layout" for sheet and subset, in "Sheets" tab.
• Remove error messages when empty subset created.

Trial download is here.

The upgrade is free for existing customers of this app. If purchase was done via Autodesk App Store the download is available on My Downloads page. Sign in with the same account used when purchasing. Otherwise contact and let us know you want the update and we send the link to the full version.

JTB Sheet Set Creator is an app for AutoCAD that creates new Sheet Sets and Sheets based on an Excel template.

• Sheet Set Properties can be populated.
• Sheet Set Custom Properties can be defined, created and populated.
• Sheet Properties can be populated.
• Sheet Custom Properties can be defined, created and populated.
• Sheets (drawings) can be defined, created and have their properties populated.

If you make use of the Sheet Set Manager in AutoCAD you might find our other apps SSMPropEditor, DST Converter, JTB DST Tool or JTB Sheet Set Publish useful.

Bricsys and BricsCAD now in the big Hexagon family of companies

Swedish Hexagon AB has acquired Bricsys and with that its BricsCAD and other software. Intergraph, Leica Geosystems and MSC Software are some other companies that Hexagon earlier acquired. Bricsys will be fully consolidated as of today, operating within Hexagon’s PPM division. Let’s see how this will affect the growth of BricsCAD.

At JTB World we develop apps for BricsCAD among other CAD platforms and welcome customers with need for either our existing apps or any custom development to further automate their design work.

JTB BatchAttEdit 2.5.1 - Batch Attribute Editor for AutoCAD

JTB BatchAttEdit 2.5.1 has been released and got some bugs fixed and improvements.

This batch attribute editor app for AutoCAD collects attributes in all blocks of specified name patterns in multiple drawings and display in a wide spreadsheet. Then you can edit attribute texts as easy as working with Excel. Once done, click "Apply Attribute Changes" to update values to drawings.

This makes it a great app to for example edit title block attributes across many drawings instead of having to do it one drawing at a time.

If you want to export the attributes to Excel use the "Export - Import" button. Optionally you can make modifications in Excel for example with help of functions and formulas and then import back.

Try it for free by downloading from JTB BatchAttEdit.

Hold updating to Windows 10 version 1809

You might want to think twice about updating Windows 10 to the latest version 1809 released October, 2018.

I run into problems with Excel’s TEXT function not being able to convert year and month correctly.

I also got problems with some VBA code I use for Outlook, causing out of memory errors. The code got stuck on this row:
Set wdDoc = objOpenInspector.WordEditor

After going back to previous Windows 10 version 1803 things are working again. Office version (Office 2016 or Office 365) 16.0.10827.20138 and 16.0.10730.20127 both work fine on Windows 10 1803.

Have you upgraded and run into any issues?

UPDATE:

Microsoft has pulled Windows 10 version 1809 from the Software download page, Windows update and update assistant as of October 6.

Known issues updating to Windows 10, version 1809

“We have paused the rollout of the Windows 10 October 2018 Update (version 1809) for all users as we investigate isolated reports of users missing some files after updating.”

LMTOOLS VD is starting, please check vendor daemon's status in debug log

If you get this message in LMTOOLS there is probably an easy solution. This is something I run into with the Autodesk Network License Manager version 11.14.1.3.

“VD is starting, please check vendor daemon's status in debug log”

Trying to start the license service (the service name is shown in LMTOOLS > Config Services > Service Name) manually in Windows Services (run services.msc) can give this error:
”The Autodesk Licenses service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.”

The last row in the FlexNet debug log may be:

(lmgrd) SLOG: Summary LOG statistics is enabled.

Perform status enquiry could show something like this:

lmgrd is not running: Cannot connect to license server system.
  The license server manager (lmgrd) has not been started yet,
  the wrong port@host or license file is being used, or the
  port or hostname in the license file has been changed.
Server name:   SERVERNAMEHERE
License path:  @SERVERNAMEHERE;
FlexNet Licensing error:-15,570

Solution

Right click on the service and select Properties followed by the tab Log On and note that Local Service account may be used. Change that to the Local System account and then start the service.

Not sure why the wrong account is used when creating the service with LMTOOLS but it sounds like a bug.

If still not working there are some other solutions to try:

• Check if the lastest version of LMTOOLS has been installed
  Latest version (11.14.1.3) at the time of posting this

• End process adskflex.exe and lmgrd.exe on Windows Task Manager, if any and try to launch the server again.

• Verify folder permissions for the License Manager
  See: Update DACL failed when saving service within LMTOOLS

• Verify Firewall settings
  See Note in Configuring the Network License Manager

• Check the Server Status. If you see FlexNet Licensing error:-1,359.  System Error: 2 "No such file or directory":
  • Make sure the license file path in the Config services tab is correct.
  • Make sure to click the option "LMTOOLS ignore license file path environment variables", and then try to restart the service.
  • Make sure your antivirus software is not modifying the Windows services, e.g. "Sophos Endpoint Security" has been reported to cause the -1,359 error.

If you now got it working and also would like to create license usage reports head over to JTB FlexReport.