Page History
| Table of Contents | ||
|---|---|---|
|
FAQs
Specific
Crawls used to work, but now fail with "The parameter is incorrect" exceptions
Check if the following stack trace is on your component logs:
| Code Block |
|---|
com.searchtechnologies.aspire.services.AspireException: Couldn't extract subFiles from url: smb://url/. Detailed exception: jcifs.smb.SmbException: The parameter is incorrect.
at com.searchtechnologies.aspire.components.CIFSSourceInfo.scan(CIFSSourceInfo.java:228)
at com.searchtechnologies.aspire.scanner.AbstractScanner.scanDirectory(AbstractScanner.java:451)
at com.searchtechnologies.aspire.scanner.AbstractScanner.scanProcess(AbstractScanner.java:320)
at com.searchtechnologies.aspire.scanner.AbstractScanner.process(AbstractScanner.java:117)
at com.searchtechnologies.aspire.application.JobHandlerImpl.runNested(JobHandlerImpl.java:141)
at com.searchtechnologies.aspire.application.PipelineManagerImpl.process(PipelineManagerImpl.java:204)
at com.searchtechnologies.aspire.application.JobHandlerImpl.processLocalJobRoute(JobHandlerImpl.java:374)
at com.searchtechnologies.aspire.application.JobHandlerImpl.runNested(JobHandlerImpl.java:291)
at com.searchtechnologies.aspire.application.JobHandlerImpl.run(JobHandlerImpl.java:75)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: jcifs.smb.SmbException: The parameter is incorrect.
at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:561)
at jcifs.smb.SmbTransport.send(SmbTransport.java:638)
at jcifs.smb.SmbSession.send(SmbSession.java:238)
at jcifs.smb.SmbTree.send(SmbTree.java:119)
at jcifs.smb.SmbFile.send(SmbFile.java:775)
at jcifs.smb.SmbFile.doFindFirstNext(SmbFile.java:1986)
at jcifs.smb.SmbFile.doEnum(SmbFile.java:1738)
at jcifs.smb.SmbFile.list(SmbFile.java:1709)
at jcifs.smb.SmbFile.list(SmbFile.java:1606)
at com.searchtechnologies.aspire.components.CIFSSourceInfo.scan(CIFSSourceInfo.java:215)
... 11 more |
| Info |
|---|
This usually means that the target share was restarted (mounted/unmounted). The underlying connection is cached by the Java Virtual Machine, so a simple restart of Aspire will solve the issue. |
Can the CIFS Connector process archive files?
Yes,
...
the CIFS Connector can process archive files so that the individual files in the archive are able to be published
...
. For more information, see Archive files processing.
...
General
| Include Page | ||||
|---|---|---|---|---|
|
Troubleshooting
| Info |
|---|
No available troubleshooting at this moment |
Problem
Solution
...
Known Issues
Microsoft recommends deactivating SMB1 from Windows servers
Problem
Due to a security issue observed with the protocol, Microsoft has recommended deactivating SMB1 from Windows servers.
This affects the CIFS component, which uses the JCIFS library to communicate with a file share. The JCIFS library only supports the SMB1 protocol; it does not support the SMB2 or SMB3 protocols currently. As a result, the CIFS component may be unable to communicate to a Windows file share (using protocol SMB2 or SMB3).
Solution
We are working on finding a solution for this scenario (SMB1 deactivated).
Overview
Content Tools