Skip to content
  • There are no suggestions because the search field is empty.

OmniServer File Wedge access to files on a network share

 

It says in the help file I can do a file wedge to a network location. I have tried to get this to work using a mapped drive or a mapped folder but the server comes back with an error "Unable to open file "The operation completed successfully." Text not written." How can I successfully allow my File Wedge in OmniServer to access a network file?

Windows restricts access to network files by mapped network drive references when the accessing application is running as a Windows service. When OmniServer is configured to run as a Windows service, the File Wedge cannot access a file via a mapped network reference.

To allow the OmniServer File Wedge to access a file on a shared network directory, you have the following options:

 

  • OmniServer Running as a Windows Service

    • In the File Name field of the Wedge configuration, it will be necessary to use the fully qualified UNC file path:  \\Computer Directory DNS Name or IP Address\Folder Name\File.txt
  • OmniServer Running as a Windows Application (Not a Service)

  • Map the network location to a local Windows drive letter and specify the file name as if it were a local file, or
  • In the File Name field of the Wedge configuration, it will be necessary to use the fully qualified UNC file path:  \\Computer Directory DNS Name or IP Address\Folder Name\File.txt

Using the method above, you should be able to successfully use the OmniServer File Wedge with a file located on a network share/drive.

Examples:

  • MyFileServer\Program Files\MyFile.txt
  • 192.169.110.6\Program Files\MyFile.txt