Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MM 5.2 Single Server PLDS Licensing error

Status
Not open for further replies.

Daudet

Vendor
May 29, 2006
49
CA
Hello Everyone.
trying to license my Single Server Modular Messaging in PLDS and i am getting error that MM R4 or R5 cannot be generated without MM TTS REALSPEAK ANY in the license entitlement.

i have 200 licenses MM R5.2.1 new seat and 1 MM TTS REALSPEAK ANY license

i have included a snapshot of PLDS

Any clue.


Daniel Audet
Avaya Application Specialist
MTS Allstream
Montreal, Quebec, Canada
 
i think your voicemail domain needs to be the host id from the vmsc not the name of the vmd.

i can't tell from the pic but did you hit the activate all?

one other thing to try is to remove the seat tracking on the top line and make it a 0 that can mess it up.



Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
On the support.avaya.com website there is a PSN002744u that states:
MM5.2 orders will have several SAP codes on them. One code represents the type of message store used for the system. It can be any one of the following three codes: 223972, 224260 or 224261. PLDS will not generate a license with these codes on an order as PLDS doesn’t think these codes are associated with MM5.2. If you attempt to activate an MM5.2 order with one of the above codes, you will see the following error from PLDS: “Activation Failed – A Modular Messaging license file for releases 4 and 5 cannot be generated without MM TTS REALSPEAK ANY in the license file entitlement. A license file must include MM TTS REALSPEAK ANY in the product field.”

Resolution
ASD will be updated in the future to use tracking codes that PLDS will view as MM5.2 codes. Until that update is available, the workaround described below should be used to activate MM5.2 licenses.

Workaround or alternative remediation
Rather than activating all the entitlements on an MM5.2 order, the entitlements for the following codes should be “un checked”, so that only the remaining codes are activated. There is no loss of functionality for not activating these codes. The following codes should NOT be activated (note, only one of these codes would ever appear on a single MM5.2 order):
223972 MM R5.X DOMINO IBM DUC SEAT TRACKING
224260 MM R5.X MS EXCHANGE SEAT TRACKING
224261 MM R5.X AV STORE SEAT TRACKING

Activations of MM5.2 entitlements without the above codes will be successful and no error message will be generated from PLDS.

Hope this helps
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top