SFHA + VCS Error

[ubiraci_rocha]

Hi for all

After changing the licenses of the SFHA, appeared the following errors and the resources are not more online.

The  High Availability service is stopped in  ative node of  the cluster and diplay errors below: 

Event Type: Error
Event Source: AgentFramework
Event Category: None
Event ID: 13067
Date:  30/01/2009
Time:  15:45:28
User:  N/A
Computer: SRVC101
Description:
Agent is calling clean for resource(SRVP02_SG-EnterpriseVaultDirectoryService) because the resource became OFFLINE unexpectedly, on its own.  After, this resource SRVP02_SG-EnterpriseVaultDirectory  appears with status failed on active node.

Event Type: Error
Event Source: Had
Event Category: None
Event ID: 52569
Date:  30/01/2009
Time:  16:04:19
User:  N/A
Computer: SRV301

Description:
Object (Remote Build) DOES NOT MATCH 

Thanks,  Ubiraci Rocha

[M__Braun]

Hi,

> After changing the licenses of the SFHA

Could you please provide some details?  Did you switch from eval licenses to permanent licenses?

Regards

Manuel

[ubiraci_rocha]

Hi Manuel!

Yes, after change eval to definitive licenses.

After reboot servers, the Veritas High Availability Engine service start, but after some seconds the service stops and its resources are with the status offline.

Thanks,

Ubiraci Rocha

[M__Braun]

Hi Ubiraci,

> Yes, after change eval to definitive licenses.

> Object (Remote Build) DOES NOT MATCH 

Could you please check if both nodes have valid licenses for the identical product. Here is a step-by-step guide:

1 Open the Windows Control Panel and click Add or Remove Programs.
2 Select Veritas Storage Foundation with High Availability 5.1 for Windows (Server) Components and click Change.
3 The Symantec Product Installer screen appears. Select License Management. Click Next.

You could also try to start only one cluster node as it seems something happens in the cluster join phase (remote build).

Additionally I would also highly recommend opening a support call in parallel.

Regards

Manuel

[ubiraci_rocha · Accepted solution]

Thanks Manuel!

I am solved this problem after run clean VCS Licenses in all nodes and reinstall the definitive licenses.

Ubiraci Rocha