Avid Media Composer with Interplay

[Jus10case]

I have the same problem as this post

https://h30434.www3.hp.com/t5/HP-Remote-Graphics-Software-RGS/Strange-error-with-Avid-Media-Composer...

It will work the first time I connect to the machines with HPRGS, but after I end my session, the only way for it to work correctly again, where media is online in AVID, is to restart the machine.  I tried restarting the Avid MI service but that didn't seem to help either.

[Jus10case]

Is there a way to keep RGS from having windows on the sender machine go back to a user login screen?  That seems to be what is causing the issue, or at least that would give me some sort of work around. Thanks!

[Jhatto]

Are you using a user account with access to NEXIS/ISIS to log into the OS?  Had this issue when using a local user that didn't have access to the storage.  Using a domain account that does have read/write onto the storage fixed it for me.

Jon

[AndreasBR]

We have the same problem here on a couple of machines. We use a Domain account to login on OS. The Nexis Client is preconfigured to log into Nexis with a Avid/Non Domain User. Read/write does work in general. We can write to Nexis. But anything that is already there is offline. 

What is interesting is the fact that the machine is not able to access the media file with the UNC path copied from Interplay Access to Windows Explorer. But if you drill down to the respective file manually you get there without problems. Any ideas?

[Jhatto]

It sounds like this is the same issue.  Can you test by using a user in NEXIS with the same credentials as the OS user?  You can then click OS Logon within the NEXIS Client. 

[Jus10case · Accepted solution]

Changing to "easy login" option in the sender fixed the issue.  

[AndreasBR]

Thanks to Jhatto and Just10Case for the input. It actually looks like the client ist somewhat using the OS account as a base to access the Nexis. We created a Nexis user with the same credentials like the OS and then it worked. Doesn´t make too much sense to me. Both worlds are completely separated. If my guess is right about the usage of the OS login this is something HP would need to take a look at. In our company we use domain accounts for OS and in general one Editor login for Nexis. We would need to create a nexis user for each edit bay in this case. Not really manageable (we have lots of them). For now we can work around as we need to use HPG only for a very limited covid related workflow.

I´ll try the easy log in setting in the sender too.