VIPR SRM 4.0.1 Error Message: Could not determine the type of file "<given URL>" is writeable Failed to tranfer using SMB Remote URL.

Summary: Schedule Reports Fails to tranfers using SMB Remote URL, Caused by: jcifs.smb.SmbException: Failed to connect to server

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms



Errors Message from taskRun-0-0.log:

170713 13:41:04 : SEVERE: Scheduled Report `EMC Capacity Report` for user `emcsrmreports` could not be sent: Thursday, July 13, 2017 1:41:04 PM CDT SEVERE: Scheduled Report `remote location` for user `emcsrmreports` for type `EMC Capacity Report` failed!
170713 13:41:04 : org.apache.commons.vfs.FileSystemException: Could not determine if file "<given URL>" is writeable.
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.isWriteable(AbstractFileObject.java:484)
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:860)
170713 13:41:04 :   at com.watch4net.apg.v2.plugins.virtualFileSystem.VirtualFileSystem.sendFileContent(VirtualFileSystem.java:82)
170713 13:41:04 :   at com.watch4net.apg.report.scheduling.generator.ReportGeneratorUtils.sentReportToRemoteURL(ReportGeneratorUtils.java:265)

170713 13:41:04 : Caused by: jcifs.smb.SmbException: Failed to connect to server
170713 13:41:04 : java.net.UnknownHostException: <Hostname>
170713 13:41:04 :   at jcifs.UniAddress.getAllByName(UniAddress.java:315)
170713 13:41:04 :   at jcifs.smb.SmbFile.getFirstAddress(SmbFile.java:810)
170713 13:41:04 :   at jcifs.smb.SmbFile.connect(SmbFile.java:897)
170713 13:41:04 :   at jcifs.smb.SmbFile.connect0(SmbFile.java:826)
170713 13:41:04 :   at jcifs.smb.SmbFile.queryPath(SmbFile.java:1279)
170713 13:41:04 :   at jcifs.smb.SmbFile.exists(SmbFile.java:1361)
170713 13:41:04 :   at jcifs.smb.SmbFile.isDirectory(SmbFile.java:1434)
170713 13:41:04 :   at com.watch4net.apg.v2.plugins.virtualFileSystem.providers.smb.SmbFileObject.createSmbFile(SmbFileObject.java:88)
170713 13:41:04 :   at com.watch4net.apg.v2.plugins.virtualFileSystem.providers.smb.SmbFileObject.doAttach(SmbFileObject.java:55)
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.attach(AbstractFileObject.java:1291)
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.getType(AbstractFileObject.java:412)
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.exists(AbstractFileObject.java:402)
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.isWriteable(AbstractFileObject.java:468)
170713 13:41:04 :   at org.apache.commons.vfs.provider.AbstractFileObject.copyFrom(AbstractFileObject.java:860)
170713 13:41:04 :   at com.watch4net.apg.v2.plugins.virtualFileSystem.VirtualFileSystem.sendFileContent(VirtualFileSystem.java:82)
170713 13:41:04 :   at com.watch4net.apg.report.scheduling.generator.ReportGeneratorUtils.sentReportToRemoteURL(ReportGeneratorUtils.java:265)

170713 13:41:04 :   at com.watch4net.apg.report.scheduling.generator.ScheduledReportGeneration.main(ScheduledReportGeneration.java:105)
170713 13:41:04 :   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
170713 13:41:04 :   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
170713 13:41:04 :   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
170713 13:41:04 :   at java.lang.reflect.Method.invoke(Method.java:498)
170713 13:41:04 :   at com.watch4net.component.loader.util.ComponentLauncher.invoke(ComponentLauncher.java:108)
170713 13:41:04 :   at com.watch4net.component.loader.util.ComponentLauncher.main(ComponentLauncher.java:49)
170713 13:41:04 :   at com.watch4net.apg.report.scheduling.generator.ScheduledReportGenerationTask.main(ScheduledReportGenerationTask.java:29)

170713 13:41:05 : Execute method (main) exited with a failure error code of 13
170713 13:41:05 : Task EMC Capacity Report failed with status 13.

Resolution

Please follow the resolution below to correct the issue:

1. Please verify if you are able to ping the host from the Frontend server and verify if the host can be resolved by performing an nslookup of the host FQDN, Shortname and IPAddress.

2. If host does not resolve or ping, please add the host DNS Suffix into /etc/resolve.conf file.

3. Then add the host shortname, FQDN and IPAddress into /etc/hosts file.

4. Restart the Host Server and test the Schedule Report from the VIPR SRM UI.

Affected Products

SRM
Article Properties
Article Number: 000052864
Article Type: Solution
Last Modified: 16 Jun 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.