I'm not sure what's going on here, the app runs on my laptop outside the development environment but will not run on Windows Server 2012 R2, absolutely no errors are generated, just doesn't load the form. I used the latest version of Visual Studio 2022 to create the application, application settings are:
Output Type: Windows Application
Target Framework: .NET 6.0
Target OS: Windows
Target OS Version: 8.0
Supported OS Version: 7.0 (tried 8.0 as well)
Target CPU: x64
The are a lot of other settings I believe are not applicable so I don't list them here. The permissions on the server are set properly. When I delete the app.dll file, the exe complains it can't find it so I know at least the exe "should" run. I get no error messages, nothing in the logs. Any suggestions?
Related
Built a UMCA 6.0 APP on Laptop 1 with platform target set to x64 and framework target set to .Net Framework 4.8. Laptop 1 is X64 based CPU running Windows 10 Enterprise. Application runs as designed.
Copied the executable and DLLs to Laptop 2, where UCMA runtime and .NetFramework 4.8 were installed. The process also required installing Visual C++ 2015-2019 redistribution. Got the infamous SIPEPS error message.
Copied the project directory (source code, project file, etc.) to Laptop 2 and rebuilt the app after doing a clean. Confirmed project properties included X64 and .Net Framework 4.8. Build was successful 1st time. Ran the app and still getting the SIPEPS error message.
Both laptops are Dells with i7 cores. Using VS 2017 for build. Need to have a backup machine for this app. If the primary fails - we are dead in the water.
You must uninstall all Visual C++ releases greater than 2013 before UCMA 6.0 will properly install. I also did a repair of .Net Framework 4.8. Installed UCMA 6.0 before anything else and that seems to have addressed this particular issue.
Now its on to a new issue: "Recorder cannot start due to I/O Error."
I have downloaded the CefSharp 71.0.0-pre01 Source code from the official release, and built it successfully by VS 2015 on my Windows 7 Ultimate x64.
I have checked all x86 and x64 release build, and the project built all 22 items successfully includes the example exe.
The WinForm Example folder has 2 output in the bin, the x64 release can run well on my Win7 x64, but the x86 (32 bit) release doesn't work. Once I run the "CefSharp.WinForms.Example.exe", it shows
CefSharp.BrowserSubprocess has stopped working
When I click to check issue details, it shows:
Event Name: APPCRASH
Application Name: CefSharp.BrowserSubprocess.exe
But when I run the x86 release on the Win7 32bit machine, it works well.
I wanted to build an AnyCPU version but the project doesn't support AnyCPU, then I assumed the x86/32bit should work on both 64/32 machines. Is it possible to do that?
A case I've experienced is setting max_old_space_size to a large value which causes render subprocess to crash on startup when running in 32bit mode. Removing this option resolved the issue for me.
I'm developing an application for a friend. I use Visual Basic 2012 (64-bit) and Windows 7 (64-bit).
I took a demo down to him to try it out to see what more features he wanted, and it was running ok.
When I got back the next week after implementing the new features, it refused to run on any of his Windows XP (32-bit) machines.
Error code:
MyApplicationName.exe is not a valid Win32 application
I tried it at a computer running Windows 7 (32-bit) which still worked all fine.
So, any ideas why it suddenly stopped running?
VS2012 will not generate an EXE that can run on XP when you use the default project settings. What matters is the .NET Framework version you target. If that's version 4.5 then there are two problems.
First one is that .NET 4.5 is not available for XP. Second one is important for this exception message, the compiler will mark the version of Windows that's required to run the EXE in the file header. That version number has always been set to 4.00. Until VS2012, it is now set to 6.00, the version number of Vista. XP will instantly reject your EXE with the "is not a valid Win32 application" message, even before it will tell you that it doesn't have .NET 4.5 installed.
Fix your problem by targeting .NET 4.0 or earlier. Project + Properties, Application tab, Target framework setting.
Try using corflags with /32bit+ and see if it works.
More information:
http://msdn.microsoft.com/en-us/library/ms164699.aspx
I have written a windows service in c# using ide visual studio 2012.
When I tried to install it on a windows server 2003 I got this error message:
Prerequisite check for system component Microsoft .NET Framework 4.5 (x86 and x64) failed with the following error message:
"Installation of the Microsoft .NET Framework 4.5 is not supported on this operating system. Contact your application vendor."
So I went back into my project and set the target framework to 4.0. I then rebuilt the solution, re-added the installer and published again. However, when I try to install I get the exact same error.
For some reason it is not detecting that I have changed the framework to 4.0. Any ideas where I have force this change or where even to look??
Extra Info: It seems to be using click-once deployment.
The only solution I came up with was to create a new project with the correct .NET version. Copied all my code across and it worked... shrug
.NET Framework 4.5 is not supported on Windows XP, Windows Server 2003 and similar.
Supported Operating Systems (as per System Requirements page):
Windows 7 Service Pack 1, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2
Windows Vista SP2 (x86 and x64)
Windows 7 SP1 (x86 and x64)
Windows Server 2008 R2 SP1 (x64)
Windows Server 2008 SP2 (x86 and x64)
If you're using Wine to install it, run winecfg and change your Windows version to higher.
Otherwise install lower version of .NET Framework such as 3.0. If you're compiling the project, change it in Target framework.
I'm having problems migrating a PowerBuilder application from XP to Windows 7.
We've built the application in PowerBuilder on Windows XP, and when we attempt to install components in to component services on Windows 7 machines, we get compatibility errors. Everything works great on Windows XP. But I think because the DLL's on 7 are so different, it's having problems.
If the program was built using a PowerBuilder IDE in a Windows 7 environment, would that possibly fix the problem?
The application is divided into
- a server component running on Server 2003
- a client component which installs sucessfully on Win7
- proxy components that are generated into an MSI when the server components are installed.
The problem is only the proxy. The MSI doesn't want to work on Windows 7.
Without the proxy installed on the client desktops, the client can't communicate with the server.
When I run the MSI in compatibility mode on Windows 7, I get some details of the error. Here they are
Program Compatibility Issues found Incompatible Application Fix
application CCS_Proxy_XP_Exports
Issues found Incompatible Application CCS_Proxy_XP_Exports is
incompatible.
Fix application CCS_Proxy_XP_Exports Provides steps to fix the
incompatible application. CompatMode CompatMode UserVerifySolution
User Verification of Solution Verify_NO
Detection details Collection information Computer Name: ##########
Windows Version: 6.1 Architecture: amd64 Time: Wednesday, November
14, 2012 11:56:36 AM
Publisher details Program Compatibility Make older programs run in
this version of Windows. Package Version: 1.5 Publisher: Microsoft
Windows
Program Compatibility Make older programs run in this version of
Windows. Package Version: 1.0 Publisher: Microsoft Corporation
If I view more details on the event log, I get the following
“Product: Client Communications (Application Proxy) -- Error 1928.
Error registering COM+ Application. Contact your support personnel
for more information.”
General idea
Actually dll on the win7 platform are not different from previous ones. There can be differences related to the multiple and different C runtimes that live now in the WinSxS dll-hell directories but this should not impact powerbuilder (as I can say from my 11.5 classic release experience).
I suspect that you might have some problems related to the UAC and or ACL management. I recently upgraded some legacy PB applications by adding compatibility to the Vista / Win7 specifications.
In short : the application must run without needing administrative privileges, and must not try to modify data in privileged places like c:\ or c:\windows.
Thus everything must no more be installed in program files directory. The application binaries can be deployed in program files but if the application need to create / modify some files they must be deployed in a ProgramData subdirectory for user-shared datad and / or in the local user data files for the private data. The application has to be modified to create or find the files in the correct directories. If you do not comply to the standard, the file virtualization mechanism can hide a lack of rights and can simulate the files in a VirtualStore directory in the user local data but is just a workaround and it provides some other problems.
Com+ error
Given you error messages, if the proxy is also a PB application, given the fact that PB only produce 32bits binaries and that your system is a 64bits one, maybe that the tips to register a 32b COM+ onto a Win2008 could help you?
Thought, your proxy exe/dll file does not have manifest or manifest does not contains compatibility section. Try to add compatibility info to manifest.