Hi,

I've think I've the same problem. I just finished the MAS configuration, and want to continue the the MSS configuration. I get an error message :failed to create postmaster subscriber postmaster : (3504 - You cannot preform this operation without a valid license.)
However I checked the Licensing at the MAS system configuration and it shows normal.

Any ideas?

 

Was the license imported into the VMSC or just put into the WebLM?

www.theviagroup.com

The Avaya MM Install files and OpenSSL have been affected by the 2038 bug. The file C:\Avaya_Support\Scripts\CreateNInstallCert.cmd has values of 10001 and 10000 that generate self-signed certificates for the MM Licensing Service and WSO to expire in 2038. Adjust these values to 9001 and 9000 so the certificates expire in 2035. Then run the recreatelicensingservice.vbs to generate and install the new Licensing Certs.

Hi,
We have installed an MM 5.2 with patchs:
- MM520008
- MM520500
- MM520501
So, the MAS & MSS seem to works correctely, but during subscriber configuration from MSS web console, we receive the error "password is invalis (1023)".
The license state is normal and we have tried to run "licensing recovery tool" as described in some posts in avaya forum, without successful.
Any idea?

Regards,

Hosse,
  It appears I am having the exact same issue. Did you find a resolution yet?

when you do the MAS host setup on MSS - ensure that the private alias has two entries separated by a space. the first one should be the FQDN of the server in its private domain then the host name.

i have found that adding both these entries allows licensing to function OK.

Yes that is there. When I run the dct file it puts it there corretly. I have read countless threads/blogs that say to take out the fqn and just have the mss name i.e. "mymss1", that hasn't worked either. I have run the license recovery tool to many times to count, no luck. Everything shows fine on the MAS, license normal. I have tried building it manually, to elminate a corruption of the dct file, no luck. After reading several entries on the Avaya User Community it appears this is a known issue but not everyone has had the same fix. What has worked for one hasn't worked for the other. I just built a system a month ago with the same software/hardware and had no issue.

I was able to finally get the install to go through. After hours on google this weekend I found someone with the same problem. Their suggestion was:
copy the file CreateNInstallCert.cmd to the directory C:\Avaya_Support\Scripts\ on MAS server (Avaya sent me this file), change the file extensión to assure that it is a batch executable. Then You only have to execute the script RecreateLicensingService.vbs located in tha same folder.

This link you can donwload the CreateNInstallCert.cmd.txt.

http://www.gigasize.com/get.php?d=31f6mfhqlvf

I downloaded this file from the above site. Removed the existing file on the MAS and loaded the new one. Install completed and MM is operational. Note: when you download the file it will have cmd.txt, you have to remove the .txt so it is just a .cmd file.