I'm running my application on a virtual machine. Every time an exception is being thrown, I get this message in event log.
The "vmStatsProvider" is successfully initialized for this virtual machine.
This application that I'm writing connect to another server to get notification in a form of string.
I want to find out, what does this means.
Appreciate any help on this.
Thank you
You can refer to http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c04179838
Cause
If user installs the VMware tools with all components, some Windows
Performance Monitor counters will be added to the VM. When this
counters are available, the Events are often caused by a Third Party
Monitoring Tool.
Answer/Solution
Install the VMware Tools without the Perfmon Component :
setup.exe ADDLOCAL=ALL REMOVE=PerfMon
This prevent the installation of the additional Windows performance
counters in the VM and the Events are gone.
Related
I have in my Win32 application WM-KILLFOCUS hanging procedure. If I try to debug and test them proper function, windows lost focus on each breakpoints. Because focus gets Visual Studio window. Is here some way, how debugging application without focus losing?
(The same problem is with mouse moving, etc.)
Sorry about the late reply - I've been v busy - but here's a brief writeup about how to debug in a VM (as per the comments above).
Download and install suitable VM software on your development machine. I use VMware Player. This is free for non-commercial use, but if you are using it in a commercial setting please buy a copy (it is not expensive).
Create a new Virtual Machine, configured roughly as follows:
memory 6GB or so (hopefully you can spare that much)
disk space 100GB (don't worry if this sounds overly large - the file that backs the virtual disk will grow as needed)
network adapter bridged (important!)
Install Windows in the VM - from an ISO image (you can use Microsoft's Media Creation Tool to do this). This need to be Windows 10, VMware Player doesn't support Windows 11.
Once that is up and running, install the Visual Studio Remote Debuggung Tools in the VM.
Copy your binary/ies (and maybe your .PDB file/s, I don't recall if these are needed) to the VM.
Launch your app in the VM and fire up the remote debugging tools there. Then configure these for 'no security' (this makes it easier to establish a connection, and, since you're presumably in a secure environment, it's safe enough).
Connect to the Remote Debugger running in the VM from VS on the host machine. You will need to know the VM's IP address (you can find out what that is by running ipconfig in the VM).
In VS, select the application to debug.
You should now be up and running and you should have all the awesome features of the VS debugger available to you. Any problems or questions, please feel free to ask (the last few steps are a bit hazy in my mind, but I've done my best and if you can't find your way through it I'll research this a bit more).
Good luck!
I'm seeing errors in StackDriver logging for my Compute instance. The logs are showing repeated issues every hour, creating a lot of noise. I have a Spring Boot API deployed in a container to a VM in Compute Engine using latest stable version of Container OS.
I'm relatively new to GCP and don't understand what is causing this issue, searches have come up empty so far.
Failed to call method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: object_path= /org/chromium/SessionManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.SessionManager was not provided by any .service files
CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.ServiceUnknown, Message=The name org.chromium.SessionManager was not provided by any .service file
Error calling D-Bus proxy call to interface '/org/chromium/SessionManager': The name org.chromium.SessionManager was not provided by any .service files
The same 3 lines are repeating every hour. Anyone aware of what might be causing this or how to fix/suppress these?
I looked into this error, and as per my findings:
The error message that you have been receiving is a manifestation of Chrome to reliably exit shortly after starting up.
The UI’s job (which encompasses Chrome, the session_manager and the window manager) gets shut down by upstart because of it's thrashing, and when the test tries to restart the session_manager, the session_manager cannot communicate it over to the D-Bus.
The crash collection software in Container OS was originally for Chromebooks (The laptop using Chrome browser). So the code typically expects Chrome and some other related software on the system.
However, Container OS is a server OS, and does not have Chrome. So if Chrome is missing, the software will report some errors. They are actually not real failures, just some verbose error messages.
Overall, It is safe to ignore these logs and continue using your VM Instances.
Hope this helps.
I have a problem with a web service that is installed and started with a .msi that is created with the WiX toolset.
The service can be installed and started on all the machines I tested so far (shown as running in the Services Manager) but on some machines it is not reachable (for example via a browser) and not shown in the list of listening ports on that machine (displayed with 'netstat -a').
I am trying to figure out what's going wrong but I am not really familiar with web service development and configuration. It's a third party service, thus I don't know how it works internally.
A good starting point for me would be to find out, what exactly happens when a service is installed and started during the execution of the .msi-file.
Maybe I could try to tackle the problem on a lower level then.
Below is my code in the ServiceInstall-Element:
<ServiceInstall
Id="ServiceID"
Type="ownProcess"
Vital="yes"
Name="ServiceName"
DisplayName="ServiceDisplayName"
Description="Lorem Ipsum"
Start="auto"
Account="LocalSystem"
ErrorControl="normal"
Interactive="no"
Arguments="action=run">
</ServiceInstall>
The argument is important - without it, the service won't start or run.
Maybe someone else encounterd the same or a similar problem and can help me out.
Thanks already in advance - each hint is appreciated.
EDIT I (15.04.18):
As it might be a problem with the specific service, I will add some further information here:
It's a third party software called CryptoLicensing:
http://www.ssware.com/cryptolicensing/cryptolicensing_net.htm
Part of this software is that specific program, that serves as a License Server and does the license registration, for example in a customer's network.
The service can be run as a Windows application or installed and run as a Windows service. In both cases it should be listening on a (pre-)specified port on the installed machine.
Whenever I start the .exe as an application, everything works as intended. The service is reachable (for example with the browser) and can be accessed from other machines in the network.
When the .exe is installed and started as a service, it does not work as intended on every machine. For example if I install and start the service on my laptop, it is shown as running in the Services Manager, but is not reachable on its assigned URL (not even on the localhost) nor is the specific port displayed in the active listening ports, for example with 'netstat -a'.
The service itself starts without any error messages and does not log any errors or exceptions as it seems to be running without any problems.
I contacted the vendor, but sometimes he doesn't reply quickly and he is not very specific in his replies.
Before asking the question I assumed that it was a problem with the Windows user rights and the WiX installer but during the discussion here I had the feeling that it might a problem with the service itself.
I hope this 'new' piece of information helps in isolating and location the problem.
Thanks to everyone who helped so far!
Hopefully not stating the obvious here, but WiX doesn't do much except populate the ServiceInstall table in the MSI file, so this is about why Windows Installer won't start the service. ServiceInstall table:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa371637(v=vs.85).aspx
Also, this isn't really about ServiceInstall - it's probably about the ServiceControl element in your WiX source, but it's not clear whether that's how you're starting it or if you're starting it manually later on. That does make a difference. What is the error message and where are you getting it, and is it a 1920 or 1921 error (in the context of ServiceControl).
The main reason a service will start on one system but not another is missing dependencies. If your service is C++ based (the post doesn't say) then there are probably dependencies on C runtimes, UCRT runtimes, MFC or ATL runtimes and so on.
First: are you sure this service is intended to run as LocalSystem? (MSDN, SO).
Second: did you check the event logs in detail for anything obvious? If the service is good you should find a hint at least. Something to start with. I find that I sometimes miss the actual logs in the event viewer because it is so "crowded". My take on it: empty the log and stop and restart the service.
Something locking / blocking: If the service installs and runs OK I would suspect other factors such as firewalls (hardware & software), security software in general (anti-virus, malware scanners), network configuration issues (proxies, WINS, DNS and all the complexities involved in networking). Is the service trying to reach an UNC path?
Diverse Machines: What are the target machines? Are they virtual, are they physical, are they test machines, are they operative SOE machines in corporate networks? Are they the same OS version and edition?
Further Ideas: It is not quite related, but maybe skim this list of suggestions for debugging from another answer (I am not sure why it was down-voted, I think it is an OK list to inspire debugging ideas): Windows Application Startup Error Exception code: 0xe0434352 (maybe just skim the bolded words for ideas - Recommended).
sc.exe: And finally, perhaps check the sc.exe tool (Service Control) and see if it can provide you with some useful information for debugging.
sc.exe in the context of killing hung services (sample use).
sc.exe from MSDN
Some further links:
Windows Services Frequently Asked Questions (FAQ). Content seems to be up to date - at face value at least. These guys claim to be experts on services. I have no idea who they are.
Essential Tools for Windows Services: SC.EXE
Run Service Control (sc.exe) command on secure port
After almost 20 months we finally (and accidentally) found a solution to the problem! For the few machines, on which the service did not run properly, setting the NoInteractiveServices value in the registry to 0 did the trick. A value of 1 (which is default) means that no service is allowed to run interactively, regardless of whether it has the SERVICE_INTERACTIVE_PROCESS property. More information on Interactive Services.
I am not completely satisfied with the solution, because on all the other machines NoInteractiveServices is set to 1 AND the service runs properly anyway. However, on the machines where the service did not run interactively this solution worked for us. Thus I will accept this as an answer.
If anyone has more information on this issue and can explain why this works, feel free to
add them - I would be very interested!
I installed VM ware recently now whenever i try to power on VMware it shows the below message:
"Not enough physical memory is available to power on this virtual machine with its configured settings.
To fix this problem, adjust the additional memory settings to allow more virtual machine memory to be swapped.
If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines."
I am not able to change the memory setting .It just shows an option to resume the virtual machine, All other options are disabled. I have by mistake increased the VM ware memory in run time .Could any one help?
For anyone who encountered this problem recently, please visit this link:
http://blogs.vmware.com/workstation/2014/10/workstation-10-issue-recent-microsoft-windows-8-1-update.html
Go to Control Panel -> Programs -> Programs and Features,then uninstall the Windows 8.1 Update KB2995388 may help
--* Edit *--
The Optional Update for Windows 8.1 for x64-based Systems (KB2995388) published on 10/13/2014 may causes issues when running VMware Workstation on a Windows 8.1 host with it installed.
And a message saying "not enough physical memory" will be reported.
Because the VMware team hasn't fix the issue, you can follow steps below to uninstall the update to boot your virtual machine:
1.Go to Control Panel -> Programs -> Programs and Features, then select View installed updates at the top left corner.
2.Scroll down the list and locate Update for Microsoft Windows (KB2995388), select it and click on the Uninstall button.
3.Follow the steps to finish the uninstallation.
In the comment list, someone also reported a fix from VMware communities:
Open the config.ini file located at C:\ProgramData\VMware\VMware Workstation.
Add this line:
vmmon.disableHostParameters = "TRUE"
Save & reboot your PC
It sounds like your VM machine is in a suspended state. What you need to do is follow the steps outlined here in this help ticket. Do these steps while vmware is not running. And once you do this, start vmware again and then you should be able to edit your memory settings.
Run it in Administrator mode in Windows 8.1. Probably a Windows Update... Deleting the suspended state didn't work for me.
Before proceeding with any alternative solutions/workarounds, please always double ensure you have updated to the latest version of VMWare Player.
My machine was running VMWare Player, Version 6.0.*, and this issue was occurring (my local machine's Operating System is Windows 8.1). The relevant error(s) were resolved after updating to the latest build currently available, VMWare Player, Version 7.0 (Please note: I did not have to remove/uninstall any Windows Updates/Features)
Just spent a few hours trying to get my VMware to boot. Power flickered off enough to shut down the computer while the VMware was in suspension and recieved this message.
Make sure the update isn't installed. Make sure to follow the accepted answer. What made it work for me was:
Right click on your development name tab
Click on "Manage" and then "Clean up disk"
It worked for me. I'm not sure why it worked, but it was able to fix my issue. Didn't need to restart.
Follow these steps:
Close the VMware.
Select VMware icon.
Run VMware as Administrator.
I have a service application that on startup and shutdown logs an event log record.
I rebuild the application frequently and also then the executable on the host machine. And here is the problem, after my service shutdown the Windows Eventlog service (not the event log viewer) is holding an open handle to the executable so I cant update it.
I have the event log messages embedded in the executable, i could move it out but then I just move the update problem to another file.
I've double checked and I have paired ::RegisterEventSource/::DeregisterEventSource correctly.
Anyone encountered this problem ?
I've also run into this issue, so just adding some of my experiences.
I have a Windows 2008 Service system (have not seen this on 2003 Server), and when I stop my service, and instance of svchost.exe loads the service executable (visible using vmmap.exe or Process Hacker) preventing it from being deleted/overwritten during uninstall/install. The instance of svchost.exe is running the DHCP Client (Dhcp), TCP/IP NetBIOS Helper (lmhosts), and Windows Event Log (EventLog) services.
In our case, we have created a registry entry to make our service executable an event source. (though I'm unsure exactly why we are doing this, or whether we should be doing this).
Empirically, if I remove that registry entry before stopping the service, the executable is not loaded by svchost.exe and all is fine. If the service has already been stopped and executable loaded by svchost.exe, restarting the Event Log service (or killing the process) also frees up the executable.
I'm guessing our service is not well-behaved (perhaps a side effect of being a 32-bit process on 64-bit OS?) or correctly installed, but haven't isolated the issue yet.
Update: It appears this issue is only happening on HP systems (and not Dell or IBM) which is curious. There are HP-specific management components installed, so perhaps one of them is altering the behavior somehow?
I've also run into this issue. In my case, nxlog service reading logs. Simply stop nxlog service before replace event source file.
I think it is probably the event log viewer. Close the viewer and you'll be fine.