Skip to main content

One of our customers went live  in FSM 6 update5 February 1st and for the first 2 weeks teches did not have any issue. But starting from 3rd week, they started seeing some of their mobile  items were not sent to server and waiting in the wait and ready queue.  If they log off and log in again, some of the waiting items get moved, but the 2nd time it tries to Sync , it does not happen. 

users mobile log has  following error

2/23/2021 4:35:09 PM|ERROR|GetMail|2|EXCEPTION: net_servererror, 400, Bad Request ...    at IFS.FSMW.Mobile!<BaseAddress>+0xbb4d20
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

Looking at the  Azure IIS log we see several  messages that say

<Data>A potentially dangerous Request.Path value was detected from the client (:). at System.Web.HttpRequest.ValidateInputIfRequiredByConfig() at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context) </Data>

<Data>https://XXX-fsm-prd.ifs.cloud:443/mobile/Activation/user=HTTPS:/XXXXXSTFSM.IFSCLOUD.NET/MOBILE/device=0</Data>

<Data>/mobile/Activation/user=HTTPS:/XXXXXSTFSM.IFSCLOUD.NET/MOBILE/device=0</Data>

We have ruled out, connectivity/internet issues. Also they use iOS and Window mobile and same is happening for both.

Have anyone seen this issue before?

Hi @didous,

Just to confirm, was the mm_message_out table cleared down after testing before going live? It may be a good idea to clear down the messages at an appropriate time to see if this clears the issue and prevent reoccurence.

Care will need to be taken that no sync information is lost when this is done though.

Kind regards,

Lee Pinchbeck

MM_MESSAGE_OUT  was cleared and no excessive records there. Issue is  it does not even go that far.

Hi @didous,

Is this always the same set of users or seen across all mobile users? Any pattern in the next items waiting to sync on the mobile device when this occurs?

It looks like Azure is spotting a request it deems harmful and blocking it so would need details of the request that is being sent in order to take a look and see why Azure might see it as dangerous. Is this IFS Cloud Azure or customers own Azure?

Kind regards,

Lee Pinchbeck

Terms & ConditionsCookie settings