Before i begin let me inform you that I've already gone through other threads here regarding the same issue, none of them seems to have helped, therefore creating my own.
The issue started recently, by the very least i think it started happening 3 weeks ago. we have a custom build application that is deployed on our Network share, the exe is lightweight program, nothing too heavy.
The EXE can be ran manually or through our a shortcut but doesn't run either ways, a window about the same size as the app pops up and disappears immediately if you constantly double click on the exe.
All our Client computers are Windows 10 1909 build. All our servers are VMs running on a Hyper-V host and Windows Server 2019 latest version as well. only the Hyper-V Host is Server 2016 and the application runs fine on that server only.
Infact all other EXEs can be opened through the network share (not on the same server but on a VM) on that 2016 host but none of the exe's open on any other client computer or VM's.
The respective GPO to trust UNC paths is enabled and applied, there are no errors or warning whatsoever when launching any of the exe's, the files just don't open no matter how many times you click on it.
Any Ideas?
Related
We are currently in the process of migrating from Azure RemoteApp to another RemoteApp deployment as the current version goes end of life soon. An issue has been raised in UAT whereby Windows cannot be dragged across the screen for more than a split second (only seems to occur in instances where the Window in question is primed to be merged with another Window).
Here are two such examples:
https://drive.google.com/open?id=0B1S4OHN3Sdfyck13UVFzT0c1eWM
https://drive.google.com/open?id=0B1S4OHN3SdfyOHg4WlJmVGdIQTQ
This problem seems to only occur when connecting to Remote Apps via Windows 7 (which is what our users use). When tested in Windows 10 and OSX there was no problem. We also tested this inside a Remote Desktop and it was working.
Our current live deployment doesn't have this issue (connecting to Windows Server 2012). The deployment with the problem is using Windows Server 2016 so we spun up a host server using Server 2012 and still had the same problem.
We have also tried modifiying settings in the connection file to eleviate the problem. These are some of the settings that didn't seem to help the problem when we changed them:
bitmapcachepersistenable
disable full window drag
disable menu anims
disable themes
enablesuperpan
Has anyone come across with problem or know how to fix it? I'm happy to answer any questions about our setup.
I've been running IIS over the years, on Windows 2000, Windows XP and Windows 7.
Since I moved to Windows 10, I've been having lots of problems with IIS running slowly.
I have a clean install of Windows 10 on my PC, not a previous Win7 version upgraded to Windows 10.
These are the versions:
Windows 10 Version 1511 (OS Build 10586.420)
Internet Information Services (Version 10.0.10586.0)
I have tried all sorts to fix this issue, such as editing my hosts file to this:
127.0.0.1 localhost
Or commenting that line out.
I've tried running as:
127.0.0.1/mysite instead of localhost/mysite
I've tried tweaking various settings on the ApplicationPool, as per reading I've done on StackOverflow and the web in general.
There is nothing in the Event Log to do with errors or problems being flagged up.
However, a lot of the time page refreshes take over 1 minute to complete, which makes local development very slow.
The issue is the same on Chrome, Firefox, IE and Edge browsers.
I just re-installed Windows 10 and had the same issue again.
My IIS files sit outside of the wwwroot folder, in the c:\data folder. The localhost site was running painfully slow again.
This time, I fixed it by giving Read access to IUSR, NETWORK SERVICE and IIS_IUSR when right-clicking the folder and going to Properties > Permissions - e.g. for NETWORK SERVICE:
After that I restarted the IIS server and it sped up a lot.
This isn't how I fixed it last time though, but I can't remember how I fixed it them - so putting in this fix this time before I forget it!
I have an ASP.net MVC application that I've developed using Visual Studio 2015 Enterprise that is not behaving nicely in IE8, and as much as I'd like to just declare IE8 as unsupported, this is unfeasible from a business perspective at the moment.
So, to test in IE8, I downloaded a VirtualBox containing an instance of windows with IE8 from here.
I've been successful in using this instance of IE8 to connect my organization's dev server (which is running Windows Server 2012r2, IIS 8.5.9600), so I've been able to reproduce the issue. I'd really like to be able to step through what's happening in the debugger, though.
So, I believe I have two options.
Connect to the IIS instance on our dev server using Visual Studio's remote debugging feature.
This is kind of intimidating to me to attempt, because there seem to be a lot of options and I'm unsure how to proceed. It would be nice to be able to figure this out, though, as being able to do remote debugging on the dev server would be very helpful for future development. I tried using the default transport and putting the host for the dev sever in the "qualifier" box in VS, but it just told me the debugger service wasn't running on the remote machine, even though I'm fairly certain it is.
Connect to my local workstation running Visual Studio from virtualbox
This seems like it would be the simplest solution, but I can't figure it out. I tried a few different network modes from virtualbox -- NAT, bridged, and Host-Only, but I could never get the page to load in IE inside the virtualbox. I tried using the ip of my workstation as reported by ipconfig /all (the IP of the normal network adapter for bridged and NAT mode, and the IP of the "Host Only" special adapter in Host Only mode) and the port VS was configured to use. No dice.
Any ideas on how I can move forward with either of these options? Or some third, better option?
First off, I think I've been to every website and forum there is that's discussing this issue and I've tried many different things. I'm at my wits end. This is the dumbest thing and I just want to start coding again!
I'm using Visual Studio Express 2012 for Windows Desktop. I have a x64 project I'm trying to run in Debug mode using the local windows debugger. The only external library I'm using is that of which is required to run DX11.
I attempt to run my program and it freezes. A window pops up saying "A remote operation is taking longer than expected."
I click Terminate and another window pops up asking if I'd like to terminate the remote session. Why yes, I would.
Then it says, "Unable to start program (my path leading to my .exe). The network connection to the Visual Studio Remote Debugger has been closed."
To my understanding, because Visual Studio itself is a 32 bit application, it needs to use the Remote Debugger to compile to x64. Is that correct?
Regardless, I'm still failing to see where that would break down. I've ran several repairs on VS and upgraded to Service Pack 2 (or 1, whichever is the latest).
I've ran a windows repair and uninstalled any VMWare type stuff on my computer. I'm not using a VPN.
I've even copied msvsmon.exe from my laptop (working instance of the project) over to this computer and still no luck.
I'm about ready to Nuke my OS and do a clean install on everything. sigh
Found the problem. It wasn't Windows Firewall like other threads describe. It was my internet filter. I guess it decided to try and block msvsmon.exe because it was using the network. Adding it, along with WDExpress.exe to the application exceptions list did the trick.
My development workstation is running VS2012 Update 1. The OS is Windows 7 Professional Service Pack 1 x64. I have a laptop running Windows 8 onto which I've installed the VS2012 Remote Debugger. I've started msvsmon and it's quietly sitting in the system tray or what passes for it on Windows 8.
I have set up a breakpoint in VS2012 at a location where I need to do some debugging. In VS2012, I click on Debug | Attach to Process... I get the dialog showing the list of processes running on my machine. I change the machine name to the name of the Laptop.
I am having two different problems:
Problem 1:
With Windows Firewall running, VS2012 connects to the remote debugger server. I see the list of the processes running on the Laptop. I choose the one I want to debug and click Attach. I get "Unable to attach to process. The RPC server is not available."
What's going on here?
Problem 2:
I turn off Windows Firewall on my desktop. When I try to connect to the process running on the laptop, it connects and loads all of the symbols. So far so good. Once all of that is finished, I perform the action that would cause my breakpoint to be hit. The process on the remote machine freezes, but so does VS2012. I've sat here as long as 10 minutes waiting with no change. At that point, I kill msvsmon on the remote machine and my program goes away with it, but VS is still locked up.
Any ideas??
I have faced a similar issue in VS 2013 showing the message "Unable to attach to process. The RPC server is not available".
I have resolved this by un-checking the "Use Managed Compatibility Mode" option from Debug > Options and Settings > General Tab.