To reinforce the customer choice of ENOVIA SmarTeam and protect customer's investment we are aligning our solution with current industry standards by ending 32-bit support.

WHAT

• Since the V5-6R2026 GA release, ENOVIA SmarTeam 32-bit is officially no longer supported, ENOVIA SmarTeam is now only supported on 64-bit from V5-6R2026 GA onwards. As a reminder, ENOVIA SmarTeam 64-bit has been introduced since V5-6R2019, which is almost 7 years ago.
• The V5-6R2025 release is the last release to include the ENOVIA SmarTeam 32-bit code.
• V5-6R2025 follows the standard release lifecycle and it will be fully supported until October 7, 2027, with extended support until October 7, 2028.

WHY

Maintaining a 32-bit architecture is no longer possible today because of the changes in the IT ecosystem:

•  All CAD software supported by ENOVIA SmarTeam are now only supported in 64-bits. For example, CATIA V5 stopped 32-bit support more than 10 years ago (with V5-6R2015). This is also true for SolidWorks and others.
• Microsoft Windows Server and Windows Client are exclusively distributed and supported on 64-bit.
• Oracle is also the critical point. since the next version of Oracle (Oracle 26ai) is available only on 64-bit.

HOW

The end of 32-bit support requires special attention regarding the impact on customer's customizations, including scripts, executables, and DLLs.

Historically, many ENOVIA SmarTeam customizations were developed in VB6, a language that is now obsolete and stuck on 32-bit. 

A 64-bit process (in our case, the ENOVIA SmarTeam V5-6R2026) cannot load a 32-bit (VB6) DLL because the VB6 DLL is compiled using ENOVIA SmarTeam 32-bits APIs. Conversely, an old 32-bit program will not be able to communicate with the 64-bit ENOVIA SmarTeam APIs.

To secure your environment for the future, 2 approaches are possible:

• Recommended approach: Migrate VB6 code to .NET (C# / VB.net)
  • This means migrating the VB6 code to the modern .NET framework (in C# or VB.net) to compile the customization directly in 64-bit. 
  • This guarantees the best performance and native compatibility with ENOVIA SmarTeam 64-bit.
     

• Possible alternative approach : Reuse the 32-bit DLL with a "Wrapper"

  If you do not have the time or budget to rewrite all your VB6 code immediate.

  • Keep your existing 32-bit DLL.
  • Create a "Wrapper" component in .NET (C# / VB.net)  compiled in 64-bit.

Warning:

While this solution avoids rewriting code immediately, it makes the architecture more complex.
Also, the end of support of 32-bit Oracle in the near future will limit the lifespan of this technical workaround.

WHERE TO GO

• Plan 1 (Recommended Target): 
  • Use this technology change to study and plan your global migration to the 3DEXPERIENCE platform. 
  • Transition solutions exist, such as the 3DEXPERIENCE Transition Assistant.
• Plan 2 (Medium term): 
  • Migrate to ENOVIA SmarTeam V5-6R2026+ (64-bit) and plan a project to update your customization code and scripts to 64-bits.
• Plan 3 (Short term): 
  • Stay on ENOVIA SmarTeam V5-6R2025 (32-bit), but keep in mind that the end of support for this release will come quickly (2027, end of extended support 2028). No new certification and obsolescence management provided. All the hardware and software supported as defined in V5-6R2025 Program Directory will be maintained.
     

We invite all our partners and customers to list their current customizations to be prepared for these changes!