+ Start a Discussion
Code MonkeeCode Monkee 

Errors inserting leads

I continue to receive faultcode 1222, faultstring "storage limit exceeded" when trying to insert a lead. This code worked in the past. There are only 2 leads in my lead area. Very frustrating.

Hi Code Monkee,

Please post the SOAP message on this thread so I can test it.


Code MonkeeCode Monkee
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xm
lns:tns="salesforce" xmlns:types="salesforce/encodedTypes" xmlns:xsd="http://www
.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" so
   <version type="string">1.9</version>
   <session_id type="string">tvuCrkuGoQQM51qWkaCsdudguGoQQM51qWkaCGzH1Odl2AcImxHXXFZMyPbtzKggVlhL</session_id>
  <tns:insert xmlns:tns="sfconnector:SalesforceConnector" type="methodCall">
   <type type="string">lead</type>
   <record type="map">
    <email type="string">bb@aol.com</email>
    <firstName type="string">Bob</firstName>
    <lastName type="string">Berry</lastName>
    <title type="string">Chief Software Development Enginee</title>
    <company type="string">Swift</company>
    <street type="string">12708 Pine View</street>
    <city type="string">Austin</city>
    <state type="string">TX</state>
    <country type="string">US</country>
    <postalCode type="string">78727</postalCode>
    <status type="string">Open</status>

Message Edited by DevAngel on 10-10-2003 11:37 AM


Hi Code Monkee,

Ok, the fog is lifting.  You recall there was a mix up in the provisioning of your account recently?  Well, as a result, your Developer Edition no longer has any licenses (Should have 2) and has 0 storage allocated (should have some).  If you want to get back on track right away, you should go ahead and sign up for another Developer Edition (your current one is fairly hosed).  You can still log into the org and, but I don't think you'll be able to do anything other than view data and certain setup functions.  You can view your custom fields if you need that info to reestablish the new DE org.

By the way, do not put actual session ids on this board.  It is a security risk and, although we are dealing with a DE that probably has no sensitive info, you should excercise secure practices at all times.  For the period that that session id is active, anyone could log into your org and trash it.

By the way, I munged the session id in your post for you. 

Message Edited by DevAngel on 10-10-2003 11:38 AM

Code MonkeeCode Monkee

Thanks Dave, I'll give a new Dev login a try.

BTW, I had mucked up the session id before posting.