UNSOLVED

angel_isakov

updated

7 years ago

A

angel_isakov

1 Rookie

•

100 Posts

0

21402

March 11th, 2013 09:00

How to stop Powerpath autoregistration error event?

Hello,

We have 4 hosts(Windows 2012) in cluster and VNX5300(last OE 201) and Power Path 5.7, UnisphereHostAgent-Win-32-x86-en_US-1.2.25.1.0163-1 and UnisphereServerUtil-Win-32-x86-en_US-1.2.25.1.0163-1

Everything work fine but there is a error event in windows on all 4 hosts:

Log Name:  Application
Source:    EmcPowerPathService
Date:      3/11/2013 5:38:59 PM
Event ID:  4

Task Category: None

Level:     Error
Keywords:  Classic
User:      N/A
Computer:  XXXXXXXXXXX

Description:

EMC Power Path Error:  Host autoregistration: Error: Failed to update host registration info

Event Xml:

http://schemas.microsoft.com/win/2004/08/events/event ">

 

4
2
0
0x80000000000000
34933
Application
xxxxxxxxxxxx

 

 

Host autoregistration: Error: Failed to update host registration info

 

  • angel_isakov

    1 Rookie

    •

    100 Posts

    3413

    0

    Posted March 12th, 2013 06:00

  • angel_isakov

    1 Rookie

    •

    100 Posts

    3413

    0

    Posted March 12th, 2013 10:00

    Yep, it's new feature in old cluster(Windows 2008R2 and PP 5.5SP1) this "auto registration" didn't exist.

  • Sam Claret

    86 Posts

    3413

    1

    Posted March 12th, 2013 10:00

    Hello

    This appears to be a new feature specific to PowerPath 5.7. We are currently researching it.

    Thank you

    Sam Claret

  • kelleg

    6 Operator

    •

    4537 Posts

    3413

    0

    Posted March 13th, 2013 10:00

    Moving Discussion to the Host Systems Support Forum - this is where PowerPath topics are more quickly responded to.

    glen

  • angel_isakov

    1 Rookie

    •

    100 Posts

    3416

    0

    Posted March 13th, 2013 14:00

    Any idea how to fix this...?

    I've checked all command in CLI, but there is no such a option.

    Maybe new Power Path will work normal with windows 2012...

  • Sam Claret

    86 Posts

    3416

    1

    Posted March 13th, 2013 23:00

    Currently there is no way to stop these events - the version of Windows is actually not relevant - it's the version of Microcode on the VMax or Flare code on VNX. Unfortunately when connected to DMX, CX type arrays and VNX or VMax running older code you will get these messages. Also possibly if using VPlex.

    We are currently investigating with Engineering a method around this issue.

    Thank you

    Sam Claret

    Technical Support Engineer III

    Global Technical Support – SSG Windows

    EMC Corporation

  • angel_isakov

    1 Rookie

    •

    100 Posts

    3417

    0

    Posted March 14th, 2013 06:00

    Thank you Sam.

    There is another way- to uninstall PP and use Microsoft MPIO, but then i can't use features like Thin pool reclamation and ODX..or i can?

  • Sam Claret

    86 Posts

    3417

    0

    Posted March 14th, 2013 06:00

    I suppose you could do that however it is purely an informational message - it does not effect anything.

    Sam Claret

  • 3417

    0

    Posted May 6th, 2013 11:00

    So where are we on this issue?  we also are seeing this error on a 2008R2 cluster members.  Other links online talk about a code update for our VNX to make this error go away.  Can you confirm?

    Thanks,

    Sean~

  • angel_isakov

    1 Rookie

    •

    100 Posts

    1018

    0

    Posted May 6th, 2013 23:00

    Software update on VNX OE won't stop this error.