WSO wizard can't find MAS URL

[kepetersen]

Trying to install Web Subscriber Options (WSO) on a separate server (not a MAS or Customer provided) HP-DL360 factory delivered Server to also be used for the Web Client server. Accepted the defaults for IIS as port 80 and virtual server (wso). Next screen in the wizard is to place the URL of the MAS using either Protocol (http or https) and the port it uses. Defaults for the Protocol is https and for the port 443.

Entering the URL for the MAS and selecting the defaults or changing to these combinations (https + 55443 or 443; http + 80 or 82 or 55080) the wizard can't find the MAS. I can ping the MAS (IP & Name) from the Web Server to the MAS and vice versa.

The server name is part of the customer ADUC. Is there other permissions I need? Where do I look for what is failing? I don't see any significant events in the Application Log and there is not a wso installation log that I have seen on the system.

Any ideas?

 

[KenMeans]

i would check this

C:\Program Files\Avaya Modular Messaging\Web Subscriber Options\masinfo.cfg.

Open masinfo.cfg in notepad.

Verify MAS entry is

https://fqdnofmas:55443/

or what ever port you want to use

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)

 

[kepetersen]

I have this in the file but still no go.
The Application Log doesn't really have any info as to why it is not working.
I do see some wsodebuglog.shm files but how do you read these and would it tell me why the wizard won't complete.

 

[KenMeans]

What happens if you just use http instead of the SSL ?

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)

 

[kepetersen]

When I am in the Protocol screen of the wizard (separate web client server) using http doesn't work either.
On each MAS it was loaded, not from DCT, but installed later using the None or SSL default setting.

Question:
1. When you use the Install wizard on a separate server, does the MAS it is pointing to need the WSO element running?
2. When rebuilding the Web Client server OS, will all the .NET Framework elements be restored that are needed for the WSO?

 

[KenMeans]

1. No
2. Web Client should have nothing to do with this part of the install. What happens if you put in the IP instead of the FQDN ? As far as restoring the elements i don;t know how it could unless you are really doing a restore from image rather than an install.


Something is blocking it. I will say that most of the time i never put the WSO or the Web client in the customer domain but leave it in it's own work group.



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)

 

[kepetersen]

Ok, reloading it today and will leave it its own workgroup.

 

[kepetersen]

Reload the server, create folders on the desktop for MAS Apps DVD 1 of 2, Web Client DVD and the patches to go from 5.0 to 5.2 SP12.
Per Avaya TAC also loaded Microsoft .NET Framework 1.1 and 3.5. Verified that ASP .NET 2.0 was on the server. The server is still its workgroup and not connected to the customer domain. The WSO wizard was run locally by the technician onsite. After all of this, the wizard still fails at the Protocol screen that won't verify the URL using https: Protocol to Port 443 or 55443.

Any ideas?

 

[KenMeans]

Is this being done at the console or remotely ?

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]

I am not really sure what is causing this. I have done this many times and not run into this type of issue. Can you give me the exact error you get at the failure point ? and any errors in the app log and system log please.


it may be a cert problem as well.


Modular Messaging (MM) Release 5.1 with SP2 patch3
Web Subscriber Options 9.0.500.2006
Message Storage Server Backend

The time on Message Application Server & Message Storage Server are same
Verified the masinfo.cfg file is set correctly in C:\Program Files\Avaya Modular Messaging\Web Subscriber Options. For example, it is set to

https://Corporate

FQDN of MAS:55443/wso
Web Subscriber options is installed on MAS

Problem Clarification

When subscribers use the

http://Corporate

FQDN/wso gets the login page but when they enter the username and password, an error "Unable to connect to Remote Server" comes.
Cause

Corporate Fully Qualified Domain Name (FQDN) is incorrect in the MAS "hosts" file.

Please note this is an example.

The host file on WSO is as following:

MSS Corporate FQDN: mss.abc1.com
MSS Corporate IP: 172.16.253.77
MSS Private FQDN: mss.abc.local
MSS Private IP: 192.168.1.1

MAS Corporate FQDN: mas.abc1.local
MAS Corporate IP: 172.16.253.78
MAS Private FQDN: mas.abc1.local
MAS Private IP: 192.168.1.250

MAS Corporate FQDN is wrong. It should be "mas.abc1.com".
Solution

Correct the Host file on MSS and send it on to MAS.

Regenerate the certificate using correct MAS Corporate FQDN.

Correct the MAS Corporate FQDN on "MAS host setup" page.

Send the "MAS Host send" on MSS.

Verify the host file on MAS is now correct. (You can do the Start\Run & type "drivers" & Enter. Then go to "etc" folder. In this etc folder you will see the hosts file).

Then follow the below steps to regenerate the new Certificates:

Clear all certificates that had been previously installed.

Click on Start -> Run -> mmc -> Add snapin -> Certificates.


1. Remove certificates with MAS FQDN and

http://www.avaya.wso.com

from personal and trusted root certificate folders.
2. Click on Start -> Programs -> Administrative Tools -> Internet Information Services (IIS) Manager.
Go to properties on Default Web Site -> Directory Security -> Server Certificate -> Remove current certificate.
Go to properties on MM_WebService -> Directory Security -> Server
Certificate -> Remove current certificate.

3. Create and import new certificates:
One the WSO server Click on Start -> Run -> cmd - When the Command Prompt Window opens type the following:

cd C:\Avaya_Support\Scripts

CreateNInstallCert /FQDN (space) FQDNofServer(Corporate)


When that completes, continue with the following:

1. Open current user temp folder (Start -> Run -> %temp%.)
2. Copy ca.cer and x509.cer to the desktop (CreateNInstallCert script creates these.)
3. Right click -> on ca.cer and select install certificate, install in the "Trusted Root" folder.
4. Right click -> on x509.cer and select install, install in the "Personal" folder.
5. Verify both certs have no issues (red x or yellow exclamation.)


Associate IIS Default Web Site and MM_WebService to the certificates you just created:

(Click on Start -> Programs -> Administrative Tools -> Internet Information Services (IIS) Manager.)
1. Go to properties on Default Web Site -> Directory Security -> Server Certificate -> Assign an existing certificate -> Select the certificate you created. This should be the one with the FQDN of the server you are installing WSO on.

2. Go to properties on MM_WebService -> Directory Security -> Server Certificate -> Assign an existing certificate -> Select the certificate you created. This should be the one with the FQDN of the server you are installing WSO on.

Verify MAS File settings:
1. Go to C:\Program Files\Avaya Modular Messaging\Web Subscriber Options\masinfo.cfg.
2. Open masinfo.cfg in notepad.
3. Verify MAS entry is

https://fqdnofmas:55443/

(Even if this in on as standalone server, it must be the FQDN of MAS 1.)
4. Save masinfo.cfg file - You may have to stop IIS to save.

Verify IIS Settings:
(Click on Start -> Programs -> Administrative Tools -> Internet Information Services (IIS) Manager.)
Under IIS Web Sites\Default Web Pages - The SSL Port must be 443.
Under IIS Web Sites\MM_Web Service - The SSL Port must be 55443.
1. Reset IIS (right click Internet Information Services -> All tasks -> Reset IIS.)

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)

 

[ChuckRCT]

I usually just add the URL anyways if I know it is right and click "next" and have the installation finish up, then install any MM patches, then get the necessary MAS certs on the WSO server. Problems with WSO seem to be 80% certificate issue related

Chuck
RCT Technologies

 

[kepetersen]

Lessons Learned: Had to install the .NET Framework 1.1 & 3.5 for the wizard to accept the URL in the masinfo.cfg file and complete the wizard. After the WSO loaded then I could load the Web Client wizard and start loading patches to the server up to MM 5.2 Service Pack 12.