Thank you for taking time here.
I created the account and tried to sign in for the first time.
I kept getting the same error message. I even reset the password.
But it did not work. I also tried to create another account by another email.
And I got the same error message.
I was trying to start using tableau for the course from Coursera.
But I cannot do exercise for it.
I am using a python connector to use snowflake from backend , I need a query or something to check whether my account is valid or it got expired basically for trial account, In Snowflake UI it is showing the error but when using the python connector I need to get a similar error like at the time of login itself
"you trail has expired" is not really a thing that people "normally" need to programmatically know about.
Unless you are repeatedly "programmatically" making more accounts, which seems against the purpose of the free accounts.
I would think that you python would start failing to log in, which it should back off and try again after an escalating timer (1s, 10s, 60s,..) but at the same time tell you there is a failure (of some sort) and at the time the account expires. You stop running your automation/python code.
I am getting an error when a user is trying to Register for the website my company is making. The error is "Lock request time out exceeded" . This mainly happens when the User is going through the registration process of the site. The tables will become locked during a read or write to the server. The lock out even occurs when the new registrant tries to confirm their email. Any ideas why. If you need anymore information I will try to add it as soon as possible.
Thanks
When I tried to add some accounts to yodlee, the program took a long time to refresh the accounts. After refreshing for more than 3 mins, the program threw the exception "InvalidConversationCredentialsExceptionFaultMessage" or "StaleConversationCredentialsExceptionFaultMessage".
I have several accounts with this problem. All the other accounts work fine.
Could somebody tell me why these kinds of exceptions happen and how to solve them?
Thanks a lot.
MCC
You get "InvalidConversationCredentialsExceptionFaultMessage" when the user context gets expired. This can be corrected by re initiating the user context
With respect to "StaleConversationCredentialsExceptionFaultMessage", you get this when yout ry logging in the same user multiple times (create user contexts)and try to use the user context that is already invalid by the subsequent one.
Please let me know if you need more information.
--Vijay
I am currently building an internal web application used in a factory/warehouse type location. The users will be sharing a single PC between several people, so we need to have a fairly short session timeout to stop people wandering off and leaving the application logged in where someone else can come to the PC and do something under the previous user's username.
The problem with this is a session can timeout while a user is currently entering information into a form, especially if they take a long time.
How would you deal with this in a user friendly manner?
Keep the server informed about the fact that the user is actively entering information.
For instance send a message to the server if the user presses the TAB key or clicks with a mouse on a field.
The final solution is up to you.
Use AJAX to regularly stash the contents of the partially filled-out form so they have not lost their work if they get booted by the system. Heck, once you're doing that, use AJAX to keep their session from timing out if they spend the time typing.
The best advice would probably be to ask the users to close the browser window once they're done. With the use of session-cookies, the session will automatically end when the browser is closed or otherwise on a 30 minute timeout (can be changed afaik).
Since there by default is no interaction between the browser and the server once a page is loaded, you would have to have a javascript contact the server in the background on forms-pages to refresh the session, but it seems a bit too much trouble for such a minor problem.
If the session timeout is so short that the user doesn't have the time to fill in a form, I would put an AJAX script that makes a http request to the server, every few minutes, to keep the session alive. I would do that only on pages that the user has to fill in something or has already started filling something.
Another solution would be to use a session timeout reminder script that popups a dialog to remind the user that the session is about to time out. The popup should display a "Logout" and a "Continue using application" that makes a ajax request to update the session time out.
Maybe that a keep-alive javascript process could be helpfull in this case. If the script capture some key triggers, it send a "I'm still typing" message to the server to keep the session alive.
have you considered breaking the form into smaller chunks?
Monitor the timeout and post a pop-up to notify the user that their current session will expire and present "OK" or "Cancel" buttons. OK to keep the session going (i.e. reset the counter to another 5 minutes or 10 minutes - whatever you need) -or- Cancel to allow the session to continue to countdown to zero and thus, ending.
That's one of lots of ways to handle it.
Using a JavaScript "thread" to keep the session open is, to me, a bad idea.
It's against the idea of session timeout which exists to free some resources if there's no user in front of the application.
I think you should adjust the session timeout with the more accurate time, in order to fill the form in an "typical normal use".
You may also be proactive by :
having a JavaScript alert displaying a non-intrusive warning (not a popup) to the user before the timeout expire, which say that the session will expire soon (and give an link to send an ajax request to reset the timeout and remove that warning - that will avoid the user to lost the form he is currently typing),
and also have a second JavaScript "thread", which, if the session has expired, redirect to the login page with a message saying that the session has now expired.
It think that's the best because it avoid the user to fill a complicated form for nothing, and handle the case when the user has gone away.
As an alternative for the technical solutions, you could make your application in such a way that everytime a particular job is done, for example filling in a form, you ask the user if he wants to continue doing another job or if he's done. Yould could have a startscreen with menu options and if the user chooses an option he first has to enter his credentials.
Or put a password field on the form. Depends on how many forms they have to fill in a session.
When the user posts the form and their session has timed out, you should make sure you save the form values somewhere and then ask the user to login again. Once they have re-authenticated you they can then re-submit the form (as none of their data will have been lost).
I had developed something requiring very long session. The user logged in on a page when he sit on the machine and after doing his work, logged out. Now he may use system for few minutes or for hours. To keep session alive till he logged out, I used timer with javascript, it went to server and updated an anthem label with current time on server.