Cluster Server 8.0 Bundled Agents Reference Guide - Windows
- Introducing VCS bundled agents
- Storage agents
- Network agents
- FileShare agents
- Services and applications agents
- VCS infrastructure and support agents
- VCS hardware replication agent for NetApp
- Troubleshooting bundled agents
Lanman agent error messages
The virtual server name exceeds the limit of 16 characters, or it contains invalid characters.
Recommended Action: Verify that the NetBios name is less than sixteen characters, and that is does not contain any of the following characters: /\:*?"<>|=.
The specified virtual name already exists in the network.
Recommended Action: Verify the VirtualName attribute defined in the configuration file is assigned a unique value.
The agent failed to update the DNS entry.
Recommended Action: Verify the DNS server is alive, and the reverse lookup zone is configured.
The agent failed to add the computer account to the Active Directory.
Recommended Action: Verify whether the user, in whose context the VCS Helper service runs, has the required permissions.
The agent failed to register the virtual server name with the NetBios.
Recommended Action: Verify whether the virtual name is already configured. Run nbtstat - n to check NetBios bindings. Contact Veritas Technical Support if the problem persists.
The agent failed to start the specified service.
Recommended Action: Verify whether the service is installed on the node. Also verify whether the user, in whose context the service will run, has the required permissions.
Invalid IP address specified in the MultiNetInfo attribute.
Recommended Action: Verify the MultiNetInfo attribute defined in the configuration file is assigned correct values.
Invalid subnet mask specified in the MultiNetInfo attribute.
Recommended Action: Verify the MultiNetInfo attribute defined in the configuration file is assigned correct values.
Invalid WINS address specified in the MultiNetInfo attribute.
Recommended Action: Verify the MultiNetInfo attribute defined in the configuration file is assigned correct values.
No value specified for VirtualName attribute.
Recommended Action: Verify the VirtualName attribute defined in the configuration file is assigned a value.
Invalid value specified for the IP address.
Recommended Action: Verify the value specified for the IP address is valid.
Invalid value specified for the subnet mask.
Recommended Action: Verify the value specified for the subnet mask is valid.
The value specified for MultiNetInfo attribute is not in the standard format.
Recommended Action: Verify the format for the MultiNetInfo attribute.
All the IP addresses specified in the configuration are invalid.
Recommended Action: Verify the IP addresses specified in the configuration file.
The specified IP address is not online in the cluster.
Recommended Action: Verify the specified IP address exists in the network.
The subnet mask specified in the configuration file does not match with the subnet mask for the configured adapter.
Recommended Action: Verify the subnet mask specified in the MultiNetInfo attribute is correct.
The specified WINS address does not exist in the WINS address list of the adapter.
Recommended Action: Verify the WINS address specified in the MultiNetInfo attribute is correct.
The agent failed to start the specified service.
Recommended Action: Verify whether the service is installed on the node. Also verify whether the user, in whose context the service will run, has the required permissions.
The agent failed to stop the specified service.
Recommended Action: Verify whether the service is installed on the node. Also verify whether the user, in whose context the service will run, has the required permissions.
The agent failed to online the Lanman resource. This is a VCS internal error.
Recommended Action: See the Windows error code for more information. Contact Veritas Technical Support if the problem persists.
This error is specific to an IPv6 environment. The Lanman agent has failed to update the virtual IPv6 address entry in the DNS records as the DNS server details are not specified.
The Lanman resource itself is able to come online, but other resources in the service group that depend on the Lanman resource (FileShare for example) may fail to come online as the virtual server name that uses an IPv6 address is not updated in the DNS.
In an IPv6 environment, the Lanman agent relies on the DNS records to validate the server name on the network.
Recommended Action: If the virtual IP is an IPv6 address then you must specify the DNS server details, either in the network adapter properties or in the Lanman agent's AdditionalDNSServers attribute.