Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Unity 7.x ADSchemaSetup failed on DC (window 2003 64 Bit)

Hi Team,

We are installing unity 7.X and this is unified voice messaging with exchange 2007. Customer has window 2003 64-bit server for first DC. Now when we are trying to install ADSchemaSetup on this DC, We are getting error that " this can be install only on 32-bit system.

Kindly advise us to solve this issue. customer cant change his system.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Unity 7.x ADSchemaSetup failed on DC (window 2003 64 Bit)

Hi,

If you're running 64-bit you'll need to run the schema extension commands manually.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsl48851

The bug cuts off some of the syntax in the release note but here's what it's supposed to read:

Workaround:

Do one of the following:
- Run adschemasetup on a 32-bit server.
- Extend the schema manually by running one or more of the following commands from the
command line (the first command is required):

For all Unity systems, the ldifde command line is:
ldifde.exe -i -k -c ""  ""
-s "" -f " \
Schema\LdifScripts\avdirmonex2k.ldf" -j ""

If you are using the Cisco Unity Bridge, also run:
ldifde.exe -i -k -c "" ""
-s "" -f " \
Schema\LdifScripts\omnigateway.ldf" -j ""

If Unity system is using VPIM also run:
ldifde.exe -i -k -c ""  ""
-s "" -f " \
Schema\LdifScripts\vpimgateway.ldf" -j ""

where:

is a literal value
is the distinguished name for the domain in which
you want to extend the schema. For example, for a domain named voice.cisco.com, you would 
use "CN=Configuration,DC=voice,DC=cisco,DC=com"
is the DC on which you want to run the  command
is the location where you want log files to be  saved

Hope that helps,

Brad

1 REPLY
Cisco Employee

Re: Unity 7.x ADSchemaSetup failed on DC (window 2003 64 Bit)

Hi,

If you're running 64-bit you'll need to run the schema extension commands manually.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsl48851

The bug cuts off some of the syntax in the release note but here's what it's supposed to read:

Workaround:

Do one of the following:
- Run adschemasetup on a 32-bit server.
- Extend the schema manually by running one or more of the following commands from the
command line (the first command is required):

For all Unity systems, the ldifde command line is:
ldifde.exe -i -k -c ""  ""
-s "" -f " \
Schema\LdifScripts\avdirmonex2k.ldf" -j ""

If you are using the Cisco Unity Bridge, also run:
ldifde.exe -i -k -c "" ""
-s "" -f " \
Schema\LdifScripts\omnigateway.ldf" -j ""

If Unity system is using VPIM also run:
ldifde.exe -i -k -c ""  ""
-s "" -f " \
Schema\LdifScripts\vpimgateway.ldf" -j ""

where:

is a literal value
is the distinguished name for the domain in which
you want to extend the schema. For example, for a domain named voice.cisco.com, you would 
use "CN=Configuration,DC=voice,DC=cisco,DC=com"
is the DC on which you want to run the  command
is the location where you want log files to be  saved

Hope that helps,

Brad

557
Views
0
Helpful
1
Replies
CreatePlease to create content