PC Doctor software underlying SupportAssist is way too intrusive. I would never trust a 3rd party app to perform some of the operations made available via SupportAssist e. I want a basic support facility that tells me when an updated driver is available.
That's pretty much it. Ideally it will give me the option to install it explicitly as does Support Assist and would never automatically install anything. If I ever have a system problem, I would like a comprehensive diagnostic that I can invoke as needed. I don't want umpteen services running all the time just to accomplish these limited functions. The new SupportAssist version now does all sorts of configuration on boot up. I want my support tools to simplify my system management, not the converse.
And I certainly do not want them to increase risk of problems. Go to Solution. I discovered the problem. The earlier versions of SupportAssist installer Support assist remdiation service as a separate package. Newer version do not not but the transition packages did a rotten job of cleaning up. If you remove Support Assist Remediation and SupportAssistant then reboot, the re-install the latest SupportAssist, the problem seems to go away - it has been a week.
View solution in original post. Proceed with caution. You are downloading trial software. Subscription auto-renews at the end of the term Learn more. Download MSIInstaller. Average User Rating. What are MSIInstaller. Some of the most common MSIInstaller. Class not registered. We are sorry for the inconvenience. Cannot find MSIInstaller. Error starting program: MSIInstaller.
The file MSIInstaller. Windows failed to start - MSIInstaller. Step 1: Restore your PC back to the latest restore point, "snapshot", or backup image before error occurred. In the search results, find and click System Restore. Follow the steps in the System Restore Wizard to choose a relevant restore point. Restore your computer to that backup image. If this Step 2 fails as well, please proceed to the Step 3 below. In the Windows Update dialog box, click " Check for Updates " or similar button depending on your Windows version If updates are available for download, click " Install Updates ".
They are indeed just warnings annoying as they are to someone watching their event logs. If you're uncomfortable with the solution, just ignore the warnings: they aren't indicative of something that needs to be fixed.
I do use and understand the least privileged model, but I am comfortable with breaking that model for the 15 minutes it takes to add the farm account as an Administrator, reboot not always necessary; but safest to do , run the "Product Version Job", and then remove the farm account from the Admistrators group. Don't forget to disable the job when your done or you'll get the event log warnings that night [by the default schedule]. Of course, it would be nice if Microsoft would come up with a resolution to the crux of the problem lol: or just get rid of the warning message altogether.
From other's research, it sounds like this may be more deeply rooted than just SharePoint, though. The issue is that users , unless the software is advertised, do not have rights to install software which is what this process is attempting to do :.
While you see the warning, the job succeeds indeed, all the way -- turn on MSI verbose logging so there is no real need to elevate your Farm Admin account to Local Admin unless you're running the UPSS Hey Trevor.
I wasn't sure which method it was failing on although I understood it was the Windows Installer Service that was getting called by the job. There are three things that are still interesting to me though:. All of this has led me to believe that there were missing permissions somewhere, probably on the file system, but I just haven't had any luck pinning that down.
One reason why I continued to pursue a solution to this is that the job doesn't actually try to install anything, it's just trying to use the Windows Installer Service to query the installed version, and the DCOM rights should be sufficient to invoke the service.
But getting much further than this has proven pretty difficult since I'm not a dev and I've kind of pushed my limited reflection skills and understanding of the Windows Installer Service to the limit. If anyone can chip in and make some progress from this point, it'd be great to join forces! At any rate, I've been taking a look at this since last night There is certainly no way to make this work securel y, as you may as well just make the Farm Admin a Local Admin if you are going to grant the necessary rights to install an MSI as a non-Administrator.
I guess I'm still not seeing that we have to grant rights to install something per se, since this job will already have rights to use the Windows Installer Service to query once we've solved the DCOM errors, right?
Or am I missing something there? I don't think we'd seriously look to solve these warnings until after solving the DCOM error, which actually stops the job from running. So the way I see it, whether we're happy with the rights to use the Windows Installer Service is a question that we should be asking when we decide whether or not to grant the DCOM rights. This is why I still assumed that there was some further permission issues for the Farm account that were triggering these warnings.
In fact, these two lines appear when you run the Farm Admin as Local Administrator:. MSI c []: Cloaking enabled. MSI c []: Attempting to enable all disabled privileges before calling Install on Server. So in that case do you reckon the Product Version Job doesn't actually work properly in terms of actually detecting the state of the installed components on a server without administrative rights? And if so, what does granting the DCOM rights actually accomplish other than removing the errors?
And it still isn't clear to me why the FIM Product Version job can succeed without admin rights when this one fails if this is all about the Windows Installer rights rather than the job itself. I must be missing something really obvious. I have come to the same conclusion. I also only add the Farm account to the Local Administrators group when needed - i.
This eliminates the errors in the Event Log. For normal daily operations, I also create a custom view for Admintrator Events that filters out the Event IDs rather than disable the Product Version Job in the SharePoint Health Analyzer - just a personal preference so I don't have to remember to re-enable the job, and I can still see any real errors without the warnings cluttering the view. I also only add the Farm account to the Local Administrators group.
Created it and followed the instructions, but it doesn't resolve the problem. I've been getting the and events since the beginning of my installation and am still seeing them. Has anyone had an official fix from Microsoft? I'm leaning towards using the workaround that Paul E suggested, but just wanted to see if there are any updates. So this is what I discovered with this problem.
Add the Farm account to the local Admin group on the server. Then restart the timer service. Now pull the Farm account out of the local Admin group.
Run the Product Version Job manually and you will notice that the Warning is now gone. Apparently, the Farm credentials are cached from the local Admin group and will eliminate the warning as well as the DCOM errors. This method will work until the server is re-booted or the Timer service is restarted again. This process works for me until Microsoft can permanaetly fix this issue.
I only use one account to act as the Farm service account and create separate accounts for each farm that I run. I pull the Farm account from the local Admin group after I restart the timer service. This allows the Product Version job to run without any error's and also allows me to not have to disable this job to run manually. I did set the schedule for this job to run weekly instead of nightly. I also disabled the Timer Recycle job as this would clear the Farm account from the timer service.
Looks like SP-Jim's been able to get the Product Version job to work without rebooting the machine and, instead, restarting the timer service. That's good news. I would highly recommend restarting the timer service after the job has ran and the Farm account has been removed from the Administrators group.
Otherwise, what's to stop other timer jobs from using this elevation of priviledge to do something they shouldn't? Without restarting the timer service, the Farm account's admin rights still linger in the service and could be used by other timer jobs.
By "function correctly", you mean function without producing the event log errors? From your previous comments in this thread on MSI verbose logging , I gather that the 'Product Version Job' does function correctly even if the farm account is not a local admin, and the error messages in the log are simply cosmetic and can be ignored. This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
We were experiencing this issue on 4 of 8 servers in our farm 2 dedicated BI and 2 dedicated Secure Store. Error: 0x" error would not appear in the logs. But every night, after the farm's automatic cleanup IIS reset, warm-up scripts the error would re-appear.
After several attempts at this and other fixes, I added the Farm service account to the local admin group, restarted the SharePoint Timer Service twice , and removed the Farm Service account from the local admin group. For whatever reason, the second time I stopped and started the service it took longer. I manually ran the Product Version Job and, like before, the error didn't appear right away. However, I fully expected the error to re-appear after the daily cleanup jobs, but it didn't.
So far, the error hasn't re-appeared and I believe the second restart of the SharePoint Timer Service was the key to getting the linked TechNet Wiki solution to work. Office Office Exchange Server. Not an IT pro? Sign in. United States English. Ask a question. Quick access.
Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Tuesday, July 27, AM. It's finally passed. Cheers, Dimitri. Monday, January 3, PM. Hi, Kindly do this Method 1: 1.
0コメント