mteece / salesforce-dotnet

Automatically exported from code.google.com/p/salesforce-dotnet
0 stars 0 forks source link

Internal Server Error (500) on login #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Try to add new lead
2. When verifying login error is thrown.

What is the expected output? What do you see instead?

Error is thrown at line 154 of GzipWebRequest.cs

What version of the product are you using? On what operating system?

Please provide any additional information below.

I have confirmed the the username/password is correct and i have tried this
with and without the token.

Original issue reported on code.google.com by adamco...@gmail.com on 28 Sep 2009 at 11:54

GoogleCodeExporter commented 9 years ago
Nevermind.  I reset my token, and it works properly.

Original comment by adamco...@gmail.com on 29 Sep 2009 at 12:31

GoogleCodeExporter commented 9 years ago
In my case, resetting the token did not fix the error. However, I found that if 
there
is a mismatch between fieldnames in the Wrapper Controller, and in my Salesforce
database, the same error will occur. One can check this by examining the 
exception in
"private QueryResult Query(int batchSize, string query, params object[] args)" 
in
SforceProvider.cs.

Original comment by porter.ea@gmail.com on 7 Oct 2009 at 11:19

GoogleCodeExporter commented 9 years ago
adam, I don't know if my issue is the same as yours. using the service, i 
login. i 
get a loginResult object which contains a sessionId.  I set the sessionId to 
the 
service header object. Then I create a new lead object, set basic fields, then 
on my 
instance of LeadController I Add(lead). I get a 500 Internal Server Error at 
line 
154 as well. I just reset my token, and seeing as I get a sessionId I don't 
think 
it's an authentication issue.  any words of wisdom?

Original comment by pop...@gmail.com on 8 Oct 2009 at 6:55

GoogleCodeExporter commented 9 years ago
In my case it was an authentication issue.  However, an exception thrown at 
line 154 
just indicates that there was an error on the server.  Probably an error in 
your 
request, so it could really be anything (authentication, bad query, etc...).

What I do is step through the code until the point where the SOQL query is 
built. 
Then copy the complete SOQL query that is generated and paste it into the Apex 
Explorer and make sure that it works there.  More often than not my problem 
lies in 
the SOQL.

Original comment by adamco...@gmail.com on 8 Oct 2009 at 7:01

GoogleCodeExporter commented 9 years ago
I experienced the "error 500" myself as well. I tried debugging it with these 
attempts, but no luck:

1. Tried resetting token
2. Edited SOQL query, tested in Explorer - worked
3. Tried taking out the "$" separating the pass and token

No matter what, I still get a 500 error on line 134.

Original comment by st...@sacredbanner.com on 12 Sep 2011 at 4:58

GoogleCodeExporter commented 9 years ago
Update: I complete scratched the project and started again from the base 
download. I'm no longer getting 500 errors, but my searches aren't returning 
any results. :(

Original comment by st...@sacredbanner.com on 12 Sep 2011 at 5:18

GoogleCodeExporter commented 9 years ago
I too has a spell of these issues and found that it was due to trying to access 
a Field Name that had been changed/removed by my client.  Spent hours trying to 
debug and fix the issue and finally found this.

Original comment by abdefi...@gmail.com on 12 Sep 2011 at 5:22

GoogleCodeExporter commented 9 years ago
Debug the app and stop at Login Method in SForceProvider.cs and see if 
Properties.Settings.Default.Username and Properties.Settings.Default.Password 
have your credentials. If not, you should copy the applicationSettings section 
from the Gaiaware.Salesforce project into the client app .config file.  That 
worked for me.

Original comment by andres.v...@gmail.com on 23 Sep 2011 at 4:41