Forum Discussion

mzadriennemc's avatar
13 years ago

Indexing Service will not start

I notice the Indexing servics for one of our EV mailbox servers will not start.  IThe error is below.  I have tried to reboot and I check the drives accessibility and space.  Everything looks normal.  Here are the errors I am seeing in the event viewer.  Help????

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          5/24/2012 11:23:46 AM
Event ID:      41293
Task Category: Index Admin Service
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Enterprise Vault_load : Error while reading file [C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\repository.xml.index.meta]: [not well-formed at line 1 col 0:+++ERROR+++] (ID: FILE_READ)error (0 ms) - Enterprise Vault_load : Error while reading file [C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\repository.xml.index.meta]: [not well-formed at line 1 col 0:+++ERROR+++] (ID: FILE_READ)error (0 ms) - Enterprise Vault_load : Reference node cannot be resolved. No [application] node [api-soap] defined (ID: XML_MACRO_REFERENCE)

and

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          5/24/2012 11:24:19 AM
Event ID:      6621
Task Category: Storage File Watch
Level:         Error
Keywords:      Classic
User:          N/A
Description:
An exception has occurred.
Type: ce
Reference: VSEMCC/CCSOS1
Reason: The system cannot find the path specified.  (0x80070003)

 

  • Does the path and xml file actually exist?
    and if the xml does exist, is it malformed? if you open it in IE it might come back and say its corrupt

    The Storage File Watch is a different error the indexing, but should be looked at, but you're going to have to dtrace SFW to see whats happening, did you move any partitions recently per chance?
     

  • Tried to open the file in IE but the file did not open.  I did not see an error nor did I see a corrupt message. 

    The Storage File Watch issue, I can run a dtrace but should I open a case to send the results?

  • If you want the community to take a look you would need to post the dtrace here, othewise, if you want a Symantec support tech to take a look open a case.

    Did the Indexing ever work?  Is this a new install?

     

  • Yes, Tony.  The Index services work before.  This just happened this morning.  Hre's the dtrace results:

    DTrace trace log for server: [Opened: 2012/05/24 14:20:01]

    Windows version: 6.1.7601

    Time zone: Pacific Daylight Time
    Time difference to UTC: -7:00

    -----

    Enabled Trace options

    Id    Name                             Detail     Include Events

    -----


    Display Filter:
      Include strings:
        EV-
        EV:
        EV~

      Exclude strings:
        CMMStream
        DBFramework
        DirectoryConnection
    -----

    Current File Rollover Settings: 100Mb

    -----


    Running in Terminal Services session...
      Monitoring debug output from processes running in the console session
      Monitoring debug output from processes running in the current Terminal Services session

    101 14:20:57.994  [3624] EV: CProcessState::SetStopping
    102 14:20:57.994  [3624] EV: CProcessState::SetStopping

    Registry info

     

  • glad you figured it out. for what it's worth, i just dealt with a similar issue and it was fixed by reinstalling the EV 10 (in our case, SP1) binaries.