DriveWorks Pro 23

Info: Known Issues (KB13103005)

Known Issues

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

Current

Activation Fails when Manually Activating a License

Problem Code: 7.51201

Cause:

This is a known issue when manually activating a DriveWorks 23 license.

Solution:

Closing the Activation Failed dialog, and re-opening the application or License Manager will have actually successfully activated the license.

Upload Control Activated from a Desktop Application

We are aware of an issue when clicking the Upload control from desktop applications.

This only applies when clicking the upload button from a running specification in:

• DriveWorks Administrator
• DriveWorks User
• DriveWorks Autopilot
• DriveWorks Live (the application)
• SOLIDWORKS Task Pane (through the DriveWorks Add-in)

When the upload control is clicked a message similar to the image below will be displayed.

Clicking OK will dismiss the message but files cannot be uploaded.

Resolution

The Upload Control functions as expected when running in a browser in the following situations:

• Personal Web Edition (PWE)
• DriveWorks Live Web Theme
• DriveWorks Live Web Theme hosted in IIS
• DriveWorks Live Integration Theme
• DriveWorks Live Integration Theme hosted in IIS

Group Table Updates Can Cause Rule Evaluations to Skip (resolved DriveWorks 23)

Updates to Group Tables can cause rule evaluations to be skipped in running specifications in exceptional circumstances.

Cause

This issue may surface when a running specification has a rule which references a Group Table which is being updated (i.e. DWGroupTable).

At the point of the running specification receiving the update, it is possible that any ongoing or scheduled rule evaluations will (for a short period) be skipped and/or yield out-of-date results.

This issue occurs in exceptional circumstances, when two processes (rule evaluation and group table update) conflict at a single point in time.

Resolution

• Upgrade to DriveWorks 23 (preferred)

  Or

• Evaluate which group tables can receive multiple updates whilst there are running specifications.

  Evaluate which Projects are affected due to rules that reference the group tables, and:

  • Do not perform Group Table updates when running specifications containing references to the Group Table, regardless of the Group Table update source.
  • Use an alternative data store (for example a SQL database) with appropriate refresh mechanisms.

Create Mate Generation Tasks Fail

An issue has been identified where Generation Tasks that create a mate will fail if the file name, used in the mating reference, contains a . (dot).

For example: "Top Plane@Bracket.LeftHand"

We recommend to avoid using . as part of the file name.

However applying the setting to show File name extensions in Windows Explorer, on each machine that generates models, will resolve this issue.

Please see Info: SOLIDWORKS System Options - Windows File Explorer for more information.

This applies to the following Generation Tasks:

• Create Angle Mate
• Create Coincident Mate
• Create Concentric Mate
• Create Coordinate System Mate
• Create Distance Mate
• Create Profile Center Mate

XR Orientation (Beta)

When viewing a 3D Scene in VR (via the XR Orientation entity) the scene will not render.

XR Orientation is a Beta (experimental) feature, we recommend disabling this feature until a fix is issued.

Integration Theme Caches Pictures Used On Controls

Pictures used on Form Controls (Picture Box, Macro Buttons, Option Button, etc.) are cached in the Integration Theme.

If an image is updated server-side, but has the same file name, the client will not receive the updated image.

Instead the (previous) cached version will be used by the client.

To force the updated image onto the client, you can either:

1. Implement your own cache busting technique by renaming the file on disk.

   Also, force the re-evaluation of the rule result (on each control) for the new image name and path.

   This is the recommended and most efficient method.

   This will enable caching to be used in other areas where it is needed.

   Or

2. If hosting through IIS, disable all caching.

   Preventing all caching will mean more client requests to the server.

   This may have a detrimental impact on performance.

   This method should be used as a last resort to cache-busting.

   1. On the machine hosting the Integration Theme through IIS, open Internet Information Services Manager.
   2. Select the site from the Sites folder in the Connections list.
   3. Double click HTTP Response Headers from the main window.
   4. Select Add from the Actions panel.
   5. In the name field enter:

      Cache-Control

   6. In the Value field enter:

      no-store, max-age=0

      

   7. Click OK.
   8. Restart the site.
   This technique does not work while the DriveWorksLiveClient downloadStyle property is set to "header".

   To implement this behavior see Integration Theme Client SDK Docs - downloadstyle.

Export Form Output Document Processed By DriveWorks Autopilot

When DriveWorks Autopilot processes an Export Form document, the image created is blank.

This was introduced on Windows 10 machines that received the following updates:

• Build 1903 - May 2019

To resolve this issue, either:

• Run DriveWorks Autopilot on a machine that is connected to a screen.

  Or

• Create a Release Documents task, that releases the Export Form document, on a state that is not processed by the DriveWorks Autopilot machine.

  For instance this can be placed on a running state, but only if the Form being exported does not use a 3D Preview.

  Or

• Roll back the Windows update to a build prior to the Build 1903 May 2019 update.

  Or

• Add the following AppContextSwitch:
  This method could introduce a memory leak and should only be used as a last resort.
  1. Open the following file in Notepad or similar tool:

     C:\Program Files\DriveWorks\<version number>\DriveWorksAutopilot.exe.config

  2. Add the following line immediately after the <runtime> element

     <AppContextSwitchOverrides value="Switch.System.Windows.Media.ShouldNotRenderInNonInteractiveWindowStation=false;Switch.System.Windows.Media.ShouldRenderEvenWhenNoDisplayDevicesAreAvailable=true" />
                             

  3. Save and close the DriveWorksAutopilot.exe.config file
  4. Restart DriveWorks Autopilot.

Error Creating Shared Group in Microsoft Azure

When creating a new Shared Group in Microsoft Azure, the New Group wizard may become unresponsive and eventually report an error.

To resolve this follow the steps below:

1. Click Create Group in the command bar (this will initially return an error message).
2. Close the window and DriveWorks Administrator.
3. Relaunch Administrator and now you will be able to log in to the Shared Group.

Installation

In some circumstances installation of DriveWorks could fail.

This is due to some DriveWorks Services (DriveWorks License Server, DriveWorks Live Floating License Server, DriveWorks Pro 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

SOLIDWORKS Crashes Closing Final Assembly (resolved SOLIDWORKS 2025 SP2)

An issue has been identified where generating a batch of models and drawings will be successful until the final top level assembly.

In these instances the final assembly generates correctly and will be saved but SOLIDWORKS crashes and the model will not be marked as generated in the Group.

Model Generation Report

The following entry will appear for the top level assembly in the model generation report:

The server threw an exception. (Exception from HRESULT: 0x8000105 (RPC_E_SERVERFAULT))

Windows Event Viewer

The following entries will appear in Windows Event Viewer:

Faulting application name: SLDWORKS.exe

Faulting module name: mfc140u.dll

Resolution

To resolve this issue:

Please update to one of the following versions of SOLIDWORKS which have been updated to address this issue:

• SOLIDWORKS 2024 SP5

  Install SOLIDWORKS 2024 SP5 before downloading and installing the following patch:

  DS Support Knowledge Base - QA Article number: QA00000413701

• SOLIDWORKS 2025 SP2

DriveWorks Add-in (for SOLIDWORKS) Crashes SOLIDWORKS (resolved DriveWorks 20 SP2)

DriveWorks is aware of an issue, where in some instances only, selecting certain sections of the Capture Assistant in the SOLIDWORKS Add-in will crash the Add-in and SOLIDWORKS.

This is related to the Microsoft .NET September 2022 Update and occurs irrespective of the fix that was built in to DriveWorks 20 SP2.

If this occurs apply the fix detailed here: Workaround 1: Suppress the new behavior caused by the update (Preferred).

WebGL context lost errors in Safari on iOS/iPadOS (resolved Safari 17.1)

Moving the Safari browser to the background (for example minimizing the browser) on iOS and iPadOS causes WebGL context lost errors.

This affects DriveWorks 3D scenes loaded into the 3D Preview Control when viewed in the Safari browser.

More information and Safari versions this affects can be found here: Apple Developer Forum

Apple are reporting this to be fixed in Safari 17.1.

Please see Safari 17.1 Release Notes for more information.

Screenshot on iOS 15 Devices (resolved iOS 16)

Taking a screenshot, on devices that use the Safari browser on iOS 15, will crash Safari when 3D is displayed.

This is a known issue, that's arisen from the latest iOS update and Apple are aware of this.

To resolve:

1. In the device settings, go to:

   Settings > Safari > Advanced > Experimental Features > GPU canvas rendering.

2. Turn off GPU canvas rendering.

Switching this setting off will prevent Safari from crashing, when taking a screenshot, on pages that display 3D content using WebGL.

Instance Mapping in SOLIDWORKS 2023 SP3 (resolved in DriveWorks 20.4 and 21.1)

There is a known issue with SOLIDWORKS 2023 SP3 when driving instances.

Captured instances that were inserted after any pattern feature was created do not get driven as expected.

We are actively investigating this issue, however, in the mean-time we have identified three work-arounds:

Option A

Re-order the model tree by dragging components inserted after any pattern features were created to the top (repeat until original component order is achieved)

Option B

Delete and recreate any pattern features so they are added after all other instances are added to the assembly, ensuring any pattern features are at the bottom of the component list.

Option C

Downgrade to a previous version of SOLIDWORKS e.g SW2023 SP2.

Microsoft .NET September 2022 Update Crash (KB22101401) (resolved in DriveWorks 20.2)

DriveWorks is aware of an issue, where opening certain stages in DriveWorks Administrator will crash immediately with UpdateExtent shown in the title of the crash dialog.

See Info: Microsoft.NET Update Crash for more information and workarounds.

Option Button Behavior in Form Test Mode

This only affects the control when in Form Test Mode.

Option Buttons will display an image when the mouse hovers over the control, even when no image is applied to the Picture (Hover) property.

Web Frame Control (Windows Server 2012 Not Supported)

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.

DriveWorks Pro Server Displays Previous Version Number After Upgrade

When a Group has been upgraded from version 18.1 to 18.2 the version number, displayed in DriveWorks Pro Server (Groups), will display 18.1.

This is by design as the version number displayed is the database schema version of the Group.

DriveWorks 18.1 was the last version that changed the database schema.

The schema has not changed for DriveWorks 18.2

Browser Zoom Level

When viewing User Forms in a browser, with the zoom level set to anything other than 100%, certain Form controls can be rendered incorrectly.

To resolve this reset the browser zoom level to 100%.

VR Camera (Beta) (resolved in DriveWorks 20.1)

When viewing a 3D Scene in VR (via the VR Camera entity) the geometry will appear distorted.

VR Camera is a Beta (experimental) feature, we recommend disabling this feature (for v20 SP0) until a fix is issued.