Re: Launcher Problem
thanks for the quick response guys, heres what i did.
i reinstalled the launcher and still no go and im on windows xp and msvcp71.dll is in the folder already. i downloaded that program and the log file is below, it says i dont have any service pack, kinda funny lol and i hope the size of the log file isnt a problem. *crosses fingers*
.1425 21:05:07 (0) ** WMIDiag v2.0 started on Monday, September 13, 2010 at 21:04.
.1426 21:05:07 (0) **
.1427 21:05:07 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1428 21:05:07 (0) **
.1429 21:05:07 (0) ** This script is not supported under any Microsoft standard support program or service.
.1430 21:05:07 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1431 21:05:07 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1432 21:05:07 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1433 21:05:07 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1434 21:05:07 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1435 21:05:07 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1436 21:05:07 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1437 21:05:07 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1438 21:05:07 (0) ** of the possibility of such damages.
.1439 21:05:07 (0) **
.1440 21:05:07 (0) **
.1441 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1442 21:05:07 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1443 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1444 21:05:07 (0) **
.1445 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1446 21:05:07 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'GAMEMACHINE\JAY' on computer 'GAMEMACHINE'.
.1447 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1448 21:05:07 (0) ** Environment: ........................................................................................................ OK..
.1449 21:05:07 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1450 21:05:07 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1451 21:05:07 (0) ** WMI repository state: ............................................................................................... N/A.
.1452 21:05:07 (0) ** BEFORE running WMIDiag:
.1453 21:05:07 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
.1454 21:05:07 (0) ** - Disk free space on 'C:': .......................................................................................... 86586 MB.
.1455 21:05:07 (0) ** - INDEX.BTR, 1286144 bytes, 6/5/2010 8:14:48 AM
.1456 21:05:07 (0) ** - INDEX.MAP, 664 bytes, 6/5/2010 8:14:48 AM
.1457 21:05:07 (0) ** - OBJECTS.DATA, 5619712 bytes, 6/5/2010 8:14:48 AM
.1458 21:05:07 (0) ** - OBJECTS.MAP, 2792 bytes, 6/5/2010 8:14:48 AM
.1459 21:05:07 (0) ** AFTER running WMIDiag:
.1460 21:05:07 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
.1461 21:05:07 (0) ** - Disk free space on 'C:': .......................................................................................... 86585 MB.
.1462 21:05:07 (0) ** - INDEX.BTR, 1286144 bytes, 6/5/2010 8:14:48 AM
.1463 21:05:07 (0) ** - INDEX.MAP, 664 bytes, 6/5/2010 8:14:48 AM
.1464 21:05:07 (0) ** - OBJECTS.DATA, 5619712 bytes, 6/5/2010 8:14:48 AM
.1465 21:05:07 (0) ** - OBJECTS.MAP, 2792 bytes, 6/5/2010 8:14:48 AM
.1466 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1467 21:05:07 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1468 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1469 21:05:07 (0) ** DCOM Status: ........................................................................................................ OK.
.1470 21:05:07 (0) ** WMI registry setup: ................................................................................................. OK.
.1471 21:05:07 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.1472 21:05:07 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1473 21:05:07 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1474 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1475 21:05:07 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1476 21:05:07 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
.1477 21:05:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
.1478 21:05:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
.1479 21:05:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
.1480 21:05:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
.1481 21:05:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
.1482 21:05:07 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
.1483 21:05:07 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1484 21:05:07 (0) ** fail depending on the operation requested.
.1485 21:05:07 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1486 21:05:07 (0) **
.1487 21:05:07 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1488 21:05:07 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1489 21:05:07 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1490 21:05:07 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1491 21:05:07 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1492 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1493 21:05:07 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
.1494 21:05:07 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
.1495 21:05:07 (0) ** - REMOVED ACE:
.1496 21:05:07 (0) ** ACEType: &h0
.1497 21:05:07 (0) ** ACCESS_ALLOWED_ACE_TYPE
.1498 21:05:07 (0) ** ACEFlags: &h0
.1499 21:05:07 (0) ** ACEMask: &h1
.1500 21:05:07 (0) ** DCOM_RIGHT_EXECUTE
.1501 21:05:07 (0) **
.1502 21:05:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1503 21:05:07 (0) ** Removing default security will cause some operations to fail!
.1504 21:05:07 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1505 21:05:07 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1506 21:05:07 (0) **
.1507 21:05:07 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
.1508 21:05:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
.1509 21:05:07 (0) ** - REMOVED ACE:
.1510 21:05:07 (0) ** ACEType: &h0
.1511 21:05:07 (0) ** ACCESS_ALLOWED_ACE_TYPE
.1512 21:05:07 (0) ** ACEFlags: &h0
.1513 21:05:07 (0) ** ACEMask: &h1
.1514 21:05:07 (0) ** DCOM_RIGHT_EXECUTE
.1515 21:05:07 (0) **
.1516 21:05:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1517 21:05:07 (0) ** Removing default security will cause some operations to fail!
.1518 21:05:07 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1519 21:05:07 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1520 21:05:07 (0) **
.1521 21:05:07 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
.1522 21:05:07 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
.1523 21:05:07 (0) ** - REMOVED ACE:
.1524 21:05:07 (0) ** ACEType: &h0
.1525 21:05:07 (0) ** ACCESS_ALLOWED_ACE_TYPE
.1526 21:05:07 (0) ** ACEFlags: &h0
.1527 21:05:07 (0) ** ACEMask: &h1
.1528 21:05:07 (0) ** DCOM_RIGHT_EXECUTE
.1529 21:05:07 (0) **
.1530 21:05:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1531 21:05:07 (0) ** Removing default security will cause some operations to fail!
.1532 21:05:07 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1533 21:05:07 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1534 21:05:07 (0) **
.1535 21:05:07 (0) **
.1536 21:05:07 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
.1537 21:05:07 (0) ** DCOM security error(s) detected: .................................................................................... 3.
.1538 21:05:07 (0) ** WMI security warning(s) detected: ................................................................................... 0.
.1539 21:05:07 (0) ** WMI security error(s) detected: ..................................................................................... 0.
.1540 21:05:07 (0) **
.1541 21:05:07 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
.1542 21:05:07 (0) ** Overall WMI security status: ........................................................................................ OK.
.1543 21:05:07 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1544 21:05:07 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1545 21:05:07 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1546 21:05:07 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1547 21:05:07 (0) ** You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1548 21:05:07 (0) ** the performance counters with the WMI performance classes with the following commands:
.1549 21:05:07 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'
.1550 21:05:07 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF'
.1551 21:05:07 (0) ** The ADAP process logs informative events in the Windows NT event log.
.1552 21:05:07 (0) ** More information can be found on MSDN at:
.1553 21:05:07 (0) ** http://msdn.microsoft.com/library/defau … events.asp
.1554 21:05:07 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1555 21:05:07 (0) ** - Root, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1556 21:05:07 (0) **
.1557 21:05:07 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1558 21:05:07 (0) ** - Root, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1559 21:05:07 (0) ** - Root, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1560 21:05:07 (0) ** - Root/Default, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1561 21:05:07 (0) ** - Root/CIMv2, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1562 21:05:07 (0) ** - Root/WMI, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1563 21:05:07 (0) **
.1564 21:05:07 (0) ** WMI GET operations: ................................................................................................. OK.
.1565 21:05:07 (0) ** WMI MOF representations: ............................................................................................ OK.
.1566 21:05:07 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1567 21:05:07 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1568 21:05:07 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1569 21:05:07 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1570 21:05:07 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1571 21:05:07 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1572 21:05:07 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1573 21:05:07 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1574 21:05:07 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1575 21:05:07 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1576 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1577 21:05:07 (0) **
.1578 21:05:07 (0) ** 6 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
.1579 21:05:07 (0) ** => This error is typically a WMI error. This WMI error is due to:
.1580 21:05:07 (0) ** - a missing WMI class definition or object.
.1581 21:05:07 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
.1582 21:05:07 (0) ** You can correct the missing class definitions by:
.1583 21:05:07 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
.1584 21:05:07 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
.1585 21:05:07 (0) ** (This list can be built on a similar and working WMI Windows installation)
.1586 21:05:07 (0) ** The following command line must be used:
.1587 21:05:07 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
.1588 21:05:07 (0) ** - a WMI repository corruption.
.1589 21:05:07 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1590 21:05:07 (0) ** to validate the WMI repository operations.
.1591 21:05:07 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1592 21:05:07 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1593 21:05:07 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
.1594 21:05:07 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1595 21:05:07 (0) ** the WMI repository must be reconstructed.
.1596 21:05:07 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1597 21:05:07 (0) ** otherwise some applications may fail after the reconstruction.
.1598 21:05:07 (0) ** This can be achieved with the following command:
.1599 21:05:07 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1600 21:05:07 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1601 21:05:07 (0) ** ALL fixes previously mentioned.
.1602 21:05:07 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1603 21:05:07 (0) **
.1604 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1605 21:05:07 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1606 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1607 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1608 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1609 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1610 21:05:07 (0) **
.1611 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1612 21:05:07 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1613 21:05:07 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1614 21:05:07 (0) **
.1615 21:05:07 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\JAY\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_GAMEMACHINE_2010.09.13_21.04.34.LOG' for details.
.1616 21:05:07 (0) **
.1617 21:05:07 (0) ** WMIDiag v2.0 ended on Monday, September 13, 2010 at 21:05 (W:52 E:30 S:1).





