Hello everyone,

Welcome to the new Integration Nation!

3 comments

· Sorted by Oldest

m.delgaizo
·
·
I'm trying to set up a file poller on a Windows share directory from a Linux groundlex, but although the connection with credentials works directly from the Linux machine, from Snap it gives me an error "Error occurred while creating a mount " : { "stacktrace": "com.snaplogic.snap.api.SnapDataException: Error occurred while creating a mount smb://my_server/my_dir/ (ERR_MOUNTERROR)\n at com.snaplogic.snap.api.fs.smb.SmbUtils.createMount(SmbUtils.java:128)\n at com.snaplogic.snap.api.fs.smb.SmbUrlConnection.connect(SmbUrlConnection.java:81)\n at com.snaplogic.snap.api.fs.smb.SmbFileSystemProvider.newFileSystem(SmbFileSystemProvider.java:47)\n at com.snaplogic.snap.api.fs.JfsUtils.getFileSystem(JfsUtils.java:277)\n at com.snaplogic.snaps.binary.FileFinder.lambda$getFileSystemFor$2(FileFinder.java:271)\n at net.jodah.failsafe.Functions$11.call(Functions.java:263)\n at net.jodah.failsafe.SyncFailsafe.call(SyncFailsafe.java:145)\n at net.jodah.failsafe.SyncFailsafe.get(SyncFailsafe.java:69)\n at com.snaplogic.snaps.binary.BinaryUtils.failsafeExecute(BinaryUtils.java:539)\n at com.snaplogic.snaps.binary.FileFinder.getFileSystemFor(FileFinder.java:275)\n at com.snaplogic.snaps.binary.FilePoller.poll(FilePoller.java:307)\n at com.snaplogic.snaps.binary.FilePoller.pollingLoop(FilePoller.java:269)\n at com.snaplogic.snaps.binary.FilePoller.process(FilePoller.java:262)\n at com.snaplogic.snap.api.ExecutionUtil.process(ExecutionUtil.java:106)\n at com.snaplogic.snap.api.ExecutionUtil.execute(ExecutionUtil.java:70)\n at com.snaplogic.snap.api.SimpleSnap.execute(SimpleSnap.java:70)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeSnap(SnapRunnableImpl.java:818)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeForSuggest(SnapRunnableImpl.java:657)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.doRun(SnapRunnableImpl.java:874)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:444)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:118)\n at java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)\n at java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n at java.base/java.lang.Thread.run(Unknown Source)\nCaused by: Error Message=Unable to connect to the server;Error Code=[ERR_MOUNTERROR,-101] ;cause=[null]\n at com.visuality.nq.client.Server.connectionAttempt(Server.java:692)\n at com.visuality.nq.client.Server.connect(Server.java:1717)\n at com.visuality.nq.client.Mount.ensureServerConnection(Mount.java:647)\n at com.visuality.nq.client.Mount.doMount(Mount.java:926)\n at com.visuality.nq.client.Mount.doMount(Mount.java:623)\n at com.visuality.nq.client.Mount.<init>(Mount.java:489)\n at com.snaplogic.snap.api.fs.smb.SmbUtils.createMount(SmbUtils.java:123)\n ... 26 more\n" "reason": "Error occurred while creating a mount smb://my_server/my_dir/ (ERR_MOUNTERROR)" "resolution": "Please check all properties and credentials" "status_code": "error" "snap_details": { "label": "File Poller CRIF" "instance_id": "e7815740-f439-4f43-9c8d-c5e829ec8430" "class_id": "com-snaplogic-snaps-binary-filepoller" "build_tag": "main34730" "views": { "in": {} "out": { "output0": { "count": 0 } } "error": { "error0": { "count": 0 } }
m.delgaizo
·
·
Does anyone know if there are any special settings to make on either Snap Poller or the running Snap agent, or something else? Thank you
Scott O.
·
·
Checking through SnapLogic docs, this is a known challenge when connecting a Linux-based Groundplex to a Windows SMB share. The error ERR_MOUNTERROR typically points to one of several root causes. Here's a structured checklist to work through: ✅ 1. Verify Your SMB Account Configuration This is the most common cause (as confirmed by community reports). In SnapLogic Manager, check your SMB Account and make sure all three fields are correct: FieldNotesDomainMust be the Active Directory / NetBIOS domain name of the Windows host. This field is often left blank and causes mount failures on Linux.UsernameThe Windows account username (without domain prefix)PasswordThe correct password for that account
💡 Even if smbclient works from the Linux command line, SnapLogic uses its own Java-based SMB library (JCIFS), which handles authentication differently — hence why it can work from CLI but fail in Snap.
✅ 2. Check the SMB URL Format Make sure the Directory field in your File Poller uses the correct format:
smb://<server_name_or_IP>/<share_name>/<optional_subfolder>/
<share_name>is theSMB share name(e.g.,SharedDocs),nota full filesystem path.
The URL must end with a trailing/.
Avoid using\\server\share(Windows UNC) style — it won't work in SnapLogic.
Example:
smb://my_server/my_share/my_dir/
✅ 3. SMB Protocol Version Mismatch (Very Common on Modern Windows) Modern Windows servers (2012+) often disable SMBv1 by default. SnapLogic's JCIFS library may attempt SMBv1 negotiation by default, which would result in a mount error. You can force a higher SMB version via JVM options in your Groundplex Node Properties (in SnapLogic Manager → Snaplex → Update → Node Properties → Global Properties): KeyValuejcc.jvm_options-Djcifs.smb.client.minVersion=SMB202 -Djcifs.smb.client.maxVersion=SMB300
⚠️ If you already have a jcc.jvm_options value, append these flags rather than replacing the existing value. Restart the Groundplex node after applying.
✅ 4. Network & Port Connectivity Even though smbclient works from the Linux machine, verify that:
Port 445(TCP) is open from the Groundplex host to the Windows server (SnapLogic's JCIFS uses port 445 by default, not 139).
There areno host-based firewall rules(Windows Defender Firewall) blocking the Groundplex's IP specifically.
The Groundplex canresolve the Windows server hostname(DNS). If not, try using the IP address directly in the URL.
✅ 5. Linux System Packages (Less Common) While SnapLogic uses Java/JCIFS internally (not OS-level mounting), ensure the Linux Groundplex host isn't missing dependencies that could affect Java's native library resolution:
# Check if cifs-utils / samba-client are installed (optional but useful for diagnostics) rpm -qa | grep -i samba apt list --installed | grep -i cifs
🔁 Summary Checklist #CheckAction1SMB Account Domain fieldFill in the Windows AD domain name2URL formatUse smb://server/sharename/subdir/3SMB versionAdd JVM options for SMBv2/v34Port 445 reachabilityTest from Groundplex host5DNS resolutionTry IP if hostname fails Start with items 1 and 3 as they are the most frequent culprits for this exact error on Linux Groundplexes connecting to modern Windows servers.

Hello everyone, | Integration Nation

m.delgaizo
·
·
I'm trying to set up a file poller on a Windows share directory from a Linux groundlex, but although the connection with credentials works directly from the Linux machine, from Snap it gives me an error "Error occurred while creating a mount " : { "stacktrace": "com.snaplogic.snap.api.SnapDataException: Error occurred while creating a mount smb://my_server/my_dir/ (ERR_MOUNTERROR)\n at com.snaplogic.snap.api.fs.smb.SmbUtils.createMount(SmbUtils.java:128)\n at com.snaplogic.snap.api.fs.smb.SmbUrlConnection.connect(SmbUrlConnection.java:81)\n at com.snaplogic.snap.api.fs.smb.SmbFileSystemProvider.newFileSystem(SmbFileSystemProvider.java:47)\n at com.snaplogic.snap.api.fs.JfsUtils.getFileSystem(JfsUtils.java:277)\n at com.snaplogic.snaps.binary.FileFinder.lambda$getFileSystemFor$2(FileFinder.java:271)\n at net.jodah.failsafe.Functions$11.call(Functions.java:263)\n at net.jodah.failsafe.SyncFailsafe.call(SyncFailsafe.java:145)\n at net.jodah.failsafe.SyncFailsafe.get(SyncFailsafe.java:69)\n at com.snaplogic.snaps.binary.BinaryUtils.failsafeExecute(BinaryUtils.java:539)\n at com.snaplogic.snaps.binary.FileFinder.getFileSystemFor(FileFinder.java:275)\n at com.snaplogic.snaps.binary.FilePoller.poll(FilePoller.java:307)\n at com.snaplogic.snaps.binary.FilePoller.pollingLoop(FilePoller.java:269)\n at com.snaplogic.snaps.binary.FilePoller.process(FilePoller.java:262)\n at com.snaplogic.snap.api.ExecutionUtil.process(ExecutionUtil.java:106)\n at com.snaplogic.snap.api.ExecutionUtil.execute(ExecutionUtil.java:70)\n at com.snaplogic.snap.api.SimpleSnap.execute(SimpleSnap.java:70)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeSnap(SnapRunnableImpl.java:818)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeForSuggest(SnapRunnableImpl.java:657)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.doRun(SnapRunnableImpl.java:874)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:444)\n at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:118)\n at java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)\n at java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n at java.base/java.lang.Thread.run(Unknown Source)\nCaused by: Error Message=Unable to connect to the server;Error Code=[ERR_MOUNTERROR,-101] ;cause=[null]\n at com.visuality.nq.client.Server.connectionAttempt(Server.java:692)\n at com.visuality.nq.client.Server.connect(Server.java:1717)\n at com.visuality.nq.client.Mount.ensureServerConnection(Mount.java:647)\n at com.visuality.nq.client.Mount.doMount(Mount.java:926)\n at com.visuality.nq.client.Mount.doMount(Mount.java:623)\n at com.visuality.nq.client.Mount.<init>(Mount.java:489)\n at com.snaplogic.snap.api.fs.smb.SmbUtils.createMount(SmbUtils.java:123)\n ... 26 more\n" "reason": "Error occurred while creating a mount smb://my_server/my_dir/ (ERR_MOUNTERROR)" "resolution": "Please check all properties and credentials" "status_code": "error" "snap_details": { "label": "File Poller CRIF" "instance_id": "e7815740-f439-4f43-9c8d-c5e829ec8430" "class_id": "com-snaplogic-snaps-binary-filepoller" "build_tag": "main34730" "views": { "in": {} "out": { "output0": { "count": 0 } } "error": { "error0": { "count": 0 } }
m.delgaizo
·
·
Does anyone know if there are any special settings to make on either Snap Poller or the running Snap agent, or something else? Thank you
Scott O.
·
·
Checking through SnapLogic docs, this is a known challenge when connecting a Linux-based Groundplex to a Windows SMB share. The error ERR_MOUNTERROR typically points to one of several root causes. Here's a structured checklist to work through: ✅ 1. Verify Your SMB Account Configuration This is the most common cause (as confirmed by community reports). In SnapLogic Manager, check your SMB Account and make sure all three fields are correct: FieldNotesDomainMust be the Active Directory / NetBIOS domain name of the Windows host. This field is often left blank and causes mount failures on Linux.UsernameThe Windows account username (without domain prefix)PasswordThe correct password for that account
💡 Even if smbclient works from the Linux command line, SnapLogic uses its own Java-based SMB library (JCIFS), which handles authentication differently — hence why it can work from CLI but fail in Snap.
✅ 2. Check the SMB URL Format Make sure the Directory field in your File Poller uses the correct format:
smb://<server_name_or_IP>/<share_name>/<optional_subfolder>/
<share_name>is theSMB share name(e.g.,SharedDocs),nota full filesystem path.
The URL must end with a trailing/.
Avoid using\\server\share(Windows UNC) style — it won't work in SnapLogic.
Example:
smb://my_server/my_share/my_dir/
✅ 3. SMB Protocol Version Mismatch (Very Common on Modern Windows) Modern Windows servers (2012+) often disable SMBv1 by default. SnapLogic's JCIFS library may attempt SMBv1 negotiation by default, which would result in a mount error. You can force a higher SMB version via JVM options in your Groundplex Node Properties (in SnapLogic Manager → Snaplex → Update → Node Properties → Global Properties): KeyValuejcc.jvm_options-Djcifs.smb.client.minVersion=SMB202 -Djcifs.smb.client.maxVersion=SMB300
⚠️ If you already have a jcc.jvm_options value, append these flags rather than replacing the existing value. Restart the Groundplex node after applying.
✅ 4. Network & Port Connectivity Even though smbclient works from the Linux machine, verify that:
Port 445(TCP) is open from the Groundplex host to the Windows server (SnapLogic's JCIFS uses port 445 by default, not 139).
There areno host-based firewall rules(Windows Defender Firewall) blocking the Groundplex's IP specifically.
The Groundplex canresolve the Windows server hostname(DNS). If not, try using the IP address directly in the URL.
✅ 5. Linux System Packages (Less Common) While SnapLogic uses Java/JCIFS internally (not OS-level mounting), ensure the Linux Groundplex host isn't missing dependencies that could affect Java's native library resolution:
# Check if cifs-utils / samba-client are installed (optional but useful for diagnostics) rpm -qa | grep -i samba apt list --installed | grep -i cifs
🔁 Summary Checklist #CheckAction1SMB Account Domain fieldFill in the Windows AD domain name2URL formatUse smb://server/sharename/subdir/3SMB versionAdd JVM options for SMBv2/v34Port 445 reachabilityTest from Groundplex host5DNS resolutionTry IP if hostname fails Start with items 1 and 3 as they are the most frequent culprits for this exact error on Linux Groundplexes connecting to modern Windows servers.