1247 réponses à ce sujet

[spiersdisarster]

Rob Bartel wrote...

Regarding the Admin problem, I've had another user reporting success with the following:

"Hi, i'm running Vista x64. I tried your fix, but it didn't work. You were right, that it is a winmgmt problem as in computer properties i had unavailible information for cpu and memory.

In my case your fix didn't work because the winmgmt service was disabled. I ran msconfig and enabled it. Then started winmgmt from comand promt. Than It worked. Hope this will help others."

nah mate this didnt work for me jsutpops up with the admin error again..( plus i can still see my system specs)

[Surimaya]

I also have the administrator error (Win7 Ultimate 64), can can see all my specs on the system screen.  I also have/had the configuration utility problem (I had it with DA origins too, but just used the workaround of skipping the config screen).

[never03]

tried all of this, nothing happens, still got the admin issue
disappointment

[chris2c2]

Ok I ran the WMI tool suggested earlier by Rob, and this is what I got. Apologies for the block of text.

31915 00:47:01 (0) ** WMIDiag v2.0 started on Saturday, March 12, 2011 at 00:42.
31916 00:47:01 (0) **
31917 00:47:01 (0) ** Copyright © Microsoft Corporation. All rights reserved - January 2007.
31918 00:47:01 (0) **
31919 00:47:01 (0) ** This script is not supported under any Microsoft standard support program or service.
31920 00:47:01 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
31921 00:47:01 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
31922 00:47:01 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
31923 00:47:01 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
31924 00:47:01 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
31925 00:47:01 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
31926 00:47:01 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
31927 00:47:01 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
31928 00:47:01 (0) ** of the possibility of such damages.
31929 00:47:01 (0) **
31930 00:47:01 (0) **
31931 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31932 00:47:01 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
31933 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31934 00:47:01 (0) **
31935 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31936 00:47:01 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'HOME\\OWNER' on computer 'HOME'.
31937 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31938 00:47:01 (0) ** Environment: ........................................................................................................ OK..
31939 00:47:01 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
31940 00:47:01 (0) ** Drive type: ......................................................................................................... IDE (ST3320620AS).
31941 00:47:01 (0) ** There are no missing WMI system files: .............................................................................. OK.
31942 00:47:01 (0) ** There are no missing WMI repository files: .......................................................................... OK.
31943 00:47:01 (0) ** WMI repository state: ............................................................................................... N/A.
31944 00:47:01 (0) ** BEFORE running WMIDiag:
31945 00:47:01 (0) ** The WMI repository has a size of: ................................................................................... 21 MB.
31946 00:47:01 (0) ** - Disk free space on 'C:': .......................................................................................... 15249 MB.
31947 00:47:01 (0) ** - INDEX.BTR, 1507328 bytes, 3/11/2011 6:05:28 PM
31948 00:47:01 (0) ** - INDEX.MAP, 768 bytes, 3/11/2011 6:05:28 PM
31949 00:47:01 (0) ** - OBJECTS.DATA, 20209664 bytes, 3/11/2011 6:05:28 PM
31950 00:47:01 (0) ** - OBJECTS.MAP, 9908 bytes, 3/11/2011 6:05:28 PM
31951 00:47:01 (0) ** AFTER running WMIDiag:
31952 00:47:01 (0) ** The WMI repository has a size of: ................................................................................... 21 MB.
31953 00:47:01 (0) ** - Disk free space on 'C:': .......................................................................................... 15243 MB.
31954 00:47:01 (0) ** - INDEX.BTR, 1507328 bytes, 3/11/2011 6:05:28 PM
31955 00:47:01 (0) ** - INDEX.MAP, 768 bytes, 3/11/2011 6:05:28 PM
31956 00:47:01 (0) ** - OBJECTS.DATA, 20209664 bytes, 3/11/2011 6:05:28 PM
31957 00:47:01 (0) ** - OBJECTS.MAP, 9908 bytes, 3/11/2011 6:05:28 PM
31958 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31959 00:47:01 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
31960 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31961 00:47:01 (0) ** DCOM Status: ........................................................................................................ OK.
31962 00:47:01 (0) ** WMI registry setup: ................................................................................................. OK.
31963 00:47:01 (0) ** WMI Service has no dependents: ...................................................................................... OK.
31964 00:47:01 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
31965 00:47:01 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
31966 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31967 00:47:01 (0) ** WMI service DCOM setup: ............................................................................................. OK.
31968 00:47:01 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
31969 00:47:01 (0) ** - C:\\WINDOWS\\SYSTEM32\\WBEM\\FASTPROX.DLL (\\CLSID\\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\\InProcServer32)
31970 00:47:01 (0) ** - C:\\WINDOWS\\SYSTEM32\\WBEM\\FASTPROX.DLL (\\CLSID\\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\\InProcServer32)
31971 00:47:01 (0) ** - C:\\WINDOWS\\SYSTEM32\\WBEM\\FASTPROX.DLL (\\CLSID\\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\\InProcServer32)
31972 00:47:01 (0) ** - C:\\WINDOWS\\SYSTEM32\\WBEM\\WBEMPROX.DLL (\\CLSID\\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\\InProcServer32)
31973 00:47:01 (0) ** - C:\\WINDOWS\\SYSTEM32\\WBEM\\WBEMPROX.DLL (\\CLSID\\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\\InProcServer32)
31974 00:47:01 (0) ** - C:\\WINDOWS\\SYSTEM32\\WBEM\\WBEMPROX.DLL (\\CLSID\\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\\InProcServer32)
31975 00:47:01 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
31976 00:47:01 (0) ** fail depending on the operation requested.
31977 00:47:01 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
31978 00:47:01 (0) **
31979 00:47:01 (0) ** WMI ProgID registrations: ........................................................................................... OK.
31980 00:47:01 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
31981 00:47:01 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
31982 00:47:01 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
31983 00:47:01 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
31984 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
31985 00:47:01 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
31986 00:47:01 (1) !! ERROR: Default trustee 'BUILTIN\\ADMINISTRATORS' has been REMOVED!
31987 00:47:01 (0) ** - REMOVED ACE:
31988 00:47:01 (0) ** ACEType: &h0
31989 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
31990 00:47:01 (0) ** ACEFlags: &h0
31991 00:47:01 (0) ** ACEMask: &h1
31992 00:47:01 (0) ** DCOM_RIGHT_EXECUTE
31993 00:47:01 (0) **
31994 00:47:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
31995 00:47:01 (0) ** Removing default security will cause some operations to fail!
31996 00:47:01 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
31997 00:47:01 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
31998 00:47:01 (0) **
31999 00:47:01 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
32000 00:47:01 (1) !! ERROR: Default trustee 'NT AUTHORITY\\INTERACTIVE' has been REMOVED!
32001 00:47:01 (0) ** - REMOVED ACE:
32002 00:47:01 (0) ** ACEType: &h0
32003 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32004 00:47:01 (0) ** ACEFlags: &h0
32005 00:47:01 (0) ** ACEMask: &h1
32006 00:47:01 (0) ** DCOM_RIGHT_EXECUTE
32007 00:47:01 (0) **
32008 00:47:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
32009 00:47:01 (0) ** Removing default security will cause some operations to fail!
32010 00:47:01 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
32011 00:47:01 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
32012 00:47:01 (0) **
32013 00:47:01 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
32014 00:47:01 (1) !! ERROR: Default trustee 'NT AUTHORITY\\SYSTEM' has been REMOVED!
32015 00:47:01 (0) ** - REMOVED ACE:
32016 00:47:01 (0) ** ACEType: &h0
32017 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32018 00:47:01 (0) ** ACEFlags: &h0
32019 00:47:01 (0) ** ACEMask: &h1
32020 00:47:01 (0) ** DCOM_RIGHT_EXECUTE
32021 00:47:01 (0) **
32022 00:47:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
32023 00:47:01 (0) ** Removing default security will cause some operations to fail!
32024 00:47:01 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
32025 00:47:01 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
32026 00:47:01 (0) **
32027 00:47:01 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
32028 00:47:01 (1) !! ERROR: Actual trustee 'NT AUTHORITY\\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
32029 00:47:01 (0) ** - ACTUAL ACE:
32030 00:47:01 (0) ** ACEType: &h0
32031 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32032 00:47:01 (0) ** ACEFlags: &h2
32033 00:47:01 (0) ** CONTAINER_INHERIT_ACE
32034 00:47:01 (0) ** ACEMask: &h1
32035 00:47:01 (0) ** WBEM_ENABLE
32036 00:47:01 (0) ** - EXPECTED ACE:
32037 00:47:01 (0) ** ACEType: &h0
32038 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32039 00:47:01 (0) ** ACEFlags: &h12
32040 00:47:01 (0) ** CONTAINER_INHERIT_ACE
32041 00:47:01 (0) ** INHERITED_ACE
32042 00:47:01 (0) ** ACEMask: &h13
32043 00:47:01 (0) ** WBEM_ENABLE
32044 00:47:01 (0) ** WBEM_METHOD_EXECUTE
32045 00:47:01 (0) ** WBEM_WRITE_PROVIDER
32046 00:47:01 (0) **
32047 00:47:01 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
32048 00:47:01 (0) ** This will cause some operations to fail!
32049 00:47:01 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
32050 00:47:01 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
32051 00:47:01 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
32052 00:47:01 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
32053 00:47:01 (0) ** A specific WMI application can always require a security setup different
32054 00:47:01 (0) ** than the WMI security defaults.
32055 00:47:01 (0) **
32056 00:47:01 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
32057 00:47:01 (1) !! ERROR: Actual trustee 'NT AUTHORITY\\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
32058 00:47:01 (0) ** - ACTUAL ACE:
32059 00:47:01 (0) ** ACEType: &h0
32060 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32061 00:47:01 (0) ** ACEFlags: &h2
32062 00:47:01 (0) ** CONTAINER_INHERIT_ACE
32063 00:47:01 (0) ** ACEMask: &h1
32064 00:47:01 (0) ** WBEM_ENABLE
32065 00:47:01 (0) ** - EXPECTED ACE:
32066 00:47:01 (0) ** ACEType: &h0
32067 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32068 00:47:01 (0) ** ACEFlags: &h12
32069 00:47:01 (0) ** CONTAINER_INHERIT_ACE
32070 00:47:01 (0) ** INHERITED_ACE
32071 00:47:01 (0) ** ACEMask: &h13
32072 00:47:01 (0) ** WBEM_ENABLE
32073 00:47:01 (0) ** WBEM_METHOD_EXECUTE
32074 00:47:01 (0) ** WBEM_WRITE_PROVIDER
32075 00:47:01 (0) **
32076 00:47:01 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
32077 00:47:01 (0) ** This will cause some operations to fail!
32078 00:47:01 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
32079 00:47:01 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
32080 00:47:01 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
32081 00:47:01 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
32082 00:47:01 (0) ** A specific WMI application can always require a security setup different
32083 00:47:01 (0) ** than the WMI security defaults.
32084 00:47:01 (0) **
32085 00:47:01 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
32086 00:47:01 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
32087 00:47:01 (0) ** - REMOVED ACE:
32088 00:47:01 (0) ** ACEType: &h0
32089 00:47:01 (0) ** ACCESS_ALLOWED_ACE_TYPE
32090 00:47:01 (0) ** ACEFlags: &h12
32091 00:47:01 (0) ** CONTAINER_INHERIT_ACE
32092 00:47:01 (0) ** INHERITED_ACE
32093 00:47:01 (0) ** ACEMask: &h13
32094 00:47:01 (0) ** WBEM_ENABLE
32095 00:47:01 (0) ** WBEM_METHOD_EXECUTE
32096 00:47:01 (0) ** WBEM_WRITE_PROVIDER
32097 00:47:01 (0) **
32098 00:47:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
32099 00:47:01 (0) ** Removing default security will cause some operations to fail!
32100 00:47:01 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
32101 00:47:01 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
32102 00:47:01 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
32103 00:47:01 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
32104 00:47:01 (0) ** A specific WMI application can always require a security setup different
32105 00:47:01 (0) ** than the WMI security defaults.
32106 00:47:01 (0) **
32107 00:47:01 (0) **
32108 00:47:01 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
32109 00:47:01 (0) ** DCOM security error(s) detected: .................................................................................... 3.
32110 00:47:01 (0) ** WMI security warning(s) detected: ................................................................................... 0.
32111 00:47:01 (0) ** WMI security error(s) detected: ..................................................................................... 3.
32112 00:47:01 (0) **
32113 00:47:01 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
32114 00:47:01 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
32115 00:47:01 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
32116 00:47:01 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
32117 00:47:01 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
32118 00:47:01 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
32119 00:47:01 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
32120 00:47:01 (0) ** 'select * from MSFT_SCMEventLogEvent'
32121 00:47:01 (0) **
32122 00:47:01 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
32123 00:47:01 (0) ** WMI ADAP status: .................................................................................................... OK.
32124 00:47:01 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
32125 00:47:01 (0) ** - ROOT/SERVICEMODEL.
32126 00:47:01 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
32127 00:47:01 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
32128 00:47:01 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
32129 00:47:01 (0) ** i.e. 'WMIC.EXE /NODE:"HOME" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\\\ROOT\\SERVICEMODEL class __SystemSecurity'
32130 00:47:01 (0) **
32131 00:47:01 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
32132 00:47:01 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
32133 00:47:01 (0) ** WMI GET operations: ................................................................................................. OK.
32134 00:47:01 (0) ** WMI MOF representations: ............................................................................................ OK.
32135 00:47:01 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
32136 00:47:01 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
32137 00:47:01 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
32138 00:47:01 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
32139 00:47:01 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
32140 00:47:01 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
32141 00:47:01 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
32142 00:47:01 (0) ** WMI static instances retrieved: ..................................................................................... 762.
32143 00:47:01 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
32144 00:47:01 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
32145 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32146 00:47:01 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
32147 00:47:01 (0) ** DCOM: ............................................................................................................. 1574.
32148 00:47:01 (0) ** WINMGMT: .......................................................................................................... 0.
32149 00:47:01 (0) ** WMIADAPTER: ....................................................................................................... 0.
32150 00:47:01 (0) ** => Verify the WMIDiag LOG at line #23674 for more details.
32151 00:47:01 (0) **
32152 00:47:01 (0) ** # of additional Event Log events AFTER WMIDiag execution:
32153 00:47:01 (0) ** DCOM: ............................................................................................................. 0.
32154 00:47:01 (0) ** WINMGMT: .......................................................................................................... 0.
32155 00:47:01 (0) ** WMIADAPTER: ....................................................................................................... 0.
32156 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32157 00:47:01 (0) ** WMI Registry key setup: ............................................................................................. OK.
32158 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32159 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32160 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32161 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32162 00:47:01 (0) **
32163 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32164 00:47:01 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
32165 00:47:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
32166 00:47:01 (0) **
32167 00:47:01 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\\DOCUMENTS AND SETTINGS\\OWNER\\LOCAL SETTINGS\\TEMP\\WMIDIAG-V2.0_XP___.CLI.RTM.32_HOME_2011.03.12_00.42.21.LOG' for details.
32168 00:47:01 (0) **
32169 00:47:01 (0) ** WMIDiag v2.0 ended on Saturday, March 12, 2011 at 00:47 (W:72 E:21 S:1).

Now, anyone who's smarter than me wanna enlighten a moron?

[Rydley Sanchez]

Same Administrator issue on Win7 64 while in Administrator account. System specifications all visible. Have tried all possible solutions/workarounds but as yet no joy just keep getting that dreaded error page.

[spiersdisarster]

any mnore ideas coz im about to return the game in like 4 hours if a HOT fix doesnt marracusly appear

[Valfreyja]

Rob Bartel wrote...

Thanks chris2c2 - and just to be triple-sure can you confirm that you...

• ...renamed/destroyed your current repository folder before running the 'winmgmt/salvagerepository' command?
• ...ran the “net localgroup administrators NetworkService /ADD” command prompt?

Sorry - still trying to hammer this out with the engineers.

Tried doing these things, but it tells me that the repository is consistent and number 2 tells me that this group does not exist. So yeah neither works for me.

[spiersdisarster]

yea ried them ages ago.. i got nuaght

[Sabriana]

Any ideas about the #EV 53905 "Dragon Age has encountered a problem and has to close" error?
It breaks my heart having the Demo working so beautifully, but I can't touch the regular game. I am not computer-savvy enough to go deep into files and such, so I'd need some hand-holding.
I'm on windows xp btw.

This is a picture of what my computer wants to report to microsoft. I have no idea what that means, perhaps one of the bright computer people can make something of it.





I can't even find this C:\\DOCUME~ folder anywhere. Shows how dense I am when it comes to the inner workings of my machine.

[Frozenmojo]

Frozenmojo wrote...

I just got my Dragon Age 2 to work, after having that annoying http://i352.photobuc.../shaoel/da2.jpg error. I was waiting for a fix here. And was looking into another problem I have been having with the Windows Experience Index. I run a Gigabyte p55-ud3 mother board whichs old bios doesn't like the WEI too much.

I updated my bios, and now I can run DA2 no problem.

I hope this will help someone who still has problems with this. If not I hope bioware will come up with a fix for you guys real soon.

This might not be the whole reason since I had to run a repair of my windows 7 64-bit after I updated my bios.

[MJ1988]

I´ve same problem as Chris 2c2. Tried to apply Beta fix, but nothing changed, game is still reporting something about insufficient privileges.

Trying to run script I´got something like this ( posting only bottom of file ).

.1545 08:37:39 (0) ** 6 error(s) 0x80041015 - (WBEM_E_TRANSPORT_FAILURE) Networking error that prevents normal operation has occurred
.1546 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1547 08:37:39 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1548 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1549 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1550 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1551 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1552 08:37:39 (0) **
.1553 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1554 08:37:39 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1555 08:37:39 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1556 08:37:39 (0) **
.1557 08:37:39 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'H:\\DOCUMENTS AND SETTINGS\\ADMIN\\LOCAL SETTINGS\\TEMP\\WMIDIAG-V2.0_XP___.CLI.RTM.32_PC-7D76003524CF_2011.03.12_08.37.31.LOG' for details.
.1558 08:37:39 (0) **
.1559 08:37:39 (0) ** WMIDiag v2.0 ended on 12. marca 2011 at 08:37 (W:48 E:18 S:1).

[GuDis]

I solved my "not starting game". I got the silent shut down of the .exe file.

I looked im my TEMP drive and found a folder named. MTKA_TMP, I looked in there and found dragonage2_activation.exe I started that file and after a while the activation program started an it checked on the net for the time I suppose. But after that nothing happened so I tried to start my game again, but still nothing happened.

So I checked the MTKA_TMP folder again and did see that there are a DRAGONAGE2.EXE too.

THIS .EXE FILE I MOVED TOO MY ORIGINAL DRAGON AGE FOLDER.
Tried to start the game and it worked !!!

I can say too that when I tried to start the dragonage2_activation.exe again I got the AWC.DLL error.

After I started dragonage2_activation.exe the first time I did see that the DRAGONAGE2.EXE was around 27Mb and after activation it was around 12Mb so something happened.

Forgot to say that I updated my .NET files though windowsupdate to version 4 and still got the AWC.DLL error.

Modifié par GuDis, 12 mars 2011 - 07:57 .

[Arnyhold]

For me it was currupted WMI. To solve it I had to do a different solution... I renamed the repository folder then run this script (from run as admin cmd), using Win7:

cd /d %windir%\\system32\\wbem
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServer

Reference: http://windowsxp.mvp...g/repairwmi.htm

[KaaZe]

 I have the problem with windows Experience Index - Updating my Bios solved it. I had a Gigabyte-p55-UD3.

[Seekirus]

Well mine is working now. I had to use an underhanded method to play, I think it might be against forums rules to state the method here, but it worked.
I'd say it's probably something do with the method of DRM launching the game.

Modifié par Seekirus, 12 mars 2011 - 09:02 .

[Sabriana]

Well, I dug a little deeper into the files, even though it makes me feel very umcomfortable. I'm one of the "Dragon Age II detected a problem and has to close" people, btw. I found this in the mtka_tmp. It's called lang_mtka.ini and had this to say:

[SETTINGS]


[DEFAULT]
LANGUAGE=0x09
LANGUAGE_SUBIDS=0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0a,0x0b,0x0c,0x0d

# ERRROR DIALOG
ERR_ACCESS_RIGHT_PROBLEM_TITLE=Error
ERR_ACCESS_RIGHT_PROBLEM=To complete the installation and activation you must have Administrator rights.\\nPlease log in as Administrator and restart this application.

So I downloaded the WMI Diagnistics Utility and ran it.

Here's what WMIDIAG had to say. It's just a part, not the whole report, that would be even longer. Sorry for all this text. It says something was removed, and I wonder how it got removed. I'm not computer-savy enough to even try removing things like these listed.


20470 09:38:24 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20471 09:38:24 (1) !! ERROR: Default trustee 'BUILTIN\\ADMINISTRATORS' has been REMOVED!
20472 09:38:24 (0) **        - REMOVED ACE:
20473 09:38:24 (0) **          ACEType:  &h0
20474 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20475 09:38:24 (0) **          ACEFlags: &h0
20476 09:38:24 (0) **          ACEMask:  &h1
20477 09:38:24 (0) **                    DCOM_RIGHT_EXECUTE
20478 09:38:24 (0) **
20479 09:38:24 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20480 09:38:24 (0) **    Removing default security will cause some operations to fail!
20481 09:38:24 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20482 09:38:24 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20483 09:38:24 (0) **
20484 09:38:24 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20485 09:38:24 (1) !! ERROR: Default trustee 'NT AUTHORITY\\INTERACTIVE' has been REMOVED!
20486 09:38:24 (0) **        - REMOVED ACE:
20487 09:38:24 (0) **          ACEType:  &h0
20488 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20489 09:38:24 (0) **          ACEFlags: &h0
20490 09:38:24 (0) **          ACEMask:  &h1
20491 09:38:24 (0) **                    DCOM_RIGHT_EXECUTE
20492 09:38:24 (0) **
20493 09:38:24 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20494 09:38:24 (0) **    Removing default security will cause some operations to fail!
20495 09:38:24 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20496 09:38:24 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20497 09:38:24 (0) **
20498 09:38:24 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20499 09:38:24 (1) !! ERROR: Default trustee 'NT AUTHORITY\\SYSTEM' has been REMOVED!
20500 09:38:24 (0) **        - REMOVED ACE:
20501 09:38:24 (0) **          ACEType:  &h0
20502 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20503 09:38:24 (0) **          ACEFlags: &h0
20504 09:38:24 (0) **          ACEMask:  &h1
20505 09:38:24 (0) **                    DCOM_RIGHT_EXECUTE
20506 09:38:24 (0) **
20507 09:38:24 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20508 09:38:24 (0) **    Removing default security will cause some operations to fail!
20509 09:38:24 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20510 09:38:24 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20511 09:38:24 (0) **
20512 09:38:24 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20513 09:38:24 (1) !! ERROR: Actual trustee 'NT AUTHORITY\\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
20514 09:38:24 (0) **        - ACTUAL ACE:
20515 09:38:24 (0) **          ACEType:  &h0
20516 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20517 09:38:24 (0) **          ACEFlags: &h2
20518 09:38:24 (0) **                    CONTAINER_INHERIT_ACE
20519 09:38:24 (0) **          ACEMask:  &h1
20520 09:38:24 (0) **                    WBEM_ENABLE
20521 09:38:24 (0) **        - EXPECTED ACE:
20522 09:38:24 (0) **          ACEType:  &h0
20523 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20524 09:38:24 (0) **          ACEFlags: &h12
20525 09:38:24 (0) **                    CONTAINER_INHERIT_ACE
20526 09:38:24 (0) **                    INHERITED_ACE
20527 09:38:24 (0) **          ACEMask:  &h13
20528 09:38:24 (0) **                    WBEM_ENABLE
20529 09:38:24 (0) **                    WBEM_METHOD_EXECUTE
20530 09:38:24 (0) **                    WBEM_WRITE_PROVIDER
20531 09:38:24 (0) **
20532 09:38:24 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
20533 09:38:24 (0) **    This will cause some operations to fail!
20534 09:38:24 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
20535 09:38:24 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20536 09:38:24 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20537 09:38:24 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
20538 09:38:24 (0) **       A specific WMI application can always require a security setup different
20539 09:38:24 (0) **       than the WMI security defaults.
20540 09:38:24 (0) **
20541 09:38:24 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20542 09:38:24 (1) !! ERROR: Actual trustee 'NT AUTHORITY\\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
20543 09:38:24 (0) **        - ACTUAL ACE:
20544 09:38:24 (0) **          ACEType:  &h0
20545 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20546 09:38:24 (0) **          ACEFlags: &h2
20547 09:38:24 (0) **                    CONTAINER_INHERIT_ACE
20548 09:38:24 (0) **          ACEMask:  &h1
20549 09:38:24 (0) **                    WBEM_ENABLE
20550 09:38:24 (0) **        - EXPECTED ACE:
20551 09:38:24 (0) **          ACEType:  &h0
20552 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20553 09:38:24 (0) **          ACEFlags: &h12
20554 09:38:24 (0) **                    CONTAINER_INHERIT_ACE
20555 09:38:24 (0) **                    INHERITED_ACE
20556 09:38:24 (0) **          ACEMask:  &h13
20557 09:38:24 (0) **                    WBEM_ENABLE
20558 09:38:24 (0) **                    WBEM_METHOD_EXECUTE
20559 09:38:24 (0) **                    WBEM_WRITE_PROVIDER
20560 09:38:24 (0) **
20561 09:38:24 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
20562 09:38:24 (0) **    This will cause some operations to fail!
20563 09:38:24 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
20564 09:38:24 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20565 09:38:24 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20566 09:38:24 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
20567 09:38:24 (0) **       A specific WMI application can always require a security setup different
20568 09:38:24 (0) **       than the WMI security defaults.
20569 09:38:24 (0) **
20570 09:38:24 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20571 09:38:24 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
20572 09:38:24 (0) **        - REMOVED ACE:
20573 09:38:24 (0) **          ACEType:  &h0
20574 09:38:24 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20575 09:38:24 (0) **          ACEFlags: &h12
20576 09:38:24 (0) **                    CONTAINER_INHERIT_ACE
20577 09:38:24 (0) **                    INHERITED_ACE
20578 09:38:24 (0) **          ACEMask:  &h13
20579 09:38:24 (0) **                    WBEM_ENABLE
20580 09:38:24 (0) **                    WBEM_METHOD_EXECUTE
20581 09:38:24 (0) **                    WBEM_WRITE_PROVIDER
20582 09:38:24 (0) **
20583 09:38:24 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20584 09:38:24 (0) **    Removing default security will cause some operations to fail!
20585 09:38:24 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20586 09:38:24 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20587 09:38:24 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20588 09:38:24 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
20589 09:38:24 (0) **       A specific WMI application can always require a security setup different
20590 09:38:24 (0) **       than the WMI security defaults.
20591 09:38:24 (0) **
20592 09:38:24 (0) **
20593 09:38:24 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
20594 09:38:24 (0) ** DCOM security error(s) detected: .................................................................................... 3.
20595 09:38:24 (0) ** WMI security warning(s) detected: ................................................................................... 0.
20596 09:38:24 (0) ** WMI security error(s) detected: ..................................................................................... 3.
20597 09:38:24 (0) **
20598 09:38:24 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
20599 09:38:24 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
20600 09:38:24 (0) ** - Started at 'Root' -----------------------------------------

Other than knowing that there is something wrong, I have absolutely no clue how to fix this wrongness. The report tells me how it can be fixed, but I don't know how to go about it. I don't know where to find all these files, for starters. Where, or what, is the security descriptor?

Sorry again for all this text, guys.

[Ned Coleman]

Rob Bartel wrote...

Ned Coleman wrote...

NO Solution for me! ...
Still get the error:The application will not run on a Windows guest account or an account with insufficient privileges... blablabla
I tried the WMI repository solution, and after this: c:>net localgroup administrators NetworkService /ADD

Still nothing, still the same problem. I can't play. Now what?

Is the System Information dialog still showing the symptom of no CPU or memory info? Can you confirm that you're renaming/destroying their current repository folder before running the 'winmgmt
/salvagerepository' command?

Thanks!

Nope,,, The system information is correct for me-showing the CPU and memory info. Repository rename/destroy confirmed and tried 3 times this night again. Used those commands what U wrote but still nothin' . There is one thing U need to know: I've no experience index since I've got 3 monitors...  motherboard: Gigabyte GA P55M-UD4 (Bios F3)

Modifié par Ned Coleman, 12 mars 2011 - 09:35 .

[Delafoi]

I have the admin problem and yeah, I'm not flashing my bios or doing anything crazy with WMI-stuff just to get it to work. This is really awesome that I can't play the game that I bought and preordered half a year ago, just because it's using some SecuROM protection to check the current date, seriously? I can't even play Dragon Age Legends in Facebook because you need to get in DA II before you can play it. I know you're working hard, but darn

[Jennisj]

Right, ive got new the latest video drivers, a fresh install with all anti virus off and the 1.01 patch and I'm still getting a silent fail when I hit play, the patch certainly hasn't fixed this for everyone. I tried GuDis' method as well but my application file is already 12mb and nothing changes

[exomundi]

EV#53094 i tried the patch and still nothing, my log reports an error with MSVCR80.dll
did anyone find a workaround for that?

[Ned Coleman]

I downloaded/upgraded the latest Bios for my Gigabyte motherboard and the game is now runnin'''
(my bad) -

The first thing is not to update the WMI or make that repository move -NO-,,, the first thing is to UPDATE Your BIOS

[glen100]

I am getting the same message as SABRIANA, i have tried some of the potential fixes like (.net framework 4 / updating graphics drivers etc. But no luck and none to the other posts seem to address this. Also the new game patch installed had no affect at all.

[Jabanoss]

Okay I have the Admin problem as well. I have Windows 7 64x.
I have tried the 'net stop winmgmt' thing but when I use it I get this reply:

"The Windows Management Instrumentation Service is not Started."

Does anyone have a clue of what to do?
For the record I cannot see my processor and all that, and I have tried the latest patch.

[Daryst]

Tried all of the above + patches and I still get the same exact problem.

[sven_usling]

[quote]seattle_scotsman wrote...

I'm getting this error:

"There is a problem with your game's setup. Please reinstall your game."

This problem still exists for me!