Try to delete and re-create the schedules. Make sure to save the config prior! Best regardsRoman
Hi!Are you using PSO together with FSM? Any Firewalls involved that may block traffic?Best regardsRoman
Hi!did you try to “refresh schedules” or “re-start Integration Monitor” ? Make sure to also check the Integration Monitor Logs on the App Server. The IM sometimes requires a couple of minutes to recover after the Server was stopped and/or restarted.Also make sure to install a newer FSM release as subsequent updates were made to the IM since FSM6UPD9.Best regardsRoman
Understood. I think if you want to go 100 % sure, you should open a support ticket to get further input on possible issues. Best regardsRoman
You can input the verification file with the “Import” function available in the Administration Workspace.The SQL Azure DB Firewall can be configured within the Azure Portal. See also here:https://learn.microsoft.com/en-us/azure/azure-sql/database/firewall-configure?view=azuresqlBest regardsRoman
Hi @elenpel !Did you try sending the corresponding verification file (which is supplied with the HTM installation files)? This should produce information messages inside the Events like this: Try also restarting all PSO Services after you made the configuration.Also note if this is an Azure SQL DB that IP Whitelisting for the PSO Servers may be required, depending on your Azure SQL DB Firewall settings.Best regardsRoman
Thanks Kasun. I don’t think it’s because the storage permissions are missing as you can access the storage but no files are shown. I would except you wouldn’t even see the folder structure if the app can’t access the device storage. Not sure, if this may be related to something in the apps manifest (target SDK) as Android made changes to their storage permissions as following: Starting from Android 11 (SDK 30), apps can no longer access the entire external storage with the READ_EXTERNAL_STORAGE permission. Instead, apps must use the Storage Access Framework (SAF) to request access to specific files or directories. This is a security enhancement to protect user data and privacy. If your Android app was previously targeting SDK 31 and was able to access the phone's gallery with the READ_EXTERNAL_STORAGE permission, but it stopped working after updating the target SDK to 33, it's likely because of the new storage permission changes introduced in Android 11 (SDK 30) and Android 12 (SDK 3
@KAMANUK Are you using some kind of corporate device policy, that may interfere? Did you try on a different device / Android OS combination? Was it working in the past? Best regardsRoman
What’s the reason for making this change? I wouldn’t recommend changing the collation, unless it’s necessary due to a well-founded reason.Best regardsRoman
Hi Daniel,unfortunately, the FSM Installation Guide doesn’t include any recommendation - only for Oracle character set. However, to my knowledge our customers usually use SQL_Latin1_General_CP1_CI_AS or SQL_Latin1_General_CI_AS for SQL Servers.Hope that helps!Best regardsRoman
Hi Gui,I could imagine that some custom policies set by the customer in Azure are blocking this. They should check their Azure AD logs and/or Azure Events for more information. Eventually also something has to be changed in their Intune Work Profile.Best regardsRoman
Hi @Thomas Widmoser !We received a Hotfix for U25 via Case CS0169321 / INC0627305 which solved it. I checked the U26 Release Notes and somehow this fix isn’t mentioned under the corrections. I suggest raising a case and either requesting the above mentioned Hotfix or ask if this is fixed in U26 and go for a update. Best regardsRoman
Could you identify what exaclty is causing the db locks? Which transactions in particular?Best regardsRoman
Please refer to the “Notification Hub Settings” section:“The FSM Mobile for Android, iOS and Windows clients support push notifications. The Notification Hub Settings need to be configured for each device platform you will be using. The specific settings for each platform are provided to you upon request.”This means our FSM Mobile App already has this capability implemented and you have to request the information required for setting up ANH from our Support.Best regardsRoman
Ah ok, then it’s a bit tricky.From an application point of view you won’t be able to get the source ips as this is not actually logged specifically in FSM Server Log. You could try raising a “ask something else” ticket with our support to check with them for any other sources from the Infrastrutcutre perspective. Best regardsRoman
Hi @jantonio !if this is an on-premise environment, you can check the IIS log files at C:\inetpub\logs\LogFiles\W3SVC1 for all incoming calls to the respective server. This file also includes the source ip and request path for each IIS request logged. Best regardsRoman
Hi Kasun,this table is related to FSM Mobile functionality and logs the IDs of successfully delivered messages to the respective person and device combination. Best regardsRoman
Hi Brian,if you are a customer of the IFS managed cloud offering, you can request ANH setup via a ticket to IFS support. Otherwise you have to purchase and setup the service on your own.You can find more information on setting up push messaging in the attached guide. Best regardsRoman
Hi Piumal,I doubt that there is a simple way to retrieve the same information as in the License Admin screen through a lobby as you can’t get these values easily from the database - at least I’m not aware of it. As an alternative you could run queries against the Person and mx_t-table to get number of users for specific license types. Note that mx_t-table includes the tokens genertated for users that are currently consuming a license (license is consumend when the user logs in the first time). Best regardsRoman
Hi George,I’m not totally sure as I haven’t seen this error before. This is the description of the SQLLITE_BUSY result code:“The SQLITE_BUSY result code indicates that the database file could not be written (or in some cases read) because of concurrent activity by some other database connection, usually a database connection in a separate process.” (source: https://www.sqlite.org/rescode.html)Further, the PRAGMA cache_size is described as following:“Query or change the suggested maximum number of database disk pages that SQLite will hold in memory at once per open database file.” (source: https://www.sqlite.org/pragma.html)The obvious reason would be that the mobile database on the device couldn’t be created / updated because of a concurrent write activity. If it was a on-off issue, I wouldn’t bother to investigate in more detail now as it could be just something temporary. However, if you will receive this error quite frequently I would suggest to raise a support case.Best regardsRoma
@ssabo fyi: Best regardsRoman
Did you make any recent changes to the PSO servers and/or FSM - PSO integration?heck, if the PSO Gateway is running (Administration Workspace > Applications). Try also to restart it and send the load again from FSM.Best regardsRoman
FSM uses a PSO User for authentication against the PSO Gateway. This User is configured in FSM Scheduling App Params, App Params: Gateway User and Gateway Password. You have to check that this User is working when accessing PSO.Best regardsRoman
Hi!please check the Gateway User and Password configured in the FSM Scheduling App Params. It seems that the login details are incorrect.Also make sure that the Gateway URL configured in FSM is correct.Best regardsRoman
@ssabo I think you should raise this with our Support to get their view on this. Best regardsRoman
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
