I've got a VFP 9 SP2 app that is running on a Windows 2012 server via Terminal Services.
Sporadically the users will get the message "This app can't run on your PC".
Any idea what causes this? This is a 32-bit app running on a 64-bit server. We've tried setting the shortcut to run in compatibility mode for WinXP SP3 and it still has this problem.
Usually rebooting the server will fix this, but surely there has to be a configuration solution?
Related
I have a vm created in Azure, Windows Server 2012, x64 with Visual Studio 2015.
I'm trying the Weather application example from the site https://taco.visualstudio.com/en-us/docs/get-started-first-mobile-app/
When I try to start the application running the emulator VS Emulator 5 KitKat (4.4) I have errors with internet connection but I actually can connect to the internet.
Just after launch the application I get this message:
I hit Accept and then, after display the screen, I get next messages (Although the message is talking about Hyper-V, i´m using my MSDN account and Azure)
When I try to start the application running the emulator VS Emulator 5 KitKat (4.4) I have errors with internet connection but I actually can connect to the internet.
VS Emulators run as Hyper-V Virtual Machines. And if you are already in a Windows Server 2012 VM environment, it is not possible to to start another VM inside of it.
In Windows Server 2016 or Windows 10 VM it is possible to start an VM inside. For details, please refer to Enable Nested Virtualization.
I was wondering if there is another option for running the Aspnet_regiis.exe command under Windows Server 2008 R2 such that the IIS worker process is not restarted. Microsoft states the Aspnet_regiis.exe "-norestart" option is not supported under Windows Server 2008. As state here under the -notestart: http://msdn.microsoft.com/en-us/library/k6h9cz8h%28v=vs.100%29.aspx
Now if we run the command it restarts the process and if users' have session variables set they loose them.
Actually the reason the "-norestart" option is not included in 2008 R2 is because it is not needed. Running the command with this server no longer restarts it like it did in previous versions. We ran tests and could see the IIS process memory did not go down after issuing the Aspnet_regiis.exe, nor did we loose session state.
Windows 7, VS2012-Update1, x64.
If i start e new MVC-project, and add the Azure project to it. I can't debug it locally in the azure emulator.
The error:
Operation taking longer than expected
A 64-bit debugging operation is
taking longer than expected. This may be caused by incompatibilities
with 3rd party networking softwar. See help for troubleshooting these issues.
When i Terminate that message (twice):
Windows Azure Tools for Microsoft Visual Studio
There was en error attaching the debugger t the role intances
'deployment18(18).mvctest.Azure.Website_IN_0' with prces Id:'8752'.
Unable to attach. The Microsoft Visual Studio remote debugging monitor
has been closed on the remote machine.
The first message, I already found that if you change your website target to x86 that this can solve the problem. (this solved a problem for debugging unit-tests)
But if I change it to x86, the nex message pops up:
Windows Azure Tools for Microsoft Visual Studio
Cannot start debugging. The role was built for a platform incompatible with the windows azure compute emulator. On this system the compute emulator supports anyCPU and x64.
If i start without debugging (not x86), the windows emulator starts, and the website opens.
Is there a solution to solve this that we can debug x64 websites on the azure emulator?
Thanks.
Problem solved:
The issue was, that oour normal account didnt had admin privileges, and that we had to use an other admin user his credentials to run it in admin mode.
If i logged on with that admin user and started everything, that user couldn't also load the azure emulator.
Every co-developer had the same issue.
But when the normal account had back the admin privileges, the emulator started normally.
So i assume that there was something missing for those admin account (what i don't know)
Ensure that the remote debugging service and the machine debug manager (for x64) are properly installed and running (services in Automatic, especially not disabled).
You can also try to download and reinstall the remote debugging tools following instructions here
Even if it is on the same machine, chances are that debugging for the emulator goes through the remote debugging path
Been googleing this for a while now and it looks like the problem is connected to network drivers installed on windows. Do you have a VPN installed? Uninstall it and try again.
Otherwise it could be some of the network card drivers. Same here, uninstall and try again.
Some people have solved this by upgrading visual studio.
When install SQL Server 2000 (Evaluation copy) on Windows 7 32 bit Home Premium desktop computer,
system gives the following error and Installation not successful:
InstallShield Engine has stopped
working A problem caused the program
to stop working correctly. Windows
will close the program and notify you
if a solution is available.
Sql server 2000 is not supported on Windows 7. You might be able to get it installed but you would have problems.
According to this blog posting you even need SP3 of Sql Server 2005 for it to work on Win7.
http://blogs.msdn.com/sqlreleaseservices/archive/2009/10/23/sql-server-on-windows-7-and-windows-server-2008-r2.aspx
Currently I have a set of web applications that need to be installed (using IIS). They can only run in 32-bit mode so requires IIS to be set to run 32-bit apps. The steps that we've taken to do this work for server 2003 64-bit, and 2008 64-bit, but does not work on server 2008 R2 64-bit. I've spent many hours on this and I'm stumped.
The following are the steps performed to get the web apps installed:
1. Set "enable32BitAppOnWin64" app to true
2. Uninstall old ASP.NET stuff using 32-bit version of aspnet_regiis.exe: "aspnet_regiis -ua"
3. Install ASP.NET stuff using 32-bit version of aspnet_regiis.exe: "aspnet_regiis -i -enable"
As mentioned before, the above works fine on server 2003 64-bit and server 2008 64-bit, just not server 2008 R2 64-bit. Steps 2 and 3 give me the error: "Operation failed with 0x8007000B. An attempt was made to load a program with an incorrect format". After some searching, this is something to do with me running 32-bit application (aspnet_regiis) with IIS which is a 64-bit app. Step one has worked, as the flag has been set in the IIS GUI.
Would really appreciate it if someone could tell me where I'm going wrong, and why this doesn't work for 2008 R2.
Thanks
I know its a late post, but what I ended up having to do was run aspnet_regiis on the Framework64 folder and selecting the "Enable 32-bit Applications" on the application pool I was using and my sites came up.
In Vista and higher OS's ASP.NET is part of the OS and needs to be installed. You can install ASP.NET from the add windows features under Web Server.
The v4.0 version should work fine from both 32 and 64 bit folders.
Check for your Windows version.
If its a Windows 32 bit try running 'aspnet_regiis -i' from
C:\Windows\Microsoft.Net\Framework\v2.0.52707 folder
Or If its a 64 bit run it from
C:\Windows\Microsoft.Net\Framework64\v2.0.52707 folder