- #Error 3334 remote desktop connection manager how to
- #Error 3334 remote desktop connection manager trial
Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file. Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"Īdding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. I was able to create new and assemblies from 64bit dll version and now it works with "An圜PU":-) An attempt was made to load a program with an incorrect format. Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll ?Įrror message when making RDP connection:Ĭould not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Note that BOTH modifications need to be performed, i.e. For comparison, 32-bit RDCMan (with /LARGEADDRESSAWARE) started failing (error 3334) after opening 23 connectionsĪnd maxing out its VM limit (4 GB), while also being noticeably slower than the 64-bit one in refreshing thumbnails. VMMap showed that the application used 4.5 GB of virtual memory.
To be precise: this switches the exe to "An圜PU", so it will run as 32-bit on 32-bit OS and as 64-bit on 64-bit OS.Īs a quick test, I was able to connect to 25 servers and work without problems. Using the corflags utility I was able to switch RDCMan to 64-bit: It runs as a 32-bit process by default only because the executable is marked so. NET application (and the Remote Desktop ActiveX control it uses is available both to 32-bit and to 64-bit processes), it could, in fact, run as a 64-bit process on 64-bit systems, which would effectively eliminate any memory limit. LARGEADDRESSAWARE is a nice first step (it enables RDCMan to use 4 GB of virtual memory instead of being limited to 2 GB), but I got a bit further.īecause RDCMan is a pure. I don't think that should have an impact, but I wanted to be thorough.
#Error 3334 remote desktop connection manager trial
Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. Just to be clear, all these RDP sessions are running on the same server.
I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.Īre there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions? In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error. If I activateĪ 7th session one of the existing 6 sessions goes off-line with a connection error message. If I add more sessions I just get a variety of connection errors for the additional sessions. I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM).
0 kommentar(er)
