category event (256) 516?

Hi all. In Event Viewer, I saw an unexplained element that presents itself almost hourly. It has been there for about a week and I am unable to find a definition or a response. It's as follows: Event Viewer / system / WARNING / 18/12/2012/03: 49:02 / MFEHIDK / category (256) / event 516 / user s/o / is it a bug or virus? Help would be appreciated. Thank you

Hello

Thanks for posting your question in the Microsoft Community!

The description of your post, I see that you have found ' category (256) / event 516 "error in Device Manager.

The issue could be due to Virus Scan Enterprise.

What anti-virus software is installed on your computer?

You can consult the following link:

https://KC.McAfee.com/corporate/index?page=content&ID=KB74174

Please come back with more information so that we can help you better.

For any query related to Windows please keep us informed.

Tags: Windows

Similar Questions

Vista hangs after login, error event ID _

Hello, I had a lot of trouble with the Vista machine for a few days. System boots, I have connection, I see the office, then after a three or four minutes, freeze current applications, then I can't do anything. Freezes even if I do not open all the apps. So I try Ctrl-Alt-Del, nothing seems more answer. So I have to hold down the power button to shut up down, then power, boot without failure. When in safe mode, system seems to work very well. I can access files, etc.

I tried the method suggested to go to msconfig, turning off all services and startup items, then try to turn them back on a few at a time to try to isolate that one poses problems. Last week, I thought that I reduced to superfetch as the problem, so I disabled it, and my system has worked fine for a day, pc used for several hours, then turn it over to freeze problems.

I also tried to go into safe mode event viewer, examine the mistakes and try to solve the problems. I do not have any progress.
I copied the error: ID of event below. Can anyone provide assistance, advice or where to start?
Thank you.
============================
my system:
Toshiba Satellite L305
Pentium Dual-Core 2.0 GHz
3.0 GB RAM
32 bit OS
Vista Home Premium, SP1

---------------------
Event Viewer
Errors
Application errors, then the system errors

=================================
Log name: Application
Source: Microsoft-Windows-EventSystem
Date: 2009-10-26 22:56:46
Event ID: 4609
Task category: event system
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Internal system of events from COM + has detected what a bad code back during his treatment. HRESULT has c 8007043 line 45 of d:\vistasp1_gdr\com\complus\src\events\tier1\eventsystemobj.cpp. Contact the Services de Support technique Microsoft to report this error.

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:46
Event ID: 3058
Task category: Gatherer
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The application cannot be initialized.

Background: Windows Application

Details:
The metadata for the content index cannot be read. (0xc0041801)

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:46
Event ID: 3028
Task category: Gatherer
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Cannot initialize the Gatherer object.

Background: Windows Application, catalog creates

Details:
The metadata for the content index cannot be read. (0xc0041801)

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:46
Event ID: 3029
Task category: Gatherer
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The plugin cannot be initialized.

Background: Windows Application, catalog creates

Details:
Item was not found. (0 x 80070490)

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:45
Event ID: 3029
Task category: Gatherer
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The plugin cannot be initialized.

Background: Windows Application, catalog creates

Details:
The metadata for the content index cannot be read. (0xc0041801)

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:45
Event ID: 9002
Task category: Search Service
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The Windows Search Service cannot load the property store information.

Background: Windows Application, catalog creates

Details:
0 x % 08 x (0xc0041800 - the content index cannot be read.)

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:45
Event ID: 7040
Task category: Search Service
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The search service has detected data files corrupted in the index. The service tries to automatically correct this problem by rebuilding the index.

Details:
The metadata for the content index cannot be read. (0xc0041801)

Log name: Application
Source: Microsoft-Windows-search
Date: 2009-10-26 22:51:45
Event ID: 9000
Task category: Search Service
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The Windows Search Service cannot open the Jet property store.

Details:
The content index cannot be read. (0xc0041800)

Log name: Application
Source: ESENT
Date: 2009-10-26 22:51:45
Event ID: 454
Task category: registration/recovery
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Windows Windows (2820): database recovery/restore failed with unexpected error - 255.

Log name: Application
Source: ESENT
Date: 2009-10-26 22:51:44
Event ID: 515
Task category: registration/recovery
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Windows Windows (2820): database C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb: 5489 (0 x 00001571) Page check failed due to incompatibility of flush order dependency. This page should be rinsed before page 2331 (0x0000091b), but the last page empty instead first. Recovery/restore will fail with error - 255. If this condition persists then please restore it from a previous backup. This problem is probably due to a defective material 'lose' one or more colors on one or two of these pages in the past. For further assistance diagnosing the problem, contact your hardware vendor.

Log name: Application
Source: FSecure-FSecure-F-Secure Management Agent
Date: 2009-10-26 22:51:41
Event ID: 103
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
2 2009-10-26 22:51:41-04:00 jwrtosh JWRTOSH\joe F-Secure Management Agent
Module F-Secure PSGB customer monitored by F-Secure Management Agent has stopped responding, or has ended. An attempt to restart will be made later. If you see this message frequently, contact the system administrator or reinstall the F-Secure products.

Log name: Application
Source: FSecure-FSecure-F-Secure Management Agent
Date: 2009-10-26 22:51:31
Event ID: 103
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
1 2009-10-26 22:51:31-04:00 jwrtosh JWRTOSH\joe F-Secure Management Agent
Module F-Secure Anti-Virus Firewall Daemon controlled by F-Secure Management Agent has stopped responding, or has ended. An attempt to restart will be made later. If you see this message frequently, contact the system administrator or reinstall the F-Secure products.

Log name: Application
Source: Application error
Date: 2009-10-26 21:17:21
Event ID: 1000
Task category: (100)
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Failed application iexplore.exe, version 7.0.6001.18319, time stamp 0x4a966702, module SkypeIEPlugin.dll, version 3.3.0.3290, time stamp 0x4a02d40b, exception code 0xc0000005, offset error 0x00001f11, 0 x 534 process id, failed to start the application time 0x01ca56a337d4a63b.

Log name: Application
Source: FSecure-FSecure-F-Secure Management Agent
Date: 2009-10-26 21:05:01
Event ID: 103
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
1 2009-10-26 21:05:01-04:00 jwrtosh JWRTOSH\admin F-Secure Management Agent
Module F-Secure Anti-Virus Firewall Daemon controlled by F-Secure Management Agent has stopped responding, or has ended. An attempt to restart will be made later. If you see this message frequently, contact the system administrator or reinstall the F-Secure products.

============================================

Log name: System
Source: Service Control Manager
Date: 2009-10-26 22:57:40
Event ID: 7001
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Network list Service service depends on the network location awareness service which failed to start because of the following error:
The dependency service or group was able to start.

Log name: System
Source: Service Control Manager
Date: 2009-10-26 22:57:40
Event ID: 7026
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The next (s) starting or starting system could not load:
AFD
DfsC
F-Secure HIPS
ESF
FSFW
jswpslwf
NetBIOS
NetBT
nsiproxy
PSched
Rdbss
Rdbss
SMB
spldr
TDX
Wanarpv6

Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2009-10-26 22:57:21
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
DCOM got error '1084' trying to start WSearch service with arguments "" to start the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}

Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2009-10-26 22:56:47
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
DCOM got error "1068" attempting to start the service netprofm with arguments "" to start the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}

Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2009-10-26 22:56:47
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
DCOM got error "1068" attempting to start the service netman with arguments "" to start the server:
{BA126AD1-2166-11D1-B1D0-00805FC1270E}

Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2009-10-26 22:56:47
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
DCOM got error "1068" try to start the service fdPHost with arguments "" to start the server:
{145B4335-FE2A-4927-A040-7C35AD3180EF}

Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2009-10-26 22:56:46
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
DCOM got error "1084" try to start the service EventSystem with arguments "" to start the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}

Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2009-10-26 22:56:39
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
DCOM got error '1084' trying to start the ShellHWDetection service with arguments "" to start the server:
{DD522ACC-F821-461A-A407-50B198B896DC}

Log name: System
Source: Service Control Manager
Date: 2009-10-26 22:51:54
Event ID: 7031
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The Windows Search service ended in unexpected ways. It has done this 1 time. The following corrective action will be performed in 30000 milliseconds: restart the service.

Log name: System
Source: Service Control Manager
Date: 2009-10-26 22:51:54
Event ID: 7024
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The Windows Search service stopped with the special service 2147749155 (0x80040D23) error.

Log name: System
Source: Microsoft-Windows-HttpEvent
Date: 2009-10-26 22:50:50
Event ID: 15016
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
Failed to initialize the Security Kerberos for authentication package on the server side. The data field contains the error number.

================================

All the error messages you have posted (most are related to research and are probably not part of this problem - some are related to DCOM which was caused by the initial error of the Service Control Manager won't start don't not because addictive has not started - but it does not say that (but it will be in the paper and I would like to know that) and you seem to have F-Secure Management Agent or something like) it as a secondary firewall that seems not to start but is no big deal if you have Windows Firewall upward and operation - this is a great product and does its job well - a secondary firewall is not really necessary but I guess that he can not hurt, if it works - although this could be the program which intrudes that Mcshane mentioned in his post - system freeze because he thinks (, there is violation of firewall, but I don't know which), the one that concerns me most is:

Log name: System
Source: Service Control Manager
Date: 2009-10-26 22:57:40
Event ID: 7026
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: JWRTOSH
Description:
The next (s) starting or starting system could not load:
AFD
DfsC
F-Secure HIPS
ESF
FSFW
jswpslwf
NetBIOS
NetBT
nsiproxy
PSched
Rdbss
Rdbss
SMB
spldr
TDX
Wanarpv6

THIS could very easily cause your system will crash - in fact, I'm surprised, he started even with this error. Did you get a lot of that or is it only once? If you get a lot of them, this is a serious problem, we will have to address.

Do you know when this problem started (it seems that you have a close time)? Try a system restore to a point in time BEFORE the problem started. Here is the procedure: http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/. Don't forget to check the box to show more than 5 days of restore points. If the first attempt fails, then try an earlier point or two. NOTE: You will need to re - install any software and updates that you have installed between now and the restore point, but you can use Windows Update for updates.

If the system restore does not work, do a startup repair, boot from the disk Installation of Windows Vista genuine (or one that you can borrow from someone) or a recovery disc. Here is the procedure: http://www.bleepingcomputer.com/tutorials/tutorial148.html. You may need to change the BIOS to do first the CD drive in the boot sequence to boot from the CD. To do this, hold the screen that tells you the key F to push to enter the menu start or start of installation. Push it quickly. Make the changes, save your work and exit. Put the CD in the drive and reboot. When you are prompted, press any key to boot from the CD.

If you do not have a floppy disk, you can make a bootable recovery disk by using http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ with burning software like: http://www.snapfiles.com/get/active-isoburner.html and, of course, a blank CD.

If this does not work, try to start in safe mode (repeatedly hit F8 key so that the start and go in safe mode with networking). Then we will check some of your system files:

Go to start / all programs / accessories / command prompt and right click on command prompt, and then click Run as administrator.

Type sfc/scannow, go and let it run. It will scan and try to correct some of your system files. If all goes well he comes complete with no corruption, it could not repair (if it has these post of corruption here or try to analyze it to find the problem or files using http://support.microsoft.com/kb/928228.

While in the command prompt, type chkdsk /f /r and enter and let it run. It will scan and try to solve any corruption or bad sectors on your hard drive and remove especially as a cause.

This is not like a malware problem, but it can't hurt to check just to be on the safe side (and since we are almost out of options). In Safe Mode with network (click several times F8 during the boot process) and try to run anti-malware programs. To resolve this problem (if it is a problem) download, install, and run the following two programs: http://www.malwarebytes.org/mbam.php and http://www.safer-networking.org/en/index.html. You can also try a free trial of Pandasoft (www.pandasoft.com). Before you download pandasoft, uninstall all anti-virus program you currently use (because the installation and execution of two simultaneously can cause conflicts, freezes and all sorts of problems). Once you have uninstalled your current AV program, download, install, update and scan using Pandasoft. I think you might be amazed at how much she notes that other software missed. Once complete, uninstall pandasoft and re - install your current AV program (unless you decide to spend that I did when I tried about 4 years ago). You can also try the new, free Microsoft Security Essentials http://www.microsoft.com/security_essentials/default.aspx (with the same caveat that only program AV one ALONE can be installed and running on your system at any time). Restart after you have completed all the scans.

If this does not work, you will need to do a repair/system upgrade using the Windows Vista Installation disc authentic (you own or that you can borrow from someone). Here is the procedure: http://www.vistax64.com/tutorials/88236-repair-install-vista.html as well as the upgrade from an earlier version of the Windows section of the following: http://support.microsoft.com/kb/918884. Although this will not affect your data, settings or programs, you should always back up your data before you start just be on the safe side. If other procedures do not work, it is almost certain to work. You can have a lot of updates to re - install (including all you need to remove service packs). If the version on system with SP1 or SP2 preinstalled cane and the disc is an earlier version, then you will need to do a slipstream drive as follows: http://www.vistax64.com/tutorials/151606-vista-sp1-slipstream-installation-dvd.html.

I hope one of these procedures can solve your problem. If this isn't the case, after return and we will try something else. Return message anyway so we know how it turns out.

Good luck! Lorien - a - MCSE/MCSA/network + / A +.

HRESULT was 80070437 line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Contact the Services de Support technique Microsoft to report this error.

It is a mess that everything seems to have something to do with the user unknown, profile and permissions? I do not know

This first paper below, is the 4th down from the top of the stack of the event view administrator. I posted it all initially due to 'please contact Microsoft Product Support Services to report this error.' requested in this journal

Log name: Application
Source: Microsoft-Windows-EventSystem
Date: 2011-08-20 15:23:12
Event ID: 4609
Task category: event system
Level: error
Keywords: Classic
User: n/a
Computer: Diane
Description:

Internal system of events from COM + has detected what a bad code back during his treatment. HRESULT was 80070437 line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Contact the Services de Support technique Microsoft to report this error.
The event XML:


    4609
    0
    2
    16
    0
    0 x 80000000000000

    36861


    Application
    Diane


    d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp
    45
    80070437

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Log name: System
Source: Service Control Manager
Date: 2011-08-20 16:51:03
Event ID: 7000
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: Diane
Description:
COM event system service + could not start due to the following error:
The account specified for this service is different from the account specified for other services running in the same process.
The event XML:


    7000
    0
    2
    0
    0
    0 x 80000000000000

    390554


    System
    Diane


    System event COM +.
    % 1079

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Log name: Application
Source: Microsoft-Windows-CertificateServicesClient-registration auto
Date: 2011-08-20 01:24:41
Event ID: 64
Task category: no
Level: WARNING
Keywords: Classic
User: n/a
Computer: Diane
Description:
Certificate for the local system with footprint 4 7 54 42 2 a 43 1 a 20 36 77 0e b2 fa 58 58 44 cd fb db is about to expire or already expired.
The event XML:


    64
    0
    3
    0
    0
    0 x 80000000000000

    36700


    Application
    Diane


    local system
    7 4 c a 54, 42, 2, 1 has 43 20 36 77 0e b2 fa 58 fb 58 44 cd db

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Log name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2011-08-20 15:23:12
Event ID: 10005
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: Diane
Description:
DCOM got error "1079" attempting to start the service EventSystem with arguments "" to start the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
The event XML:


    10005
    0
    2
    0
    0
    0 x 80000000000000

    390544


    System
    Diane


    1079
    EventSystem


    {1BE1F766-5536-11D1-B726-00C04FB926AF}

Keep aside the papers, there are real problems with your computer?

If so, can you describe the same thing in short?

"Please contact Support Services Microsoft support to report this error." is a robotic message and generic. Nothing spectacular as such.

In the meantime, scanner SFC on your computer:

How to use the System File Checker tool to fix the system files missing or corrupted on Windows Vista or Windows 7
http://support.Microsoft.com/kb/929833

Windows Server 2012R2 replication errors

Hi, just work through exams 2012R2 if it is in a lab environment, but would like some help on this one that I had trouble finding a solution on this one.

Just to give you a little history, until recently, I had a single DC 2012R2 environment on my lab. About 6 months ago I had to follow the nets below to retrieve my DC after what can't that assume was an unclean shutdown of my host.

http://blog.Shiraj.com/2014/10/how-to-fix-c00002e2-directory-services-could-not-start-blue-screen/

https://support.Microsoft.com/en-us/KB/2751452

I'm working through scenarios without problem until recently.

I added a 2nd DC to the existing successful domain although while they inspected the State of replication I seem to come through a few questions in relation to the folder sysvol replica don't properly on the additional domain controller.

The folder and subfolders are but empty during the 2nd DC.

I run DCDiag on the original domain controller today, the majority of the tests pass ok (some have failed, but I transfer the roles, closing the vms on and outside, as I used it, but the below was obvious as I promoted the 2nd DC):

There are warning or error events in the last 24 hours after the
SYSVOL is shared. Don't not SYSVOL replication problems can cause
The Group of political problems. (from DCDIAG)

I ran the monitor of the replication on the original domain controller health and get the 2 outputs following.

1. the DFS replication service failed to recover from an internal database error on the C: volume. Replication stopped for all folders replicated on this volume until the database is automatically rebuilt. If the database is rebuilt successfully, replication will resume once the reconstruction is complete. If the database cannot be rebuilt, a separate event is generated. If you see this error more than twice in seven days, we recommend that you run Chkdsk on the volume that contains the database. Event ID: 2104

2. the service stopped DFS replication on the C: volume replication. This failure can occur because the disk is full, the disc is a failure or a quota limit has been reached. Event ID: 2004

I followed the discussions to try and resolve this problem without a bit of luck, I can also confirm that the disk is not full or failed.

On the 2nd DC health is:

This member is waiting for initial replication for replicated folder SYSVOL share and does not currently participate in replication. This delay can occur because the Member is waiting for the replication service DFS retrieve the settings from Active Directory Domain Services replication. After the Member detects that it is part of the replication group, the Member will start the initial replication.

Where papers on the original domain controller I was also picking up the following event logs:

Log name: Application
Source: ESENT
Date: 16/04/2016 13:51:57
Event ID: 516
Task category: registration/recovery
Level: error
Keywords: Classic
User: n/a
Computer: server.domain

Description:
\\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db SRBHT (1388): database \\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: Page 46 (0x0000002e) due to a timestamp mismatch verification failure. The timestamp "before" persisted in the paper of record was 0x10fbb, but the current timestamp on page 0 x 11004. The update 'after' timestamp 0 11017 x which would have updated the time stamp on the page. Recovery/restore will fail with the error-567. If this condition persists then please restore it from a previous backup. This problem is probably due to a defective material 'lose' one or more colors on this page in the past. For further assistance diagnosing the problem, contact your hardware vendor.
The event XML:


    516
    2
    3
    0 x 80000000000000

    7033
    Application
    Server


    SRBHT
    1388
    \\.\C:\System volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db:
    \\.\C:\System volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db
    46 (0x0000002e)
    0x10fbb
    0 x 11004
    -567
    0 x 11017

Log name: Application
Source: ESENT
Date: 16/04/2016 13:51:57
Event ID: 454
Task category: registration/recovery
Level: error
Keywords: Classic
User: n/a
Computer: server.domain
Description:
\\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db SRBHT (1388): database recovery/restore failed with the error unexpected-567.
The event XML:


    454
    2
    3
    0 x 80000000000000

    7034
    Application
    Server


    SRBHT
    1388
    \\.\C:\System volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db:
    -567

I think that these are related to my original question, but any advice would be appreciated.

Thank you

Please post your query to:

https://social.technet.Microsoft.com/forums/

Server issues are better addressed there.

ESXi 4.0 and VMs extremely slow

Hey there.
I installed an ESXi 4.0.0 Build 208167 with German-000 just a few months, there is and he worked there with a normal return (please).
Well, last week, the virtual machines have become performance issues. As an example, windows Explorer takes only a few moments to appear like other tasks such as closing windows systems, or create on SLES11 xterm windows.
I tried to restart my system, but with this, I got new problems: some virtual machines cannot start or became disabled (appears under the name VM and (invalid) appended to the virtual machine).
I try to start other systems, press play and the machine seems to have started, but it remains on 95% for a minute and then, it appears a message called: "the attempted operation is not in the current state (off) happen."
My diary in the var (last lines)
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:07 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:22:15 vmkernel: 0:15:19:26.677 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:15 vmkernel: 0:15:19:26.677 cpu6:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:15 vmkernel: 0:15:19:26.815 cpu6:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu14:4334) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:15 vmkernel: 0:15:19:26.938 cpu14:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:17 vmkernel: 0:15:19:28.790 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:17 vmkernel: 0:15:19:28.790 cpu6:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:17 vmkernel: 0:15:19:28.945 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:18 vmkernel: 0:15:19:29.069 cpu1:5139) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.319 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.319 cpu2:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:26 vmkernel: 0:15:19:37.456 cpu2:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu2:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu2:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu1:4363) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu11:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:26 vmkernel: 0:15:19:37.579 cpu11:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:28 vmkernel: 0:15:19:39.437 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:28 vmkernel: 0:15:19:39.437 cpu14:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:28 vmkernel: 0:15:19:39.581 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:28 vmkernel: 0:15:19:39.704 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:35 vmkernel: 0:15:19:46.078 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:35 vmkernel: 0:15:19:46.078 cpu14:4328) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:35 vmkernel: 0:15:19:46.078 cpu14:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:36 vmkernel: 0:15:19:47.936 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:36 vmkernel: 0:15:19:47.936 cpu14:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:37 vmkernel: 0:15:19:48.085 cpu14:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:37 vmkernel: 0:15:19:48.208 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:37 vmkernel: 0:15:19:48.208 cpu2:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu2:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu1:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu14:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:37 vmkernel: 0:15:19:48.209 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:39 vmkernel: 0:15:19:50.066 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:39 vmkernel: 0:15:19:50.066 cpu4:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:39 vmkernel: 0:15:19:50.216 cpu4:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:39 vmkernel: 0:15:19:50.339 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.547 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.547 cpu4:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:47 vmkernel: 0:15:19:58.739 cpu4:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu1:4097) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu4:4337) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu4:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu1:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:47 vmkernel: 0:15:19:58.862 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:47 vmkernel: 0:15:19:58.863 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:49 vmkernel: 0:15:20:00.719 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:49 vmkernel: 0:15:20:00.720 cpu0:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:49 vmkernel: 0:15:20:00.869 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:49 vmkernel: 0:15:20:00.992 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.242 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.242 cpu4:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:22:58 vmkernel: 0:15:20:09.385 cpu4:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu2:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu2:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:22:58 vmkernel: 0:15:20:09.509 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23 vmkernel: 0:15:20:11.367 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23 vmkernel: 0:15:20:11.367 cpu8:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23 vmkernel: 0:15:20:11.516 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23 vmkernel: 0:15:20:11.639 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:08 vmkernel: 0:15:20:19.877 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:08 vmkernel: 0:15:20:19.877 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:09 vmkernel: 0:15:20:20.026 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu8:4332) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu4:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:09 vmkernel: 0:15:20:20.150 cpu4:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:11 vmkernel: 0:15:20:22.008 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:11 vmkernel: 0:15:20:22.008 cpu2:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:11 vmkernel: 0:15:20:22.157 cpu2:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:11 vmkernel: 0:15:20:22.281 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.512 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.512 cpu2:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:19 vmkernel: 0:15:20:30.650 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:19 vmkernel: 0:15:20:30.773 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.773 cpu0:4325) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:19 vmkernel: 0:15:20:30.773 cpu0:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:19 vmkernel: 0:15:20:30.774 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:19 vmkernel: 0:15:20:30.774 cpu6:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:19 vmkernel: 0:15:20:30.774 cpu6:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:21 vmkernel: 0:15:20:32.625 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:21 vmkernel: 0:15:20:32.625 cpu2:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:21 vmkernel: 0:15:20:32.780 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:21 vmkernel: 0:15:20:32.904 cpu14:5140) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.148 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.148 cpu1:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:30 vmkernel: 0:15:20:41.285 cpu1:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu0:4329) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:30 vmkernel: 0:15:20:41.409 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:32 vmkernel: 0:15:20:43.260 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:32 vmkernel: 0:15:20:43.260 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:32 vmkernel: 0:15:20:43.410 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:32 vmkernel: 0:15:20:43.533 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:40 vmkernel: 0:15:20:51.759 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:40 vmkernel: 0:15:20:51.759 cpu1:4325) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:40 vmkernel: 0:15:20:51.908 cpu1:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu6:4326) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:41 vmkernel: 0:15:20:52.032 cpu6:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:42 vmkernel: 0:15:20:53.883 cpu14:5040) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:42 vmkernel: 0:15:20:53.883 cpu6:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:43 vmkernel: 0:15:20:54.027 cpu6:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:43 vmkernel: 0:15:20:54.150 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.370 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.370 cpu4:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:51 vmkernel: 0:15:21:02.513 cpu4:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4331) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4324) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:23:51 vmkernel: 0:15:21:02.637 cpu0:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:53 vmkernel: 0:15:21:04.489 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:23:53 vmkernel: 0:15:21:04.489 cpu12:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:23:53 vmkernel: 0:15:21:04.638 cpu12:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:23:53 vmkernel: 0:15:21:04.762 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:12.999 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:12.999 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:02 vmkernel: 0:15:21:13.131 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:02 vmkernel: 0:15:21:13.254 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:13.254 cpu12:4332) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:02 vmkernel: 0:15:21:13.254 cpu12:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:02 vmkernel: 0:15:21:13.255 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:02 vmkernel: 0:15:21:13.255 cpu8:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:02 vmkernel: 0:15:21:13.255 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:04 vmkernel: 0:15:21:15.112 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:04 vmkernel: 0:15:21:15.112 cpu6:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:04 vmkernel: 0:15:21:15.249 cpu6:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:04 vmkernel: 0:15:21:15.373 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:11 pass: Activation N5Vmomi10ActivationE:0x5b3c7ea8 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
23 Feb 07:24:11 pass: Arg version: '111 '.
23 Feb 07:24:11 pass: throw vmodl.fault.RequestCanceled
23 Feb 07:24:11 pass: result: (vmodl.fault.RequestCanceled) {dynamicType = < unset >, faultCause = (vmodl. {MethodFault) null, msg = "",}
23 Feb 07:24:11 pass: PendingRequest: HTTP Transaction failed, closes the connection: N7Vmacore15SystemExceptionE (connection reset by peer)
23 Feb 07:24:12 vmkernel: 0:15:21:23.622 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:12 vmkernel: 0:15:21:23.622 cpu0:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:12 vmkernel: 0:15:21:23.820 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:12 vmkernel: 0:15:21:23.943 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:12 vmkernel: 0:15:21:23.944 cpu8:4334) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:21 vmkernel: 0:15:21:32.199 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:21 vmkernel: 0:15:21:32.199 cpu8:4338) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:21 vmkernel: 0:15:21:32.342 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu6:4324) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu6:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu2:4331) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:21 vmkernel: 0:15:21:32.466 cpu2:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:23 vmkernel: 0:15:21:34.323 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:23 vmkernel: 0:15:21:34.323 cpu8:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:23 vmkernel: 0:15:21:34.467 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:23 vmkernel: 0:15:21:34.590 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:31 vmkernel: 0:15:21:42.822 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:31 vmkernel: 0:15:21:42.822 cpu8:4328) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:31 vmkernel: 0:15:21:42.971 cpu8:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu8:4332) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:32 vmkernel: 0:15:21:43.095 cpu2:4327) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:32 vmkernel: 0:15:21:43.096 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:33 vmkernel: 0:15:21:44.953 cpu14:6103) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:33 vmkernel: 0:15:21:44.953 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:34 vmkernel: 0:15:21:45.078 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:34 vmkernel: 0:15:21:45.202 cpu14:6103) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.433 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.433 cpu2:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:42 vmkernel: 0:15:21:53.583 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:42 vmkernel: 0:15:21:53.706 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.706 cpu0:4331) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:42 vmkernel: 0:15:21:53.707 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:44 vmkernel: 0:15:21:55.558 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:44 vmkernel: 0:15:21:55.558 cpu2:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:44 vmkernel: 0:15:21:55.695 cpu2:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:44 vmkernel: 0:15:21:55.819 cpu14:6105) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.128 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.128 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:53 vmkernel: 0:15:22:04.284 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:53 vmkernel: 0:15:22:04.407 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.407 cpu2:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:24:53 vmkernel: 0:15:22:04.408 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:55 vmkernel: 0:15:22:06.265 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:24:55 vmkernel: 0:15:22:06.265 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:24:55 vmkernel: 0:15:22:06.414 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:24:55 vmkernel: 0:15:22:06.538 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.645 cpu14:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.645 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:01 vmkernel: 0:15:22:12.794 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu14:5192) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu2:4327) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu14:5192) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:01 vmkernel: 0:15:22:12.918 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:03 vmkernel: 0:15:22:14.769 cpu14:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:03 vmkernel: 0:15:22:14.770 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:03 vmkernel: 0:15:22:14.907 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:04 vmkernel: 0:15:22:15.031 cpu14:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.268 cpu14:5138) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.268 cpu3:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:12 vmkernel: 0:15:22:23.411 cpu3:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:12 vmkernel: 0:15:22:23.535 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.535 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu14:4984) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu4:4325) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:12 vmkernel: 0:15:22:23.536 cpu4:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:14 vmkernel: 0:15:22:25.387 cpu14:5040) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:14 vmkernel: 0:15:22:25.387 cpu3:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:14 vmkernel: 0:15:22:25.536 cpu3:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:14 vmkernel: 0:15:22:25.660 cpu14:5040) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:22 vmkernel: 0:15:22:33.873 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:22 vmkernel: 0:15:22:33.873 cpu1:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:23 vmkernel: 0:15:22:34.023 cpu1:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu3:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu3:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:23 vmkernel: 0:15:22:34.147 cpu0:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:23 vmkernel: 0:15:22:34.148 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:24 vmkernel: 0:15:22:35.998 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:24 vmkernel: 0:15:22:35.998 cpu8:4328) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:25 vmkernel: 0:15:22:36.154 cpu8:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:25 vmkernel: 0:15:22:36.278 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.402 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.402 cpu1:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:31 vmkernel: 0:15:22:42.545 cpu1:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:31 vmkernel: 0:15:22:42.669 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.669 cpu8:4333) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:31 vmkernel: 0:15:22:42.669 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:31 vmkernel: 0:15:22:42.670 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:31 vmkernel: 0:15:22:42.670 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:31 vmkernel: 0:15:22:42.670 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:33 vmkernel: 0:15:22:44.520 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:33 vmkernel: 0:15:22:44.520 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:33 vmkernel: 0:15:22:44.670 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:33 vmkernel: 0:15:22:44.794 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.037 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.037 cpu0:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:42 vmkernel: 0:15:22:53.180 cpu0:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:42 vmkernel: 0:15:22:53.304 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.304 cpu2:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu2:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu14:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu2:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:42 vmkernel: 0:15:22:53.305 cpu2:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:44 vmkernel: 0:15:22:55.156 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:44 vmkernel: 0:15:22:55.156 cpu2:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:44 vmkernel: 0:15:22:55.305 cpu2:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:44 vmkernel: 0:15:22:55.429 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.660 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.660 cpu1:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:52 vmkernel: 0:15:23:03.804 cpu1:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu2:4336) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu2:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu14:4110) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:25:52 vmkernel: 0:15:23:03.928 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:54 vmkernel: 0:15:23:05.779 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:25:54 vmkernel: 0:15:23:05.779 cpu8:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:25:54 vmkernel: 0:15:23:05.928 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:25:55 vmkernel: 0:15:23:06.052 cpu14:188206) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.117 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.117 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:01 vmkernel: 0:15:23:12.254 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu14:6090) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu1:4327) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:01 vmkernel: 0:15:23:12.379 cpu1:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:03 vmkernel: 0:15:23:14.229 cpu14:5009) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:03 vmkernel: 0:15:23:14.230 cpu0:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:03 vmkernel: 0:15:23:14.409 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:03 vmkernel: 0:15:23:14.533 cpu14:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:11 vmkernel: 0:15:23:22.776 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:11 vmkernel: 0:15:23:22.776 cpu2:4325) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:11 vmkernel: 0:15:23:22.931 cpu2:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:12 vmkernel: 0:15:23:23.056 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:13 vmkernel: 0:15:23:24.913 cpu5:185904) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:13 vmkernel: 0:15:23:24.913 cpu8:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:14 vmkernel: 0:15:23:25.062 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:14 vmkernel: 0:15:23:25.186 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.423 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.423 cpu6:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:22 vmkernel: 0:15:23:33.560 cpu6:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu5:6088) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu5:6088) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:22 vmkernel: 0:15:23:33.685 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:24 vmkernel: 0:15:23:35.542 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:24 vmkernel: 0:15:23:35.542 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:24 vmkernel: 0:15:23:35.685 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:24 vmkernel: 0:15:23:35.809 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:30 vmkernel: 0:15:23:41.922 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:30 vmkernel: 0:15:23:41.922 cpu6:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:31 vmkernel: 0:15:23:42.059 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:31 vmkernel: 0:15:23:42.183 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:31 vmkernel: 0:15:23:42.183 cpu0:4327) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:31 vmkernel: 0:15:23:42.183 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:31 vmkernel: 0:15:23:42.184 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:31 vmkernel: 0:15:23:42.184 cpu0:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:31 vmkernel: 0:15:23:42.184 cpu4:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:33 vmkernel: 0:15:23:44.040 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:33 vmkernel: 0:15:23:44.040 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:33 vmkernel: 0:15:23:44.190 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:33 vmkernel: 0:15:23:44.314 cpu5:6087) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.569 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.569 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:41 vmkernel: 0:15:23:52.718 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu0:4325) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu0:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:41 vmkernel: 0:15:23:52.843 cpu2:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:41 vmkernel: 0:15:23:52.844 cpu2:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:43 vmkernel: 0:15:23:54.699 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:43 vmkernel: 0:15:23:54.699 cpu10:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:43 vmkernel: 0:15:23:54.903 cpu10:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:44 vmkernel: 0:15:23:55.027 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.258 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.258 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:52 vmkernel: 0:15:24:03.395 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu14:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu14:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:26:52 vmkernel: 0:15:24:03.520 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:54 vmkernel: 0:15:24:05.377 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:26:54 vmkernel: 0:15:24:05.377 cpu10:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:26:54 vmkernel: 0:15:24:05.514 cpu10:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:26:54 vmkernel: 0:15:24:05.638 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27 vmkernel: 0:15:24:11.733 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27 vmkernel: 0:15:24:11.733 cpu0:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27 vmkernel: 0:15:24:11.888 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu5:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4327) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu5:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4331) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:01 vmkernel: 0:15:24:12.012 cpu2:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:02 vmkernel: 0:15:24:13.869 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:02 vmkernel: 0:15:24:13.869 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:03 vmkernel: 0:15:24:14.013 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:03 vmkernel: 0:15:24:14.137 cpu5:4367) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.392 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.392 cpu8:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:11 vmkernel: 0:15:24:22.541 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4326) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:11 vmkernel: 0:15:24:22.666 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:13 vmkernel: 0:15:24:24.516 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:13 vmkernel: 0:15:24:24.516 cpu10:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:13 vmkernel: 0:15:24:24.660 cpu10:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:13 vmkernel: 0:15:24:24.784 cpu5:186428) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.015 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.015 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:22 vmkernel: 0:15:24:33.158 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu10:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu10:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu5:4101) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu2:4324) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:22 vmkernel: 0:15:24:33.283 cpu2:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:24 vmkernel: 0:15:24:35.134 cpu5:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:24 vmkernel: 0:15:24:35.134 cpu1:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:24 vmkernel: 0:15:24:35.295 cpu1:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:24 vmkernel: 0:15:24:35.419 cpu5:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.507 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.507 cpu0:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:30 vmkernel: 0:15:24:41.675 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:30 vmkernel: 0:15:24:41.799 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.799 cpu6:4331) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:30 vmkernel: 0:15:24:41.799 cpu6:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:30 vmkernel: 0:15:24:41.800 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:30 vmkernel: 0:15:24:41.800 cpu0:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:30 vmkernel: 0:15:24:41.800 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:32 vmkernel: 0:15:24:43.650 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:32 vmkernel: 0:15:24:43.650 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:32 vmkernel: 0:15:24:43.793 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:32 vmkernel: 0:15:24:43.918 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.137 cpu11:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.137 cpu6:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:41 vmkernel: 0:15:24:52.280 cpu6:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu11:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu6:4326) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu6:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu11:11155) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu14:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:41 vmkernel: 0:15:24:52.405 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:42 pass: created task: haTask-304 - vim.VirtualMachine.powerOn - 306
23 Feb 07:27:42 pass: 2010-02-23 07:27:42.209 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' power on request received
23 Feb 07:27:51 vmkernel: 0:15:25:02.742 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:51 vmkernel: 0:15:25:02.742 cpu0:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:51 vmkernel: 0:15:25:02.891 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:52 vmkernel: 0:15:25:03.016 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:52 vmkernel: 0:15:25:03.016 cpu6:4335) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:27:52 vmkernel: 0:15:25:03.016 cpu6:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:52 vmkernel: 0:15:25:03.017 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:52 vmkernel: 0:15:25:03.017 cpu0:4326) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:27:52 vmkernel: 0:15:25:03.017 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:53 vmkernel: 0:15:25:04.873 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:27:53 vmkernel: 0:15:25:04.873 cpu0:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:27:54 vmkernel: 0:15:25:05.022 cpu0:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:27:54 vmkernel: 0:15:25:05.147 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.246 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.246 cpu0:4337) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28 vmkernel: 0:15:25:11.390 cpu0:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu2:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu2:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu6:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28 vmkernel: 0:15:25:11.515 cpu6:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:02 vmkernel: 0:15:25:13.365 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:02 vmkernel: 0:15:25:13.365 cpu8:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:02 vmkernel: 0:15:25:13.556 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:02 vmkernel: 0:15:25:13.681 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:09 sfcb [6070]: peripheral device ID storelib physical: 0xD
23 Feb 07:28:10 vmkernel: 0:15:25:21.924 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:10 vmkernel: 0:15:25:21.924 cpu0:4329) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:11 vmkernel: 0:15:25:22.067 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu8:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu8:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu14:4328) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:11 vmkernel: 0:15:25:22.192 cpu14:4328) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:13 vmkernel: 0:15:25:24.042 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:13 vmkernel: 0:15:25:24.042 cpu0:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:13 vmkernel: 0:15:25:24.186 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:13 vmkernel: 0:15:25:24.310 cpu11:4107) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:20 pass: HostCtl Exception when the collection of statistics: SysinfoException: node (VSI_NODE_sched_cpuClients_numVcpus); (Bad0001) status = failure; Message = Instance (1): 0 Input (0)
23 Feb 07:28:21 vmkernel: 0:15:25:32.529 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:21 vmkernel: 0:15:25:32.529 cpu0:4330) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:21 vmkernel: 0:15:25:32.672 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu0:4326) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu14:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:21 vmkernel: 0:15:25:32.797 cpu14:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:23 vmkernel: 0:15:25:34.653 cpu11:6089) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:23 vmkernel: 0:15:25:34.653 cpu2:4325) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:23 vmkernel: 0:15:25:34.815 cpu2:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:30 vmkernel: 0:15:25:41.045 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:30 vmkernel: 0:15:25:41.045 cpu0:4335) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:30 vmkernel: 0:15:25:41.195 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:30 vmkernel: 0:15:25:41.319 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:30 vmkernel: 0:15:25:41.319 cpu0:4330) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu0:4330) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu6:4326) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:30 vmkernel: 0:15:25:41.320 cpu6:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:32 vmkernel: 0:15:25:43.176 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:32 vmkernel: 0:15:25:43.176 cpu9:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:32 vmkernel: 0:15:25:43.325 cpu9:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:32 vmkernel: 0:15:25:43.450 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu8:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu2:4337) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:38 vmkernel: 0:15:25:49.854 cpu2:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:40 vmkernel: 0:15:25:51.710 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:40 vmkernel: 0:15:25:51.711 cpu6:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:40 vmkernel: 0:15:25:51.848 cpu6:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu9:4339) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu9:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu6:4325) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:40 vmkernel: 0:15:25:51.973 cpu6:4325) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:42 vmkernel: 0:15:25:53.829 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:42 vmkernel: 0:15:25:53.829 cpu6:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:43 vmkernel: 0:15:25:54.044 cpu6:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:43 vmkernel: 0:15:25:54.169 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.400 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.400 cpu0:4326) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:28:51 vmkernel: 0:15:26:02.531 cpu0:4326) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu9:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu9:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu6:4336) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:28:51 vmkernel: 0:15:26:02.656 cpu6:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:28:52 vmkernel: 0:15:26:03.467 cpu4:68711) megasas: sn 352358 cmd = 0 x 28 attempts ABORT = tmo 0 = 0
23 Feb 07:28:52 vmkernel: 0:15:26:03.467 cpu4:68711) < 5 > 0: megasas: RESET 352358 cmd = 28 attempts sn = 0
23 Feb 07:28:53 vmkernel: 0:15:26:04.512 cpu5:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:28:54 vmkernel: 0:15:26:05.491 cpu0:68711) megasas < 5 >: successful reset
23 Feb 07:29:02 vmkernel: 0:15:26:12.999 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:02 vmkernel: 0:15:26:12.999 cpu14:4339) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:02 vmkernel: 0:15:26:13.136 cpu14:4339) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu12:4334) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu12:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu0:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:02 vmkernel: 0:15:26:13.261 cpu0:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:04 vmkernel: 0:15:26:15.117 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:04 vmkernel: 0:15:26:15.117 cpu0:4327) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:04 vmkernel: 0:15:26:15.261 cpu0:4327) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:04 vmkernel: 0:15:26:15.386 cpu7:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.616 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.616 cpu0:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:12 vmkernel: 0:15:26:23.754 cpu0:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu0:4329) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu0:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu8:4332) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:12 vmkernel: 0:15:26:23.879 cpu8:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:12 vmkernel: 0:15:26:23.995 cpu0:190779) megasas: ABORT sn 352531 cmd = attempts 0x2a = tmo 0 = 0
23 Feb 07:29:12 vmkernel: 0:15:26:23.995 cpu0:190779) < 5 > 0: megasas: RESET sn 352531 cmd = attempts 2 a = 0
23 Feb 07:29:14 vmkernel: 0:15:26:25.735 cpu7:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.293 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.293 cpu12:4334) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:23 vmkernel: 0:15:26:34.442 cpu12:4334) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:23 vmkernel: 0:15:26:34.567 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.567 cpu1:4337) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu1:4337) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu4:4363) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu8:4333) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:23 vmkernel: 0:15:26:34.568 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:25 vmkernel: 0:15:26:36.424 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:25 vmkernel: 0:15:26:36.424 cpu2:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:25 vmkernel: 0:15:26:36.574 cpu2:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:25 vmkernel: 0:15:26:36.699 cpu4:6389) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:32 pass: 2010-02-23 07:29:32.555 verbose 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas03/petas03.vmx" unknown unexpected toolsVersionStatus, use status offline guestToolsCurrent
23 Feb 07:29:32 pass: 2010-02-23 07:29:32.562 verbose 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" unknown unexpected toolsVersionStatus, use status offline guestToolsCurrent
23 Feb 07:29:32 pass: 2010-02-23 07:29:32.568 verbose 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx" unknown unexpected toolsVersionStatus, use status offline guestToolsCurrent
23 Feb 07:29:34 vmkernel: 0:15:26:45.030 cpu4:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:34 vmkernel: 0:15:26:45.030 cpu12:4332) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:34 vmkernel: 0:15:26:45.161 cpu12:4332) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:34 pass: created task: haTask-80 - vim.VirtualMachine.powerOn - 315
23 Feb 07:29:34 spend: 2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' power on request received
23 Feb 07:29:34 spend: 2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' ethernet reconfigures protective is required
23 Feb 07:29:34 pass: 257 of the event: petas01 on the RTHUS7002.rintra.ruag.com ha-Data Center host begins
23 Feb 07:29:34 spend: 2010-02-23 07:29:34.173 1680BB90 info 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
23 Feb 07:29:34 vmkernel: 0:15:26:45.286 cpu4:5039) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.635 cpu4:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.635 cpu8:4333) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:44 vmkernel: 0:15:26:55.785 cpu8:4333) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu4:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu8:4338) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu8:4338) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu4:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu6:4329) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:44 vmkernel: 0:15:26:55.910 cpu6:4329) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:46 vmkernel: 0:15:26:57.766 cpu4:6104) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:46 vmkernel: 0:15:26:57.766 cpu0:4324) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:46 vmkernel: 0:15:26:57.915 cpu0:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:47 vmkernel: 0:15:26:58.040 cpu4:4363) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.276 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.276 cpu6:4331) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:55 vmkernel: 0:15:27:06.414 cpu6:4331) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:55 vmkernel: 0:15:27:06.539 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.539 cpu2:4324) megasas_hotplug_work < 6 > [6]: 0x006e event code
23 Feb 07:29:55 vmkernel: 0:15:27:06.539 cpu2:4324) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:55 vmkernel: 0:15:27:06.540 cpu1:9738) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:55 vmkernel: 0:15:27:06.540 cpu4:4335) megasas_hotplug_work < 6 > [6]: 0x005d event code
23 Feb 07:29:55 vmkernel: 0:15:27:06.540 cpu4:4335) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:57 vmkernel: 0:15:27:08.395 cpu1:190710) megasas_service_aen < 6 > [6]: NEA received
23 Feb 07:29:57 vmkernel: 0:15:27:08.395 cpu3:4336) megasas_hotplug_work < 6 > [6]: code event 0 x 0071
23 Feb 07:29:57 vmkernel: 0:15:27:08.538 cpu3:4336) megasas_hotplug_work < 6 > [6]: registered AIA
23 Feb 07:29:57 vmkernel: 0:15:27:08.664 cpu1:190710) megasas_service_aen < 6 > [6]: NEA received
And then there is my hostd.log
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': open with success (21) size = 53687091200, hd = 0. Type 3
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': closed.
Reminder of Foundry recorded on 4
Reminder of Foundry recorded on 17
Reminder of Foundry recorded on 5
Reminder of Foundry recorded on 11
Reminder of Foundry recorded on 12
Reminder of Foundry recorded 13
Reminder of Foundry recorded on 14
Reminder of Foundry recorded on 15
Reminder of Foundry recorded 26
Reminder of Foundry saved on 16
2010-02-23 06:52:24.922 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Lack of recall tolerance status received
2010-02-23 06:52:24.922 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Record/replay reminder of the State received
2010-02-23 06:52:24.922 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 5, 2
2010-02-23 06:52:24.922 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" The State of Transition (VM_STATE_INITIALIZING-> VM_STATE_OFF)
Cannot find the content reflected in extended config xml.
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': open with success (21) size = 53687091200, hd = 0. Type 3
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': closed.
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': open success (23) size = 53687091200, hd = 0. Type 3
DISKLIB-VMFS: ' / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05/app-back-05-flat.vmdk ': closed.
2010-02-23 06:52:35.532 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Version initial tools: 3:guestToolsNotInstalled
2010-02-23 06:52:35.532 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Overhead VM predicted: 118587392 bytes
2010-02-23 06:52:35.532 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Initialized virtual machine.
ModeMgr::End: op = current, normal = normal, count = 2
Task completed: success of haTask-ha-folder-vm-vim.Folder.createVm-243 status
Event 244: Created the virtual machine on RTHUS7002.rintra.ruag.com ha-data center
2010-02-23 06:52:35.533 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Create worker thread successfully completed
2010-02-23 06:52:35.539 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
The task was created: haTask-320 - vim.VirtualMachine.powerOn - 246
2010-02-23 06:52:53.868 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Power on request received
2010-02-23 06:52:53.868 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Reconfigure the ethernet support if necessary
Event 245: app-back-05-neu on host RTHUS7002.rintra.ruag.com ha-data center begins
2010-02-23 06:52:53.868 info 5B168B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 1
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 06:52:53.899 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' PowerOn request queue
2010-02-23 06:52:53.913 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 7, 6
/VM/ #1dea389a74a8b231 /: VMHSVMCbPower: status of the VM powerOn with option soft
2010-02-23 06:52:53.913 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 190710
2010-02-23 06:52:53.965 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" An established connection.
Airfare to CIMOM version 1.0, root user
PersistAllDvsInfo called
2010-02-23 06:53:20.200 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Paths on the virtual machine of mounting connection: /db/connection / #14bc.
2010-02-23 06:53:20.248 5B1EAB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' No upgrade required
2010-02-23 06:53:20.253 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Completion of Mount VM for vm.
2010-02-23 06:53:20.254 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Mount VM Complete: OK
Airfare to CIMOM version 1.0, root user
2010-02-23 06:54:45.556 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' MKS ready for connections: true
2010-02-23 06:54:45.556 info 1688CB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Information request: insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1176 x 885 to 16 bits per pixel. To use the configured maximum resolution of 2360 x 1770 to 16 bits per pixel, increase the amount of video memory allocated to this virtual machine by setting svga.vramSize = "16708800" in the virtual machine configuration file.
Id: 0: Type: 2, default: 0, number of options: 1
2010-02-23 06:54:45.556 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:54:45.556 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' No upgrade required
2010-02-23 06:54:45.556 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 7, 6
VixVM_AnswerMessage returned 0
2010-02-23 06:54:45.562 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:54:45.562 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 7, 6
Event 246: Message on app-back-05-neu on RTHUS7002.rintra.ruag.com ha-Datacenter: insufficient video RAM. The maximum resolution of the virtual machine will be limited to 1176 x 885 to 16 bits per pixel. To use the configured maximum resolution of 2360 x 1770 to 16 bits per pixel, increase the amount of video memory allocated to this virtual machine by setting svga.vramSize = "16708800" in the virtual machine configuration file.
2010-02-23 06:54:45.562 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Auto-répondu insufficient video RAM issue. The maximum resolution of the virtual machine will be limited to 1176 x 885 to 16 bits per pixel. To use the configured maximum resolution of 2360 x 1770 to 16 bits per pixel, increase the amount of video memory allocated to this virtual machine by setting svga.vramSize = "16708800" in the virtual machine configuration file.
2010-02-23 06:55:26.096 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' State of the Tools version: noTools
2010-02-23 06:55:26.096 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" VMX status has been defined.
2010-02-23 06:55:26.097 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:55:26.097 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' The event of Imgcust read vmdb tree values State = 0, errorCode = 0, errorMsgSize = 0
2010-02-23 06:55:26.097 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Disconnect the current control.
2010-02-23 06:55:26.097 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Tools running status changed to: keep
2010-02-23 06:55:41.030 info 1698FB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Connected to testAutomation-fd, sent remotely end pid: 190710
2010-02-23 06:55:41.032 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Current state recovered VM Foundry 4, 8
2010-02-23 06:55:41.034 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' No upgrade required
247 event: app-back-05-neu on RTHUS7002.rintra.ruag.com ha-data center power is on
2010-02-23 06:55:41.036 info 5B0E6B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" The State of Transition (VM_STATE_POWERING_ON-> VM_STATE_ON)
Change of State received for VM ' 320'
2010-02-23 06:55:41.065 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Actual VM overhead: 88780800 bytes
2010-02-23 06:55:41.139 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Time to pick up some config: 73 (MS)
Task completed: success of status haTask-320 - vim.VirtualMachine.powerOn - 246
Add vm 320 poweredOnVms list
2010-02-23 06:55:43.211 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Time to pick up some config: 67 (MS)
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. Using English.
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. With the help of C.
Event 248: [email protected] user
2010-02-23 06:55:47.873 info 5B0E6B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 06:55:55.843 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 1
2010-02-23 06:56:00.279 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Actual VM overhead: 89305088 bytes
RefreshVms overhead to 1 VM update
Airfare to CIMOM version 1.0, root user
2010-02-23 06:56:40.293 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Actual VM overhead: 88829952 bytes
RefreshVms overhead to 1 VM update
Ability to root pool changed 18302 MHz / 43910MB at 18302 MHz / 43909MB
Airfare to CIMOM version 1.0, root user
PersistAllDvsInfo called
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 224" failed.
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 224" failed.
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 240" failed.
Rising with name = "haTask - vim.SearchIndex.findByInventoryPath - 240" failed.
Airfare to CIMOM version 1.0, root user
FetchSwitches: added 0 items
FetchDVPortgroups: added 0 items
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43909MB at 18302 MHz / 43908MB
2010-02-23 07:01:46.927 168CDB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:47.586 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petaw02/petaw02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:47.593 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petaw01/petaw01.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:48.412 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas03/petas03.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:48.418 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:48.425 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:01:50.707 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 0
The task was created: haTask-304 - vim.VirtualMachine.powerOn - 268
2010-02-23 07:01:52.340 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Power on request received
2010-02-23 07:01:52.340 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Reconfigure the ethernet support if necessary
Event 249: PETA-route on the RTHUS7002.rintra.ruag.com ha-Data Center host starts
2010-02-23 07:01:52.341 info 1680BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 2
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 07:01:59.118 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' PowerOn request queue
2010-02-23 07:02:00.513 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
Airfare to CIMOM version 1.0, root user
2010-02-23 07:02:07.643 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 7, 6
/VM/ #c27a9ee2a691ac1a /: VMHSVMCbPower: status of the VM powerOn with option soft
CloseSession called for the session id = 5206e96f - 88-2e3f-9187-60932847859f 0c
Rising with name = "haTask-304 - vim.VirtualMachine.powerOn - 129 ' failed.
GetPropertyProvider failed for haTask-304 - vim.VirtualMachine.powerOn - 129
Rising with name = "haTask-256 - vim.VirtualMachine.reset - 124 ' failed.
GetPropertyProvider failed for haTask-256 - vim.VirtualMachine.reset - 124
Event 250: Rzhmi_ope disconnected user
2010-02-23 07:02:24.668 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 192683
Rising with name = "haTask-ha-folder-vm-vim.Folder.createVm-243" failed.
Rising with name = "haTask-ha-folder-vm-vim.Folder.createVm-243" failed.
2010-02-23 07:02:58.683 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" An established connection.
PersistAllDvsInfo called
Ability to root pool changed 18302 MHz / 43908MB at 18302 MHz / 43907MB
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43907MB in 18302 MHz / 43909MB
Airfare to CIMOM version 1.0, root user
Rising with name = "haTask-320 - vim.VirtualMachine.powerOn - 246" failed.
Rising with name = "haTask-320 - vim.VirtualMachine.powerOn - 246" failed.
FoundryVMDBPowerOpCallback: Op to VMDB reports power failed for VM /vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx with error msg = "the operation has timed out" and error code-41.
2010-02-23 07:06:02.208 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 5, 2
Have not power Op: error: (3006) the virtual machine must be turned on
2010-02-23 07:06:02.209 5B22BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" Failed operation
Event 251: Cannot power on PETA-router on RTHUS7002.rintra.ruag.com ha-data center. A general error occurred:
2010-02-23 07:06:02.209 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_POWERING_ON-> VM_STATE_OFF)
ModeMgr::End: op = current, normal = normal, count = 3
Task completed: error status haTask-304 - vim.VirtualMachine.powerOn - 268
Airfare to CIMOM version 1.0, root user
PersistAllDvsInfo called
Ability to root pool changed 18302 MHz / 43909MB at 18302 MHz / 43906MB
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43906MB at 18302 MHz / 43908MB
Activation N5Vmomi10ActivationE:0x5b68a8b0 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
ARG version:
'93.
Launch vmodl.fault.RequestCanceled
Result:
{(vmodl.fault.RequestCanceled)
dynamicType = < unset >
faultCause = (vmodl. NULL in MethodFault),
MSG = ""
}
PendingRequest: HTTP Transaction failed, closes the connection: N7Vmacore15SystemExceptionE (connection reset by peer)
Ability to root pool changed 18302 MHz / 43908MB at 18302 MHz / 43909MB
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. Using English.
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. With the help of C.
Event 252: [email protected] user
2010-02-23 07:13:13.852 info 5B1EAB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Airfare for mks to user connections: rzhmi_ope
PersistAllDvsInfo called
2010-02-23 07:13:19.794 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 1
2010-02-23 07:14:18.185 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 0
Activation N5Vmomi10ActivationE:0x5c0f4dc0 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
ARG version:
« 3 »
CloseSession called for the session id = 528c7c0f-5bce-6ea5-CE22-e4927fab2c89
Launch vmodl.fault.RequestCanceled
Result:
{(vmodl.fault.RequestCanceled)
dynamicType = < unset >
faultCause = (vmodl. NULL in MethodFault),
MSG = ""
}
Event 253: Rzhmi_ope disconnected user
Error reading the client while you wait header: N7Vmacore15SystemExceptionE (connection reset by peer)
Error reading the client while you wait header: N7Vmacore15SystemExceptionE (connection reset by peer)
Error reading the client while you wait header: N7Vmacore15SystemExceptionE (connection reset by peer)
2010-02-23 07:14:20.843 info 1680BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 07:14:26.122 5AF25DC0 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 1
Airfare to CIMOM version 1.0, root user
Rising with name = "haTask-304 - vim.VirtualMachine.powerOn - 268 ' failed.
Rising with name = "haTask-304 - vim.VirtualMachine.powerOn - 268 ' failed.
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
PersistAllDvsInfo called
CloseSession called for the session id = 520edca0-62aa - 19 c 8-8c9d-bd710bd6c882
Event in 254: Rzhmi_ope disconnected user
2010-02-23 07:19:01.520 5B0A5B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/app-back-05-neu/app-back-05-neu.vmx' Number of connections new MKS: 0
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. Using English.
Requested locale "and/or derived from locale ' en_US.utf - 8', is not compatible with the operating system. With the help of C.
Event 255: [email protected] user
2010-02-23 07:19:05.616 info 5B0E6B90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Airfare for mks to user connections: rzhmi_ope
Airfare to CIMOM version 1.0, root user
2010-02-23 07:19:11.260 5B127B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 1
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
PersistAllDvsInfo called
Airfare to CIMOM version 1.0, root user
Activation N5Vmomi10ActivationE:0x5b3c7ea8 : invoke made on vmodl.query.PropertyCollector:ha - property-collector
ARG version:
"111".
Launch vmodl.fault.RequestCanceled
Result:
{(vmodl.fault.RequestCanceled)
dynamicType = < unset >
faultCause = (vmodl. NULL in MethodFault),
MSG = ""
}
PendingRequest: HTTP Transaction failed, closes the connection: N7Vmacore15SystemExceptionE (connection reset by peer)
Airfare to CIMOM version 1.0, root user
Airfare to CIMOM version 1.0, root user
The task was created: haTask-304 - vim.VirtualMachine.powerOn - 306
2010-02-23 07:27:42.209 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Power on request received
2010-02-23 07:27:42.209 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Reconfigure the ethernet support if necessary
Event 256: PETA-route on the RTHUS7002.rintra.ruag.com ha-Data Center host starts
2010-02-23 07:27:42.210 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 2
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 07:27:49.686 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' PowerOn request queue
2010-02-23 07:27:58.217 1690EB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 7, 6
/VM/ #c27a9ee2a691ac1a /: VMHSVMCbPower: status of the VM powerOn with option soft
Airfare to CIMOM version 1.0, root user
PersistAllDvsInfo called
2010-02-23 07:28:15.230 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 191945
HostCtl Exception while collecting statistics: SysinfoException: node (VSI_NODE_sched_cpuClients_numVcpus); (Bad0001) status = failure; Message = Instance (1): 0 Input (0)
2010-02-23 07:28:34.614 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' The Tools version state: ok
2010-02-23 07:28:34.616 168CDB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' MKS ready for connections: false
2010-02-23 07:28:34.660 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Number of connections new MKS: 0
2010-02-23 07:28:34.782 info 5AF25DC0 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Airfare for mks to user connections: rzhmi_ope
2010-02-23 07:28:49.390 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" An established connection.
2010-02-23 07:29:04.550 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Overhead VM predicted: 143904768 bytes
RefreshVms overhead to 1 VM update
2010-02-23 07:29:29.573 verbose 1690EB90 ' vm: / vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_Radius + Jg - CA/Test_Radius + Jg - CA.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:29:32.555 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas03/petas03.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:29:32.562 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
2010-02-23 07:29:32.568 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/petas02/petas02.vmx' Unknown, unexpected toolsVersionStatus use guestToolsCurrent of the offline state
The task was created: haTask-80 - vim.VirtualMachine.powerOn - 315
2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Power on request received
2010-02-23 07:29:34.172 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Reconfigure the ethernet support if necessary
Event 257: petas01 on the RTHUS7002.rintra.ruag.com ha-Data Center host begins
2010-02-23 07:29:34.173 1680BB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" The State of Transition (VM_STATE_OFF-> VM_STATE_POWERING_ON)
ModeMgr::Begin: op = current, normal = normal, count = 3
Load: Existing file loading: /etc/vmware/license.cfg
2010-02-23 07:29:34.327 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' PowerOn request queue
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43909MB at 18302 MHz / 43910MB
Airfare to CIMOM version 1.0, root user
Ability to root pool changed 18302 MHz / 43910MB at 18302 MHz / 43909MB
HostCtl Exception while collecting statistics of network for vm 256: SysinfoException: node (VSI_NODE_net_openPorts_type); (Bad0001) status = failure; Message = cannot get Int
2010-02-23 07:31:52.964 1688CB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' Current state recovered VM Foundry 7, 6
/VM/ #dd20eb79a599aa61 /: VMHSVMCbPower: status of the VM powerOn with option soft
2010-02-23 07:31:52.984 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" VMHS: Exec () ING/bin/vmx
VMHS: VMKernel_ForkExec (/ bin/vmx, flag = 1): rc = 0 pid = 200813
FoundryVMDBPowerOpCallback: Op to VMDB reports power failed for VM /vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx with error msg = "the operation has timed out" and error code-41.
2010-02-23 07:31:52.985 5B168B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx' Current state recovered VM Foundry 5, 2
Have not power Op: error: (3006) the virtual machine must be turned on
2010-02-23 07:31:52.985 5B22BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" Failed operation
Event 258: Cannot power on PETA-router on RTHUS7002.rintra.ruag.com ha-data center. A general error occurred:
2010-02-23 07:31:52.986 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/PETA-Router/PETA-Router.vmx" The State of Transition (VM_STATE_POWERING_ON-> VM_STATE_OFF)
ModeMgr::End: op = current, normal = normal, count = 4
Task completed: error status haTask-304 - vim.VirtualMachine.powerOn - 306
vmdbPipe_Streams could not read: OVL_STATUS_EOF
2010-02-23 07:31:52.988 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' No upgrade required
2010-02-23 07:31:52.989 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Disconnect the current control.
2010-02-23 07:31:52.989 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Disassembly of the virtual machine.
2010-02-23 07:31:52.990 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" VMDB disassemble insiders.
2010-02-23 07:31:52.990 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" VM complete disassembly.
2010-02-23 07:31:53.000 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Mt. state values have changed.
2010-02-23 07:31:53.000 1680BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Failed to get resource for a motor home on VM settings
There is no worldId 4294967295 world
2010-02-23 07:31:53.001 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Mt. state values have changed.
2010-02-23 07:31:53.002 info 1676AB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Reloading configuration state.
2010-02-23 07:31:53.106 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" An established connection.
2010-02-23 07:32:24.650 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" Paths on the virtual machine of mounting connection: /db/connection/#158 d.
TAKEN 2 (13)
client closed connection detected recv
Intake automation detected ready for VM (/ vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx)
2010-02-23 07:32:24.709 5B1A9B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx' No upgrade required
2010-02-23 07:32:24.720 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" Completion of Mount VM for vm.
2010-02-23 07:32:24.721 1676AB90 info "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Test_DHCP/Test_DHCP.vmx" Mount VM Complete: OK
2010-02-23 07:32:24.777 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 31779 (MS)
2010-02-23 07:32:24.782 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Current state recovered VM Foundry 5, 2
2010-02-23 07:32:24.782 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Current state recovered VM Foundry 5, 2
2010-02-23 07:32:24.849 1690EB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:24.850 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Receipt Foundry power state update 5
2010-02-23 07:32:24.850 info 5B22BB90 "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" The State of Transition (VM_STATE_ON-> VM_STATE_OFF)
ModeMgr::End: op = current, normal = normal, count = 3
Change of State received for VM ' 256'
2010-02-23 07:32:24.850 5B22BB90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Could not find activation record, user unknown event.
Event 259: Std-Server on RTHUS7002.rintra.ruag.com ha-data center is turned off
2010-02-23 07:32:24.851 5B22BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Lack of recall tolerance status received
2010-02-23 07:32:24.851 5B0E6B90 WARNING "vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx" Received a double transition of Foundry: 2, 0
2010-02-23 07:32:24.919 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 66 (MS)
Remove the vm 256 poweredOnVms list
2010-02-23 07:32:24.990 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 65 (MS)
2010-02-23 07:32:25.061 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Time to pick up some config: 65 (MS)
2010-02-23 07:32:25.065 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' The event of Imgcust read vmdb tree values State = 0, errorCode = 0, errorMsgSize = 0
2010-02-23 07:32:25.066 1680BB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Tools running status changed to: keep
2010-02-23 07:32:25.066 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' State of the Tools version: unknown
2010-02-23 07:32:25.066 5B0E6B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' No upgrade required
2010-02-23 07:32:25.081 16A11B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:25.088 1698FB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:25.090 16A11B90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
2010-02-23 07:32:25.090 1698FB90 verbose 'vm:/vmfs/volumes/4b0a69a8-3934ecfc-866f-001999742fbb/Std-Server/Std-Server.vmx' Unknown, unexpected toolsVersionStatus use guestToolsNotInstalled of the offline state
Airfare to CIMOM version 1.0, root user
My Server includes:
2 x Intel Xeon X 5550, 4 c/8 t 2.66 GHz, 8 MB
48 GB DDR3 RAM
12 HD SAS 3 g 146 GB 10 k HOT PLUG
-11 HD than RAID 5
-1 global hot spare
Anyone know more about these symptoms?

If it is a server supported (Dell, HP, IBM, etc.) the State of health of the host will be visible from the vSphere client (hardware status tab if managed vCentre, or the tab configuration, health if not).

Otherwise, you will need to get a diagnostic utility currently out of the manufacturer and use it.

Please give points for any helpful answer.

'Detected wireless networks' followed by 'no wireless networks were found in range ".

Trying to help a friend with their laptop! It's a Lenovo R61i laptop model A 8932, 54, around the age of 16 months. WIN/XP SP3 is the only OS. He was working on this wireless network until they are gone on vacation and tried to connect to public wireless networks! Their daughter portable computer continues to operate properly with this wireless network, and it also shows the neighborhood wireless networks as well. The R61i has a built-in 'Pro\wireless Intel 3945ABG Network ' wireless wireless adapter.

Connectivity and internet access works very well through the ethernet port.

Here's what I've done so far:

He has Norton AV. I made sure that it was up to date and then ran a full system scan. It was clean.

Any help will be appreciated, and I WILL ANSWER about the results!

Windows Update ran (after I got it work - see below) for all critical updates.

Fact a "repair" on the wireless connection with these results:
- Wireless networks detected
- No wireless networks were found in range
- Windows could not finish repairing the problem because it is impossible to perform the following action: connect to the wireless network
That when the laptop is 5 feet of the wireless router. It is a Dlink
Updated the driver from Lenovo web site by the support of the Intel boards:
- former pilot was 11.1.1.11
- new driver is 12.4.0.21 with a date of 04/03/2009
Went into the BIOS and reset the BIOS to its original, saved and reloaded settings.

Checked the Device Manager. Everything looks OK, no yellow or red devices

Remove the network card and let Windows re - create.

Disabled and enabled the network card

Check the event logs. The only entrance is on the system log. I don't know if this event log entry is significant or not, but it's here:

Source: NETw5x32, zero category, event 7036.
The service entered the \DEVICE\{78E5EBB6-A194-4E9F-A840-E05CC39A5823} State.

0000: 00 00 08 00 02 00 62 00
0008: 00 00 00 00 7 c 00 40 1 b
0010: 00 00 00 00 00 00 00 00
0018: 00 00 00 00 00 00 00 00
0020: 00 00 00 00 00 00 00 00
0028: 57 44 52 56 00 00 00 e7

I have not yet tried it raise in "Safe Mode with networking".

I would add that "Windows Update" was also not working. Graduation: A few updates have not been installed. Error code 0 x 41. I had going in downloading and installing the latest version of Windows Installer 3.1, version 3.1.4001.5512

Do not think that there is a relationship between these two issues, but stranger things have happened.

The laptop has a 3-year extended warranty and I'm about to throw it in the face of Lenovo as a hardware error. The thing that blows my mind is 'Detected wireless networks' followed by 'no wireless networks were found in range ".

Hi Shawn

Thank you for your help. Here is the final solution to this problem.

The "clean boot" you suggested worked as described, but it had no effect of awareness of wireless networks. Ditto to start in "Safe Mode with network. We took the laptop to Office Depot; They basically ran the same tests that I did, with the same results. Their technology has managed to get it to connect to Wireless store by manually setting, but it would not show under 'view available networks '. He suggested that we call their 800 support number. The only novelty with that phone support guy came was to "Ping 127.0.0.1" which I don't think inherent in the wireless somehow. He wanted me to call Comcast to check the internet connection. Under the principle of "do not create a new problem while you're working on a problem", I resisted to go here as two other computers work fine on this connection from Comcast.

We finally opted for a full charge of Windows. This included a blue key on the laptop at boot to bring up "Rescue and recovery", then by specifying 'Restore my hard drive to the original factory condition' and "don't save all files" - we have previously saved the contents of "My Documents" on a USB key. This charge really don't take as much time as I thought he might; only about an hour. Most importantly - WIRELESS NETWORKS APPEAR NOW; and connect as it should! We had to apply SP3 as reloading he brought back to SP2 status.

I guess the lesson here is that sometimes he just reload Windows is the shortest possible solution to some of these mysterious problems.

I had a hard time to convince me it was a hardware problem, when the system detects wireless networks but are simply not them!

Thanks again for your help.

Bruce Butler (np560)

Complex problem to start Adobe Photoshop CS 5

I use Windows Vista Home Basic SP2 with updates installed and a new hard drive.
Processor: Pentium (R) Dual Core CPU [email protected] GHz
(Vivid RAM) memory 4 GB
32 bit
AMD Radeon HD 6450 memory: 1024 MB

My tech says IT is no longer his side of the issue because he put in a new card graphics & power to run these programs at my request, before I installed the below; my computer must have the power to run these programs; There must be MS or Adobe, and I also ask Adobe support. I'm working with Photoshop CS 5.1 and Lightroom 4.1 - both aware.

It crashes after a while saying I have not enough memory (RAM). I can't save my work and if I close I lose everything I've done. No error codes appear, but in the registry I don't see Id event 256, 257, 1000 & 1530. Source: CardSpace 3.0.0.0. I did some research and am puzzled that none of the real solutions are found. Space map Windows refuses to open also.

I ran: sfc/scannow - no problem.

I changed the pagefile to 20000 mb, and that did not help.

I hope that I have given relevant information and appreciate any help I can get. I spent more time in the last 2 weeks looking for solutions to work on my photos...

Thanks for any help in advance. I think it's great that people help this site!

As well as a user of Adobe Photoshop to another, I hope you find a solution to your needs.

But RAM is your main problem here and not on your hard drive.

I am a Member here: http://forums.adobe.com/index.jspa?promoid=JOPCT help is here when you need it.

I am also a Member here: https://discussions.apple.com/index.jspa

I have an Apple product, visit the forum when you have some time, you will be surprised to see as many problems as Microsoft.

Vista keeps hooked randomly

Hello, I use Vista for 2 years and it has been quite a good experience. But recently these last months the computer maintains suspended, with the mouse cursor, being unable to move. They occur randomly sometimes it hangs while loading the main screen while other times it crashes when using to halfway. Usually we will just manually force the computer to shut down and then turn it back on, however sometimes suspended just repeats. Hang the problem seems to be worsening = now)

We tried to analyze the computer using anti-virus software, analysis mode FAILURE but nothing has been found every time. There was once when the stand-alone computer is analyzed for a long time, due to a bad closing down previously, and the system "decided that it will be safer restore the computer system of a few days in time, when he thought it was safe. I don't know if you understand what I mean, but all programs that have been installed in the dangerous period has been all deleted, something like go back in history?

I watched the similar thread and technical support engineers have asked to look at the computer manager event log and the Manager of devices for more information. I don't know if that's what you're looking for, but I found no error in the Device Manager, but a surprising amount of "reviews & error" in the event log. " I'm pasting some of the log of today down only. I don't know if it's something to do with Vista, but I hope you can help me solve the problem.

Thank you.

My system information:
Windows Vista Edition Home Premium
Service Pack 1
Acer Aspire M5600
Intel (r) CPU 2.20 GHz Core Duo
2.00 GB
32-bit operating system

Event logs:

Log name: Application
Source: Microsoft-Windows-CAPI2
Date: 2009-06-14 23:02:08
Event ID: 11
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
Has not taken from the root list third-party auto update cab at: with error: these data are incorrect.
.
The event XML:


    11
    0
    2
    0
    0
    0 x 80000000000000

    62433


    Application
    user-PC


    http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab
    These data are incorrect.

Log name: System
Source: Service Control Manager
Date: 2009-06-14 23:00:49
Event ID: 7026
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
The next (s) starting or starting system could not load:
i8042prt
The event XML:


    7026
    0
    2
    0
    0
    0 x 80000000000000

    289405


    System
    user-PC



i8042prt

Log name: System
Source: Service Control Manager
Date: 2009-06-14 23:00:34
Event ID: 7000
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
The npkcrypt service failed to start due to the following error:
The system cannot find the specified file.
The event XML:


    7000
    0
    2
    0
    0
    0 x 80000000000000

    289377


    System
    user-PC


    npkcrypt
    %%d Ko

Log name: System
Source: Microsoft-Windows-HttpEvent
Date: 2009-06-14 23:00:14
Event ID: 15016
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
Failed to initialize the Security Kerberos for authentication package on the server side. The data field contains the error number.
The event XML:


    15016
    0
    2
    0
    0
    0 x 80000000000000

    289329


    System
    user-PC


    \Device\Http\ReqQueue
    Kerberos
    000004000200300000000000A83A00C00000000000000000000000000000000000000000000000000E030980

Log name: Application
Source: Microsoft-Windows-user profiles Service
Date: 2009-06-14 21:15:06
Event ID: 1530
Task category: no
Level: WARNING
Keywords: Classic
User: SYSTEM
Computer: PC-user
Description:
Windows detected your registry file is still in use for other applications or services. The file will be unloaded now. Applications or services that keep your registry file may not work properly thereafter.

DETAIL-
Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3014647990-4058933392-455723151-1003_Classes:
1024 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) process has opened \registry\user\s-1-5-21-3014647990-4058933392-455723151-1003_classes-cles

The event XML:


    1530
    0
    3
    0
    0
    0 x 80000000000000

    62405


    Application
    user-PC


    Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3014647990-4058933392-455723151-1003_Classes:
1024 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) process has opened \registry\user\s-1-5-21-3014647990-4058933392-455723151-1003_classes-cles

Log name: Application
Source: Microsoft-Windows-user profiles Service
Date: 2009-06-14 21:15:05
Event ID: 1530
Task category: no
Level: WARNING
Keywords: Classic
User: SYSTEM
Computer: PC-user
Description:
Windows detected your registry file is still in use for other applications or services. The file will be unloaded now. Applications or services that keep your registry file may not work properly thereafter.

DETAIL-
Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3014647990-4058933392-455723151-1003:
1024 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) process has opened \registry\user\s-1-5-21-3014647990-4058933392-455723151-1003-cles

The event XML:


    1530
    0
    3
    0
    0
    0 x 80000000000000

    62404


    Application
    user-PC


    Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3014647990-4058933392-455723151-1003:
1024 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) process has opened \registry\user\s-1-5-21-3014647990-4058933392-455723151-1003-cles

Log name: Application
Source: Microsoft-Windows-EventSystem
Date: 2009-06-14 21:15:03
Event ID: 4621
Task category: event system
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
System event COM + was unable to delete the EventSystem.EventSubscription {CEB8B221-89C5-41A8-98CE-79B413BF150B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000} object. The HRESULT is 80070005.
The event XML:


    4621
    0
    2
    16
    0
    0 x 80000000000000

    62401


    Application
    user-PC


    80070005
    EventSystem.EventSubscription
    {CEB8B221-89C5-41A8-98CE-79B413BF150B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}

Log name: Application
Source: Microsoft-Windows-ApplicationExperienceInfrastructure
Date: 2009-06-14 19:25:05
Event ID: 1
Task category: no
Level: WARNING
Keywords:
User: user-PC\user
Computer: PC-user
Description:
Enforcement (Maple story, provider Wizet) has the following problem: Maple story is not compatible with this version of Windows. For more information, contact Wizet.
The event XML:


    1
    0
    3
    0
    2
    0 x 8000000000000000

    62379


    Application
    user-PC


    15
    12
    History of Maple
    6
    Wizet
    95
    Maple story is incompatible with this version of Windows. For more information, contact Wizet.
    1

Log name: Application
Source: Microsoft-Windows-CAPI2
Date: 2009-06-14 18:55:40
Event ID: 11
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
Has not taken from the root list third-party auto update cab at: with error: these data are incorrect.
.
The event XML:


    11
    0
    2
    0
    0
    0 x 80000000000000

    62371


    Application
    user-PC


    http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab
    These data are incorrect.

Log name: System
Source: Service Control Manager
Date: 2009-06-14 18:55:37
Event ID: 7026
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
The next (s) starting or starting system could not load:
i8042prt
The event XML:


    7026
    0
    2
    0
    0
    0 x 80000000000000

    289185


    System
    user-PC



i8042prt

Log name: System
Source: Service Control Manager
Date: 2009-06-14 18:55:19
Event ID: 7000
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
The npkcrypt service failed to start due to the following error:
The system cannot find the specified file.
The event XML:


    7000
    0
    2
    0
    0
    0 x 80000000000000

    289157


    System
    user-PC


    npkcrypt
    %%d Ko

Log name: System
Source: Microsoft-Windows-HttpEvent
Date: 2009-06-14 18:54:57
Event ID: 15016
Task category: no
Level: error
Keywords: Classic
User: n/a
Computer: PC-user
Description:
Failed to initialize the Security Kerberos for authentication package on the server side. The data field contains the error number.
The event XML:


    15016
    0
    2
    0
    0
    0 x 80000000000000

    289106


    System
    user-PC


    \Device\Http\ReqQueue
    Kerberos
    000004000200300000000000A83A00C00000000000000000000000000000000000000000000000000E030980

Log name: Application
Source: Microsoft-Windows-user profiles Service
Date: 2009-06-14 17:01:36
Event ID: 1530
Task category: no
Level: WARNING
Keywords: Classic
User: SYSTEM
Computer: PC-user
Description:
Windows detected your registry file is still in use for other applications or services. The file will be unloaded now. Applications or services that keep your registry file may not work properly thereafter.

DETAIL-
Register of the 1 handles user are escaped from \Registry\User\S-1-5-21-3014647990-4058933392-455723151-1003_Classes:
1008 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) process has opened \registry\user\s-1-5-21-3014647990-4058933392-455723151-1003_classes-cles

Hello tudexy,

Thank you for using the Microsoft Windows Vista Forums.

Are you currently with all Windows updates? It seems that your computer has performed a system restore as you said, "at some point before the problem" can lose any changes that you made to your computer. Do you receive error messages when your computer starts successfully after that it crashes? Please let us know status. Thank you!

Windows updates help protect the security and reliability of your computer. If you wish, you can set Windows to automatically install recommended both updates that you specify, or you can manually check for updates.

To run Windows Update manually and look for the updates and new drivers when you use the start menu in Vista, follow these steps:
1. Click Startand then click Control Panel. Or point to settingsand then click Control Panel.
2. In Control Panel, double-click Windows Update. Or click system and Maintenance, and then click Windows Update.
3. If the window that opens shows Windows is up-to-date, go to the section check and install the drivers from the manufacturer of your computer up to date . Or, if Windows finds updates, click install.
For more information about Windows updates, see the following help and how-to topic:

Install Windows updates

Optimize Windows Vista for better performance:
http://windowshelp.Microsoft.com/Windows/en-us/help/83EC0FFE-EE04-4D53-8B87-25D1F05C954E1033.mspx

Engineer James Microsoft Support answers visit our Microsoft answers feedback Forum and let us know what you think.

BSOD, error: BAD_POOL_HEADER

Hi all

My laptop restarts randomly with a mistake that we called BAD_POOL_HEADER.
I'm not much of a gamer, BSOD occurs when im reading PDF, editing documents, watching movies.
I know that I had this problem when I brought my lappy, but it has increased since the week last 2.

In my event log, I saw so many critical mistakes [kernell power ID:41, task category event: 63].
I couldn't event 8.1 update, whenever it crashed when I tried to do an update. So I stopped to do an update.

And now since this morning I have no why, my processor and disk % use maximum.

I thought it will decrease thereafter, but they do not.

I hope someone can find a solution to my problem.
Thanks in advance.

My minidumps and PC info is uploaded here

[www.mediafire.com/download/oizjjj8uz1kokj7/MiniDumps.zip]

Loki

Devi this handler simply checks against a list. You have no old drivers.

This accident has been verified and connected to the driver volsnap.sys volume shadow copy update of Microsoft Corporation to win 8.1 should solve the problem. I would also like to run a file system check to verify the operating system

Please run a check of system files (SFC)

All instructions are in our Wiki article below...
If you have any questions please ask us for .

File System check (SFC) Scan and repair system filesone

Old drivers

NTIDrvr.sys 19/04/2010 21:37:59
UBHelper.sys 06/07/2010 12:19:26 AM
mwlPSDFilter.sys 25/03/2011 03:12:11
mwlPSDNServ.sys 25/03/2011 03:12:13
mwlPSDVDisk.sys 25/03/2011 03:12:23
GEARAspiWDM.sys 03/05/2012 15:56:17

Integrate Google Chrome / V8 JavaScript engine
Hello!

I have a few questions about the integration of a browser with Java FX.

Is it possible to easily integrate Google Chrome (or use the JavaScript V8 engine) with Java FX / WebEngine?
Is there a roadmap, which version of WebKit is included in which free Java FX?

Kind regards
Dominik
Is it possible to easily integrate Google Chrome (or use the JavaScript V8 engine) with Java FX / WebEngine?

NO.

Is there a roadmap, which version of WebKit is included in which free Java FX?

NO.

I have a Java FX application which, inside, integrates a Web browser, which is governed in several independent web pages.

http://docs.Oracle.com/JavaFX/2/WebView/jfxpub-WebView.htm "oracle sample webview.
http://code.Google.com/p/Willow-browser/ «stand-alone javafx browser»

Applications can access the DOM event and lights to the browser.

http://docs.Oracle.com/JavaFX/2/API/JavaFX/scene/Web/webengine.html#GetDocument%28%29 'get the dom '.
http://docs.Oracle.com/JavaFX/2/API/JavaFX/scene/Web/webengine.html#ExecuteScript%28Java.lang.String%29 «exec javascript»
Re: can I integrate jQuery into JavaFX WebEngine? «exec jquery javascript»
http://API.jQuery.com/category/events/event-object/ 'raise events on the selections of dom using jquery.

I'm looking for a technology where Google Chrome can easily be incorporated.

JavaFX has no such technology.

Area calendar: date range

Hello

I am trying to add tracks to a report of the calendar.
Here is exactly what I'm trying to achieve...

http://www.sumneva.com/Apex/f?p=15000:305:0

Does anyone know how this?
I tried messign autour with the date on the calendar, calendar end date, but I do not seem to get anywhere?

Thank you
Richard

Hello

I did it just now; do not use an application process as has been suggested in this thread, but created a procedure as follows:

create or replace
procedure json (p_app_id in varchar2, p_session in varchar2, p_debug in varchar2, p_category_id IN NUMBER default -1, start_date in varchar2 default null, end_date in varchar2 default null) as
  --Same type as the internal apex vc_assoc_arr, just incase we can just use that later
  TYPE vc_assoc_arr is table of varchar2(32767) index by varchar2(255);
  event vc_assoc_arr;
  v_output clob;
  v_buffer pls_integer := 255;
  v_index pls_integer := 1;

  function json_escape(p_text varchar2) return varchar2 is
  --TODO: Correctly escape as per json specs
  begin
    return REGEXP_REPLACE(p_text,'[[:space:]]',' ');
  end;

  function jsonify_array(p_arr vc_assoc_arr, p_nest number := 0) return varchar2 is
    v_json_array VARCHAR2(32767) := '';
    v_newline VARCHAR2(10) := ','||CHR(10);
    v_key VARCHAR2(255);
    v_nesting VARCHAR2(100) := LPAD(' ', p_nest, ' ');
  begin
    v_key := p_arr.FIRST;
    WHILE v_key IS NOT NULL LOOP
      v_json_array := v_json_array||v_nesting||'"'||v_key||'": "'||json_escape(p_arr(v_key))||'"'||v_newline;
      v_key := p_arr.NEXT(v_key);
    END LOOP;

    return REGEXP_REPLACE(v_json_array,v_newline||'$');
  end;
begin
  owa_util.mime_header('text/html', false);
  owa_util.http_header_close;

  --Because the JSON needs to return an array, it needs to return in the format
  --[{"property1" : "value1", "property2":"value2"},{"property1" : "value1", "property2":"value2"}]

  v_output := '[';
  for e in (select e.event_id, e.title, e.start_date, e.end_date, e.description, e.category
            from v_event e
            where (e.category_id = p_category_id or p_category_id = -1 )
            and (e.start_date > sysdate-365 and e.start_date < sysdate+365)) LOOP --only return events that occur a year either side of today's date
    event('id') := e.event_id;
    event('title') := e.title;
    event('start') := to_char(e.start_date, 'yyyy-mm-dd');
    event('end') := to_char(e.end_date, 'yyyy-mm-dd');
    event('className') := replace(e.category, ' ', '');
    event('url') := 'f?p='||p_app_id||':5:'||p_session||'::'||p_debug||'::P5_EVENT_ID:'||e.event_id;
    v_output := v_output || '{';
    v_output := v_output || jsonify_array(event,2);
    v_output := v_output || '},';
  END LOOP;
  v_output := substr(v_output, 1, dbms_lob.getlength(v_output)-1);--strip away the last comma
  v_output := v_output || ']';

    --print out the contents of output
    for i in 1..ceil(dbms_lob.getlength(v_output)/v_buffer) loop
        htp.prn(substr(v_output,v_index,v_buffer));
        v_index := v_index + v_buffer;
    end loop; 

end;

I spent in the application and the session only id for proposed to provide a detailed link. You also NEED to have the parameters start and end - but the default (from the fullCalender.js) is start and end, which will not because they are reserved words, that's why they have been renamed 'start_date' and 'end_date' respectively; Also must be matched to the actual fullCalendar.js file; There is a section:

// event ajax
     lazyFetching: true,
     startParam: 'start_date', --modify these two lines to be in the parameter specification of the procedure
     endParam: 'end_date',

Also in comment the following code in the fullcalendar.js file (it creates a parameter _ used for the cache - so you can comment out this line, or include this parameter in the procedure):

cache: options.cacheParam || false, // don't let jquery prevent caching if cacheParam is being used

And then the call to generate the real schedule looks like this:

$(document).ready(function(){

     $('#calendar').fullCalendar({
events: "&OWNER..json?p_app_id=&APP_ID.&p_session=&SESSION.&p_debug=&DEBUG.&p_category_id=&P1_FILTER."
     });

});

Of course, you should be at your request of slider to suit your table - I also have my events classified by color, which probably do not need you (which is also one of the parameters of the proceedings, once again if you do not need, just remove this last parameter). And the grant procedure, it can be called.

grant execute on json to apex_public_user; --where json is the name of the procedure

Hope that helps.

Van
Trent

Published by: tr3nton on September 18, 2010 19:49

Published by: tr3nton on September 18, 2010 19:56

Failed application Surescripts_borero.exe, Source: Application error event ID: 1000, the task category: 100

Need solution for Application error.
Error details:
Log name: Application
Source: Application error
Event ID: 1000
Level: error
User: n/a
Connected: 10/01/2012 01:42:21
Task category: (100)
Keywords: Classic
Computer: Suitemed_DB2

Details:
Failed application Surescripts_Borero.exe, Version 14.0.0.0, time stamp 0x4bce57d1, failed module pbdwe1154.dll, version 11.5.1.4740, time stamp 0x4bce57fe, exception 0xc0000005 code,

I faced this error more than 200 times a day. Necessary solution.

Thank you
Manon.

Hello

Your question is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the IT Pro TechNet public. Please post your question in the Windows Server forum.

Please find the link below,
http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer

Hope this information is useful.

System error category (102) event ID 1003

During the last two weeks, my system crashed repeatedly. It seems that the problem was a third newly installed, but after I installed an update for C++, it seemed that the problem has been resolved.

However, my system crashed again today, and I found the following error, I had seen before, too. Any suggestions on how to fix this?

Event type: error
Event source: System error
Event category: (102)
Event ID: 1003
Date: 19/01/2011
Time: 15:35:49

Description:
100000d error code 1, parameter1 00000020, parameter2 00000002, parameter3 00000000, parameter4 a9b39520.

0xD1 bug check code

http://msdn.Microsoft.com/en-us/library/ff560244 (v = VS. 85) .aspx

What wireless network adapter?

Hope this helps, Gerry Cornell

Problem signature__Problem Event Name:_BlueScreen__OS Version:_6.0.6001.2.1.0.256.1____Locale ID:_1033____

Signature of the problem
Problem event name: BlueScreen
OS version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Files helping to describe the problem (some files may be is no longer available)
Mini090410 - 02.dmp
SysData. XML
Version.txt

See a temporary copy of these files
WARNING: If a virus or other security threat caused the problem, open a copy of file can harm your computer.

Additional information about the problem
BCCode: 1000008e
BCP1: C0000005
BCP2: 81C61BD2
BCP3: A11BDA44
BCP4: 00000000
OS version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Information about the server: af85b418-30e5-42eb-bbb4-92c486763481

Hello

You really need this post in Vista - Hardware Forum

Pilots and answers - Vista - Hardware
http://social.answers.Microsoft.com/forums/en-us/vistahardware/threads?filter=answered

=============================================================

To troubleshoot try safe mode (repeatedly press F8 as you start) or boot with a Vista DVD.

For troubleshooting see BlueScreens using BlueScreenView and MyEventViewer and other methods
This thread.

http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

--------------------------------------------------------------------------------------------------------------

Two main causes of this blue screen video drivers and BIOS - check with the system manufacturer
Site for graphics (Video) card and BIOS, then on site of the manufacturer of the device for the last video. It may be
other pilots to check there. Disable the installation of self as those who are older and if
Updates Windows suggests a pilot just HIDE. Antivirus is another possibility.

See methods of update driver generic in the next message.

BCCode: 8th 0x0000008E is the same as 0x1000008E

Cause

Bug KERNEL_MODE_EXCEPTION_NOT_HANDLED control is a very common bug control. To interpret it, you must identify which exception has been generated.

Common exception codes are:
- 0xc0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation has occurred.
Solve the problem

If you do not have to debug this problem, you must use certain basic troubleshooting techniques:
- Make sure you have enough disk space.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Try changing video cards.
- Check with your hardware vendor for updates to the BIOS.
- Disable the BIOS memory options such as implementing caching or shading.
If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

If you do not know the specific cause of the exception, consider the following:
- Hardware incompatibility. Ensure that all new equipment installed is listed in the list of the products tested Microsoft Windows market.
- Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.
If the verification of the message bug list a driver by name, disable or remove that driver. In addition, disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system Safe Mode, you must start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error may be a third-party remote control program. If this software is installed, you can remove the system startup service using the recovery and then Console by removing the offending system service file.

Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x1E. You can disable the cache in memory of the BIOS to try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved.chk, which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation.

You can solve the problems of BIOS by upgrading the version of the system BIOS

BCCode: 8th 0x0000008E is the same as 0x1000008E<-- read="">
* 1151.html? order = date http://www.faultwire.com/solutions-fatal_error/kernel-mode-exception-not-HANDLED-0x0000008E-

=============================================

Look in the Event Viewer to see if something is reported on those.
http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
http://www.NirSoft.NET/utils/my_event_viewer.html

-------------------------------------------------------------------------

Also this, so you can see the probable bluescreens. (If necessary)

Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
http://www.winvistatips.com/disable-automatic-restart-T84.html

-------------------------------------------------------------------------

It comes to my convenience store generic bluescreen:

Here are a few ways to possibly fix the blue screen issue. If you could give the info to blue screen
This would help. Such as ITC and 4 others entered at the bottom left. And another error
information such as the STOP codes and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples:

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format:

Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

It is an excellent tool for displaying the blue screen error information

BlueScreenView scans all your minidump files created during 'blue screen of death '.
hangs and displays information about all accidents of a table - free
http://www.NirSoft.NET/utils/blue_screen_view.html

BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
There are other causes.

You can do without if needed fail or the Vista DVD or recovery command prompt mode
Options if your system was installed by the manufacturer.

This tells you how to access the System Recovery Options and/or a Vista DVD
http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

You can try a system restore to a point before the problem started when one exists.

How to make a Vista system restore
http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

-------------------------------------------------------------------------

Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
RUN AS ADMIN

Enter this at the command prompt - sfc/scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker
(SFC.exe) program generates in Windows Vista cbs.log
http://support.Microsoft.com/kb/928228

The log can give you the answer if there is a corrupted driver. (Says not all possible
driver problems).

Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

How to run the check disk at startup in Vista
http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

-------------------------------------------------------------------------

Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
keyboard and mouse, as well as of other major device drivers.

Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

How to install a device driver in Vista Device Manager
http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

How to disable automatic driver Installation in Windows Vista - drivers
http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

-------------------------------------------------------------------------

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
quit unexpectedly
http://support.Microsoft.com/kb/958233

Troubleshooting, STOP error blue screen Vista
http://www.chicagotech.NET/Vista/vistabluescreen.htm

Understanding and decoding BSOD (blue screen of death) Messages
http://www.Taranfx.com/blog/?p=692

Windows - troubleshooting blue screen errors
http://KB.wisc.edu/page.php?id=7033

-------------------------------------------------------------------------

In some cases, it may be necessary.

The Options or Vista recovery disk Startup Repair

How to do a startup repair
http://www.Vistax64.com/tutorials/91467-startup-repair.html

This tells you how to access the System Recovery Options and/or a Vista DVD
http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

I hope this helps.

Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

Problem event name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 locale ID: 1032

My computer freezes on the blue screen every time it starts normally. It seems that when I go on safe mode.

Signature of the problem:
Problem event name: BlueScreen
OS version: 6.1.7601.2.1.0.256.1
Locale ID: 1032

More information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 91301CBB
BCP3: 82966B9D
BCP4: 00000000
OS version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files helping to describe the problem:
C:\Windows\Minidump\051816-16036-01.dmp
C:\Users\Phil\AppData\Local\Temp\WER-42822-0.SysData.XML

Any ideas on how to solve this problem or what is causing the problem?

You can see the files here: https://onedrive.live.com/redir?resid=F07A10C17A1ACFE! 322 & authkey =! AEA_9Q8i0qX9VKI & ithint = file %2 c

It contains the file Msinfo32 and the DMP those.

Thank you very much in advance.

Problem devices

Coprocessor PCI\VEN_10DE & DEV_07DA & SUBSYS_75041462 & REV_A2\3 & 267A616A & 0 & 1 b, that the drivers for this device are not installed.

NVIDIA nForce Networking Controller Driver

You need to update NVIDIA nForce Networking Controller Driver.
http://www.driverscape.com/manufacturers/Fujitsu/laptops-desktops/AMILO-desktop-li3745a/27003

NVIDIA nForce Networking Controller Driver version 73.3.5:

http://www.driverscape.com/files/share/8af4eb244eccff4a15ba32cb11756d87.zip

I don't like suggesting to update for the third-party driver sites but I see no other option.

category event (256) 516?

Similar Questions

Maybe you are looking for