setwindowdisplayaffinity() is not working in Windows server 2012 R2
When I apply setwindowdisplayaffinity() in remote system get crashes without showing me any error. whereas if I don't apply setwindowdisplayaffinity() in remote system it works properly.
Could someone please help me out where I am going wrong.
Related
In my company, we have upgraded the Windows Server 2003 to Windows Server 2012 and we have some thin clients with an old version of RDP and they can't connect to the Server 2012 because when I does, I get this message: Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again.
Our thin clients are: Compaq Evo T30 and a Neoware CA19 and they have Windows CE 4.0 installed by default.
Searching in internet, I've found this tutorial: http://www.hjgode.de/wp/2014/03/12/windows-server-2012-rds-and-windows-mobile-connection-error/ but I can't apply it to our server because we don't want to have less security.
I've searched everything on internet to configure the Windows CE to be able to connect to our server 2012 but I can't find anything helpful :( Seriously, we don't want to apply the steps of the previous tutorial, we prefer buying new Thin Clients instead of doing that, but it will be better if there is a way to be able to connect to the server 2012 without changing anything in the server.
Anyone can help me? Please, it's very important.
Thanks in advance! :)
Unless there is a way to update your clients to a newer release of Windows CE that support new RDP versions (you should test that first) probably replacing them is the only option.
I have created a console application in visual studio 2013 on windows server 2012 standard version and the exe file seems to run ok but when I copy it to the windows server 2012 R2 standard version it come up with the following error when I try to run it - Application erro - The application was unable to start correctly (0xc000007b). Click ok to close the aplication. Can anyone help me fix this issue?
It's look like your 32-bit application tried to load some 64-bit "dll".
Try to check by Dependency Walker
I'm working with Selenium in VB.NET using IEDriver. I want to launch my ordered tests suite on my windows server 2008 R2 (My server used IE 11). I launch my test by command line : vstest.console.exe.
When I launch this on Windows 7, that works. I try to launch it on my server ( OS : windows server 2008 R2). That launch my Internet Explorer and my first page test. My test fail on the first try to find element (text input) and send key . However the element is present on my web page and I launch on the same website. I don't know where is my problem. I have some idea :
IE Driver compatibility with Windows Server 2008 R2 can't modify
Security server, some rights don't allow my driver to interact with IE
Problem in my code tests (Impossible for me, because the same code run perfectly on the same website)
Someone have any idea ?
This seems like a problem with windows server. Look for installed updates in server. This will probably occur because of that. Windows sometimes install updates without telling you and there are some updates that tamper with IEdriver and breakes it
We have a backup application that uses the Windows API BackupRead. It works correctly on Windows Server 2003, 2008, 2008 R2. It does not work on Storage Server 2008 R2. It always fails with error 50 - The request is not supported. The documentation for BackupRead gives no indication that it will not work with Storage Server 2008 R2.
Anyone else have any experience using this API on Storage Server 2008 R2? Did you need to make any changes to your use of the API in order for it to work?
Known problem between Windows 2008 and non-2008 volumes. Hot fix resolves it.
We have been running a Visual FoxPro (version 9) application on a Server under Microsoft Windows Server 2003 Operating system for a number of years now. We are now trying to migrate it to a different Server running under Microsoft Windows Server 2003 R2 and the application crashes. The problem occurs when it is trying to create HTML files from the FoxPro reports it has just created. To do this is uses the system variable _ReportOutput and aborts with the message “ox is not an object”. The application resides on the Network in a directory accessible to both Servers. Since hitting this problem I have changed the program to use the Htmllistener class within _ReportListener and get the same problem (works on one not on the other (R2)). Wait windows have been inserted to gain additional information but they only show that the object has not been created returning a data type of .Logical. It appears to me the problem is with the R2 version of the operating system, has anybody any ideas.
Have you installed ReportOutput.APP in the same folder as the application?