Home Search

DriveWorks Solo 19
Info: Known Issues (KB13103005)

Send Feedback

Known Issues

This document highlights any known issues with regards to compatibility when using DriveWorks products.

Current

Installation

In some circumstances installation of DriveWorks could fail.

This is due to some DriveWorks Services (DriveWorks License Server) being left over when previous versions have been uninstalled.

To resolve:

  1. Uninstall ALL DriveWorks versions.
  2. Check Windows Services.
  3. Note down the versions of any left over DriveWorks services.
    Right-Click on the DriveWorks Service and select Properties.
  4. Install and then uninstall each version in turn.

    Perform in order from newest to oldest.

    Check services each time to ensure expected services appear and then disappear.

Team Viewer

The Team Viewer feature - Mirror Driver is known to cause issues with 3rd party applications, including DriveWorks.

Trend Micro Anti-virus

If you receive a message stating that a new project cannot be created, and you have Trend Micro Anti-virus installed, please try disabling Trend Micro Anti-virus and creating your project. This issue is caused by Trend Micro Anti-virus locking the new project file before DriveWorks has a chance to open it.

Resolved

XML Documents Cannot Be Added Or Edited (Resolved in DriveWorks 19 SP0.1)

There is a known issue in DriveWorks Solo 19 SP0 whereby XML documents cannot be added or edited.

This includes XML Documents in Projects created in any version of DriveWorks Solo.

Until a fix is released, if you need to add or edit XML documents in DriveWorks Solo please reinstall DriveWorks Solo 18 SP2 and restore your data from that version.

This issue does not affect any document types in DriveWorks Pro, including simple and advanced XML documents.

Creating Or Running Projects From A UNC Location (Resolved in DriveWorks 19 SP0.1)

There is a known issue in DriveWorks Solo 19 SP0 whereby Projects cannot be created or run from a UNC path.

A UNC path is a path to a folder, on a network, that contains the server name.

For example:

\\server01\DriveWorksSolo\MySoloProject.driveprojx

Drawing Sheet Export (Resolved in DriveWorks 19 SP0.1)

There is a known issue in DriveWorks Solo 19 SP0 where Drawing sheets, named with a file extension, are not exported.

License Activation (Resolved in DriveWorks 17.2)

This issue has been resolved with the release of DriveWorks 17 Service Pack 2.

We recommend upgrading to this version to prevent this issue occurring.

When activating a DriveWorks 17 License you are asked to complete some Registration Information (see image below).

Entering any non-English characters in the Name and Company fields of this dialog will cause activation to fail.

If any non-English characters are entered the following Flex error code will be returned:

  • 5.50018.41145.32

Examples of non-English characters include (but not limited to):

  • ç
  • Þ
  • ù
  • ä
  • é

Please do not use non-English characters in the fields mentioned above.

.NET Framework 4.7 (Resolved)

This issue applies to the following supported operating systems:

  • Windows 7 Service Pack 1 (SP1)
  • Windows 8.1
  • Windows 10 Anniversary Update (Version 1607)
  • Windows 10 Creators Update

Removing items from the following areas of DriveWorks where items have been displayed in a list will cause a crash:

  • Group Tables
  • Calculation Tables
  • Documents
  • Model Rules
  • Generation Tasks
  • Specification Explorer

This issue affects all versions of DriveWorks prior to version 15.1.

This has been introduced by the changes made to the .NET Framework as part of the 4.7 update.

If possible avoid installing the .NET Framework 4.7 update to prevent this issue from occurring.

This issue has been resolved with the release of DriveWorks 15 Service Pack 1.

We recommend upgrading to this version to prevent the above issue from occurring.

If upgrading to this version is not possible please see the Microsoft article How to temporarily block installation of the .NET Framework 4.7

**UPDATE**

Microsoft .NET Framework 4.7.1 resolves all of the issues described above.

Please update all machines running DriveWorks Modules.

If automatic updates are turned off this version can be downloaded from this link:

Select .NET Framework 4.7.1.

Windows 10 Creators Update (Resolved)

The recent update to Windows 10 has introduced the following issue with System Colors:

Windows 10 Creators update has changed some default system colors.

This is most noticeable in the Form Design property grid.

This issue has been resolved with the release of DriveWorks 15 Service Pack 1.

We recommend upgrading to this version to prevent the above issue from occurring.

If upgrading to this version is not possible please see the Microsoft article How to temporarily block installation of the .NET Framework 4.7

**UPDATE**

Microsoft .NET Framework 4.7.1 resolves all of the issues described above.

Please update all machines running DriveWorks Modules.

If automatic updates are turned off this version can be downloaded from this link:

Select .NET Framework 4.7.1.

SOLIDWORKS 2016 (Resolved)

This notice applies to the following versions:

  • SOLIDWORKS 2016 SP0 to SOLIDWORKS 2016 SP3 inclusive.
This issue has been fixed in SOLIDWORKS 2016 SP4

When generating models using OnDemand (Real Time Preview) there is a known issue where:

Having more than one subassembly that share identical parts may result in a mismatch of part geometry across the sub-assemblies.

The issue can be avoided by giving each part generated a unique file name within your DriveWorks rules.

The preview issue may also resolve if you reload the assembly. With the OnDemand model active, from the SOLIDWORKS menu, click:

  1. File>Reload
  2. Click the Show References button and deselect any models that do not require to be reloaded.
  3. Click OK
  4. Click OK/Rebuild on any confirmation dialogs that appear
In certain circumstances the above steps may need repeating.