I am using CLIq to build a CLI Data Loader Job.  I keep getting exceptions that tell me that the field mappings are invalid for the fields in the CSV that should not be mapped.  I get the following exception...

Exception occured during loadingcom.salesforce.dataloader.exception.MappingInitializationException: Field mapping is invalid: Street2 => 

For some reason, it does not like the fields that arent mapped.  I am really confused why this is happening because the SDL file workes in the Data Loader GUI, but not the CLI.  

Here is my process-conf file...

<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
	<bean id="paLeadInsert" class="com.salesforce.dataloader.process.ProcessRunner" singleton="false">
		<description>Created by Dataloader Cliq.</description>
		<property name="name" value="paLeadInsert"/>
		<property name="configOverrideMap">
			<map>
				<entry key="dataAccess.name" value="C:\dataloader\cliq_process\paLeadInsert\read\paLeadInsert.csv"/>
				<entry key="dataAccess.readUTF8" value="true"/>
				<entry key="dataAccess.type" value="csvRead"/>
				<entry key="dataAccess.writeUTF8" value="true"/>
				<entry key="process.enableExtractSuccessOutput" value="true"/>
				<entry key="process.enableLastRunOutput" value="true"/>
				<entry key="process.lastRunOutputDirectory" value="C:\dataloader\cliq_process\paLeadInsert\log"/>
				<entry key="process.mappingFile" value="C:\dataloader\cliq_process\paLeadInsert\config\paLeadInsert.sdl"/>
				<entry key="process.operation" value="insert"/>
				<entry key="process.statusOutputDirectory" value="C:\dataloader\cliq_process\paLeadInsert\log"/>
				<entry key="sfdc.bulkApiCheckStatusInterval" value="5000"/>
				<entry key="sfdc.bulkApiSerialMode" value="5000"/>
				<entry key="sfdc.debugMessages" value="false"/>
				<entry key="sfdc.enableRetries" value="true"/>
				<entry key="sfdc.endpoint" value="https://test.salesforce.com/services/Soap/u/21.0"/>
				<entry key="sfdc.entity" value="Lead"/>
				<entry key="sfdc.extractionRequestSize" value="500"/>
				<entry key="sfdc.insertNulls" value="false"/>
				<entry key="sfdc.loadBatchSize" value="100"/>
				<entry key="sfdc.maxRetries" value="3"/>
				<entry key="sfdc.minRetrySleepSecs" value="2"/>
				<entry key="sfdc.noCompression" value="false"/>
				<entry key="sfdc.password" value="ENCRYPTEDPASSWORD"/>
				<entry key="sfdc.timeoutSecs" value="60"/>
				<entry key="sfdc.useBulkApi" value="false"/>
				<entry key="sfdc.username" value="username@test.com"/>
			</map>
		</property>
	</bean>
</beans>

And here is my SDL file....

# SDL Mapping File
SearchKey=
BorrowerBirthDate=Borrower_Birthdate__c
MiddleName=
FirstName=FirstName
LoanPurpose=Purpose__c
EmailHId=
HashedSSN=
Zip=PostalCode
LeadSystemId=
City=City
Email=Email
OwnerID=
Street2=
WorkPhone=Work_Phone__c
Street1=Street
CoBorrowerHomePhone=Co_Borrower_Home_Phone__c
Stat60Dt=
CoBorrowerBirthDate=Co_Borrower_Birthdate__c
CellularPhone=Mobile_Phone__c
County=County__c
Suffix=
CLTV=
CoBorrowerMaritalStatus=Co_Borrower_Marital_Status__c
LoanNumber=Loan_Number__c
WorkPhoneExtension=
CoBorrowerLastName=Co_Borrower_Last__c
GCId=GCId__c
LoanAmount=Loan_Amount__c
FICO=
Comments=Description
CoBorrowerFirstName=Co_Borrower_First__c
DOB=
BorrowerMaritalStatus=Marital_Status__c
Zip4=
HomePhone=Phone
State=State
CoBorrowerWorkPhone=Co_Borrower_Work_Phone__c
InterestRate=
LeadTypeCode=Lead_Type__c
EncryptedSSN=
LTV=
CoBorrowerMiddleName=
StatusId=
LastName=LastName
CoBorrowerCellPhone=Co_Borrower_Mobile_Phone__c
BankerName=Banker_Name__c

Anyone know how to fix?

I am using an outputText tag along with a param tag to format a date file.  This works quite well in the sprin'09 release.  I get compile errors in Summer '09.  Here is a simple page that works in spring'09 but gets an error on save in the summer '09 release.

<apex:page >
  <h1>Congratulations</h1>
  This is your new Page
            <apex:outputText value="{0,date, MMMM d', 'yyyy}">
                <apex:param value="{!NOW()}" />
            </apex:outputText>

</apex:page>

The error message I get in summer '09 is below.  Does anyone have any idea how to get around this?  I have opened a case on this - the number is 02709898