{"id":31776,"date":"2022-10-13T01:23:19","date_gmt":"2022-10-13T05:23:19","guid":{"rendered":"https:\/\/blogs.solidworks.com\/tech\/?p=31776"},"modified":"2023-01-11T23:59:30","modified_gmt":"2023-01-12T04:59:30","slug":"solidworks-support-monthly-news-october-2022","status":"publish","type":"post","link":"https:\/\/blogs.solidworks.com\/tech\/2022\/10\/solidworks-support-monthly-news-october-2022.html","title":{"rendered":"SOLIDWORKS\u00ae Support Monthly News &#8211; October 2022"},"content":{"rendered":"<p>Hello to all,<\/p>\n<p>Welcome to the new edition of the SOLIDWORKS\u00ae Support Monthly News! This monthly news blog is co-authored by members of the SOLIDWORKS\u00ae Technical Support teams worldwide. <strong>Here is the list of topics covered in this month&#8217;s Blog.<\/strong><\/p>\n<ol>\n<li>\n<h2><span style=\"color: #003366\">How can I apply decal on part face excluding its background color in SOLIDWORKS\u00ae Visualize?<\/span><\/h2>\n<\/li>\n<li>\n<h2><span style=\"color: #003366\">Workaround to obtain the reaction moment on a fixed face having SOLID mesh.<\/span><\/h2>\n<\/li>\n<li>\n<h2><span style=\"color: #003366\">Overriding quantity using UNIT_OF_MEASURE custom property in PDM.<\/span><\/h2>\n<\/li>\n<li>\n<h2><span style=\"color: #003366\">How to ensure a SOLIDWORKS PDM system can reach the correct TCP port of a SQL instance?<\/span><\/h2>\n<\/li>\n<\/ol>\n<h1><strong>How can I apply decal on part face excluding its background color in SOLIDWORKS\u00ae Visualize?<\/strong><\/h1>\n<h5><em>By Vinod KALE<\/em><\/h5>\n<p>Recently, there was a requirement where the user wanted to remove the background color of logo from the decal (refer the above image showing white color around text) in SOLIDWORKS<strong>\u00ae<\/strong> Visualize.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31778 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-107-615x570.png\" alt=\"\" width=\"615\" height=\"570\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-107-615x570.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-107-300x278.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-107-768x712.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-107-728x675.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-107.png 873w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>SOLIDWORKS\u00ae Visualize<\/strong> allows you to generate photo-quality images from the 3D CAD data. If you want to make any changes in the existing image that is not created from Visualize, you have to make use of Photo Editor applications (like Photoshop, Photopea, etc.) and then use that image in Visualize to get the desired output.<\/p>\n<p>There are few ways you can insert decal without its background:<\/p>\n<p><strong>A. Create a decal with mask in SOLIDWORKS\u00ae &gt; Insert decal on part face &gt; Export the part to Visualize using its add-in.<\/strong><\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31779 size-full\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-98.png\" alt=\"\" width=\"531\" height=\"281\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-98.png 531w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-98-300x159.png 300w\" sizes=\"auto, (max-width: 531px) 100vw, 531px\" \/><\/p>\n<p>Use following steps to create decal with mask:<\/p>\n<ol>\n<li>In the Task Pane in SOLIDWORKS<strong>\u00ae<\/strong>, select the Appearances, Scenes, and Decals tab<\/li>\n<li>Expand Decals and select the decals folder or a folder containing custom decals<\/li>\n<li>In the lower pane, identify the decal and drag it onto part face<\/li>\n<li>In the Decals PropertyManager, in the Image tab under \u2018Mask Image\u2019, Click Selective color mask<\/li>\n<li>Double-click the rectangular boxes to the right of Pick color<\/li>\n<li>In the Color dialog box, select the color, Click OK<\/li>\n<li>Items of the selected color are removed from the Decal Preview (but still some background color appear around alphabet)<\/li>\n<li>Open the decal image in MS Paint<\/li>\n<li>File &gt; Save the image to \u2018Monochrome Bitmap\u2019 format<\/li>\n<li>Edit the inserted decal in SOLIDWORKS<strong>\u00ae<\/strong> &gt; Select the \u2018Image mask file\u2019 under \u2018Mask Image\u2019 &gt; Browse the mask file (Monochrome Bitmap) &gt; Check \u2018Invert mask\u2019 option &gt; Observe the background color around logo is now removed correctly.<\/li>\n<\/ol>\n<p><strong>B. The other way is to use \u2018Online Photo Editor\u2019 to remove background color from the decal image.<\/strong><\/p>\n<ol>\n<li>a. Go to Photopea website and launch this online photo editor application<\/li>\n<li>Open the decal image.<\/li>\n<li>Create new layer and switch back to the Background layer.<\/li>\n<li>Click on the \u201cMagic Wand\u201d tool and select the logo related text from the image.<\/li>\n<li>Switch to \u2018Layer 1\u2019.<\/li>\n<li>Select the \u2018Paint Bucket Tool\u2019 and click on same alphabet. Observe some text gets added to new layer.<\/li>\n<li>Switch back to Background layer and repeat steps from \u2018c\u2019 to \u2018e\u2019 to add entire text.<\/li>\n<li>Once all alphabets are added to new layer, toggle the show\/hide icon in Background layer to confirm that text displays correctly without its background color.<\/li>\n<li>File -&gt; Export -&gt; Save as PNG. Then use this image when inserting decal on part face in SOLIDWORKS<strong>\u00ae<\/strong> Visualize as shown in this image.<\/li>\n<\/ol>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31780 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-95-615x499.png\" alt=\"\" width=\"615\" height=\"499\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-95-615x499.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-95-300x243.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-95-768x623.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-95-728x591.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-95.png 916w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<h1><strong>Workaround to obtain the reaction moment on a fixed face having SOLID mesh<\/strong><\/h1>\n<h5><em>By Suresh NIKALAJE<\/em><\/h5>\n<p>As we know, it is not possible to get the reaction moment on a fixed face of a solid mesh using the Reaction Force option. In SOLIDWORKS\u00ae Simulation, the nodes of solid elements have no degree of freedom in rotation (have only three translations degrees of freedom), therefore, the nodes on the face of a solid cannot have any nodal reaction moment. The Reaction Moment values are null if the selection is the face of a solid.<\/p>\n<p>On the other hand, for the nodes on SHELLS (including sheet metal) and for nodes on BEAMS have 6 degrees of freedom per node (3 translations, 3 rotations). Therefore, you can plot, probe and list the Reaction moment on nodes that belong to shell and beam elements.<\/p>\n<p><strong>Even with this limitation of SOLID mesh,<\/strong> do you know the result force PropertyManager allows you to get the reaction moment on a fixed face using the \u2018Free Body Force\u2019 option?<\/p>\n<p>If you want the reaction moment on a fixed face in you model, then follow this procedure:<\/p>\n<ol>\n<li>Create a \u2018Point\u2019 at the geometrical center of the face. [Go to Insert &gt; Reference Geometry &gt; Point &amp; selects the Center of Face construction method in the PropertyManager]<\/li>\n<li>If the direction of the reaction moment you want are not aligned with global coordinate system, then create new with the orientation you desired.<\/li>\n<li>In the Simulation Manager tree, right click on the <strong>Results<\/strong> folder and select <strong>List Results Force<\/strong><\/li>\n<li>Select <strong>\u2018Free body force\u2019<\/strong> as the option. Select the &#8216;Point&#8217; you created in the <strong>\u2018Vertex of Reference Point for Location of Moment\u2019<\/strong> field, select the newly created coordinate system in the <strong>\u2018Plane, Axis or Coordinate System\u2019<\/strong> fields and select the fixed face.<\/li>\n<li>The <strong>magnitude<\/strong> of moment components and resultant are listed in the Free body moment table.<\/li>\n<\/ol>\n<p><strong>For example,<\/strong> the expected reaction moment of a cantilever T beam of length L = 2000&#8243; subjected to a force of 100 lbs acting on its free end is <strong>2E+05 Ibf.in<\/strong> as see in following image.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31782 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh-615x330.jpg\" alt=\"\" width=\"615\" height=\"330\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh-615x330.jpg 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh-300x161.jpg 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh-768x412.jpg 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh-1536x824.jpg 1536w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh-728x391.jpg 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-BEAM-mesh.jpg 1920w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<h6>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<strong>\u00a0\u00a0<em> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Fig 1: Reaction Moment using BEAM mesh<\/em><\/strong><\/h6>\n<p>After creating new point at \u2018Point\u2019 at the geometrical center of the T face at fixed end, the Free body moment table shows expected reaction moment as 2 E+05 Ibf.in as shown below.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31783 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh-615x330.jpg\" alt=\"\" width=\"615\" height=\"330\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh-615x330.jpg 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh-300x161.jpg 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh-768x412.jpg 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh-1536x824.jpg 1536w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh-728x391.jpg 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Reaction-Moment-using-SOLID-mesh.jpg 1920w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<h6><em>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<strong> \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0 Fig 2: Reaction Moment using SOLID mesh<\/strong><\/em><\/h6>\n<p><strong>Note:<\/strong> To download the \u2018Bending of a T Section Beam\u2019 example model, browse to [drive letter:\\Users\\Public\\Public Documents\\SOLIDWORKS\\SOLIDWORKS version\\samples\\Simulation Examples\\Verification\\Static_8.SLDPRT].<\/p>\n<h1><strong>Overriding quantity using UNIT_OF_MEASURE custom property in PDM<\/strong><\/h1>\n<h5><em>By James FALCONER<\/em><\/h5>\n<p>In SOLIDWORKS<strong>\u00ae<\/strong>, you can use the BOM Quantity override to display quantities instead of instance counts. A SOLIDWORKS<strong>\u00ae<\/strong> PDM computed BOM takes advantage of this feature when you map the part data card to the UNIT_OF_MEASURE property. The custom property UNIT_OF_MEASURE has a surprisingly powerful feature that not everyone may know about.<\/p>\n<p>This feature is discussed in the SOLIDWORKS<strong>\u00ae<\/strong> PDM Admin Guide, but due to its brevity, could easily be missed:<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31788 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-108-615x151.png\" alt=\"\" width=\"615\" height=\"151\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-108-615x151.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-108-300x74.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-108-728x179.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-108.png 738w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>In SOLIDWORKS<strong>\u00ae<\/strong> PDM the quantity value is determined by the instance count of the file. But sometimes you may want to show an amount, such as length or quantity, instead of the instance count. The following steps will show us how PDM computed BOMs can provide a value by using a SOLIDWORKS<strong>\u00ae<\/strong> custom property. Let\u2019s start by showing how BOM Quantity override works in SOLIDWORKS<strong>\u00ae<\/strong>.<\/p>\n<p>For this example we\u2019ll use the basic speaker assembly that is included in most SOLIDWORKS<strong>\u00ae<\/strong> installations and found in the folder C:\\Users\\Public\\Documents\\SOLIDWORKS\\SOLIDWORKS 2022\\samples\\tutorial\\PDMWorks. Add and check these files into a PDM vault.<\/p>\n<p>Open and check out speaker.sldasm main assembly and add 2 more instances of the magnet file by going to Insert &gt; Component &gt; Existing Part and select magnet.sldprt. Also, add an assembly BOM table. See the quantity value of 3 for magnet. This means there are 3 instances of Magnet in this assembly.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31789 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-99-615x357.png\" alt=\"\" width=\"615\" height=\"357\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-99-615x357.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-99-300x174.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-99-768x446.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-99-728x423.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-99.png 1465w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>What if we wanted to override each instance with a different base quantity value? <\/strong>Close the assembly. Open and check out the magnet.sldprt file and create a Custom Property value named QT with a value of 100. Note BOM quantity override is by default set to \u2013 None -.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31790 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-96-615x432.png\" alt=\"\" width=\"615\" height=\"432\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-96-615x432.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-96-300x211.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-96-768x540.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-96-728x512.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-96.png 1101w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>Select BOM quantity: QT as marked below &amp; click OK. (Note BOM Quantity overrides the base quantity value). What this does is that the BOM quantity QT is overridden with the value of 100. These steps will be repeated for each file that needs to show a custom value for its quantity in a BOM. Save &amp; check the file in.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31791 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-85-615x341.png\" alt=\"\" width=\"615\" height=\"341\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-85-615x341.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-85-300x166.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-85-768x426.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-85-728x404.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-85.png 1139w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>Now, when we reopen the assembly we will see the overridden BOM quantity value of 300.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31792 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-77-615x357.png\" alt=\"\" width=\"615\" height=\"357\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-77-615x357.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-77-300x174.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-77-768x446.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-77-728x423.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-77.png 1465w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>When this data set is stored in a default SOLIDWORKS<strong>\u00ae<\/strong> PDM vault, the default SOLIDWORKS<strong>\u00ae<\/strong> part card will automatically use the overridden BOM quantity value and display the 300 value.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31793 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-53-615x302.png\" alt=\"\" width=\"615\" height=\"302\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-53-615x302.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-53-300x147.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-53-768x377.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-53-728x358.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-53.png 1396w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>So how can we make use of this feature in other files, vaults, and data cards?<\/strong> In the PDM Admin Tool open the Card Editor and select the default SOLIDWORKS Part Data card: The CustomProperty UNIT_OF_MEASURE attribute will need to be used to override quantity value as described previously.<\/p>\n<ol>\n<li>Create a variable, named for example \u201cBOM Quantity.<\/li>\n<li>Add a variable mapping with block \u201cCustomProperty\u201d, the attribute \u201cUNIT_OF_MEASURE and the extension \u201cSLDPRT\u201d. Please note that this will be a read-only variable mapping and you cannot override this value via the data card.<\/li>\n<li>Add the variable to the SOLIDWORKS<strong>\u00ae<\/strong> part data card (.sldprt)<\/li>\n<\/ol>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31794 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-44-615x525.png\" alt=\"\" width=\"615\" height=\"525\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-44-615x525.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-44-300x256.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-44-768x655.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-44-728x621.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-44.png 1432w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>If we did not use the UNIT_OF_MEASURE override for the BOM Quantity variable, then we would have seen the regular instance count of magnet.sldprt as seen below (3).<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31795 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-32-615x256.png\" alt=\"\" width=\"615\" height=\"256\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-32-615x256.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-32-300x125.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-32-768x319.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-32-728x303.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-32.png 1409w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<h1><strong>How to ensure a SOLIDWORKS\u00ae PDM system can reach the correct TCP port of a SQL instance<\/strong><\/h1>\n<h5><em>By Tor IVEROTH<\/em><\/h5>\n<p>In order to communicate with the SQL server and access the file vault database, a SOLIDWORKS<strong>\u00ae<\/strong> PDM system establishes an ODBC connection over the TCP protocol to the SQL server instance name that is stored in the registry.<\/p>\n<p>The SQL server instance listens on a specific TCP port. If the client system (or a server) cannot find the correct port to communicate over, log in to the vault will fail with various ODBC related communication errors.<\/p>\n<p><strong>Some examples of errors<\/strong> that you would encounter if the system cannot reach the SQL server port are:<\/p>\n<p><strong><span style=\"text-decoration: underline\">With SOLIDWORKS\u00ae PDM 2020 and later<\/span>:<\/strong> The database access error would reference \u201cODBC Driver 17 for SQL Server\u201d<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31798 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-109-615x378.png\" alt=\"\" width=\"615\" height=\"378\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-109-615x378.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-109-300x184.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-109-768x472.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-109-728x447.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/1-109.png 1016w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31799 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-100-615x347.png\" alt=\"\" width=\"615\" height=\"347\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-100-615x347.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-100-300x169.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-100-768x433.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-100-728x411.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/2-100.png 1175w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong><span style=\"text-decoration: underline\">With SOLIDWORKS\u00ae PDM 2019 and earlier : <\/span><\/strong>The database access error would reference \u201cODBC SQL Server Driver\u201d.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31800 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-97-615x331.png\" alt=\"\" width=\"615\" height=\"331\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-97-615x331.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-97-300x162.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-97-768x414.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-97-728x392.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/3-97.png 986w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31801 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-86-615x345.png\" alt=\"\" width=\"615\" height=\"345\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-86-615x345.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-86-300x168.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-86-768x430.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-86-728x408.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/4-86.png 967w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>Use the following troubleshooting guidelines to address this problem<\/strong>:<\/p>\n<p><strong>A \u2013 Start the SQL Server Browser service: <\/strong>The SQL Server Browser Service will broadcast the current SQL ports for each SQL instance on the Server. Make sure the service is started on the SQL server.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31802 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-78-615x387.png\" alt=\"\" width=\"615\" height=\"387\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-78-615x387.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-78-300x189.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-78-768x483.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-78-728x458.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/5-78.png 1077w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>B \u2013 Confirm the SQL Server Instance name: <\/strong>The SQL server name will be in the form of a default instance name <strong>(SERVERNAME)<\/strong> or a named instance <strong>(SERVERNAME\\INSTANCE)<\/strong>.<\/p>\n<p>When you create a vault view, or attach to an archive server, the SQL instance name will be stored in the registry. Make note of which SQL server name that the vault is using.<\/p>\n<p><span style=\"text-decoration: underline\">The connection details for the local file vault view of the vault:<\/span><\/p>\n<p>\u201cDbServer\u201d value under key: HKEY_LOCAL_MACHINE\\SOFTWARE\\SolidWorks\\Applications\\PDMWorks Enterprise\\Databases\\[VAULTNAME]<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31803 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-54-615x198.png\" alt=\"\" width=\"615\" height=\"198\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-54-615x198.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-54-300x96.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-54-768x247.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-54-728x234.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/6-54.png 914w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><span style=\"text-decoration: underline\">The connection details for the vault on the archive server:<\/span><\/p>\n<p>\u201cDbServer\u201d value under key: HKEY_LOCAL_MACHINE\\SOFTWARE\\SolidWorks\\Applications\\PDMWorks Enterprise\\ArchiveServer\\Vaults\\[VAULTNAME]<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31804 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-45-615x192.png\" alt=\"\" width=\"615\" height=\"192\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-45-615x192.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-45-300x94.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-45-768x239.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-45-728x227.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/7-45.png 1097w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><span style=\"text-decoration: underline\">The connection details for the Database Server Service:<\/span><\/p>\n<p>\u201cServer\u201d value under key: HKEY_LOCAL_MACHINE\\SOFTWARE\\SolidWorks\\Applications\\PDMWorks Enterprise\\MailService<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31805 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-33-615x187.png\" alt=\"\" width=\"615\" height=\"187\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-33-615x187.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-33-300x91.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-33-768x233.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-33-728x221.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/8-33.png 1185w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>C \u2013 Verify the SQL instance TCP port: <\/strong>You can see what port the SQL server instance is currently listening on via the SQL log file (for more details, refer to Knowledge Base Solution S-051979).<\/p>\n<p>In this example, the SQL Server named instance <strong>VM-TIV-PDM\\SQLEXPRESS2019<\/strong> is listening on port<strong> 55206<\/strong><\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31806 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/9-22-615x217.png\" alt=\"\" width=\"615\" height=\"217\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/9-22-615x217.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/9-22-300x106.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/9-22-768x270.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/9-22-728x256.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/9-22.png 1153w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>Alternatively, you can find the current port via the SQL configuration manager, SQL Server Network Configuration, Protocols for SQLSERVERNAME, TCP, IP Addresses.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31807 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/10-20-615x514.png\" alt=\"\" width=\"615\" height=\"514\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/10-20-615x514.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/10-20-300x251.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/10-20-768x641.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/10-20-728x608.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/10-20.png 874w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>D \u2013 Make sure the system can reach the TCP port: <\/strong>Now that you know the correct SQL name and SQL port, the client system (or remote server) must be able to communicate over the specific TCP port that the SQL instance listens on. The easiest method to ensure the system can reach the SQL port is to use the SOLIDWORKS<strong>\u00ae<\/strong> PDM Connectivity Test Tool. You can find this tool in Knowledge Base Solution S-069274.<\/p>\n<p>Run the tool and select the \u201cSQL Server\u201d option. Fill in the hostname of the SQL Server (note that if the SQL Server is a named instance (I.e. VM-TIV-PDM\\SQLEXPRESS2019), you should only fill in the server hostname (i.e. VM-TIV-PDM) in this field. Fill in the port to test (from step C).<\/p>\n<p>If the port is accessible, the tool should show a success result.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31808 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/11-23-615x289.png\" alt=\"\" width=\"615\" height=\"289\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/11-23-615x289.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/11-23-300x141.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/11-23-768x361.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/11-23-728x342.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/11-23.png 1069w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>If the port is inaccessible, the test will fail. You should double check that you are connecting to the correct port (step C) and that the port is not blocked in the network (by firewall rule or similar). For example, this image shows that this system cannot connect to TCP port 42045.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31809 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/12-20-615x297.png\" alt=\"\" width=\"615\" height=\"297\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/12-20-615x297.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/12-20-300x145.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/12-20-768x371.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/12-20-728x352.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/12-20.png 1013w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>E \u2013 Create an ODBC connection alias: <\/strong>If the SQL TCP port is accessible, but the ODBC connection still fails, you should create an ODBC Alias in order for the system to use the correct port. An ODBC Alias maps the SQL instance name to a specified port number.<\/p>\n<p>In this example, the SQL server host (VM-TIV-PDM) and the SQL instance port (55206) can be connected to, but the SQL instance name (VM-TIV-PDM\\SQLEXPRESS2019) cannot be resolved to the proper port. The connectivity test tool will have a similar error that the PDM client log shows.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31810 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/13-11-615x444.png\" alt=\"\" width=\"615\" height=\"444\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/13-11-615x444.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/13-11-300x217.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/13-11-768x555.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/13-11-728x526.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/13-11.png 1250w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>To create the ODBC Alias:<\/strong><\/p>\n<ol>\n<li>Read over the document in Knowledge Base Solution S-042701.<\/li>\n<li>Focus on the chapter \u201cCreating an ODBC alias when using the using ODBC 17 (msodbcsql17.dll) driver\u201d<br \/>\n<hr \/>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-31811\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/14-5-300x295.png\" alt=\"\" width=\"300\" height=\"295\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/14-5-300x295.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/14-5-615x606.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/14-5.png 718w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/p>\n<hr \/>\n<\/li>\n<li>Create the ODBC alias on the system that cannot establish an ODBC connection with the SQL server instance. Update with the SQL instance name (see step B) and the correct port (step C). For example, the ODBC Alias for an SQL instance named \u201cVM-TIV-PDM\\SQLEXPRESS2019\u201d to port \u201c55206\u201d should look like this under both the 64-bit and 32-bit registry (name should be: VM-TIV-PDM\\SQLEXPRESS2019 and the data value should have: DBMSSOCN, VM-TIV-<\/li>\n<\/ol>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31812 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/15-4-615x232.png\" alt=\"\" width=\"615\" height=\"232\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/15-4-615x232.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/15-4-300x113.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/15-4-768x290.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/15-4-728x275.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/15-4.png 1142w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>With the ODBC alias correctly defined, the connectivity test tool should now successfully connect to the SQL instance name, the port and successfully establish an ODBC connection.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31813 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/16-5-615x438.png\" alt=\"\" width=\"615\" height=\"438\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/16-5-615x438.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/16-5-300x214.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/16-5-768x547.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/16-5-728x518.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/16-5.png 1169w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p>The vault should now be accessible via the administration tool or local vault view.<\/p>\n<p style=\"padding-left: 40px\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31814 size-large\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/17-5-615x327.png\" alt=\"\" width=\"615\" height=\"327\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/17-5-615x327.png 615w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/17-5-300x160.png 300w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/17-5-768x409.png 768w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/17-5-728x387.png 728w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/17-5.png 1216w\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" \/><\/p>\n<p><strong>If you are still unable to connect<\/strong>: Go over the chapter \u201cAfter Installing SQL Server Express\u201d in the install guide and make sure remote connections are allowed and that the TCP protocol is enabled.<\/p>\n<h1><strong>Noteworthy Solutions from the SOLIDWORKS\u00ae Knowledge Base<\/strong><\/h1>\n<p style=\"margin: 0in;font-family: Calibri;font-size: 11.0pt\"><strong>\u00a0<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-31825\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/PDM.png\" alt=\"\" width=\"16\" height=\"16\" \/> When I use the SOLIDWORKS\u00ae PDM quick search or integrated search functionality, why do the SOLIDWORKS file open or save dialog boxes stop responding (hangs or crashes)?<\/strong>This problem can happen on a SOLIDWORKS\u00ae PDM client workstation if the file type associations for SOLIDWORKS files are incorrect. To get more information, see solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/siebel\/app\/customerportal\/enu?SWECmd=GotoView&amp;SWEView=SW+OUI+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+OUI+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-B68EXFP\">S-079778<\/a><\/p>\n<p style=\"margin: 0in;font-family: Calibri;font-size: 11.0pt\"><strong><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31826\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/simulation-9.png\" alt=\"\" width=\"24\" height=\"20\" \/>What can I do if every SOLIDWORKS\u00ae Flow Simulation project I run shows a \u2018Preparing model\u2019 Solver Monitor status indefinitely and any FloXpress analysis never finishes the \u2018Meshing in progress\u2019 step? <\/strong>To get more information, see solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/siebel\/app\/customerportal\/enu?SWECmd=GotoView&amp;SWEView=SW+OUI+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+OUI+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-B65ZG30\">S-079776<\/a><\/p>\n<p style=\"margin: 0in;font-family: Calibri;font-size: 11.0pt\"><strong>\u00a0<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31827\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Toolbox-1.png\" alt=\"\" width=\"23\" height=\"23\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Toolbox-1.png 202w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Toolbox-1-120x120.png 120w\" sizes=\"auto, (max-width: 23px) 100vw, 23px\" \/> Is there a SolidPractices document available on the topic of \u201cSOLIDWORKS Toolbox\u201d?<\/strong> The objective of this SolidPractices document is to share information that relates to setting up the SOLIDWORKS\u00ae Toolbox (\u201cthe Toolbox\u201d). To get more information, see solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/siebel\/app\/customerportal\/enu?SWECmd=GotoView&amp;SWEView=SW+OUI+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+OUI+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-APQ7H7E\">S-078795<\/a><\/p>\n<p style=\"margin: 0in;font-family: Calibri;font-size: 11.0pt\"><strong>\u00a0<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-31828\" src=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Inspection-1.png\" alt=\"\" width=\"17\" height=\"17\" srcset=\"https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Inspection-1.png 222w, https:\/\/blog-assets.solidworks.com\/uploads\/sites\/4\/Inspection-1-120x120.png 120w\" sizes=\"auto, (max-width: 17px) 100vw, 17px\" \/>When I click \u2018New Inspection Project\u2019 in the SOLIDWORKS\u00ae Inspection addin toolbar, why is there no template listed from Project Template Selection PropertyManager?<\/strong> To get more information, see solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/siebel\/app\/customerportal\/enu?SWECmd=GotoView&amp;SWEView=SW+OUI+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+OUI+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-B4XN8T6\">S-079716<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hello to all, Welcome to the new edition of the SOLIDWORKS\u00ae Support Monthly News! This monthly news blog is co-authored by members of the SOLIDWORKS\u00ae Technical Support teams worldwide. Here is the list of topics covered in this month&#8217;s Blog.<\/p>\n... <a href=\"https:\/\/blogs.solidworks.com\/tech\/2022\/10\/solidworks-support-monthly-news-october-2022.html\">Continued<\/a>","protected":false},"author":625,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[21,30,497,1577],"tags":[874,893,1082],"class_list":["post-31776","post","type-post","status-publish","format-standard","hentry","category-solidworks","category-solidworks-simulation","category-solidworks-support-monthly-news","category-solidworks-visualize","tag-pdm","tag-solidworks-simulation","tag-solidworks-visualize"],"acf":[],"_links":{"self":[{"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/posts\/31776","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/users\/625"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/comments?post=31776"}],"version-history":[{"count":24,"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/posts\/31776\/revisions"}],"predecessor-version":[{"id":32338,"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/posts\/31776\/revisions\/32338"}],"wp:attachment":[{"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/media?parent=31776"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/categories?post=31776"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.solidworks.com\/tech\/wp-json\/wp\/v2\/tags?post=31776"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}