DriveWorks Pro 15: Info: Known Issues (KB13103005) [send feedback...]

Known Issues

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

Google Chrome Version 63 - (Date of issue 22 December 2017)

There is an issue in Chrome from build 63.0.3239.84 onwards whereby in some circumstances, the DriveWorks Live browser client will continually post to DriveWorks Live, causing the DriveWorks Live browser client to hang.

How to find the version of Google Chrome
  1. From Google Chrome, type chrome://settings/help in the address bar.
  2. The About Chrome page will load displaying the version number.

The issue occurs because Chrome is auto-filling and posting known passwords, even when auto-fill is disabled on each text box. If your users do not request Chrome to manage passwords, then you will not be affected by this.

If your site uses the DriveWorks Integration Module to log users in anonymously, you should not be affected by this issue.

We have worked with Google to fix this issue which they have done for Build 64 of Chrome.

While it is great that they have moved quickly to resolve this issue, Build 64 is not due to be rolled out until mid January 2018.

We have therefore created some workarounds. We have had to create more than one as it will depend on the impact you are seeing and how easy it is for you to communicate with your DriveWorks Live Client users

The options are as follows:

Option A

Use a different browser.

This is only really viable if you have a small number of users that you can communicate with directly and who are more likely to change their browser of choice.

Option B

Ask your users to use the beta version of Chrome Build 64.

This is quite extreme, but it might be an easy way to still use DriveWorks Live if it is mission critical

The beta can be downloaded from Google.

Option C

Ask your Chrome users to switch off the option in Google Chrome to manage passwords.

Again, this is quite an extreme measure, and not all users might be willing to change their habits.

To set Chrome to not manage passwords, in Chrome, click on Settings>Advanced>Manage passwords and switch it off.

Option D

Ask your Chrome users to switch off the option to remember password, for just your DriveWorks Live sites.

Other sites will not be affected, but you will need to ask them to not remember for all sites using your DriveWorks Live domain name.

When they log in to DriveWorks Live for the first time after deleting the site (and domain) from the remember password section, they will need to check the option to NOT have Chrome remember the password for this site.

Option E

We have created a hot fix for DriveWorks 15.2 that is available on request.

Please send your request to DriveWorks Support.

There are some caveats with using this hot-fix that you need to be aware of:

  • This hot-fix will only work with DriveWorks 15 Service Pack 2.
  • This hot-fix removes the Hide Characters capability of a text box. If you are using this Property then you will need to be aware of this and may need to alter you're implementation accordingly. Any hidden characters would now show as plain text.
  • If you uninstall and re-install DriveWorks 15.2, then you would need to re-apply this hot fix.

.NET Framework 4.7 (Now Resolved - see note below)

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 (Now Resolved - see note below)

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.

Web Frame Control

Please note the Web Frame control runs in IE11 mode on all supported operating systems with the exception of Windows Server 2012, which will still run in IE7 compatibility mode. This does not affect Windows Server 2012 R2 which uses IE11.

SOLIDWORKS 2016

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.

This does not occur when using Manual/Automatic Queued Generation.

If you are unsure about the different model generation methods please refer to the article Info: Model Generation Behavior for more information.

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.

Table of Contents