This is in case anyone else has this issue. After Microsoft's April 2017 upgrade, my VirtualBox running Laravel 4.2 stopped working. I found this in my event log files:
Faulting application name: VirtualBox.exe, version: 5.0.26.8824, time stamp: 0x578cc301
Faulting module name: VirtualBox.exe, version: 5.0.26.8824, time stamp: 0x578cc301
Exception code: 0xc0000005
Fault offset: 0x00000000000139ed
Faulting process id: 0x2ca8
Faulting application start time: 0x01d2ba0aeebae4e7
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: 4632a9fe-85d8-4f5b-8feb-f5079407f195
Faulting package full name:
I searched the internet and found other people had this issue with previous Microsoft Updates. They recommended reinstalling VirtualBox. I tried it and it resolved my issue. I reinstalled with the latest 5.0 version. The latest 5.1 version did not work since my framework was made for 5.0.
Confirmed: Uninstalling and re-installing fixes this issue for me also. Was on 5.0.26 but re-installed 5.0.40 with upgraded extension pack and all VM's worked fine.
Related
I have an msi installer that installs two windows services. There are no errors during installation on a Windows Server 2016 64-bit machine, the installation succeeds but the services are not installed. I was able to install the services manually using installutil but there are no clues as to why the msi failed to install the services. The installer has worked so far in hundreds of installations. I was able to get the event logs from the machine and the only errors I was able to find are in the Application log are of the kind:
Faulting application name: MsiExec.exe, version: 5.0.14393.0, time
stamp: 0x57899002
Faulting module name: MSIC9AE.tmp, version: 4.0.30319.33440, time
stamp: 0x52004298
Exception code: 0xc0000005
Fault offset: 0x000064ff
Faulting process id: 0x2244
Faulting application start time: 0x01d3db09c12691f2
Faulting application path: C:\Windows\syswow64\MsiExec.exe
Faulting module path: C:\Windows\Installer\MSIC9AE.tmp
Report Id: c5ffdc35-5ccd-4b00-9d60-1a198848062e
Faulting package full name:
Faulting package-relative application ID:
Installing again with verbose logging is not an option.
Any help is greatly appreciated.
There isn't much information on how you are installing the services, or what tool you are using to generate the MSI and install those services, but I can make some guesses from that log:
It appears that you are using installer class custom actions to install the services. In every case I'm aware of (except Visual Studio setups) this is unnecessary. Windows Installer has built-in support for installing services without running any code. Custom actions (instead of standard built-in functionality) are error prone. The better tools provide support for the ServiceInstall table and the ServiceControl table and that gets you out of the need to run code and the related issues.
That log shows that you are running a 32-bit msiexec.exe process to install services on a 64-bit system. I believe the 32-bit subsystem is optional on Windows Server, but it's not clear if that's an issue because the install apparently succeeds, although installer class failures typically throw an error and completely roll back the install. Are you installing silently? The other issue could be that there is no 32-bit NET FW to run that (apparently) 32-bit custom action. Or there is a NET FW architecture mismatch (you have some NET 2 code attempting to run in the 4.0 runtime). If that error 0xC0000005 is to be trusted, then you have an access violation inside the custom action code - custom actions work by extracting the code from the MSI Binary table into a random name .tmp file and then calling it from an msiexec.exe process, so perhaps the custom action code has lost access to that \installer folder for some reason. There is also a C++ shim Dll that loads a framework to run the managed code, so there is room for a C++ dependency failure in there as well
The installer class custom action framework is really difficult to debug when it fails because there are plenty of failure points, which is why I pointed out that installer classes can be error-prone as well as unnecessary.
Windows requires different setups for different architectures, so for a 64-bit install it's worth making sure that all the custom action code is explicitly built for 64-bit, if the issue is cross-architecture related.
I am breaking my head over this for a while now:
I have tried installing both professional and community version of visual studio 2017 v 15.5.2
and installed .net core Runtime 2.0.3 and .net core SDK 2.1.2.
When I open a new web application I get an error saying
"the sdk 'microsoft.net.sdk.web' specified could not be found"
When I try to build an existing project I get an error
"the current .NET SDK does not support targeting .NET Core 2.0. Either
target .NET Core 1.1 or lower, or use a version of the .NET SDK that
supports .NET Core 2.0."
I don't see ".net core 2.0" in my target framework
I don't have global.json file in my computer
When I try dotnet --info, I get this
.NET Command Line Tools (2.1.2)
Product Information:
Version: 2.1.2
Commit SHA-1 hash: 5695315371
Runtime Environment:
OS Name: Windows
OS Version: 10.0.10586
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.2\
Microsoft .NET Core Shared Framework Host
Version : 2.0.3
Build : a9190d4a75f4a982ae4b4fa8d1a24526566c69df
Some one please help
Fixed it by adding a MSBuildSdksPath userVariable.
Add an Enviroment variable named MSBuildSdksPath.
It's value should point to a Dotnet SDK folder. Eg:
C:\Program Files\dotnet\sdk\2.2.102\Sdks
I'm implementing deep-link in ionic, in Android works fine but in IOS don't send the url to the JS. The plugin is capable of opening the app but the function handleOpenURL is never called.
When I click over a link the debugger's log:
IonicDeepLinkPlugin: Handle continueUserActivity (internal)
https://www.example.com
My versions are:
Cordova CLI: 6.5.0
Ionic CLI Version: 2.2.3
Ionic App Lib Version: 2.2.1
ios-deploy version: 1.9.1
ios-sim version: 5.0.13
OS: macOS Sierra
Node Version: v6.10.0
Xcode version: Xcode 8.3.2 Build version 8E2002
Am I doing something wrong? Any Idea?
Thanks in advance!
Windows Service Error:
Error 1053: The service did not respond to the start or control request in a timely fashion
Event Log Error Recorded:
Faulting application [applicationname].exe, version 0.0.0.0, time stamp 0x541e3f33, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x00000000, process id 0x12c, application start time 0x01cfd54841eed684.
Libraries used:
Several Boost(1.55.0) Libraries: chrono, date_time, filesystem, iostreams, log, system, thread, zlib
OpenSSL(1.0.1i): libeay32.dll, ssleay32.dll
ZMQ: libzmq.dll, czmq.dll
When run as LocalSystem Privilege:
The same application works without any problem in Windows Server 2003,
but on Window Server 2008, it crashes instantly.
When run as Administrator, it's work in both 2003 and 2008 server.
How do I debug this problem?
I don't think there is any problem with the code, coz if there was, I wouldn't have been able to run it in my local (Windows8) and Windows server 2003.
Here is the code for reference anyway.
http://pastebin.com/zxh52Xdm
When I try to create a new PyDev Django Project I get this error:
Error creating Django project.
settings.py file not created
Stdout:
Stderr:
Apparently this was meant to have been fixed in 2.5
But I still am experiencing it with the latest Aptana Studio 3.0. The PyDev plugin is version 2.5.02012031515
Any idea please?
I have found the problem. It is a bug in PyDev that is fixed in 2.5.0.2012040618
According to PyDev there is no way to update the plugins of Aptana Studio. So we are at their mercy to update it soon.
Latest Eclipse is using the latest PyDev mentioned above and it works fine.
UPDATE:
I have found the solution here: https://jira.appcelerator.org/browse/APSTUD-4759
It is indeed a bug in Aptana 3.1.1, which has been solved now in 3.1.2. I can confirm that this bug has now been solved in latest 3.1.2 stable version on Ubuntu 12.04