Mixing
when applying a sql server cumulative update or service pack on a virtual machine - what could be a safe way of stopping VMWaretools?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
While applying cumulative updates to sql server 2016 SP1, there are a bunch of services and applications that need to be stopped for the update to go on.
Among those is the very core of the virtual machine, the VMware Tools core service.
Is it safe to stop all the instances of this application in order to go on with the updates?
What could be a safe way of doing it?
sql-server sql-server-2016 virtualisation patching windows-server-2012-r2
asked 2 hours ago
marcello miorelli
5,2401659123
add a comment |Â
up vote
1
down vote
favorite
While applying cumulative updates to sql server 2016 SP1, there are a bunch of services and applications that need to be stopped for the update to go on.
Among those is the very core of the virtual machine, the VMware Tools core service.
Is it safe to stop all the instances of this application in order to go on with the updates?
What could be a safe way of doing it?
sql-server sql-server-2016 virtualisation patching windows-server-2012-r2
asked 2 hours ago
marcello miorelli
5,2401659123
Where do you see VMware in there?
– Tom V
2 hours ago
Simply go ahead and click next to install the patch and later just reboot the machine. I hope reboot is option here
– Shanky
2 hours ago
what this is basically telling you that these files are in use and will not be updated until you restart the server. it will not stop the upgrade
– Bob Klimes
57 mins ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
While applying cumulative updates to sql server 2016 SP1, there are a bunch of services and applications that need to be stopped for the update to go on.
Among those is the very core of the virtual machine, the VMware Tools core service.
Is it safe to stop all the instances of this application in order to go on with the updates?
What could be a safe way of doing it?
sql-server sql-server-2016 virtualisation patching windows-server-2012-r2
asked 2 hours ago
marcello miorelli
5,2401659123
While applying cumulative updates to sql server 2016 SP1, there are a bunch of services and applications that need to be stopped for the update to go on.
Among those is the very core of the virtual machine, the VMware Tools core service.
Is it safe to stop all the instances of this application in order to go on with the updates?
What could be a safe way of doing it?
sql-server sql-server-2016 virtualisation patching windows-server-2012-r2
sql-server sql-server-2016 virtualisation patching windows-server-2012-r2
asked 2 hours ago
marcello miorelli
5,2401659123
asked 2 hours ago
marcello miorelli
5,2401659123
asked 2 hours ago
marcello miorelli
5,2401659123
asked 2 hours ago
marcello miorelli
5,2401659123
asked 2 hours ago
marcello miorelli
5,2401659123
5,2401659123
Where do you see VMware in there?
– Tom V
2 hours ago
Simply go ahead and click next to install the patch and later just reboot the machine. I hope reboot is option here
– Shanky
2 hours ago
what this is basically telling you that these files are in use and will not be updated until you restart the server. it will not stop the upgrade
– Bob Klimes
57 mins ago
add a comment |Â
Where do you see VMware in there?
– Tom V
2 hours ago
Simply go ahead and click next to install the patch and later just reboot the machine. I hope reboot is option here
– Shanky
2 hours ago
what this is basically telling you that these files are in use and will not be updated until you restart the server. it will not stop the upgrade
– Bob Klimes
57 mins ago
Where do you see VMware in there?
– Tom V
2 hours ago
Where do you see VMware in there?
– Tom V
2 hours ago
Simply go ahead and click next to install the patch and later just reboot the machine. I hope reboot is option here
– Shanky
2 hours ago
Simply go ahead and click next to install the patch and later just reboot the machine. I hope reboot is option here
– Shanky
2 hours ago
what this is basically telling you that these files are in use and will not be updated until you restart the server. it will not stop the upgrade
– Bob Klimes
57 mins ago
what this is basically telling you that these files are in use and will not be updated until you restart the server. it will not stop the upgrade
– Bob Klimes
57 mins ago
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
5
down vote
None of the services in your screenshot have anything to do with VMWare.
The one you highlighted is Wmiprvse.exe which is basically WMI
WMI resides in a shared service host with several other services. To avoid stopping all the services when a provider fails, providers are loaded into a separate host process named "Wmiprvse.exe".
The other ones are
SSISTELEMETRYis basically the customer improvement service
Windows Agent Service is probably something for NetIQ.
PBIEgwService is an on-prem Power BI gateway.
In any case, just update the box and reboot it afterwards (I'm assuming you have a maintenance window for the update anyway), I'm fairly sure you can stop those 4 services during the update.
answered 1 hour ago
Tom V
13.3k74373
add a comment |Â
up vote
2
down vote
The WmiPrvSE.exe belongs to the service Windows Management Instrumentation and is located in the %WINDIR%SysWOW64wbem directory.
However, when looking at the Task Manager compared to the details of the Windows Management Instrumentation service, you may notice that the service runs via the C:WINDOWSsystem32svchost.exe -k netsvcs -p process/executable.
So you will have a WmiPrvSE.exe running in the Task Manager, but the service is running via said svchost.exe process. What is the reason for this?
Explaining (Some) Windows Services
You can determine what is actually running as a service by starting the Sysinternals tool procexp.exe and looking at the details of the individual svchost.exe processes running by mousing over the various svchost.exe processes running.
It looks a bit like this:
You can then click on the details of that process and will find the following:
And if you switch to the Service tab you will find this:
...scroll a bit to the right and you are presented with:
What's Going On?
When various windows services start (and you might have noticed there are a few), they don't always start the actual <service_name>.exe, but instead a kind of shell executable, which is the svchost.exe and a corresponding *.DLL required by the service.
If the system or user actually requires a portion of that service, either by starting a program or opening up an Management Console, then the *.DLL which has been loaded by the svchost.exe process will trigger the actual executable required.
In fact during the writing of this answer the WmiPrvSE.exe started multiple times and then closed again, even though the service was always in the running state.
Answering Your Question
Is it safe to stop all the instances of this application in order to go on with the updates?
Option 1
You can safely stop the Windows Management Instrumentation service and continue with your SQL Server upgrade/installation.
However, when you stop the Windows Management Instrumentation service, you might be prompted to close other services that rely on WMI to be in a running state. Examples from my computer:
- VMware USB Arbitration Service
- IP Helper
- ...
This can reduce the probability of having to reboot after upgrading. It will not stop the installation routing from rebooting the SQL Server service (if required).
Option 2
In some cases you can wait a bit for the WmiPrvSE.exe to shut itself down and then continue with the installation. But, depending on what your server is running, this could take a while.
Option 3
Let the installation continue and reboot the server. Your SQL Server service might go down anyway.
answered 27 mins ago
hot2use
7,58941951
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
None of the services in your screenshot have anything to do with VMWare.
The one you highlighted is Wmiprvse.exe which is basically WMI
WMI resides in a shared service host with several other services. To avoid stopping all the services when a provider fails, providers are loaded into a separate host process named "Wmiprvse.exe".
The other ones are
SSISTELEMETRYis basically the customer improvement service
Windows Agent Service is probably something for NetIQ.
PBIEgwService is an on-prem Power BI gateway.
In any case, just update the box and reboot it afterwards (I'm assuming you have a maintenance window for the update anyway), I'm fairly sure you can stop those 4 services during the update.
answered 1 hour ago
Tom V
13.3k74373
add a comment |Â
up vote
5
down vote
None of the services in your screenshot have anything to do with VMWare.
The one you highlighted is Wmiprvse.exe which is basically WMI
WMI resides in a shared service host with several other services. To avoid stopping all the services when a provider fails, providers are loaded into a separate host process named "Wmiprvse.exe".
The other ones are
SSISTELEMETRYis basically the customer improvement service
Windows Agent Service is probably something for NetIQ.
PBIEgwService is an on-prem Power BI gateway.
In any case, just update the box and reboot it afterwards (I'm assuming you have a maintenance window for the update anyway), I'm fairly sure you can stop those 4 services during the update.
answered 1 hour ago
Tom V
13.3k74373
add a comment |Â
up vote
5
down vote
up vote
5
down vote
None of the services in your screenshot have anything to do with VMWare.
The one you highlighted is Wmiprvse.exe which is basically WMI
WMI resides in a shared service host with several other services. To avoid stopping all the services when a provider fails, providers are loaded into a separate host process named "Wmiprvse.exe".
The other ones are
SSISTELEMETRYis basically the customer improvement service
Windows Agent Service is probably something for NetIQ.
PBIEgwService is an on-prem Power BI gateway.
In any case, just update the box and reboot it afterwards (I'm assuming you have a maintenance window for the update anyway), I'm fairly sure you can stop those 4 services during the update.
answered 1 hour ago
Tom V
13.3k74373
None of the services in your screenshot have anything to do with VMWare.
The one you highlighted is Wmiprvse.exe which is basically WMI
WMI resides in a shared service host with several other services. To avoid stopping all the services when a provider fails, providers are loaded into a separate host process named "Wmiprvse.exe".
The other ones are
SSISTELEMETRYis basically the customer improvement service
Windows Agent Service is probably something for NetIQ.
PBIEgwService is an on-prem Power BI gateway.
In any case, just update the box and reboot it afterwards (I'm assuming you have a maintenance window for the update anyway), I'm fairly sure you can stop those 4 services during the update.
answered 1 hour ago
Tom V
13.3k74373
edited 1 hour ago
answered 1 hour ago
Tom V
13.3k74373
answered 1 hour ago
Tom V
13.3k74373
answered 1 hour ago
Tom V
13.3k74373
13.3k74373
add a comment |Â
add a comment |Â
up vote
2
down vote
The WmiPrvSE.exe belongs to the service Windows Management Instrumentation and is located in the %WINDIR%SysWOW64wbem directory.
However, when looking at the Task Manager compared to the details of the Windows Management Instrumentation service, you may notice that the service runs via the C:WINDOWSsystem32svchost.exe -k netsvcs -p process/executable.
So you will have a WmiPrvSE.exe running in the Task Manager, but the service is running via said svchost.exe process. What is the reason for this?
Explaining (Some) Windows Services
You can determine what is actually running as a service by starting the Sysinternals tool procexp.exe and looking at the details of the individual svchost.exe processes running by mousing over the various svchost.exe processes running.
It looks a bit like this:
You can then click on the details of that process and will find the following:
And if you switch to the Service tab you will find this:
...scroll a bit to the right and you are presented with:
What's Going On?
When various windows services start (and you might have noticed there are a few), they don't always start the actual <service_name>.exe, but instead a kind of shell executable, which is the svchost.exe and a corresponding *.DLL required by the service.
If the system or user actually requires a portion of that service, either by starting a program or opening up an Management Console, then the *.DLL which has been loaded by the svchost.exe process will trigger the actual executable required.
In fact during the writing of this answer the WmiPrvSE.exe started multiple times and then closed again, even though the service was always in the running state.
Answering Your Question
Is it safe to stop all the instances of this application in order to go on with the updates?
Option 1
You can safely stop the Windows Management Instrumentation service and continue with your SQL Server upgrade/installation.
However, when you stop the Windows Management Instrumentation service, you might be prompted to close other services that rely on WMI to be in a running state. Examples from my computer:
- VMware USB Arbitration Service
- IP Helper
- ...
This can reduce the probability of having to reboot after upgrading. It will not stop the installation routing from rebooting the SQL Server service (if required).
Option 2
In some cases you can wait a bit for the WmiPrvSE.exe to shut itself down and then continue with the installation. But, depending on what your server is running, this could take a while.
Option 3
Let the installation continue and reboot the server. Your SQL Server service might go down anyway.
answered 27 mins ago
hot2use
7,58941951
add a comment |Â
up vote
2
down vote
The WmiPrvSE.exe belongs to the service Windows Management Instrumentation and is located in the %WINDIR%SysWOW64wbem directory.
However, when looking at the Task Manager compared to the details of the Windows Management Instrumentation service, you may notice that the service runs via the C:WINDOWSsystem32svchost.exe -k netsvcs -p process/executable.
So you will have a WmiPrvSE.exe running in the Task Manager, but the service is running via said svchost.exe process. What is the reason for this?
Explaining (Some) Windows Services
You can determine what is actually running as a service by starting the Sysinternals tool procexp.exe and looking at the details of the individual svchost.exe processes running by mousing over the various svchost.exe processes running.
It looks a bit like this:
You can then click on the details of that process and will find the following:
And if you switch to the Service tab you will find this:
...scroll a bit to the right and you are presented with:
What's Going On?
When various windows services start (and you might have noticed there are a few), they don't always start the actual <service_name>.exe, but instead a kind of shell executable, which is the svchost.exe and a corresponding *.DLL required by the service.
If the system or user actually requires a portion of that service, either by starting a program or opening up an Management Console, then the *.DLL which has been loaded by the svchost.exe process will trigger the actual executable required.
In fact during the writing of this answer the WmiPrvSE.exe started multiple times and then closed again, even though the service was always in the running state.
Answering Your Question
Is it safe to stop all the instances of this application in order to go on with the updates?
Option 1
You can safely stop the Windows Management Instrumentation service and continue with your SQL Server upgrade/installation.
However, when you stop the Windows Management Instrumentation service, you might be prompted to close other services that rely on WMI to be in a running state. Examples from my computer:
- VMware USB Arbitration Service
- IP Helper
- ...
This can reduce the probability of having to reboot after upgrading. It will not stop the installation routing from rebooting the SQL Server service (if required).
Option 2
In some cases you can wait a bit for the WmiPrvSE.exe to shut itself down and then continue with the installation. But, depending on what your server is running, this could take a while.
Option 3
Let the installation continue and reboot the server. Your SQL Server service might go down anyway.
answered 27 mins ago
hot2use
7,58941951
add a comment |Â
up vote
2
down vote
up vote
2
down vote
The WmiPrvSE.exe belongs to the service Windows Management Instrumentation and is located in the %WINDIR%SysWOW64wbem directory.
However, when looking at the Task Manager compared to the details of the Windows Management Instrumentation service, you may notice that the service runs via the C:WINDOWSsystem32svchost.exe -k netsvcs -p process/executable.
So you will have a WmiPrvSE.exe running in the Task Manager, but the service is running via said svchost.exe process. What is the reason for this?
Explaining (Some) Windows Services
You can determine what is actually running as a service by starting the Sysinternals tool procexp.exe and looking at the details of the individual svchost.exe processes running by mousing over the various svchost.exe processes running.
It looks a bit like this:
You can then click on the details of that process and will find the following:
And if you switch to the Service tab you will find this:
...scroll a bit to the right and you are presented with:
What's Going On?
When various windows services start (and you might have noticed there are a few), they don't always start the actual <service_name>.exe, but instead a kind of shell executable, which is the svchost.exe and a corresponding *.DLL required by the service.
If the system or user actually requires a portion of that service, either by starting a program or opening up an Management Console, then the *.DLL which has been loaded by the svchost.exe process will trigger the actual executable required.
In fact during the writing of this answer the WmiPrvSE.exe started multiple times and then closed again, even though the service was always in the running state.
Answering Your Question
Is it safe to stop all the instances of this application in order to go on with the updates?
Option 1
You can safely stop the Windows Management Instrumentation service and continue with your SQL Server upgrade/installation.
However, when you stop the Windows Management Instrumentation service, you might be prompted to close other services that rely on WMI to be in a running state. Examples from my computer:
- VMware USB Arbitration Service
- IP Helper
- ...
This can reduce the probability of having to reboot after upgrading. It will not stop the installation routing from rebooting the SQL Server service (if required).
Option 2
In some cases you can wait a bit for the WmiPrvSE.exe to shut itself down and then continue with the installation. But, depending on what your server is running, this could take a while.
Option 3
Let the installation continue and reboot the server. Your SQL Server service might go down anyway.
answered 27 mins ago
hot2use
7,58941951
The WmiPrvSE.exe belongs to the service Windows Management Instrumentation and is located in the %WINDIR%SysWOW64wbem directory.
However, when looking at the Task Manager compared to the details of the Windows Management Instrumentation service, you may notice that the service runs via the C:WINDOWSsystem32svchost.exe -k netsvcs -p process/executable.
So you will have a WmiPrvSE.exe running in the Task Manager, but the service is running via said svchost.exe process. What is the reason for this?
Explaining (Some) Windows Services
You can determine what is actually running as a service by starting the Sysinternals tool procexp.exe and looking at the details of the individual svchost.exe processes running by mousing over the various svchost.exe processes running.
It looks a bit like this:
You can then click on the details of that process and will find the following:
And if you switch to the Service tab you will find this:
...scroll a bit to the right and you are presented with:
What's Going On?
When various windows services start (and you might have noticed there are a few), they don't always start the actual <service_name>.exe, but instead a kind of shell executable, which is the svchost.exe and a corresponding *.DLL required by the service.
If the system or user actually requires a portion of that service, either by starting a program or opening up an Management Console, then the *.DLL which has been loaded by the svchost.exe process will trigger the actual executable required.
In fact during the writing of this answer the WmiPrvSE.exe started multiple times and then closed again, even though the service was always in the running state.
Answering Your Question
Is it safe to stop all the instances of this application in order to go on with the updates?
Option 1
You can safely stop the Windows Management Instrumentation service and continue with your SQL Server upgrade/installation.
However, when you stop the Windows Management Instrumentation service, you might be prompted to close other services that rely on WMI to be in a running state. Examples from my computer:
- VMware USB Arbitration Service
- IP Helper
- ...
This can reduce the probability of having to reboot after upgrading. It will not stop the installation routing from rebooting the SQL Server service (if required).
Option 2
In some cases you can wait a bit for the WmiPrvSE.exe to shut itself down and then continue with the installation. But, depending on what your server is running, this could take a while.
Option 3
Let the installation continue and reboot the server. Your SQL Server service might go down anyway.
answered 27 mins ago
hot2use
7,58941951
answered 27 mins ago
hot2use
7,58941951
answered 27 mins ago
hot2use
7,58941951
answered 27 mins ago
hot2use
7,58941951
7,58941951
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f219206%2fwhen-applying-a-sql-server-cumulative-update-or-service-pack-on-a-virtual-machin%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Where do you see VMware in there?
– Tom V
2 hours ago
Simply go ahead and click next to install the patch and later just reboot the machine. I hope reboot is option here
– Shanky
2 hours ago
what this is basically telling you that these files are in use and will not be updated until you restart the server. it will not stop the upgrade
– Bob Klimes
57 mins ago