I’m hoping someone might have some experience that could get us to the next step in troubleshooting as we are at a bit of a standstill.
Does anyone know how many customers are on Aurena Native, MWO?
Issue: When I run the MWO Service 10 app, I am continuously getting a time-out error during sync at the point where it is “Waiting for Server”.
Details:
We are in the middle of our upgrade going from Apps8 to Apps10. Everything is IFS, not FSM, so IFS MWO only.
TAS is installed
We intend to use Aurena Native, not RTM
All necessary System Parameter setup was done between our database architect and IFS’s TAS specialist
The setup for the user for my test case was verified by IFS SME as being correct (for both user setup and mobile user setup)
Our url is internal only at this time and I am accessing it internally
There are no errors in the logs.
In the Mobile User Log, the last action is consistently “Initialize data Waiting for Grouped Push”. It is Type-Info, not Type-Error or Warning.
I did a thorough trace log, but so far IFS has not identified any issue in the trace results.
We are working with IFS experts to identify the root cause, but I am asking the community as well since this is perplexing to all involved.
Anyone have a similar issue at any point during their upgrade or after go-live? Any input is much appreciated. If more details would help, please let me know.
Thanks in advance!
MWO Sync Failing
Hi,
Here are some of the things you can check that are set up to control the Group push process
- Check whether Group Push user and sites set up
- Check end user got correct site settings in the user allowed sites
- Check any errors in the Group Push Transaction Queue
-
- Check Database processers are active and running
-
+13There can be various reason for this, but you can try with redeploying .ins file. Here's the steps for that.
- Find the native app in the IEE (navigate the Applications form and search for your app)
- Delete the app versions
- Delete the app
Find the meta data file from one of the following location:
In the delivery installation files we have provided you please go to:
\InstallationFiles_<DeliveryID>\database\mwo
File Name:
ServiceEngAppOfflineMetaData.ins
Redeploy the ServiceEngAppOfflineMetaData.ins DB file properly(please make sure you have properly deployed and commit the changes to the DB. Deployment of this file takes few minutes). And check that the app is now available again in the 'Applications' form in IEE. And check the issue in the app again.
I’m hoping someone might have some experience that could get us to the next step in troubleshooting as we are at a bit of a standstill.
Does anyone know how many customers are on Aurena Native, MWO?
Issue: When I run the MWO Service 10 app, I am continuously getting a time-out error during sync at the point where it is “Waiting for Server”.
Details:
We are in the middle of our upgrade going from Apps8 to Apps10. Everything is IFS, not FSM, so IFS MWO only.
TAS is installed
We intend to use Aurena Native, not RTM
All necessary System Parameter setup was done between our database architect and IFS’s TAS specialist
The setup for the user for my test case was verified by IFS SME as being correct (for both user setup and mobile user setup)
Our url is internal only at this time and I am accessing it internally
There are no errors in the logs.
In the Mobile User Log, the last action is consistently “Initialize data Waiting for Grouped Push”. It is Type-Info, not Type-Error or Warning.
I did a thorough trace log, but so far IFS has not identified any issue in the trace results.
We are working with IFS experts to identify the root cause, but I am asking the community as well since this is perplexing to all involved.
Anyone have a similar issue at any point during their upgrade or after go-live? Any input is much appreciated. If more details would help, please let me know.
Thanks in advance!
Does the Group Push User have access to the sites?
+14Hi
In addition to above comments, Pls see below:
If you see device app state as “Initialize data Waiting for Grouped Push” means Grouped push has not yet finished the job. If this state keep longer time, then as in above post you need to check the data setup in the GP entities and GP user. You can also check the Grouped Push Transaction Trace to identify any Oracle errors.
But timeout you see in client sync screen is a different issue. May be you have a really slow running MWS/Database which could give TAS/Client to timeout the connections.
Thank you all for your responses! Sorry it took me so long to update this one. The parameter in our Batch Queue Configuration was set too low. IFS Tech Support in Sri Lanka was able to identify the root cause after quite a bit of troubleshooting.
Thanks again!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.