Invalid Session

[Bernadine Phenna]

Hello - I can connect using my Salesforce login but attempting
anything is kicking me out - I can see in the Metadata
"INVALID_SESSION_ID: Invalid Session ID found in SessionHeader:
Illegal Session".

Itching to write a few queries so if you could help me I would be most
appreciative.

Thank you

[Ryan Brainard]

Thanks for reporting this. A couple questions:

• Is your user a System Administrator?
• After login, do you go to select.php?
• When you say you are "attempting anything," can you be more specific? What are you clicking on after login that shows you the error?
• You said that you see the error "in the Metadata." Where exactly are you seeing the error? Is it in the standard red error box or are you seeing it somewhere else?

[Kenia, Ketan]

Please make sure you are using the correct Login Id for the Org you are connecting to. You might be connecting to Production and using Login credentials for Sandbox or vice versa.

--
You received this message because you are subscribed to the Google Groups "Workbench News & Discussion" group.
To post to this group, send email to forcewo...@googlegroups.com.
To unsubscribe from this group, send email to forceworkbenc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/forceworkbench?hl=en.

[Kenia, Ketan]

sforce.connection.sessionId = "{!$Api.Session_ID}

-----Original Message-----
From: forcewo...@googlegroups.com [mailto:forcewo...@googlegroups.com] On Behalf Of Bernadine Phenna
Sent: Monday, July 09, 2012 5:23 AM
To: Workbench News & Discussion
Subject: [Workbench: 198] Invalid Session

[sfid...@gmail.com]

Hello,

I am very frequently having this same issue and it makes workbench unusable for me.  Yes, I am an admin.  I do get to the select.php page upon login.  After logging in I usually go to do a SOQL query.  Sometime I immediately get the error message and sometime I can click a few buttons before I get the error.  Sometimes I can even get to the point that I execute my query.  But inevitably I always get a message saying that my session is invalid or expired.  The error message even appears sometimes right on the select.php page after logging in.  So, it really is when I try to do anything and very random.

[Ryan Brainard]

Hmm, have you noticed this with any other API tools (e.g. Data Loader)? This feels like an issue with Salesforce, but its hard to say for sure. Can you let me know what your Session Settings are for your org in Setup? I'm wondering if there is something there misconfigured. Also, is there anything else special about your org/user? 

[Stacey Chale]

I have not had this issue with any other tools.  Here are the session settings for my org.  

[Ryan Brainard]

Ah, I see what's happening! You have "Lock sessions to the IP address from which they originated" enabled. Workbench is running on Heroku, which distributes load across a fleet of "dynos" all which could have their own IP addresses, so when you login you are on a given dyno, but your next request might be on another one, so you are being logged out. It's a bit intermittent because there are (currently) four web dynos, so you have a 1/4 chance on each request to be booted out. I tried turing this on on my org and was easily able to reproduce it. Try disabling this and see if it solves the problem for you.

[Stacey Chale]

Yep, that did it!  And explains why it seemed totally random.  Thank you!!

On Fri, May 31, 2013 at 2:20 PM, <brai...@heroku.com> wrote:

Ah, I see what's happening! You have "Lock sessions to the IP address from which they originated" enabled. Workbench is running on Heroku, which distributes load across a fleet of "dynos" all which could have their own IP addresses, so when you login you are on a given dyno, but your next request might be on another one, so you are being logged out. It's a bit intermittent because there are (currently) four web dynos, so you have a 1/4 chance on each request to be booted out. I tried turing this on on my org and was easily able to reproduce it. Try disabling this and see if it solves the problem for you.

On Friday, May 31, 2013 10:32:04 AM UTC-7, Stacey Chale wrote: