Error Code details
V-16-13-4333
Severity: Error 
Component: Cluster Server 
Message:
Error in starting Exchange services
Description:

This error may occur due to permission issues with the hadhelper account. 
 

To find more details about the errors that occur while running the Exchange Setup Wizard, review the ExchInstaller_A.txt file. By default, this file is located here:
 

C:\Program Files\Veritas\cluster server\log

 

ExchInstaller_A.txt contains a log of each function that is called while the Exchange Setup Wizard runs and the corresponding outcomes. Most of the error codes that appear in this log are standard Windows error codes that can be translated with the net helpmsg command. 
 

For example, part of an ExchInstaller_A.txt file includes the following: 
 

2007/08/11 22:39:24 VCS ERROR V-16-13-10005 Call to function
VLibSecurityContext::Init() failed.  Error Type = 2  Error Code = 5 
./Util.cpp:CUtil::SecureUpdateDNSAndAD[3859]


 

In this case, ERROR CODE = 5 is displayed. 
 

From a Windows command prompt, use this command to translate the error: 
 

net helpmsg 5
 

This message is returned:
 

Access is denied.

If you suspect that permission issues exist, review the following:
 

  • Verify that the hadhelper account has the correct rights and permissions. For more information, see:

    http://support.veritas.com/docs/267067
     
  • Security templates that have been designed for high security may interfere with the Exchange Setup Wizard and Configuration Wizard. In some cases, you must temporarily revert to a less secure template for the duration of the installation. For information on security templates for Windows 2003, see: 

    http://support.microsoft.com/kb/816585/en-us

 

Note: You should only import or modify a security template if you have a full understanding of the effects that the changes make.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2012-06-06 04:07:57 PDT
Platform: Generic
Release: Generic
Content:

If you establish that the error occurs due to permission issues, take the following course of action. 
 

This workaround may allow the move database wizard to complete successfully. This effectively shifts the permissions burden from the logged in user to the hadhelper account.


Note: Before you use this workaround, follow the steps in Technote 267067 (http://support.veritas.com/docs/267067) to ensure that the hadhelper account has sufficient permissions.

 

  1. From Cluster Explorer, create a new service group. This group is only used temporarily. Do the following in the order presented:
    • Click Edit.
       
    • Click Add.
       
    • Click Service Group.
       
    • From Service Group Name, type a name for the service group.
       
    • From Available Systems, add the nodes of the cluster.
       
  2. Add resources to the new service group, and configure the dependencies and define the attributes for each resource as specified in the following table:
     

Resource type (dependency)

Number: Name

Attribute

Value

IP

1: IP_resource_name

Address

IP_address

 

 

SubNetMask

subnet_mask

 

 

MACAddress

mac_address

Lanman (depends on IP)

1: lanman_resource_name

ADUpdateRequired

TRUE

 

 

DNSCriticalForOnline

TRUE

 

 

ADCriticalForOnline

TRUE

 

 

VirtualName

exchange_virtual_server

ExchService2007 (depends on Lanman)

1: MSExchangeSA

Service

MSExchangeSA

 

 

LanmanResName

lanman_resource_name

 

2: MSExchangeIS

Service

MSExchangeSA

 

 

LanmanResName

lanman_resource_name

 

3. Bring the resources online.
 

4. Run the Exchange Setup Wizard to move the database.
 

5. After the wizard has finished, bring the temporary service group offline.


6. Delete the temporary service group.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service