• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

SharePoint/Mingle freezing up

 2 Replies
 3 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Leonard Courchaine
New Member Send Private Message
Posts: 0
New Member
9/25/2015 1:35 PM

Hi,

We went live on Lawson V10 (10.0.6/AIX) this past Monday and, 3 out of 4 days of being live, have had Lawson "downs" where the Mingle login page has become unresponsive due to the SharePoint server freezing up.  Each time this has happened, logging on the server has stopped and server has become unreachable.  Reboots have been required.  Once reboot occurs, folks can then login to Mingle/Lawson fine.  For users already logged in, they continue to run fine.  

Has anyone else experienced issues like this one?  We have a high priority ticket open with Infor along with Microsoft.  

Frustrated in Georgia,
Lenny

Carl.Seay
Veteran Member Send Private Message
Posts: 109
Veteran Member
10/1/2015 1:57 AM
Hi. Did you get this resolved?

I've seen Ming.le be slow to load, but have not seen the entire server freeze. SharePoint/Ming.le does require quite a bit of resources: 4 CPU and 8GB as a minimum, if I remember correctly. SharePoint also utilizes several databases.
Leonard Courchaine
New Member Send Private Message
Posts: 0
New Member
10/1/2015 11:00 AM
Carl, Thanks for responding.
Yes, the first thing we did was crank up the memory and processors but the issue still occured. One of our internal SharePoint experts then warned of this type of irrational behavior happening due to antivirus scanning so he pointed us to a MS kb article on scanning exclusions. Those were put into place. Now, here's the quandary. We think they activated those exclusions but the issue happened one more time after that. But then it hasn't happened again. So my theory is that it was indeed the scanning and that the exclusions put into place just took some time to propagate. We're hopeful that we're past this episode.
Thanks again, Lenny