| Home | Register | Members | Search | Windows Vista Tips | File Database | Links |
![]() |
| Thread Tools | Display Modes |
|
|
|
| |
|
Andrew McLaren
Guest
Posts: n/a
|
It sounds like the log is reporting the info you require:
> ---------------------------------------------------------------------------------------------------------------------------------- > 26043 22:16:07 (0) ** INFO: User Account Control (UAC): > .................................................. ................................. > DISABLED. > 26051 22:16:07 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED! > 26061 22:16:07 (0) ** => The REMOVED ACE was part of the DEFAULT setup for > the trustee. > 26062 22:16:07 (0) ** Removing default security will cause some > operations to fail! Firstly, you disabled UAC - which isn't necessarily a problem; but it makes you vulnerable to strange security side-effects. Applications which have a manifest setting to elevate, cannot elevate if UAC is disabled; so you might get plain "access denied" errors instead of normal function. Secondly, it looks like the Everyone ACE has been removed. The log then tells us "Removing default security will cause some operations to fail". Plus there are a lot of 0x80070005 "Access Denied" errors reading the MOF files. I'm not sure if that's a real access denied on the objects; or whether you're running WMIDiag in a security context which doesn't have access (safest thing is to run as Administrator, on the local box, not remotely) So it sounds like you need to find ways to work around these two problems - either by rolling back the changes (re-enabling UAC, adding the Everyone Trustee); or by further modifying security, to the point things start working again. Or is there something I'm missing? Hope it helps, -- Andrew McLaren amclar (at) optusnet dot com dot au |
|
|
|
|
|||
|
|||
|
ColSchmoll
Guest
Posts: n/a
|
Try adding the NETWORK SERVICE account to you local Adminstrators. This fixed the WMI problem for me. However, I'm still still getting access problems from SQL Server Configuration Manager and SQL Server Reporting Services. WMIDiag output is as follows (can anyone help?), turned on UAC to gett a better error output: 34343 13:29:29 (0) ** WMIDiag v2.0 started on 17 October 2007 at 13:20. 34344 13:29:29 (0) ** 34345 13:29:29 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007. 34346 13:29:29 (0) ** 34347 13:29:29 (0) ** This script is not supported under any Microsoft standard support program or service. 34348 13:29:29 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all 34349 13:29:29 (0) ** implied warranties including, without limitation, any implied warranties of merchantability 34350 13:29:29 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance 34351 13:29:29 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors, 34352 13:29:29 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for 34353 13:29:29 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits, 34354 13:29:29 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of 34355 13:29:29 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised 34356 13:29:29 (0) ** of the possibility of such damages. 34357 13:29:29 (0) ** 34358 13:29:29 (0) ** 34359 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34360 13:29:29 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ---------------------------------------------------------- 34361 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34362 13:29:29 (0) ** 34363 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34364 13:29:29 (0) ** Windows Vista - No service pack - 32-bit (6000) - User 'CKISH-PC\CKISH' on computer 'CKISH-PC'. 34365 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34366 13:29:29 (0) ** INFO: Environment: .................................................. ................................................ 1 ITEM(S)! 34367 13:29:29 (0) ** INFO: => 4 incorrect shutdown(s) detected on: 34368 13:29:29 (0) ** - Shutdown on 17 September 2007 06:46:11 (GMT-0). 34369 13:29:29 (0) ** - Shutdown on 30 July 2007 20:31:49 (GMT-0). 34370 13:29:29 (0) ** - Shutdown on 29 July 2007 06:16:41 (GMT-0). 34371 13:29:29 (0) ** - Shutdown on 26 July 2007 07:54:36 (GMT-0). 34372 13:29:29 (0) ** 34373 13:29:29 (0) ** System drive: .................................................. .................................................. ... C: (Disk #0 Partition #2). 34374 13:29:29 (0) ** Drive type: .................................................. .................................................. ..... IDE (WDC WD1200BEVS-75RST0 ATA Device). 34375 13:29:29 (0) ** There are no missing WMI system files: .................................................. ............................ OK. 34376 13:29:29 (0) ** There are no missing WMI repository files: .................................................. ........................ OK. 34377 13:29:29 (0) ** WMI repository state: .................................................. ............................................. CONSISTENT. 34378 13:29:29 (0) ** BEFORE running WMIDiag: 34379 13:29:29 (0) ** The WMI repository has a size of: .................................................. ................................. 26 MB. 34380 13:29:29 (0) ** - Disk free space on 'C:': .................................................. ........................................ 27050 MB. 34381 13:29:29 (0) ** - INDEX.BTR, 2990080 bytes, 17/10/2007 13:19:54 34382 13:29:29 (0) ** - MAPPING1.MAP, 75916 bytes, 17/10/2007 13:19:54 34383 13:29:29 (0) ** - MAPPING2.MAP, 75916 bytes, 17/10/2007 13:19:24 34384 13:29:29 (0) ** - OBJECTS.DATA, 23740416 bytes, 17/10/2007 13:19:53 34385 13:29:29 (0) ** AFTER running WMIDiag: 34386 13:29:29 (0) ** The WMI repository has a size of: .................................................. ................................. 26 MB. 34387 13:29:29 (0) ** - Disk free space on 'C:': .................................................. ........................................ 27045 MB. 34388 13:29:29 (0) ** - INDEX.BTR, 2990080 bytes, 17/10/2007 13:19:54 34389 13:29:29 (0) ** - MAPPING1.MAP, 75916 bytes, 17/10/2007 13:19:54 34390 13:29:29 (0) ** - MAPPING2.MAP, 75916 bytes, 17/10/2007 13:19:24 34391 13:29:29 (0) ** - OBJECTS.DATA, 23740416 bytes, 17/10/2007 13:19:53 34392 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34393 13:29:29 (0) ** INFO: Windows Firewall status: .................................................. .................................... ENABLED. 34394 13:29:29 (0) ** Windows Firewall Profile: .................................................. ......................................... PUBLIC. 34395 13:29:29 (0) ** Inbound connections that do not match a rule BLOCKED: .................................................. ............. ENABLED. 34396 13:29:29 (0) ** => This will prevent any WMI remote connectivity to this computer except 34397 13:29:29 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING: 34398 13:29:29 (0) ** - 'Windows Management Instrumentation (DCOM-In)' 34399 13:29:29 (0) ** - 'Windows Management Instrumentation (WMI-In)' 34400 13:29:29 (0) ** - 'Windows Management Instrumentation (ASync-In)' 34401 13:29:29 (0) ** Verify the reported status for each of these three inbound rules below. 34402 13:29:29 (0) ** 34403 13:29:29 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED. 34404 13:29:29 (0) ** => This will prevent any WMI remote connectivity to/from this machine. 34405 13:29:29 (0) ** - You can adjust the configuration by executing the following command: 34406 13:29:29 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES' 34407 13:29:29 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once! 34408 13:29:29 (0) ** You can also enable each individual rule instead of activating the group rule. 34409 13:29:29 (0) ** 34410 13:29:29 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED. 34411 13:29:29 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine. 34412 13:29:29 (0) ** - You can adjust the configuration of this rule by executing the following command: 34413 13:29:29 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES' 34414 13:29:29 (0) ** 34415 13:29:29 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... DISABLED. 34416 13:29:29 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine. 34417 13:29:29 (0) ** - You can adjust the configuration of this rule by executing the following command: 34418 13:29:29 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES' 34419 13:29:29 (0) ** 34420 13:29:29 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED. 34421 13:29:29 (0) ** => This will prevent any WMI inbound connectivity to this machine. 34422 13:29:29 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity. 34423 13:29:29 (0) ** - You can adjust the configuration of this rule by executing the following command: 34424 13:29:29 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES' 34425 13:29:29 (0) ** 34426 13:29:29 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED. 34427 13:29:29 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine. 34428 13:29:29 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity. 34429 13:29:29 (0) ** - You can adjust the configuration of this rule by executing the following command: 34430 13:29:29 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES' 34431 13:29:29 (0) ** 34432 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34433 13:29:29 (0) ** DCOM Status: .................................................. .................................................. .... OK. 34434 13:29:29 (0) ** WMI registry setup: .................................................. ............................................... OK. 34435 13:29:29 (0) ** INFO: WMI service has dependents: .................................................. ................................. 2 SERVICE(S)! 34436 13:29:29 (0) ** - Security Center (WSCSVC, StartMode='Automatic') 34437 13:29:29 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual') 34438 13:29:29 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well. 34439 13:29:29 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but 34440 13:29:29 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped, 34441 13:29:29 (0) ** this can prevent the service/application to work as expected. 34442 13:29:29 (0) ** 34443 13:29:29 (0) ** RPCSS service: .................................................. .................................................. .. OK (Already started). 34444 13:29:29 (0) ** WINMGMT service: .................................................. .................................................. OK (Already started). 34445 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34446 13:29:29 (0) ** WMI service DCOM setup: .................................................. ........................................... OK. 34447 13:29:29 (0) ** WMI components DCOM registrations: .................................................. ................................ OK. 34448 13:29:29 (0) ** WMI ProgID registrations: .................................................. ......................................... OK. 34449 13:29:29 (0) ** WMI provider DCOM registrations: .................................................. .................................. OK. 34450 13:29:29 (0) ** WMI provider CIM registrations: .................................................. ................................... OK. 34451 13:29:29 (0) ** WMI provider CLSIDs: .................................................. .............................................. OK. 34452 13:29:29 (0) ** WMI providers EXE/DLL availability: .................................................. ............................... OK. 34453 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34454 13:29:29 (0) ** INFO: User Account Control (UAC): .................................................. ................................. ENABLED. 34455 13:29:29 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context. 34456 13:29:29 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command 34457 13:29:29 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and 34458 13:29:29 (0) ** selecting 'Run as Administrator'. 34459 13:29:29 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task 34460 13:29:29 (0) ** in the Task Scheduler within the right security context. 34461 13:29:29 (0) ** 34462 13:29:29 (0) ** INFO: Local Account Filtering: .................................................. .................................... ENABLED. 34463 13:29:29 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative 34464 13:29:29 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer 34465 13:29:29 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote 34466 13:29:29 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group. 34467 13:29:29 (0) ** 34468 13:29:29 (0) ** Overall DCOM security status: .................................................. ..................................... OK. 34469 13:29:29 (0) ** Overall WMI security status: .................................................. ...................................... OK. 34470 13:29:29 (0) ** - Started at 'Root' -------------------------------------------------------------------------------------------------------------- 34471 13:29:29 (0) ** INFO: WMI permanent SUBSCRIPTION(S): .................................................. .............................. 1. 34472 13:29:29 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer". 34473 13:29:29 (0) ** 'select * from MSFT_SCMEventLogEvent' 34474 13:29:29 (0) ** 34475 13:29:29 (0) ** WMI TIMER instruction(s): .................................................. ......................................... NONE. 34476 13:29:29 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................. .................. 5 NAMESPACE(S)! 34477 13:29:29 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM. 34478 13:29:29 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTVOLUMEENCRYPTION. 34479 13:29:29 (0) ** - ROOT/CIMV2/TERMINALSERVICES. 34480 13:29:29 (0) ** - ROOT/MICROSOFTIISV2. 34481 13:29:29 (0) ** - ROOT/SERVICEMODEL. 34482 13:29:29 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to 34483 13:29:29 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level. 34484 13:29:29 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags) 34485 13:29:29 (0) ** i.e. 'WMIC.EXE /NODE:"CKISH-PC" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity' 34486 13:29:29 (0) ** 34487 13:29:29 (0) ** WMI MONIKER CONNECTIONS: .................................................. .......................................... OK. 34488 13:29:29 (0) ** WMI CONNECTIONS: .................................................. .................................................. OK. 34489 13:29:29 (0) ** WMI GET operations: .................................................. ............................................... OK. 34490 13:29:29 (0) ** WMI MOF representations: .................................................. .......................................... OK. 34491 13:29:29 (0) ** WMI QUALIFIER access operations: .................................................. .................................. OK. 34492 13:29:29 (1) !! ERROR: WMI ENUMERATION operation errors reported: .................................................. ................. 16 ERROR(S)! 34493 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Cache', 0x80004002 - No such interface supported. 34494 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34495 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Memory', 0x80004002 - No such interface supported. 34496 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34497 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Objects', 0x80004002 - No such interface supported. 34498 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34499 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_PagingFile', 0x80004002 - No such interface supported. 34500 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34501 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Processor', 0x80004002 - No such interface supported. 34502 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34503 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_System', 0x80004002 - No such interface supported. 34504 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34505 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Process', 0x80004002 - No such interface supported. 34506 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34507 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Thread', 0x80004002 - No such interface supported. 34508 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34509 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMP', 0x80004002 - No such interface supported. 34510 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34511 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMPv6', 0x80004002 - No such interface supported. 34512 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34513 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv4', 0x80004002 - No such interface supported. 34514 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34515 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv6', 0x80004002 - No such interface supported. 34516 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34517 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv4', 0x80004002 - No such interface supported. 34518 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34519 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv6', 0x80004002 - No such interface supported. 34520 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34521 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv4', 0x80004002 - No such interface supported. 34522 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34523 13:29:29 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv6', 0x80004002 - No such interface supported. 34524 13:29:29 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF' 34525 13:29:29 (0) ** 34526 13:29:29 (0) ** WMI EXECQUERY operations: .................................................. ......................................... OK. 34527 13:29:29 (0) ** WMI GET VALUE operations: .................................................. ......................................... OK. 34528 13:29:29 (0) ** WMI WRITE operations: .................................................. ............................................. NOT TESTED. 34529 13:29:29 (0) ** WMI PUT operations: .................................................. ............................................... NOT TESTED. 34530 13:29:29 (0) ** WMI DELETE operations: .................................................. ............................................ NOT TESTED. 34531 13:29:29 (0) ** WMI static instances retrieved: .................................................. ................................... 1660. 34532 13:29:29 (0) ** WMI dynamic instances retrieved: .................................................. .................................. 0. 34533 13:29:29 (0) ** WMI instance request cancellations (to limit performance impact): .................................................. . 1. 34534 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34535 13:29:29 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s): 34536 13:29:29 (0) ** DCOM: .................................................. .................................................. ......... 0. 34537 13:29:29 (0) ** WINMGMT: .................................................. .................................................. ...... 0. 34538 13:29:29 (0) ** WMIADAPTER: .................................................. .................................................. ... 0. 34539 13:29:29 (0) ** 34540 13:29:29 (0) ** # of additional Event Log events AFTER WMIDiag execution: 34541 13:29:29 (0) ** DCOM: .................................................. .................................................. ......... 0. 34542 13:29:29 (0) ** WINMGMT: .................................................. .................................................. ...... 0. 34543 13:29:29 (0) ** WMIADAPTER: .................................................. .................................................. ... 0. 34544 13:29:29 (0) ** 34545 13:29:29 (0) ** 16 error(s) 0x80004002 - (WBEM_UNKNOWN) This error code is external to WMI. 34546 13:29:29 (0) ** => This error is not a WMI error. It is a DCOM error due to the following reasons: 34547 13:29:29 (0) ** - An application has changed the COM/DCOM settings of OLE32.DLL and/or OLEAUT32.DLL. 34548 13:29:29 (0) ** - The registry settings of COM/DCOM has been damage or wrongly modified. 34549 13:29:29 (0) ** => To correct this situation, you must re-register the original COM/DCOM DLLs with REGSVR32.EXE 34550 13:29:29 (0) ** i.e. 'REGSVR32.EXE OLE32.DLL' 34551 13:29:29 (0) ** i.e. 'REGSVR32.EXE OLEAUT32.DLL' 34552 13:29:29 (0) ** 34553 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34554 13:29:29 (0) ** WMI Registry key setup: .................................................. ........................................... OK. 34555 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34556 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34557 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34558 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- 34559 13:29:29 (0) ** 34560 13:29:29 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- -- ColSchmoll ------------------------------------------------------------------------ ColSchmoll's Profile: http://forums.techarena.in/member.php?userid=33155 View this thread: http://forums.techarena.in/showthread.php?t=834393 http://forums.techarena.in |
|
|
|
|
|||
|
|||
|
|
|
| |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| EQ2 issue Help | Spanky | Windows Vista Games | 2 | 01-15-2008 04:00 PM |
| An odd issue | afar1 | Windows Vista Installation | 2 | 06-25-2007 04:07 PM |
| NEW PC Issue | lightfla | Windows Vista Installation | 1 | 06-19-2007 07:58 AM |
| Monitor issue or full instal issue | DaymItzJack | Windows Vista Installation | 2 | 10-24-2006 12:52 AM |
| Routre Issue or Vista Issue | Gary MCSE | Windows Vista General Discussion | 1 | 10-15-2006 03:26 PM |
Forum Software Powered by vBulletin®, Copyright Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc. |



Linear Mode

