Network Shares SMB Epitasks Server 2012 R2

Hello there,

Please can somebody help.

We have just migrated from Mac to Windows. We are running Episode 7.1. We have 2 Windows Server 2012 R2 machines in a cluster. We have network shares mounted via SMB which have read/Write access to shared storage. Episode is running under a user with Administrator privilages.

The problem we are having is that from within Episode its self we can not import any .epitask configurations from the Network Shares. We just get the message "failed to Open Import".

If you copy the same epitask configuration to the desktop, it imports fine.

Any advice Appreciated

Regards

Matt

6replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Can you check the privileges on the file itself (.epitask) even though it would that's not the issue because moving it local does work.
    Have you been able to use media placed on the Network Share as a source in Episode? I want to make sure the issue is specific to the .epitask.

    Reply Like
  • Once you confirmed those scenarios (please confirm) fill out the support form and link to this forum thread.
    Episode Support Form

    Reply Like
  • Thanks GraigS,

     

    I will have a look at this when back in the office, operating on UK time here. I am suspecting some kind of permissions / privileges between the episode services and the network storage.

    On a windows level the permissions act as expected read / write to the network locations. Do you know if the services need to authenticate with the storage using a user / password that is known to the storage, or do the episode services use windows authentication?

    I tried to use a file from the storage as source a .mxf and episode complained that it could not find the path specified. When copied and pasted into the windows run box this path was fine and correct.

     

    Matt

    Reply Like
  • Episode should use Windows as I understand it but I'm thinking this might be permissions specific to the file. It may not be of course which is why I'm suggesting the test. There's also the possibility that something about the path name is throwing Episode.

    Reply Like
  • Hello

    I can confirm that the permissions are all ok, on a Posix linux level the are 777 and ACL Level all permissions are RW.

    No about the path theory. I turned on debugging and got the following output this shows the action of trying to import a .epitask from the shared storage using File>Import.

    #INFO - 2016-09-30T07:38:22.0041273+01:00 - >>> SendSync enter: port = 40429; name = read.config-file; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0051280+01:00 -     --->>> SendSync LOCK: port = 40429; name = read.config-file; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0071146+01:00 -     Read packet: port = 40429; size = 161; type = Reply; name = read.config-file
    #INFO - 2016-09-30T07:38:22.0071146+01:00 - HandleReply: packetName = read.config-file; asyncCommand = read.config-file
    #INFO - 2016-09-30T07:38:22.0071146+01:00 - HandleReply asyncObject.Release(): packetName = read.config-file
    #INFO - 2016-09-30T07:38:22.0071146+01:00 -     <<<--- SendSync RELEASE LOCK: port = 40429; name = read.config-file; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0071146+01:00 - ------- SendSync ERROR: port = 40429; name = read.config-file; ERROR = 'Failed to open file file:/N%3a/media/episodeSettings/import/f1Proxy.epitask (The system cannot find the path specified.)'
    #INFO - 2016-09-30T07:38:22.0071146+01:00 - <<< SendSync exit: port = 40429; name = read.config-file; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0071146+01:00 - >>> SendSync enter: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0081008+01:00 -     --->>> SendSync LOCK: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0091027+01:00 -     Read packet: port = 40429; size = 43; type = Reply; name = tsbase::url_password
    #INFO - 2016-09-30T07:38:22.0091027+01:00 - HandleReply: packetName = tsbase::url_password; asyncCommand = tsbase::url_password
    #INFO - 2016-09-30T07:38:22.0091027+01:00 - HandleReply asyncObject.Release(): packetName = tsbase::url_password
    #INFO - 2016-09-30T07:38:22.0091027+01:00 -     <<<--- SendSync RELEASE LOCK: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0091027+01:00 - <<< SendSync exit: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #WARN - 2016-09-30T07:38:22.0091027+01:00 -  - Unable to load plugin configuration (file:/N:/media/episodeSettings/import/f1Proxy.epitask): 
    #INFO - 2016-09-30T07:38:22.0091027+01:00 - >>> SendSync enter: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0091027+01:00 -     --->>> SendSync LOCK: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0101035+01:00 -     Read packet: port = 40429; size = 43; type = Reply; name = tsbase::url_password
    #INFO - 2016-09-30T07:38:22.0101035+01:00 - HandleReply: packetName = tsbase::url_password; asyncCommand = tsbase::url_password
    #INFO - 2016-09-30T07:38:22.0101035+01:00 - HandleReply asyncObject.Release(): packetName = tsbase::url_password
    #INFO - 2016-09-30T07:38:22.0101035+01:00 -     <<<--- SendSync RELEASE LOCK: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #INFO - 2016-09-30T07:38:22.0101035+01:00 - <<< SendSync exit: port = 40429; name = tsbase::url_password; milliTimeout = -1
    #DEBUG - 2016-09-30T07:38:22.0101035+01:00 -  - Unable to load plugin configuration (file:/N:/media/episodeSettings/import/f1Proxy.epitask): System.Exception: read.config-file returned error: Failed to open file file:/N%3a/media/episodeSettings/import/f1Proxy.epitask (The system cannot find the path specified.) ; path: file:/N%3a/media/episodeSettings/import/f1Proxy.epitask
       at Telestream.Ico.DataModel.AppHelperDataProvider.LoadPluginConfiguration(String configurationFilePath, Properties& configuration, Properties& values)
    #ERROR - 2016-09-30T07:38:22.0111039+01:00 - Telestream.Ico.Editor.WorkflowEditorViewModel - Failed to import. System.NullReferenceException: Object reference not set to an instance of an object.
       at Telestream.Ico.DataModel.AppHelperDataProvider.ConfigurationTypeFromValuesProperties(Properties valuesProperties)
       at Telestream.Ico.DataModel.AppHelperDataProvider.CreatePluginConfigurationModelFromUrl(UrlModel url)
       at Telestream.Ico.Editor.WorkflowEditorViewModel.OpenOnExecute(Object sender, ExecutedRoutedEventArgs e)
     

    The abstract below is interesting as it shows the path formatted incorrectly.

    Failed to open file file:/N%3a/media/episodeSettings/import/f1Proxy.epitask (The system cannot find the path specified.)'

    "2N%3a" is trying to refrence our N: drive.

    Any help still appreciated, without this working out whole new cluster might as well be a paper weight. We require this access so out MAM can move workflows around freely.

    Matt

    Reply Like
  • Thanks for that. Matt Drew fill out the above form link or, if you already have and received your case number, respond back by email with case number and the above information. It looks like Episode may be having problems with the path.

    Reply Like
Like Follow
  • 2 yrs agoLast active
  • 6Replies
  • 753Views
  • 2 Following