02-01-2019 02:59 PM
My colleagues and I use ACT Premium for web, and we all have ACT companion on our mobile phones. The majority of us have no problems, but one of my employees cannot get it to login. He is using all the correct credentials and his app is up to date. Are there any suggestions to fix this... or anyone know of reasons why this won't work for him?
02-02-2019 06:48 PM
Hello ... Question... did You check if the server URL has been typed correctly..?
On the log in page, enter your database username and database password in the respective fields, then tap Continue
In the Server Address URL field, enter the appropriate URL, depending on how you use Act!:
Act! Premium (access via web) or Act! Premium Cloud: Enter the URL (web address) you use to access your database (For example: https://[yourwebsite].com/apfw -or- https://[yourwebsite].com/[yourdatabasename] )
Act! Premium for Windows: Logged into Act! from the server, click Act! Connect in the Navbar on the left side of the screen. Use the URL (web address) shown at the top of the page. This cannot be obtained from a workstation. (For example: https://[port number].g2c.cloud-elements.com/act.web.api)
In the Server Database Name field, enter your database name exactly as shown in the drop-down menu on the login page for your database if you’re using Act! Premium (access via web), or as it appears in the top left corner of the Act! Program if you’re using Act! Premium for Windows
To avoid typing in the server address and database name in the future, enable the option to “Remember Server and Database”
Note: If you log out of the app, you will still need to enter your database username and password to log back into the app.
Good luck and do not forget to make a daily Database backup (File - Backup - Database - click on Browse to place this backup in your documents folder), and place a copy of that ZIP file in a USB memory or external disk for better security... In case the Hard Drive is damaged or receive a virus attack
Best regards... Praxi Solutions Inc
02-06-2019 07:08 AM
Yes we have confirmed The URL is typed exactly the same as all of the rest of ours but for some reason it will not let this particular employee login on the app. If we call customer service is this something they could help him with?
02-06-2019 08:57 AM
I've posted this in another thread, but wanted to make sure everyone was aware of how this can be resolved:
I wanted to provide an update to this thread on this issue, and it's status.
The development teams for Act! Companion and the Act! API reviewed the issue, were able to reproduce and identified its root cause. The issue stemmed from a CORS implementation on the API, which changed with the last update. The issue has been resolved, and will be released with Act! Companion v2.4 (releases this month - February) and a new API build being released alongside it. You'll be notified of the new Act! Companion version via the Google/Apple app store's update feature. New versions of the API can be downloaded from https://developer.act.com/
In the interim the issue can be resolved by updating the webconfig file for Act!/API to include both http://localhost:9595 AND https://localhost:9595.
Please let us know if you have any additional questions. If you would like early access to Act! Companion v2.4 for this fix, please email your app store email address (Google Play or Apple), and we will add you to the beta to get an early version - my email address is firstname.lastname@example.org. Beta will be available early next week.