liferaysass.dll : A dynamic link library initialization routine failedliferaysass.dll : A dynamic link library initialization routine failedhttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1183992522024-03-29T13:39:28Z2024-03-29T13:39:28ZRE: liferaysass.dll : A dynamic link library initialization routine failedDominik Markshttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184425982020-02-06T07:54:30Z2020-02-06T07:54:30ZGood that it is working for you Luke. I was able to find the issue with Java 11 here: <a href="https://issues.liferay.com/browse/LPS-87211">https://issues.liferay.com/browse/LPS-87211</a><br /><br />The other parts, that it was working on Windows 32-bit and is now no longer working on Windows 64-bit, is a personal observation. I don't know if there is a specific jira issue for that.Dominik Marks2020-02-06T07:54:30ZRE: liferaysass.dll : A dynamic link library initialization routine failedLuke Palnauhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184365892020-02-05T16:45:13Z2020-02-05T16:45:13ZThanks Dominik, this is a great suggestion and <strong>works for me</strong>. I found a reported bug related to JDK 11, but had trouble finding any other reported bugs related bugs, if you know the link, please add for others that are unfortunate enough to run into this issue. Its possible the old build server was windows 32-bit and could build it without issue.Luke Palnau2020-02-05T16:45:13ZRE: liferaysass.dll : A dynamic link library initialization routine failedDominik Markshttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184333002020-02-05T12:05:36Z2020-02-05T12:05:36Z<html><head></head><body>As far as I know there is a bug in the native sass compiler when running under Windows (probably 64-bit only?).You can change the sass compiler to use ruby instead. That can be done by adding "<pre><code>sass.compiler.class.name=ruby</code></pre>" to the gradle.properties file.More information can be found here: <a href="https://portal.liferay.dev/docs/7-1/reference/-/knowledge_base/r/css-builder-gradle-plugin"></a><a href="https://portal.liferay.dev/docs/7-0/reference/-/knowledge_base/r/css-builder-gradle-plugin">https://portal.liferay.dev/docs/7-0/reference/-/knowledge_base/r/css-builder-gradle-plugin</a><br><a href="https://portal.liferay.dev/docs/7-0/reference/-/knowledge_base/r/css-builder-gradle-plugin"></a><a href="https://portal.liferay.dev/docs/7-1/reference/-/knowledge_base/r/css-builder-gradle-plugin"></a></body></html>Dominik Marks2020-02-05T12:05:36ZRE: liferaysass.dll : A dynamic link library initialization routine failedLuke Palnauhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184244032020-02-04T19:59:50Z2020-02-04T19:59:50ZAny advice?Luke Palnau2020-02-04T19:59:50Zliferaysass.dll : A dynamic link library initialization routine failedLuke Palnauhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1183992512020-01-31T22:00:35Z2020-01-31T22:00:35Z<html><head></head><body>I'm migrating to a new Windows Server 2016 build server and running into gradlew build errors when it tries to compile the first portlet module in the Liferay CE 7.0.4 GA5 workspace. On the gradle "task" buildCSS, I see:<br><pre><code>Using native Sass compiler</code></pre><pre><code># BridJ: LoadLibrary error when loading C:\Users\WES-DA~3\AppData\Local\Temp\BridJExtractedLibraries3401615323110354692\liferaysass.dll : A dynamic link library (DLL) initialization routine failed
</code></pre><pre><code></code></pre>I think I am just missing an installation, version incompatibility, or path issues on the new server. Here are some of the new build server installation details: <br>node v8.9.4, npm 5.6.0<br>Python 3.7.6, pip 20.0.1<br>openjdk version "1.8.0_212", OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03), OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode)<br>npm global packages (output from npm list -g --depth 0)+-- bower@1.8.8<br>+-- grunt@1.0.4<br>+-- grunt-cli@1.3.2<br>+-- gulp-cli@2.2.0<br>+-- karma-cli@2.0.0<br>+-- npm@5.6.0<br>+-- protractor@5.4.2<br>`-- <a href="mailto:windows-build-tools@5.2.2">windows-build-tools@5.2.2</a><br><a href="mailto:windows-build-tools@5.2.2"></a>I saw a similar error reported that was due to JDK 11, but since OpenJDK 1.8 is being used on the new build server. I have also confirmed the path C:\Users\WES-DA~3\AppData\Local\Temp\BridJExtractedLibraries3401615323110354692\liferaysass.dll does not exist before or after the build. During the build the folder appears with the dll present, and when I make a copy of the dll (during the build) I can see the liferaysass.dll has a file version 1.0.0.0 and product version 0.9.0.0. I've been comparing the new build serv