![]() Open the start screen (press the Windows key) and type gpedit.msc and open it.Ģ. This is controlled in Group policy management.ġ. Windows can, beside the local session, allow multiple RDP sessions without you being aware. I don't know if I have the solution for your case, but I have seen similar issues with windows servers that are part of a domain and know the same options exist in windows 10 (and I guess windows 7 and 11 as well). + Jump Desktop Connect 6.10.11 (latest version)īuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!Įxis01\PRODUCTION_NAME_03_ingest_03\avid mediafiles\mxf \ca_2023_10_12\c0045v0144eb2d97.mxfĪlso, we're using Active Directory for lookup, but we do not use domain accounts/users. Media Composer 2022.12.4 (+ currently testing 2023.3 on few workstations) Also, I'm curious to know if any else is encountering the same issues, even though it is quite "specific".īlackmagic Decklink or Ultrastudio 4k - all running Desktop Video Setup 12.5 Now, we've tried to investiguate as much as we could but I have to admit we have no idea left, so any help with this would be greatly appreciated. Also, we're using Active Directory for lookup, but we do not use domain accounts/users. I have to specifiy for troubleshooting purposes, that every editing workstation use the same user/password combination (for specific purposes, please don't dig this). * Exception: SYS_ERROR, status:1317, msg:The specified account does not exist. You can imagine how inconvenient this is because we constantly have to keep track of which editing machines has the BMD drivers installed or not, and so we regularly have complaints about not having external video and audio monitoring because the drivers are missing.Ĭhecking the console's output, I get this : Upon completion, a reboot is required and then, launching MC and connecting to MCPM, playback is finally available. ![]() Don't ask why is this related, I've no idea! But it does the trick, as long as the remote editor keeps the Jump Desktop connection open/running on the target machine while uninstalling/installing the BMD Video Setup. It consists in, on the station where the problem occurs, either uninstall or install the Blackmagic Desktop Video Setup software. So far, we've been able to find only one workaround, which itself does temporarily resolve the issue, but it is very inconvenient and again, it does not last. All is fine for the few stations which are not (because one specific production does not use MCPM). Now hang on : this "DISK_INVALID_USER" comes up only when remoting on a station connected to MCPM. We've runned several tests, in order to try and indentify the context in which this does happen, because it doesn't in every scenario ! Indeed, our facility runs mostly on MediaCentral | Production Management (more than a 3/4 of our different productions do), but all of our productions are using Avid NEXIS. ![]() Guess at least, the error message got more "specific". This "DISK_INVALID_USER" we're having now used to translate a pure and simple "Media Offline" on version 2018.12.15. It worked well for a couple of years until sometime during last year, when this problem started to show up : when connecting to an editing station through Jump Desktop, Media Composer won't playback timelines or clips, displaying this " DISK_INVALID_USER" error message in the bottom left corner of a blackened record monitor. We're a large facility which, during the pandemic, adopted Jump Desktop as our first choice for remote editing gave us incredibly good results, no latency, really comfortable to use. We've been sracthing our heads for a while now about this one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |