MM 1.1 issue with extension in use via active directory

[ayavauser]

we have a slight issue with the far end admin personal removed the active directory account / purged account before actually going into AD Account / modular messaging tasks and disable extension from associated account then remove account - we are trying to add new account in AD
and associate it with the old extension / mailbox but comes back with error.

the mailbox number must be unique
the mailbox number you entered is the same as the one for.
its must be unique within the voicemail domain

field where mailbox extension entered is yellow
field where mailbox subscriber entered ( fills in after assigning mbox ext #) is red

its not letting me free up the extension for the new account I can although assign it something else but its a
number already given out

We do not have mailbox manager as an option / not licensed


regards

ayavauser

 

[KenMeans]

i think you may have to restore the AD account and then remove the mb number and ext number. I have seen this before and am trying to locate the steps

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[ayavauser]

Ken
I tried that but it still will not allow even the "old"
AD account to use the extension / same error with the reply

the mailbox number must be unique
the mailbox number you entered is the same as the one for.
its must be unique within the voicemail domain

if you do find the steps by all means please post as from what I am told it should work either way / even if you remove AD account and do not disable the extension from the account via modular messaging tasks > disable extension from account

regards

ayavauser

 

[ayavauser]

Ken
I was able to add accounts - associate to ext # (new)/ disable extension from accounts / remove accounts /re-add extension to and re-add account its just the one extension number thats in limbo that will not allow me to use the
extension number in any account ( reports show name as unknown )
I actually went through all the accounts ( 200+) and nothing is using extension #
I waited 5 minutes in between steps while do all the above my thought was they removed and added the account back agin within a couple of minutes - I even did a back up just in case and shutdown system - rebooted - still no luck with that one extension # - ended up making a vdn to route to step so we could still use that published #
My next thought is the FEDB rebuild this is a MM1.1
S3400 ( single box MAS/MSS ) as this had helped me with some funky things in a MM3.0 system even though it says
it does it in looking at the history/ doing the manual FEDB resolved a password issue for All users - resynch you wouldn't happen to have the steps to do it with versions MM1 & MM2 as I have the steps for MM3 ( may be the same but with Avaya you never know )

Happy Turkey Day to all

regards

ayavauser

 

[KenMeans]

The following steps outline the process to re-synch the FEDB:

1) 1) Stop the voice service
2) 2) Backup the copy of FEDB. You can find it in
• • \\Unified Messenger\Vserver\fedb.mdb on UM4.x /UM5.0 systems
• • \\Avaya Modular Messaging\Vserver\fedb.mdb on MM1.0+ systems
3) 3) Open the registry by clicking on Start->Run and typing regedt32
CAUTION: Ensure that you are working on the registry of the server that you wish to re-synch. The title bar of the Registry window will indicate if it’s the local server or a remote server.

Version UM4.x:
• • Navigate to HKLM\Software\Octel\Geneva
• • Edit the value : Last Incremental USN
• • Set it to 0000000000000000.

Versions UM5.0 and MM1.1 with the Exchange Messaging Backend:
• • Navigate to the HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr
• • Edit the Value Peer Directory Servers
For example: If the value is set as
CAQ010AVDC1::48e33c0200000000
Delete everything except the name of the peer directory server.
i.e., CAQ010AVDC1

Versions MM1.0 + with the MSS Messaging Backend:
• • Navigate to the key HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr
• • Edit the Value NodeSeqTable
• • In the Data Value, enter 0,0;
• • Edit the Value CosSeqNo
• • In the Data Value, enter 0

4) 4) Close the registry.
5) 5) Re-start the voice service.
6) 6) Event 1030 in the Event Viewer will indicate that full FEDB synchronization has started.
7) 7) After the re-synch has been completed a 1027 event will be generated showing how many entries were created/updated

The following steps show how to re-create the database.

1) 1) Stop the voice service
2) 2) Rename the copy of the file FEDB.mdb. You can find FEDB.mdb in
• • \\Unified Messenger\Vserver\fedb.mdb on UM4.x /UM5.0 systems
• • \\Avaya Modular Messaging\Vserver\fedb.mdb on MM1.0+ systems
3) 3) Make a copy of the file fedb.bak and rename this copy to fedb.mdb
4) 4) Open the registry by clicking on Start->Run and typing regedt32
5) 5) Depending on the version of UM/MM proceed through the following steps:

Version UM4.x:
• • Navigate to HKLM\Software\Octel\Geneva
• • Edit the key : Last Incremental USN
• • Set it to 0000000000000000.

Version UM5.0 and MM1.1 with the Exchange Messaging Backend:
• • Navigate to the HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr
• • Edit the Value Peer Directory Servers
For example: If the value is set as
CAQ010AVDC1::48e33c0200000000
Delete everything except the name of the peer directory server.
I.e., CAQ010AVDC1

Version MM1.0+ with the MSS Messaging Backend: and 2.0
• • Navigate to the key HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr
• • Edit the Value NodeSeqTable
• • In the Data Value, enter 0,0;
• • Edit the Value CosSeqNo
• • In the Data Value, enter 0
6) 6) Close the registry.
7) 7) Re-start the voice service.
8) 8) Event 1030 in the Event Viewer will indicate that full FEDB synchronization has started.
9) 9) After the FEDB is re-created a 1027 event will be generated showing how many entries were created/updated

1.1.3 More Information
The voice server will not be available while re-synching or recreating the FEDB.


Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[KenMeans]

this says 1.0 but it is the same with 2.0. With 3.0 you do not have to rename any files since they switched to a SQL database.



The following steps show how to re-create the database.



1) 1) Stop the voice service

2) 2) Rename the copy of the file FEDB.mdb. You can find FEDB.mdb in

· · \\Unified Messenger\Vserver\fedb.mdb on UM4.x /UM5.0 systems

· · \\Avaya Modular Messaging\Vserver\fedb.mdb on MM1.0+ systems

3) 3) Make a copy of the file fedb.bak and rename this copy to fedb.mdb --> make sure and leave a copy of fedb.bak in case you ever need to do this again.

4) 4) Open the registry by clicking on Start->Run and typing regedt32

5) 5) Depending on the version of UM/MM proceed through the following steps:


Version MM1.0+ with the MSS Messaging Backend:

· · Navigate to the key HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr

· · Edit the Value NodeSeqTable

· · In the Data Value, enter 0,0;

· · Edit the Value CosSeqNo

· · In the Data Value, enter 0

1) 6) Close the registry.

2) 7) Re-start the voice service.

3) 8) Event 1030 in the Event Viewer will indicate that full FEDB synchronization has started.

4) 9) After the FEDB is re-created a 1027 event will be generated showing how many entries were created/updated





Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[ayavauser]

Ken
That did it ......finally got around to going in after hours but then upgraded to SP 8 and now have slight issue
but thank as this re-sync has solved a few issues at different sites : )

issue with going from SP5 to SP8 on MM1.1 / exchange backend

thread1496-1332117

cheers

ayavauser