Verify that you have sufficient privileges to install system services как исправить

Hi Everyone
  • Remove From My Forums
  • Вопрос

  • Hi Everyone

    I have a msi package which I was need to be modified in a way that it will install as unprivilege user so I modified it. I took following steps

    1. Add property in Property table (MSIINSTALLPERUSER
    1)

    2. Edit ALLUSER value to 2 in property table

    3. In Registry table change Root column value to -1

    Now package can be installed as unpriviliged user and it is not calling UAC for Administrator Password but after some progress of installation eventually a pop up generate and ask for «Service
    ‘PRODUCTNAME Service’ (PRODUCTNAME Service) could not be installed. Verify that you have sufficient privileges to install system services» 
     
    I assume that it is a permission issue so I install it using administrator account but
    same pop up come again. I dont know how to rectify this problem. Please help me out of this

Ответы

  • Even if you are administrator on your system, you don’t usually run with admin privileges.

    If you run as admin or you don’t make that change you made and the package is forced to run as administrator then your problem would go away.

    It seems your requirement to be able to install as a non admin user is incompatible with the requirements of your product.

    Maybe you should reconsider this requirement.

    Seeing as it’s going to stop you installing your software at all.


    • Предложено в качестве ответа

      19 мая 2016 г. 9:15

    • Помечено в качестве ответа
      Moonlight ShengMicrosoft contingent staff
      20 мая 2016 г. 8:52

Содержание

  1. Verify that you have sufficient privileges to start system services error 1920
  2. Описание ситуации
  3. Решение проблемы
  4. Verify that you have sufficient privileges to start system services error 1920
  5. Asked by:
  6. General discussion
  7. All replies
  8. Verify that you have sufficient privileges to start system services error 1920
  9. Общие обсуждения

Verify that you have sufficient privileges to start system services error 1920

Всем привет сегодня расскажу как решается ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services при установке MegaRAID Storage Manager. напомню MegaRAID Storage Manager или как ее еще называют MSM, это утилита для мониторинга и работы с контроллерами LSI.

Описание ситуации

Есть сервер под Windows Server 2008 R2, на нем стоит RAID контроллер ServeRAID M5015 на базе LSI 9260-8i, при попытке поставить утилиту MegaRAID Storage Manager выскакивает ошибка, что не возможно запустить службу утилиты.

Как видите, что кроме отмены и повторной попытки ничего сделать не получается.

Решение проблемы

Поискав информацию на просторах интернета, было найдено несколько вариантов. В начале попробуйте во время того как у вас выскочит диалоговое окно с кнопкой Retry, откройте командную строку от имени администратора и попробуйте в ручную запустить службу MSMFramework. Если все ок, то установка MSM продолжиться, если нет то вы получите ошибку

запуск службы MSMFramework

Это уже небольшая победа так как мы выяснили, что запуск службы MSMFramework не возможен по причине, того что есть дополнительный сервис который не работает.

Так же более детальный лог установки утилиты LSI можно посмотреть в файле MSM_install, лежит он в той же папке где и дистрибутив установщика.

Вот небольшая выдержка из этого файла

Зайдем в Администрирование-Службы

тут нам необходимо определить какие зависимые службы у MSMFramework. Выбираем службу MegaRAID Storage Manager, щелкаем правым кликом и переходим в Зависимости. Видим, что для работы необходима работающая служба Инструментарий управления Windows.

зависимые службы у MSMFramework

Запустив Инструментарий управления Windows ваша установка MSM продолжится в штатном режиме.

Вот так вот просто решается ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start. Спасибо за внимание. Если у вас есть вопрос, то задавайте их в комментариях.

Источник

Verify that you have sufficient privileges to start system services error 1920

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

I am getting Error 1920. Service Email Poller (Email Poller) failed to start. Verify that you have sufficient privilege to start system services while installing a web application.

I know for sure that I have sufficient privilege to start the services. In fact, I was able to install a week ago, but decide to remove it. When I try to install again, I keep getting Error 1920, any idea in resolving this issue please? I am suspecting a registry issue or while uninstalling there could be remnant from the uninstalling? Please help

I did some checking in

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices and I removed it

From my experience, you can follow the methods:
1. Run the installer as Administrator.
2. Turn off the firewalls.

Please let me know if this helps or not.
Aland Li Please mark the replies as answers if they help and unmark if they don’t. This can be beneficial to other community members reading the thread.

We are changing the issue type to “General Discussion” because you have not followed up with the necessary information. If you have more time to look at the issue and provide more information, please feel free to change the issue type back to “Question” by opening the Options list at the top of the post window, and changing the type. If the issue is resolved, we will appreciate it if you can share the solution so that the answer can be found and used by other community members having similar questions.

Please mark the replies as answers if they help and unmark if they don’t. This can be beneficial to other community members reading the thread.

Источник

Verify that you have sufficient privileges to start system services error 1920

Общие обсуждения

Столкнулся с проблемой установки windows servise, на серверах Windows 2012 R2. Суть проблемы, есть два десятка однотипных серверов Windows 2012 R2, на которые периодически средствами SCCM 2012 R2 происходит установка виндовс сервисов. Установка может пройти успешно на всех серверах, а периодически на нескольких серверах при выходе новой версии сервиса возникает ошибка установки, (— Error 1920. Service ‘WinSvc_V3’ (WinSvc_V3) failed to start. Verify that you have sufficient privileges to start system services.), если после, выполнить установку вручную msi пакета, установка проходит успешно. В журнале событий есть ошибки, но они таки еже как и в логе установки msi, с кодом 1920.

У меня есть подозрение что сервис не может запуститься из за ошибки при первом старте, либо долго запускается, а установщик думает что он не рабочий, как имея лог установки сервиса можно выяснить истинную причину ошибки.

Ниже привожу лог:

Action start 16:49:34: InstallFinalize.
MSI (s) (FC:E0) [16:49:34:593]: Executing op: ProductInfo(ProductKey=,ProductName=MegaWinSvc_MoneyRus_V3,PackageName=MegaWinSvc_MoneyRus_V3.msi,Language=1033,Version=50528379,Assignment=1,ObsoleteArg=0. PackageCode=<15a6a973-3509-474a-a0ab-d6638b14d67b>. InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=1)
MSI (s) (FC:E0) [16:49:34:594]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (FC:E0) [16:49:34:594]: Executing op: DialogInfo(Type=1,Argument=MegaWinSvc_MoneyRus_V3)
MSI (s) (FC:E0) [16:49:34:595]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (FC:E0) [16:49:34:595]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (FC:E0) [16:49:34:595]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (FC:E0) [16:49:34:595]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,)
MSI (s) (FC:E0) [16:49:34:595]: Executing op: ProgressTotal(Total=9,Type=1,ByteEquivalent=24000)
MSI (s) (FC:E0) [16:49:34:595]: Executing op: ComponentRegister(ComponentId=,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:598]: Executing op: ComponentRegister(ComponentId=<3896b1b4-65d6-4dd5-9ab8-53d3cf3178b1>,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaWinSvc_MoneyRus_V3.exe,State=3,,Disk=1,SharedDllRefCount=1,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:599]: WIN64DUALFOLDERS: Substitution in ‘C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaWinSvc_MoneyRus_V3.exe’ folder had been blocked by the 1 mask argument (the folder pair’s iSwapAttrib member = 0).
MSI (s) (FC:E0) [16:49:34:599]: WIN64DUALFOLDERS: Substitution in ‘C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaWinSvc_MoneyRus_V3.exe’ folder had been blocked by the 1 mask argument (the folder pair’s iSwapAttrib member = 0).
MSI (s) (FC:E0) [16:49:34:600]: Executing op: ComponentRegister(ComponentId=,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:602]: Executing op: ComponentRegister(ComponentId=,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:603]: Executing op: ComponentRegister(ComponentId=<9bacefe9-9534-e831-f861-21724982b4e5>,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:604]: Executing op: ComponentRegister(ComponentId=<42de044f-0300-4478-9491-8d09559bb36d>,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:607]: Executing op: ComponentRegister(ComponentId=<95a34f16-6f60-607c-47cc-2823061c29dd>,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:608]: Executing op: ComponentRegister(ComponentId=,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:609]: Executing op: ComponentRegister(ComponentId=<69071530-6cb4-4ca2-9416-d61bbdb67327>,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3Log,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:610]: Executing op: ComponentRegister(ComponentId=<69071530-6cb4-4ca2-9416-d61bbdb67327>,KeyPath=C:Program Files (x86)MegaWinSvc_MoneyRus_V3Log,State=3,ProductKey=<00000000-0000-0000-0000-000000000000>,Disk=1,SharedDllRefCount=0,BinaryType=0)
MSI (s) (FC:E0) [16:49:34:610]: Executing op: ActionStart(Name=StopServices,Description=Stopping services,Template=Service: [1])
MSI (s) (FC:E0) [16:49:34:611]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (FC:E0) [16:49:34:611]: Executing op: ServiceControl(,Name=MegaWinSvc_MoneyRus_V3,Action=2,Wait=1,)
MSI (s) (FC:E0) [16:49:34:613]: Executing op: ActionStart(Name=CreateFolders,Description=Creating folders,Template=Folder: [1])
MSI (s) (FC:E0) [16:49:34:614]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:614]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:615]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:615]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:616]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:616]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:616]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3,Foreign=0,,)
MSI (s) (FC:E0) [16:49:34:617]: Executing op: FolderCreate(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3Log,Foreign=0,SecurityDescriptor=BinaryData,)
MSI (s) (FC:E0) [16:49:34:618]: Executing op: ActionStart(Name=InstallFiles,Description=Copying new files,Template=File: [1], Directory: [9], Size: [6])
MSI (s) (FC:E0) [16:49:34:618]: Executing op: ProgressTotal(Total=6954234,Type=0,ByteEquivalent=1)
MSI (s) (FC:E0) [16:49:34:619]: Executing op: SetTargetFolder(Folder=C:Program Files (x86)MegaWinSvc_MoneyRus_V3)
MSI (s) (FC:E0) [16:49:34:619]: Executing op: SetSourceFolder(Folder=1w7dlqbn5|MegaWinSvc_MoneyRus_V3)
MSI (s) (FC:E0) [16:49:34:619]: Executing op: ChangeMedia(,MediaPrompt=Please insert the disk: ,MediaCabinet=Main.cab,BytesPerTick=65536,CopierType=2,ModuleFileName=C:WINDOWSInstaller859c9941.msi. IsFirstPhysicalMedia=1)
MSI (s) (FC:E0) [16:49:34:619]: Executing op: FileCopy(SourceName=rc0ymxcs.dll|deploy.user.dll,SourceCabKey=deploy.user.dll,DestName=deploy.user.dll,Attributes=16384,FileSize=14,PerTick=65536,,VerifyMedia=1. CheckCRC=0. InstallMode=58982400,HashOptions=0,HashPart1=-1161824164,HashPart2=-77832926,HashPart3=282098485,HashPart4=294170731,,)
MSI (s) (FC:E0) [16:49:34:619]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3deploy.user.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:620]: Source for file ‘deploy.user.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:627]: Executing op: FileCopy(SourceName=pv2o0dq7.dll|FirebirdSql.Data.FirebirdClient.dll,SourceCabKey=firebirdsql.data.firebirdclient.dll,DestName=FirebirdSql.Data.FirebirdClient.dll,Attributes=16384,FileSize=702464,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=4.2.0.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:627]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3FirebirdSql.Data.FirebirdClient.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:627]: Source for file ‘firebirdsql.data.firebirdclient.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:638]: Executing op: FileCopy(SourceName=lsw2kbip.dll|GlobalSpirits.ServiceModel.WcfIisHost.dll,SourceCabKey=globalSpirits.serviceModel.wcfIishost.dll,DestName=GlobalSpirits.ServiceModel.WcfIisHost.dll,Attributes=16384,FileSize=12800,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=0.1.3.2,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:638]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3GlobalSpirits.ServiceModel.WcfIisHost.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:638]: Source for file ‘globalSpirits.serviceModel.wcfIishost.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:641]: Executing op: FileCopy(SourceName=frrbgxjy.dll|MegaDAL_Money_V3.dll,SourceCabKey=megadal_money_v3.dll,DestName=MegaDAL_Money_V3.dll,Attributes=16384,FileSize=5630066,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=3.3.123.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:641]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaDAL_Money_V3.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:641]: Source for file ‘megadal_money_v3.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:726]: Executing op: FileCopy(SourceName=4rfwcwtw.dll|MegaDAL_Money_V3.XmlSerializers.dll,SourceCabKey=MegaDAL_Money_V3.XmlSerializers.dll,DestName=MegaDAL_Money_V3.XmlSerializers.dll,Attributes=16384,FileSize=136704,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=3.3.123.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:727]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaDAL_Money_V3.XmlSerializers.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:727]: Source for file ‘MegaDAL_Money_V3.XmlSerializers.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:731]: Executing op: FileCopy(SourceName=apbmtiz8.dll|MegaDAL_MoneyRus_V3.dll,SourceCabKey=MegaDAL_MoneyRus_V3.dll,DestName=MegaDAL_MoneyRus_V3.dll,Attributes=16384,FileSize=54395,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=3.3.123.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:732]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaDAL_MoneyRus_V3.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:732]: Source for file ‘MegaDAL_MoneyRus_V3.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:736]: Executing op: FileCopy(SourceName=9x_x1_jm.dll|MegaPostSharpUtils_V3.dll,SourceCabKey=megapostsharputils_V3.dll,DestName=MegaPostSharpUtils_V3.dll,Attributes=16384,FileSize=21099,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=1.0.0.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:736]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaPostSharpUtils_V3.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:736]: Source for file ‘megapostsharputils_V3.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:738]: Executing op: FileCopy(SourceName=z7j1zqms.dll|MegaUtils_V3.dll,SourceCabKey=megautils_v3.dll,DestName=MegaUtils_V3.dll,Attributes=16384,FileSize=182784,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=1.0.2.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:738]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaUtils_V3.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:738]: Source for file ‘megautils_v3.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:742]: Executing op: FileCopy(SourceName=g5bmbuwx.exe|MegaWinSvc_MoneyRus_V3.exe,SourceCabKey=MegaWinSvc_MoneyRus_V3.exe,DestName=MegaWinSvc_MoneyRus_V3.exe,Attributes=16384,FileSize=9857,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=3.3.123.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:743]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaWinSvc_MoneyRus_V3.exe; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:743]: Source for file ‘MegaWinSvc_MoneyRus_V3.exe’ is compressed
MSI (s) (FC:E0) [16:49:34:744]: Executing op: FileCopy(SourceName=fmgs0vlu.con|MegaWinSvc_MoneyRus_V3.exe.config,SourceCabKey=MegaWinSvc_MoneyRus_V3.exe.config,DestName=MegaWinSvc_MoneyRus_V3.exe.config,Attributes=16384,FileSize=2611,PerTick=65536,,VerifyMedia=1. CheckCRC=0. InstallMode=58982400,HashOptions=0,HashPart1=-672353352,HashPart2=1702369711,HashPart3=83781760,HashPart4=-318990276,,)
MSI (s) (FC:E0) [16:49:34:744]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaWinSvc_MoneyRus_V3.exe.config; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:744]: Source for file ‘MegaWinSvc_MoneyRus_V3.exe.config’ is compressed
MSI (s) (FC:E0) [16:49:34:746]: Executing op: FileCopy(SourceName=kywn7xyb.dll|PostSharp.dll,SourceCabKey=postsharp.dll,DestName=PostSharp.dll,Attributes=16384,FileSize=201440,PerTick=65536,,VerifyMedia=1. CheckCRC=0,Version=3.1.48.0,Language=0,InstallMode=58982400. )
MSI (s) (FC:E0) [16:49:34:746]: File: C:Program Files (x86)MegaWinSvc_MoneyRus_V3PostSharp.dll; To be installed; Won’t patch; No existing file
MSI (s) (FC:E0) [16:49:34:746]: Source for file ‘postsharp.dll’ is compressed
MSI (s) (FC:E0) [16:49:34:750]: Executing op: CacheSizeFlush(,)
MSI (s) (FC:E0) [16:49:34:750]: Executing op: ActionStart(Name=InstallServices,Description=Installing new services,Template=Service: [2])
MSI (s) (FC:E0) [16:49:34:753]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (FC:E0) [16:49:34:753]: Executing op: ServiceInstall(Name=MegaWinSvc_MoneyRus_V3,DisplayName=MegaWinSvc_MoneyRus_V3,ImagePath=»C:Program Files (x86)MegaWinSvc_MoneyRus_V3MegaWinSvc_MoneyRus_V3.exe»,ServiceType=16,StartType=2,ErrorControl=1,,Dependencies=[

]. Password=**********,Description=MegaWinSvc_MoneyRus_V3,,)
MSI (s) (FC:E0) [16:49:34:763]: Note: 1: 2205 2: 3: Error
MSI (s) (FC:E0) [16:49:34:763]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1923
Error 1923. Service ‘MegaWinSvc_MoneyRus_V3’ (MegaWinSvc_MoneyRus_V3) could not be installed. Verify that you have sufficient privileges to install system services.
MSI (s) (FC:E0) [16:49:34:764]: Note: 1: 2205 2: 3: Error
MSI (s) (FC:E0) [16:49:34:764]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (FC:E0) [16:49:34:764]: Product: MegaWinSvc_MoneyRus_V3 — Error 1923. Service ‘MegaWinSvc_MoneyRus_V3’ (MegaWinSvc_MoneyRus_V3) could not be installed. Verify that you have sufficient privileges to install system services.

MSI (s) (FC:E0) [16:49:34:767]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
MSI (s) (FC:E0) [16:49:34:769]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (FC:E0) [16:49:34:769]: Executing op: ServiceControl(,Name=MegaWinSvc_MoneyRus_V3,Action=1,Wait=1,)
MSI (s) (FC:E0) [16:50:04:790]: Note: 1: 2205 2: 3: Error
MSI (s) (FC:E0) [16:50:04:790]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1920
Error 1920. Service ‘MegaWinSvc_MoneyRus_V3’ (MegaWinSvc_MoneyRus_V3) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (FC:E0) [16:50:04:793]: Note: 1: 2205 2: 3: Error
MSI (s) (FC:E0) [16:50:04:793]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (FC:E0) [16:50:04:793]: Product: MegaWinSvc_MoneyRus_V3 — Error 1920. Service ‘MegaWinSvc_MoneyRus_V3’ (MegaWinSvc_MoneyRus_V3) failed to start. Verify that you have sufficient privileges to start system services

Источник

Обновлено 15.05.2016

Ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services

Всем привет сегодня расскажу как решается ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start.  Verify that you have sufficient privileges to start system services при установке MegaRAID Storage Manager. напомню MegaRAID Storage Manager или как ее еще называют MSM, это утилита для мониторинга и работы с контроллерами LSI.

Описание ситуации

Есть сервер под Windows Server 2008 R2, на нем стоит RAID контроллер ServeRAID M5015 на базе LSI 9260-8i, при попытке поставить утилиту MegaRAID Storage Manager выскакивает ошибка, что не возможно запустить службу утилиты.

Error 1920.Service MSMFramework (MSMFramework) failed to start.  Verify that you have sufficient privileges to start system services

Error 1920.Service MSMFramework (MSMFramework) failed to start-01

Установка MSM

Как видите, что кроме отмены и повторной попытки ничего сделать не получается.

Решение проблемы

Поискав информацию на просторах интернета, было найдено несколько вариантов. В начале попробуйте во время того как у вас выскочит диалоговое окно с кнопкой Retry, откройте командную строку от имени администратора и попробуйте в ручную запустить службу MSMFramework. Если все ок, то установка MSM продолжиться, если нет то вы получите ошибку

Error 1920.Service MSMFramework failed to start-02

запуск службы MSMFramework

Это уже небольшая победа так как мы выяснили, что запуск службы MSMFramework не возможен по причине, того что есть дополнительный сервис который не работает.

Так же более детальный лог установки утилиты LSI можно посмотреть в файле MSM_install, лежит он в той же папке где и дистрибутив установщика.

Error 1920.Service MSMFramework failed to start-03

Вот небольшая выдержка из этого файла

Info 2835.The control ErrorIcon was not found on dialog SetupError.
Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1288788 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1296368 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1300576 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1267836 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1265760 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1300736 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1287160 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1299780 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1292168 could not be cancelled. Error: 1168
MSI (s) (90:00) [12:12:26:203]: Product: MegaRAID Storage Manager — Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services.

Error 1920.Service MSMFramework failed to start-04

лог ошибки

Зайдем в Администрирование-Службы

Error 1920.Service MSMFramework failed to start-05

тут нам необходимо определить какие зависимые службы у MSMFramework. Выбираем службу MegaRAID Storage Manager, щелкаем правым кликом и переходим в Зависимости. Видим, что для работы необходима работающая служба Инструментарий управления Windows.

зависимые службы у MSMFramework

зависимые службы у MSMFramework

Запустив Инструментарий управления Windows ваша установка MSM продолжится в штатном режиме.

Error 1920.Service MSMFramework failed to start

Вот так вот просто решается ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start. Спасибо за внимание. Если у вас есть вопрос, то задавайте их в комментариях.

Материал сайта pyatilistnik.org

  • Remove From My Forums
  • Question

  • Hi Everyone

    I have a msi package which I was need to be modified in a way that it will install as unprivilege user so I modified it. I took following steps

    1. Add property in Property table (MSIINSTALLPERUSER
    1)

    2. Edit ALLUSER value to 2 in property table

    3. In Registry table change Root column value to -1

    Now package can be installed as unpriviliged user and it is not calling UAC for Administrator Password but after some progress of installation eventually a pop up generate and ask for «Service
    ‘PRODUCTNAME Service’ (PRODUCTNAME Service) could not be installed. Verify that you have sufficient privileges to install system services» 
     
    I assume that it is a permission issue so I install it using administrator account but
    same pop up come again. I dont know how to rectify this problem. Please help me out of this

Answers

  • Even if you are administrator on your system, you don’t usually run with admin privileges.

    If you run as admin or you don’t make that change you made and the package is forced to run as administrator then your problem would go away.

    It seems your requirement to be able to install as a non admin user is incompatible with the requirements of your product.

    Maybe you should reconsider this requirement.

    Seeing as it’s going to stop you installing your software at all.


    • Proposed as answer by

      Thursday, May 19, 2016 9:15 AM

    • Marked as answer by
      Moonlight ShengMicrosoft contingent staff
      Friday, May 20, 2016 8:52 AM

  • Remove From My Forums
  • Question

  • Hi Everyone

    I have a msi package which I was need to be modified in a way that it will install as unprivilege user so I modified it. I took following steps

    1. Add property in Property table (MSIINSTALLPERUSER
    1)

    2. Edit ALLUSER value to 2 in property table

    3. In Registry table change Root column value to -1

    Now package can be installed as unpriviliged user and it is not calling UAC for Administrator Password but after some progress of installation eventually a pop up generate and ask for «Service
    ‘PRODUCTNAME Service’ (PRODUCTNAME Service) could not be installed. Verify that you have sufficient privileges to install system services» 
     
    I assume that it is a permission issue so I install it using administrator account but
    same pop up come again. I dont know how to rectify this problem. Please help me out of this

Answers

  • Even if you are administrator on your system, you don’t usually run with admin privileges.

    If you run as admin or you don’t make that change you made and the package is forced to run as administrator then your problem would go away.

    It seems your requirement to be able to install as a non admin user is incompatible with the requirements of your product.

    Maybe you should reconsider this requirement.

    Seeing as it’s going to stop you installing your software at all.


    • Proposed as answer by

      Thursday, May 19, 2016 9:15 AM

    • Marked as answer by
      Moonlight ShengMicrosoft contingent staff
      Friday, May 20, 2016 8:52 AM

  • Hi tronixmart, the problem is not a bad key. . .

    First of all, if you are using Win 7 Home Premium (as I am), Home Basic, or Starter, you will not have a Local Users and Groups option. It is only for Win 7 Ultimate, Professional, or Enterprise.

    Jennifer Zhan’s second suggestion regarding the changing of ‘This account’ to ‘Local system account’ under the «Log on» tab in the properties window of Office Software Protection Platform is better, but still not adequate. If you try this, as I
    did, and then manually start Office Software Protection Platform before continuing the Office 2010 installation from the point of error, you will receive a new surprise. The Error 1920 message goes away, but then it is replaced with an oh-so-descriptive dialogue
    box telling you that «Microsoft Office 2010 installation encountered an error.» Nice.

    Changing ‘This account’ to ‘Local system account’ is useless, because after the error described above, the system somehow reverts the log on selection for Office Software Protection Platform back to ‘This account,’ with ‘Network service’ selected by default.

    The better solution is to give the user account called ‘Network service’ full permissions for the appropriate folders and registry entries. Simply follow these instructions I found on another forum:

    In Windows Explorer:

    Right Click  on the folder OfficeSoftwareProtection Platform
    from C:Program FilesCommon FilesMicrosoft Shared and Microsoft from
    C:Program data(hidden folder) Properties > Security > Edit > Add > Type Network Service > OK > Check the Full control box > Apply and OK.

    In Registry Editor (regedit.exe):

    Go to HKEY_CLASSES_ROOTAppID registry >Right Click on the folder > Permissions > Add > TypeNETWORK SERVICE >  OK > Check Full Control > Apply > OK

    This worked for me and many others with the same problem, and took mere minutes to do.

    • Marked as answer by

      Thursday, November 18, 2010 7:14 AM

  • Понравилась статья? Поделить с друзьями:
  • Viber status custom error
  • Viber opengl error
  • Viber loadlibrary failed with error 87 параметр задан неверно
  • Viber error 2318
  • Viber error 2203