Warning: Invalid argument supplied for foreach() in template_preprocess_search_results()

I add more error information:
I activated the taxonomy option of solr, then I have this error when searching for taxonomy:

Exception: "400" Status: Cant_use_ms_function_on_nonnumeric_legacy_date_field_created: Cant_use_ms_function_on_nonnumeric_legacy_date_field_created Error 400

HTTP ERROR: 400

Can't use ms() function on non-numeric legacy date field created

RequestURI=/solr/select

Powered by Jetty://

in DrupalApacheSolrService->_sendRawGet() (line 277 of /home/empresa/public_html/sites/all/modules/apachesolr/Drupal_Apache_Solr_Service.php).

Changed for the correct version of apache solr.
Nobody has similar issue?
it is a blocking bug for me
I have being using solr for several sites, works perfect for 6.x
but here with 7.x here is my blocking problem i don't know how to continue.
the solr service is up and running, it is shared with another drupal site 6.x where it is works OK.
Please help

I don't know what to do.
fund this http://drupal.org/node/443980
but don't apply because of the other sites sharing the solr service that are runing ok (with 6.x).
Lucene is working ok also
Index seem to work solr indexes the documents
but for solr search I have this

The Apache Solr search engine is not available. Please contact your site administrator.

and the previous errors

Seems to work for others? what we are missing, do we do something wrong? Is there anywhere we can try to find out?
Sorry for insisting;)

Installede apache solr search autocomplete and shows the autocomplete but when selection result:

The Apache Solr search engine is not available. Please contact your site administrator.

same errors as before and in the watchdog

"400" Status: Cant_use_ms_function_on_nonnumeric_legacy_date_field_created:

I think the problem is on the date.
I deactivated the filters by date published and updated
Now i don't have the error, apache solr is contacted at search results, and the template causes no problem.
I found the documents but I have this:

Notice: Undefined property: stdClass::$entity en apachesolr_search_process_response() (línea 577 de /home/empresa/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$bundle en apachesolr_search_process_response() (línea 577 de /home/empresa/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$entity en apachesolr_search_process_response() (línea 617 de /home/empresa/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$bundle en apachesolr_search_process_response() (línea 618 de /home/empresa/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$entity en apachesolr_search_process_response() (línea 622 de /home/empresa/public_html/sites/all/modules/apachesolr/apachesolr_search.module).

I will continue testing to check if the search results are ok with more nodes

You maybe right.
But i corrected deactivating and activating again the date filters, this maybe corrected the schema, but i tried before deleting the index with no results. Now it seems ok but still have the #7 messages
Many Thanks!

There's someway a problem with the dates, I updated more records and the problem of invalid foreach() and apache solr not contacted came again, deleting the index is not a result, now i have suppressed any filter by date and it works, I only have the #7 errors. If you want me to give more detailed info i will be very happy to reproduce or do any test you want me, now it works onlu the problem of #7

As written before, the issue of 400 is fixed, I am not sure if the solution was reindexing or activating/deactivating the date index.
Anyway the only issue now is

Notice: Undefined property: stdClass::$entity en apachesolr_search_process_response() (línea 580 de /home/boletin/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$bundle en apachesolr_search_process_response() (línea 580 de /home/boletin/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$entity en apachesolr_search_process_response() (línea 617 de /home/boletin/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$bundle en apachesolr_search_process_response() (línea 618 de /home/boletin/public_html/sites/all/modules/apachesolr/apachesolr_search.module).
Notice: Undefined property: stdClass::$entity en apachesolr_search_process_response() (línea 622 de /home/boletin/public_html/sites/all/modules/apachesolr/apachesolr_search.module).

it seems they don't prevend solr working.
I write this because i thing this is not related with deleting and reindexing or I am wrong? Please correct me
I don't change the status of this issue waiting for your indications

many Thanks

this is my shema and i do not have the requested lines. I did delete and restored index

<!--
 $Id: schema.xml,v 1.16 2010/12/09 04:39:00 pwolanin Exp $ 
-->
−
<!--

 This is the Solr schema file. This file should be named "schema.xml" and
 should be in the conf directory under the solr home
 (i.e. ./solr/conf/schema.xml by default)
 or located where the classloader for the Solr webapp can find it.

 For more information, on how to customize this file, please see
 http://wiki.apache.org/solr/SchemaXml
-->
−
<schema name="drupal-7.1.0" version="1.2">
−
<!--
 attribute "name" is the name of this schema and is only used for display purposes.
         Applications should change this to reflect the nature of the search collection.
         version="1.2" is Solr's version number for the schema syntax and semantics.  It should
         not normally be changed by applications.
         1.0: multiValued attribute did not exist, all fields are multiValued by nature
         1.1: multiValued attribute introduced, false by default 
         1.2: omitTermFreqAndPositions attribute introduced, true by default except for text fields.
       
-->
−
<types>
−
<!--
 field type definitions. The "name" attribute is
       just a label to be used by field definitions.  The "class"
       attribute and any other attributes determine the real
       behavior of the fieldType.
         Class names starting with "solr" refer to java classes in the
       org.apache.solr.analysis package.
    
-->
−
<!--
 The StrField type is not analyzed, but indexed/stored verbatim.
       - StrField and TextField support an optional compressThreshold which
       limits compression (if enabled in the derived fields) to values which
       exceed a certain size (in characters).
    
-->
<fieldType name="string" class="solr.StrField" sortMissingLast="true" omitNorms="true"/>
<!-- boolean type: "true" or "false" -->
<fieldType name="boolean" class="solr.BoolField" sortMissingLast="true" omitNorms="true"/>
−
<!--
 The optional sortMissingLast and sortMissingFirst attributes are
         currently supported on types that are sorted internally as strings.
       - If sortMissingLast="true", then a sort on this field will cause documents
         without the field to come after documents with the field,
         regardless of the requested sort order (asc or desc).
       - If sortMissingFirst="true", then a sort on this field will cause documents
         without the field to come before documents with the field,
         regardless of the requested sort order.
       - If sortMissingLast="false" and sortMissingFirst="false" (the default),
         then default lucene sorting will be used which places docs without the
         field first in an ascending sort and last in a descending sort.
    
-->
−
<!--
 numeric field types that store and index the text
         value verbatim (and hence don't support range queries, since the
         lexicographic ordering isn't equal to the numeric ordering) 
-->
<fieldType name="integer" class="solr.IntField" omitNorms="true"/>
<fieldType name="long" class="solr.LongField" omitNorms="true"/>
<fieldType name="float" class="solr.FloatField" omitNorms="true"/>
<fieldType name="double" class="solr.DoubleField" omitNorms="true"/>
−
<!--

      Note:
      These should only be used for compatibility with existing indexes (created with older Solr versions)
      or if "sortMissingFirst" or "sortMissingLast" functionality is needed. Use Trie based fields instead.

      Numeric field types that manipulate the value into
      a string value that isn't human-readable in its internal form,
      but with a lexicographic ordering the same as the numeric ordering,
      so that range queries work correctly.
    
-->
<fieldType name="sint" class="solr.SortableIntField" sortMissingLast="true" omitNorms="true"/>
<fieldType name="slong" class="solr.SortableLongField" sortMissingLast="true" omitNorms="true"/>
<fieldType name="sfloat" class="solr.SortableFloatField" sortMissingLast="true" omitNorms="true"/>
<fieldType name="sdouble" class="solr.SortableDoubleField" sortMissingLast="true" omitNorms="true"/>
−
<!--

     Numeric field types that index each value at various levels of precision
     to accelerate range queries when the number of values between the range
     endpoints is large. See the javadoc for NumericRangeQuery for internal
     implementation details.

     Smaller precisionStep values (specified in bits) will lead to more tokens
     indexed per value, slightly larger index size, and faster range queries.
     A precisionStep of 0 disables indexing at different precision levels.
    
-->
<fieldType name="tint" class="solr.TrieIntField" precisionStep="8" omitNorms="true" positionIncrementGap="0"/>
<fieldType name="tfloat" class="solr.TrieFloatField" precisionStep="8" omitNorms="true" positionIncrementGap="0"/>
<fieldType name="tlong" class="solr.TrieLongField" precisionStep="8" omitNorms="true" positionIncrementGap="0"/>
<fieldType name="tdouble" class="solr.TrieDoubleField" precisionStep="8" omitNorms="true" positionIncrementGap="0"/>
−
<!--
 The format for this date field is of the form 1995-12-31T23:59:59Z, and
         is a more restricted form of the canonical representation of dateTime
         http://www.w3.org/TR/xmlschema-2/#dateTime
         The trailing "Z" designates UTC time and is mandatory.
         Optional fractional seconds are allowed: 1995-12-31T23:59:59.999Z
         All other components are mandatory.

         Expressions can also be used to denote calculations that should be
         performed relative to "NOW" to determine the value, ie...

               NOW/HOUR
                  ... Round to the start of the current hour
               NOW-1DAY
                  ... Exactly 1 day prior to now
               NOW/DAY+6MONTHS+3DAYS
                  ... 6 months and 3 days in the future from the start of
                      the current day

         Consult the DateField javadocs for more information.
      
-->
<fieldType name="date" class="solr.DateField" sortMissingLast="true" omitNorms="true"/>
−
<!--
 A Trie based date field for faster date range queries and date faceting. 
-->
<fieldType name="tdate" class="solr.TrieDateField" omitNorms="true" precisionStep="6" positionIncrementGap="0"/>
−
<!--
 solr.TextField allows the specification of custom text analyzers
         specified as a tokenizer and a list of token filters. Different
         analyzers may be specified for indexing and querying.

         The optional positionIncrementGap puts space between multiple fields of
         this type on the same document, with the purpose of preventing false phrase
         matching across fields.

         For more info on customizing your analyzer chain, please see
         http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters
     
-->
−
<!--
 One can also specify an existing Analyzer class that has a
         default constructor via the class attribute on the analyzer element
    <fieldType name="text_greek" class="solr.TextField">
      <analyzer class="org.apache.lucene.analysis.el.GreekAnalyzer"/>
    </fieldType>
    
-->
−
<!--
 A text field that only splits on whitespace for exact matching of words 
-->
−
<fieldType name="text_ws" class="solr.TextField" positionIncrementGap="100">
−
<analyzer>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
</fieldType>
−
<!--
 A text field that uses WordDelimiterFilter to enable splitting and matching of
        words on case-change, alpha numeric boundaries, and non-alphanumeric chars,
        so that a query of "wifi" or "wi fi" could match a document containing "Wi-Fi".
        Synonyms and stopwords are customized by external files, and stemming is enabled.
        Duplicate tokens at the same position (which may result from Stemmed Synonyms or
        WordDelim parts) are removed.
        
-->
−
<fieldType name="text" class="solr.TextField" positionIncrementGap="100">
−
<analyzer type="index">
<charFilter class="solr.MappingCharFilterFactory" mapping="mapping-ISOLatin1Accent.txt"/>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
−
<!--
 in this example, we will only use synonyms at query time
        <filter class="solr.SynonymFilterFactory" synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
        
-->
−
<!--
 Case insensitive stop word removal.
          add enablePositionIncrements=true in both the index and query
          analyzers to leave a 'gap' for more accurate phrase queries.
        
-->
<filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt" enablePositionIncrements="true"/>
<filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1" preserveOriginal="1"/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.SnowballPorterFilterFactory" language="English" protected="protwords.txt"/>
<filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
</analyzer>
−
<analyzer type="query">
<charFilter class="solr.MappingCharFilterFactory" mapping="mapping-ISOLatin1Accent.txt"/>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
<filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt" ignoreCase="true" expand="true"/>
<filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt" enablePositionIncrements="true"/>
<filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="0" catenateNumbers="0" catenateAll="0" splitOnCaseChange="1" preserveOriginal="1"/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.SnowballPorterFilterFactory" language="English" protected="protwords.txt"/>
<filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
</analyzer>
</fieldType>
−
<!--
 Edge N gram type - for example for matching against queries with results 
        KeywordTokenizer leaves input string intact as a single term.
        see: http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
   
-->
−
<fieldType name="edge_n2_kw_text" class="solr.TextField" positionIncrementGap="100">
−
<analyzer type="index">
<tokenizer class="solr.KeywordTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.EdgeNGramFilterFactory" minGramSize="2" maxGramSize="25"/>
</analyzer>
−
<analyzer type="query">
<tokenizer class="solr.KeywordTokenizerFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
</fieldType>
<!--  Setup simple analysis for spell checking -->
−
<fieldType name="textSpell" class="solr.TextField" positionIncrementGap="100">
−
<analyzer>
<tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt"/>
<filter class="solr.LengthFilterFactory" min="4" max="20"/>
<filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
</analyzer>
</fieldType>
−
<!--
 This is an example of using the KeywordTokenizer along
         With various TokenFilterFactories to produce a sortable field
         that does not include some properties of the source text
      
-->
−
<fieldType name="sortString" class="solr.TextField" sortMissingLast="true" omitNorms="true">
−
<analyzer>
−
<!--
 KeywordTokenizer does no actual tokenizing, so the entire
             input string is preserved as a single token
          
-->
<tokenizer class="solr.KeywordTokenizerFactory"/>
−
<!--
 The LowerCase TokenFilter does what you expect, which can be
             when you want your sorting to be case insensitive
          
-->
<filter class="solr.LowerCaseFilterFactory"/>
−
<!--
 The TrimFilter removes any leading or trailing whitespace 
-->
<filter class="solr.TrimFilterFactory"/>
−
<!--
 The PatternReplaceFilter gives you the flexibility to use
             Java Regular expression to replace any sequence of characters
             matching a pattern with an arbitrary replacement string,
             which may include back refrences to portions of the orriginal
             string matched by the pattern.

             See the Java Regular Expression documentation for more
             infomation on pattern and replacement string syntax.

             http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/package-summary.html

        <filter class="solr.PatternReplaceFilterFactory"
                pattern="(^\p{Punct}+)" replacement="" replace="all"
        />
        
-->
</analyzer>
</fieldType>
<!-- A random sort type -->
<fieldType name="rand" class="solr.RandomSortField" indexed="true"/>
−
<!--
 since fields of this type are by default not stored or indexed, any data added to
         them will be ignored outright
     
-->
<fieldtype name="ignored" stored="false" indexed="false" class="solr.StrField"/>
</types>
−
<fields>
−
<!--
 Valid attributes for fields:
     name: mandatory - the name for the field
     type: mandatory - the name of a previously defined type from the <types> section
     indexed: true if this field should be indexed (searchable or sortable)
     stored: true if this field should be retrievable
     compressed: [false] if this field should be stored using gzip compression
       (this will only apply if the field type is compressable; among
       the standard field types, only TextField and StrField are)
     multiValued: true if this field may contain multiple values per document
     omitNorms: (expert) set to true to omit the norms associated with
       this field (this disables length normalization and index-time
       boosting for the field, and saves some memory).  Only full-text
       fields or fields that need an index-time boost need norms.
   
-->
−
<!--
 The document id is derived from a site-spcific key (hash) and the entity type and ID like:
     $document->id = $hash . '/node/' . $node->nid; 
-->
<field name="id" type="string" indexed="true" stored="true" required="true"/>
−
<!--
 entity_id is tlong, since in some cases we may want to use it as a default sort to
        get deterministic ordering of results 
-->
<field name="entity_id" type="tlong" indexed="true" stored="true" required="true"/>
−
<!--
 entity is 'node', 'file', 'user', or some other Drupal object type 
-->
<field name="entity" type="string" indexed="true" stored="true" required="true"/>
−
<!--
 bundle is a node type, or as appropriate for other entity types 
-->
<field name="bundle" type="string" indexed="true" stored="true"/>
<field name="bundle_name" type="string" indexed="true" stored="true"/>
−
<!--
 legacy: type is a node type, or can be used flexibly for other entity types 
-->
<field name="type" type="string" indexed="true" stored="true"/>
<field name="type_name" type="string" indexed="true" stored="true"/>
−
<!--
 Copy the bundle to the type so Drupal 6 sites get expected fields in multisite search 
-->
<copyField source="bundle" dest="type"/>
<copyField source="bundle_name" dest="type_name"/>
<field name="site" type="string" indexed="true" stored="true"/>
<field name="hash" type="string" indexed="true" stored="true"/>
<field name="url" type="string" indexed="true" stored="true"/>
−
<!--
 title is the default field for a human-readable string for this entity 
-->
<field name="title" type="text" indexed="true" stored="true" termVectors="true" omitNorms="true"/>
<field name="sort_title" type="sortString" indexed="true" stored="false"/>
−
<!--
 body is the default field for full text search - dump crap here 
-->
<field name="body" type="text" indexed="true" stored="true" termVectors="true"/>
<field name="teaser" type="text" indexed="false" stored="true"/>
<field name="path" type="string" indexed="true" stored="true"/>
<field name="path_alias" type="text" indexed="true" stored="true" termVectors="true"/>
−
<!--
 These are the fields that correspond to a Drupal node. The beauty of having
     Lucene store title, body, type, etc., is that we retrieve them with the search
     result set and don't need to go to the database with a node_load. 
-->
<field name="uid" type="long" indexed="true" stored="true"/>
<field name="name" type="text" indexed="true" stored="true" termVectors="true"/>
<field name="sname" type="string" indexed="true" stored="false"/>
<field name="sort_name" type="sortString" indexed="true" stored="false"/>
<field name="created" type="tdate" indexed="true" stored="true"/>
<field name="changed" type="tdate" indexed="true" stored="true"/>
<field name="last_comment_or_change" type="tdate" indexed="true" stored="true"/>
<field name="nid" type="long" indexed="true" stored="true"/>
<field name="status" type="boolean" indexed="true" stored="true"/>
<field name="promote" type="boolean" indexed="true" stored="true"/>
<field name="moderate" type="boolean" indexed="true" stored="true"/>
<field name="sticky" type="boolean" indexed="true" stored="true"/>
<field name="tnid" type="long" indexed="true" stored="true"/>
<field name="translate" type="boolean" indexed="true" stored="true"/>
<field name="language" type="string" indexed="true" stored="true"/>
<field name="comment_count" type="tint" indexed="true" stored="true"/>
<field name="tid" type="long" indexed="true" stored="true" multiValued="true"/>
<field name="vid" type="long" indexed="true" stored="true" multiValued="true"/>
<field name="taxonomy_names" type="text" indexed="true" stored="false" termVectors="true" multiValued="true" omitNorms="true"/>
−
<!--
 The string version of the title is used for sorting 
-->
<copyField source="title" dest="sort_title"/>
−
<!--
 The string versions of the name used for sorting/multi-site facets 
-->
<copyField source="name" dest="sname"/>
<copyField source="name" dest="sort_name"/>
−
<!--
 Copy terms to a single field that contains all taxonomy term names 
-->
<copyField source="ts_vid_*" dest="taxonomy_names"/>
<copyField source="tm_vid_*" dest="taxonomy_names"/>
−
<!--
 Here, default is used to create a "timestamp" field indicating
        when each document was indexed.
-->
<field name="timestamp" type="date" indexed="true" stored="true" default="NOW" multiValued="false"/>
−
<!--
 This field is used to build the spellchecker index 
-->
<field name="spell" type="textSpell" indexed="true" stored="true" multiValued="true"/>
−
<!--
 copyField commands copy one field to another at the time a document
        is added to the index.  It's used either to index the same field differently,
        or to add multiple fields to the same field for easier/faster searching.  
-->
<copyField source="title" dest="spell"/>
<copyField source="body" dest="spell"/>
−
<!--
 Dynamic field definitions.  If a field name is not found, dynamicFields
        will be used if the name matches any of the patterns.
        RESTRICTION: the glob-like pattern in the name attribute must have
        a "*" only at the start or the end.
        EXAMPLE:  name="*_i" will match any field ending in _i (like myid_i, z_i)
        Longer patterns will be matched first.  if equal size patterns
        both match, the first appearing in the schema will be used.  
-->
−
<!--
 A set of fields to contain text extracted from HTML tag contents which we
        can boost at query time. 
-->
<dynamicField name="tags_*" type="text" indexed="true" stored="false" omitNorms="true"/>
−
<!--
 We use long everywhere we used int previously since 64 bit ints are now typical in PHP. 
-->
<dynamicField name="is_*" type="long" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="im_*" type="long" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="sis_*" type="slong" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="sim_*" type="slong" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="ss_*" type="string" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="sm_*" type="string" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="ts_*" type="text" indexed="true" stored="true" multiValued="false" termVectors="true"/>
<dynamicField name="tm_*" type="text" indexed="true" stored="true" multiValued="true" termVectors="true"/>
<dynamicField name="tsen2k_*" type="edge_n2_kw_text" indexed="true" stored="true" multiValued="false" omitNorms="true" omitTermFreqAndPositions="true"/>
<dynamicField name="twsm_*" type="text_ws" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="ds_*" type="tdate" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="dm_*" type="tdate" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="bm_*" type="boolean" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="bs_*" type="boolean" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="fs_*" type="sfloat" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="fm_*" type="sfloat" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="ps_*" type="sdouble" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="pm_*" type="sdouble" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="tis_*" type="tlong" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="tim_*" type="tlong" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="tfs_*" type="tfloat" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="tfm_*" type="tfloat" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="tps_*" type="tdouble" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="tpm_*" type="tdouble" indexed="true" stored="true" multiValued="true"/>
−
<!--
 In rare cases a date rather than tdate is needed for sortMissingLast 
-->
<dynamicField name="dds_*" type="date" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="ddm_*" type="date" indexed="true" stored="true" multiValued="true"/>
−
<!--
 In case a 32 bit int is really needed, we provide these fields 
-->
<dynamicField name="iis_*" type="integer" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="iim_*" type="integer" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="isis_*" type="sint" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="isim_*" type="sint" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="itis_*" type="tint" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="itim_*" type="tint" indexed="true" stored="true" multiValued="true"/>
<!-- Sortable version of the dynamic string field -->
<dynamicField name="sort_ss_*" type="sortString" indexed="true" stored="false"/>
<copyField source="ss_*" dest="sort_ss_*"/>
<!-- A random sort field -->
<dynamicField name="random_*" type="rand" indexed="true" stored="true"/>
−
<!--
 This field is used to store node access records, as opposed to CCK field data 
-->
<dynamicField name="nodeaccess*" type="integer" indexed="true" stored="false" multiValued="true"/>
−
<!--
 The following causes solr to ignore any fields that don't already match an existing
        field name or dynamic field, rather than reporting them as an error.
        Alternately, change the type="ignored" to some other type e.g. "text" if you want
        unknown fields indexed and/or stored by default 
-->
<dynamicField name="*" type="ignored" multiValued="true"/>
</fields>
−
<!--
 Field to use to determine and enforce document uniqueness.
      Unless this field is marked with required="false", it will be a required field
   
-->
<uniqueKey>id</uniqueKey>
−
<!--
 field for the QueryParser to use when an explicit fieldname is absent 
-->
<defaultSearchField>body</defaultSearchField>
−
<!--
 SolrQueryParser configuration: defaultOperator="AND|OR" 
-->
<solrQueryParser defaultOperator="AND"/>
</schema>

I am very sorry, i did a complete and clean procedure from the begining again and now i have no more te related errors.
One of my mistakes was not copying again the config files from the apachesolr modules since i was updating from 6 to 7, and i had other sites running 6 and sharing the solr service on the same machine. I did not try no restart the solr modules on the 6.x installations sharing the solr, but i don't want more errors and i don't know if they will be compatible, it is not urgent for me anyway but if you can confirm they will be compatible it will help.

I apologize for the incovenience since it was my error.

Now i have 2 installations of drupal 7 with solr sharing the new 7.x config files. As i said i have no errors now in one of them, but in the other, after deleting and rebuilding, even after uncheking all the filters i have the following error when indexing:

Hubo un error HTTP AJAX. Código de Resultado HTTP: 500 A continuación se detalla la información de depuración. Ruta: /batch?render=overlay&id=125&op=do StatusText: error ResponseText: Recoverable fatal error: Argument 1 passed to drupal_http_build_query() must be an array, string given, called in /home/empresa/public_html/includes/common.inc on line 2157 and defined en drupal_http_build_query() (línea 473 de /home/empresa/public_html/includes/common.inc).

Please help because i am indexing each day and the number of documents will be big, in case i will have to delete and reindex several times.

I also noticed that when i delete the index on one site, the index on the other site is also deleted, is that correct?

Many Thanks!
Enrique

I tried to uninstall apachesolr and then reinstall, then delete the index but after deleting i allways have a number of documents left to send even before queueing content after deleting the index. I also have another misbehaviour, i have several content types, then trying to reset everything, on content bias i try to exclude/include types on the index but this stays unchanged and i cannot modify.

regards
Enrique