Error: Please try later... when login from specific IPs

Error: Please try later... when login from specific IPs

It may be possible that the source IP may be lengthier than 20 characters and axpert will fail to insert in connections, axaudit tables.
The login trace in such scenarios would show up something like below and to resolve this, the IP field width has to be increased accordingly in the backend tables.
Error in login :value too long for type character varying(20)
Result : <error><msg>Please try later...</msg><pwdconf><minpwdchars>0</minpwdchars><pwdalphanumeric>F</pwdalphanumeric></pwdconf></error>


    • Related Articles

    • Error Activation Failed, Try later

      If you experience the below issue, when activating license or refreshing license. It may be due to agile' license server not reachable. You may check by using the below url over browser to see, if it opens without any error. Sometimes local network ...

    • Oops! there seems to be some problem. Please try later!

      This is a generic custom error page to hide any HTTP errors such as a 404 Not Found, or a 500 Server Error related errors to the end users. Below is the setting in web.config to switch on / off custom errors and it will be "On" by default. If ...

    • Error - REPOSTGENMAP

      Got an error when copy and run new latest 10.9 desktop exe on installed axpert folder. Please run this script oracle ALTER TABLE AXUSERS ADD REPOSTGENMAP VARCHAR2(1) mysql ALTER TABLE AXUSERS ADD COLUMN REPOSTGENMAP VARCHAR(1) mssql ALTER TABLE ...

    • Error Object reference not set to an instance of an object, when login through axpert developer connecting to postgres

      If you experience the below issue when establishing login through axpert developer over browser, it may be due to run schema connection details not available in developer scripts connections. (i.e. axapps.xml)

    • Error: License / App key invalid. Please contact Agile Support Team

      It could be due to following reasons. User may be trying to refresh the partner license using old exe. Use of latest exe may fix this problem The license may be originally activated from one windows login and user may be trying to refresh the same ...