Last post Nov 22, 2006 04:19 AM by gcadet
Nov 20, 2006 12:19 PM|ultracrystal|LINK
Last night I was sending SOAP messages to MPS when suddenly the system stopped responding. I then tried to log into MPSSampleCP to confirm the system's state, but was unable to do so. I am able to authorize the username and password, but after that, it
just hangs. The log files state that '/MPSSampleCP/Logon.aspx - 1 Connection_Dropped DefaultAppPool'. I restarted the MPS01 server, recycled the DefaulAppPool and even restarted IIS. All to no avail. If anyone has any ideas it would be greatly appreciated.
Nov 20, 2006 04:26 PM|DGaikovoi|LINK
Is the error from HTTPERR file? Any additional errors in Event Viewer?
What did you cahnge (or try to change) when "suddenly the system stopped responding"?
Nov 20, 2006 04:52 PM|ultracrystal|LINK
The error is form the HTTPERR file. Event viewer has been consitently showing the following error:
The agent was unable to send data to the MOM Server at MOM01.#####. The error code is 10054, An existing connection was forcibly closed by the remote host..
The agent connection timed out waiting for a response from the MOM Server MOM01.##### The timeout is 4800000 milliseconds.
When the system stopped responding I was sending SOAP requests from a Java application. After sending 3 or 4, the system completely stopped responding to my requests. I was sanding SOAP requests to retrieve the MailboxPLans from Plans.asmx. I then proceeded
to log into MPSSampleCP but was unable. I did not change anything on the system to provoke this behaviour.
Nov 20, 2006 04:53 PM|ultracrystal|LINK
Also, SP1 is installed on the servers so this shouldn't be the issue.
Nov 20, 2006 05:10 PM|DGaikovoi|LINK
Nov 21, 2006 06:00 AM|gcadet|LINK
I don't see any reason why the MOM agent could freeze the MPS engine.
Do you use HMC 3.5? I don't think so because In MPS 2.1 (HMC 3.5), the
SOAP ISAPI is discontinued.
If you are in HMC 3.0 there is a hotfix for a deadlock in MpasClient.dll.
Did your soap request used to work ?
Did you try to restart SQL services?
Nov 21, 2006 01:04 PM|ultracrystal|LINK
Nov 21, 2006 01:17 PM|DGaikovoi|LINK
Nov 21, 2006 01:29 PM|ultracrystal|LINK
Nov 21, 2006 01:54 PM|DGaikovoi|LINK
You HMC setup is in the disaster. Nothing will works without MPSSQL01. MPS keeps all configuration info on that server (in default HMC setup).
Push "IT guy at the customer site" to restore old MPSSQL01 for you. Or you have to re-install whole solution.
Nov 21, 2006 02:05 PM|ultracrystal|LINK
Nov 21, 2006 02:26 PM|ultracrystal|LINK
Nov 21, 2006 03:06 PM|DGaikovoi|LINK
It will much easier for you if he will change server name to MPSSQL01. By the way, could you describe you MPSSQL01/02 setup in details?
Nov 21, 2006 04:14 PM|ultracrystal|LINK
My understanding of the SQL server setup is that there are two SQL servers (MPSSQL01 and MPSSQL02) running in a virtual cluster named MPSSQLVC01. That is the extennt of my knowledge with regards to the SQL setup. Also, when I browse through the MPS deployment
tool I see may references to MPSSQL01 and MPSSQL02 which bothers me because the IT guy is under the impression that both servers contain the same information. I'm certainly no expert in this domain, but it would seem to me that the servers do not contain
the same information if they are individually reference in the deployment. Any thoughts?
Nov 21, 2006 05:00 PM|DGaikovoi|LINK
Actually, the situation is quite different. MPSSQL01 and MPSSQL02 are cluster nodes (passive and active). This cluster runs virtual SQL server named MPSSQLVC01. In your HMC deployment tool, all references to SQL Server should point to MPSSQLVC01. In this
case, it will not matter what cluster node is off-line, because virtual server (cluster) MPSSQLVC01 will be available.
Try to edit Deployment tool configuration file to point all references to MPSSQLVC01. Then try to re-install related features.
Nov 22, 2006 04:19 AM|gcadet|LINK
I understand tha tyou have SLQ installed on a cluster. Your cluster is a 2 nods cluster : MPSSQL01 and MPSSQL02 and the SLQ virtual instance is MPSSQLVC01.
The SQL server that must be referenced in MPS is MPSSQLVC01. This virtual SQL instance can run on both nods but this has no importance.
If you reference in MPS, the SQL server with the nod name (example : MPSSQL01 ) it will work as soon as you fail over the SQL vritual server on the second nod. After the failover, SQL service are not any more on MPSSQL01 but are on MPSSQL02.
Your IT SQL admin will confirm.
It is not easy to change the name of the SQL server after MPS deployment.
MPS create few databases on SQL and cannot work without these databases. if you manually try to change SQL server name you will face a lot of problem (I tried and finally reinstall everything after a huge amount of time wasted)
If you are in a test/deployment step, you must unsinstall and reinstall with the correct SQL virtual server name.
If you already provisionned users, you can try to backup MPS databases, uninstall, reinstall and restore. But I am not sure that this will work.
Look at the doc:
Procedure DWSPV.20: To deploy the Core Platform