Video Screencast Help

The file system volume \\SERVER\PATH\FILES has no Archive points associated.

Created: 22 Jun 2009 • Updated: 22 May 2010 | 48 comments
This issue has been solved. See solution.

Hi,

I had our EV 8 SP1 Server run out of disk space a few nights ago during an archive run. After creating and moving the temporary files location to another drive. Now when I run the archiving task I receive the following error in the EV event log.

Event Type: Warning
Event Source: Enterprise Vault
Event Category: File System Archiving Task
Event ID: 40976
Date: 22/06/2009
Time: 09:08:58
User: N/A
Computer: SHDCFM1
Description:
The file system volume \\?\UNC\SHDCFS1.south-hams.gov.uk\Users has no Archive points associated.

No items will be archived for this volume.

See the Administrator Help for information on configuring file system volume archive points.

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp

However if you check the archive points on the file server volumes you can clearly see they have archive points associated.

I really need a help fixing this as this has grounded our archiving project. I have logged a call with Symantec and its been 5 days without reply.

Any ideas?

Thanks in advance,

Dan

Comments 48 CommentsJump to latest comment

AndrewB's picture

I have a support call open for over 2 weeks already. I mentioned this to our sales rep and and he ask them to escalate. You might consider doing the same since you state it impacts your project.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

Liam Finn's picture

 Sounds like you are trying to put an archive point in the root of a share

you need to do thisvia command line

go to C:\program files\ enterprise vault  in the command prompt

if thats where your EV is installed on the EV server

The type archivepoints \\servername\share /CREATE

like this archivepoints \\SHDCFS1.south-hams.gov.uk\Users /CREATE

where servername = the funn UNC path of the server and where share = the name of the share 

dfwood's picture

The odd thing is EV had been working fine until the disk ran out of space and it stopped during the archiving process.

The archive point set on \\shdcfs1.south-hams.gov.uk\Users is autoenabled so it creates an archive of each indiviual users homedrive folder, this exact same problem is happening on another servers volume but this time the archive point is a standard one set on a folder below the share.

Yet oddly enough the other volume being archived on SHDCFS1 is being happly having its archive points recognised by EV.

MichelZ's picture

Hmm

ArchivePoints.exe does find the archive points, too?

Liam Finn's picture

The error says it cant find the archive point for the users share not the sub folders.

An archive point thats auto enabled has no archive point at the root, the archive point is on every sub folder.

If the archive point error was at the sub folder then it would show the archive point for users\foldername which it is not doing

If you ask me i would remove the archive points and create new ones

Also does this disk have space now, i ask because you said it ran out of disk space

dfwood's picture

Thanks for the question guys to answer you on those.

If I run ArchivePoints.exe with the Find switch it happly lists the archive point for those shared volumes.

The server did run out of space due to temorary file usage, I have since allocated the server an additional drive and moved the location for temporary file usage onto there.

I don't really want to delete and recreate all the archive points as this will create a new duplicate archives when we next run the archiving task.
 
Dan

Liam Finn's picture

So it lists the ones for the sub folders but the root is where the error is.

the error specifies the root of users which you have no archive point for

consider adding an archive point for the root of users

check your archiving task to see if the root of users is listed to be archived. the only reason why the system would try to archive the root of the folder would be if you have a task to do so

Did you always have the users set to auto enabled or were you once archiving the root of users then later changed to auto enabled?

dfwood's picture

Users has always been set to auto enabled, we have never had an archive point set there.

The really annoying thing is we are getting this on another servers volume which has a normal archive point set on a folder below the root share.

Liam Finn's picture

 is there any other event in the logs?

have you tried have tried FSAUTILITY -a -s unc path of target


Liam Finn's picture

When you moved the folder to the new disk did you recreate the share then restore the data to the new share?

If yes thats whats causing the issue. Your root folder creation date has changed and thats why the archive point is complaining

try this

archivepoints delete
FSAUtility -a -s


dfwood's picture

To clarify the EV server ran out of disk space during an archiving run, due to temporary file usage. I have since added a additional disk and moved the location of the temporary files to it.

I will try the FSAUtility -a -s and let you know how I get on.

dfwood's picture

I've run the FSAUtility -a -s and then run the archiving task again, but I still get the 2 eventlog messages stating The file system volume \\?\UNC\SHDCFS1.south-hams.gov.uk\Users has no Archive points associated & The file system volume \\?\UNC\web.south-hams.gov.uk\PlanningFiles has no Archive points associated.

Liam Finn's picture

 hmm let me think about this one

If you ask me I would recreate the archive points but thats me

dfwood's picture

Just to clarify, would recreating the archive points create new archives? as that would look untidy in the archive explorer ui for the end users.

Liam Finn's picture

 I have never seen it create new archives. All creating a new archive point does is establish, for EV, a location on the file server which it can archive from

Fro what you have told me EV is already trying to archive from these locations.

The options for me would be

1. add the archive point for the root of these folders
2. find out where this root folder is being archived from and change the targets to remove the root

dfwood's picture

I've deleted and recreated the archive points, rerun the archiving task and still the same to errors appear in the event viewer.

I looked in the xml outputs from the FSAUtility and it found all the archive points already exist.

Liam Finn's picture

 hmm do a dtrace when you kick off the FSA and let us see the output

dfwood's picture

I know its not huge but here is the output after you run the File Archiving Task, If you want me to enable any additional options please let me know.

DTrace trace log for server: SHDCFM1.south-hams.gov.uk
[Opened: 2009/06/23 15:36:31]

Enabled Trace options

Id Name Detail Include Events
4 - ArchiveTask Verbose Yes

-----

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

Exclude strings:
CMMStream
DBFramework
DirectoryConnection
-----

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

1 15:36:49.709 [5752] (EvFsaArchivingTask) <5608> EV~I |Event ID: 40983 Starting to process task: File System Archiving Task.
2 15:36:51.190 [5752] (EvFsaArchivingTask) <1668> EV~W |Event ID: 40976 The file system volume \\?\UNC\SHDCFS1.south-hams.gov.uk\Users has no Archive points associated.| No items will be archived for this volume.|See the Administrator Help for information on configuring file system volume archive points.
3 15:36:51.190 [5752] (EvFsaArchivingTask) <2868> EV~W |Event ID: 40976 The file system volume \\?\UNC\web.south-hams.gov.uk\PlanningFiles has no Archive points associated.| No items will be archived for this volume.|See the Administrator Help for information on configuring file system volume archive points.
4 15:38:05.731 [5752] (EvFsaArchivingTask) <5608> EV~I |Event ID: 40987 Completed processing task: File System Archiving Task with 0 (0.00 MB) items matched.
5 15:38:12.997 [1716] (EvFsaSyncTask) <2564> EV~I |Event ID: 40991 Starting a synchronization run for task: File System Archiving Task_Synchronization.

-----

[Closed: 2009/06/23 15:39:31]
=====

Liam Finn's picture

 Hmm. the mystery continues

If it were my system, I would remove and recreate the archive points. 

dfwood's picture

Scanner001,

How would you recommend I do this? just to make sure I clean up the system properly.

Thanks for the ongoing help,

Dan

MichelZ's picture

Hi

Could you try this on your PlanningFiles Share?
http://seer.entsupport.symantec.com/docs/319277.htm
http://seer.entsupport.symantec.com/docs/306649.htm

If it works there, it's probably the solution for the Users, too.
I can only imagine that when it ran out of space that the archive point somehow got corrupted... ?

Cheers

Liam Finn's picture

 So this is the same that he needs to recreate the archivepoint for the root folder as I mentioned earlier


Liam Finn's picture

 Good at least i know i'm not loosing my mind hahahah even if I am already crazy hahahaha

Liam Finn's picture

 Dan,

Looks like the creating of the archive points for the root is needed

Liam Finn's picture

Dan,

Just follow my first posting to create the archive point. If you get any errors post them here and we will help you 

dfwood's picture

Sadly using ArchivePoints.exe to delete and recreate the archive points has made no difference.

I have to say this is very frustrating.

MichelZ's picture

Hi

Sorry, then I have no other option as telling you to open a support case @ SYMC.... :(

Cheers

Liam Finn's picture

 hmm maybe we need to manually recreate the archive stream....not sure if that will work in this case though

Can you check your FSA tasks to see what targets you have setup. See if there is a target in there for the root of users

When you created the archive point using the archivepoints.exe a moment ago can you post the syntax you used to delete and to create

dfwood's picture

If I look at the Task Properties and select Targets, I have \\Shdcfs1\Users, \\Web\PlanningFiles & \\Shdcfs1\Data listed.

Strangely \\Shdcfs1\Data is fine.

The syntax used to delete and create was ArchivePoints delete or create \\SERVER\SHARE & FOLDER if required.

Would deleting and recreating the FSA Task help?

Liam Finn's picture

Have you tried disableing and re-enableing the autoenable on the shares?

dfwood's picture

I've spoken to Symantec support and they have taken a deployment scanner output. They seem to think its to do with the Alternative Data Streams for the Archive Points.

Will post the outcome of there findings, hopefully will also have a fix.

Liam Finn's picture

 hmmm i wonder what they mean by alternative data streams for the archive points. I have never heard them use that term before

dfwood's picture

What ever has happened here the normal solutions for fixing it using FSAUtility or Delete and Recreated the Archive Points don't work.

Liam Finn's picture

 OK well sorry I could not be more help

Please when you get the fix, post it here so we all have the info.

I'm very interested in the steps needed to correct this one

dfwood's picture

Scanner001,

No need to apologise, I'm very thankful for all the help!

As soon as this one is sorted I shall post our findings.

Many thanks,

Dan 

MichelZ's picture

Liam

Alternate Data Stream = XML File attached to the Folder.
They save this in an Alternate NTFS Data Stream: 
http://www.ntfs.com/ntfs-multiple.htm

/Michel

dfwood's picture

Guys,

After checking the Alternate Data Streams they were fine. After providing Symantec with a full DTrace it would appear the problem is with the Check Pointing EV performs to keep a track of where it was when the system crashed due to running out of space.

Symantec found that the Users and PlanningFiles had been fully walked yet Data hadn't finished.

They have found an Etrack where it mentions a warning is thrown, when a task fails for a targets, the targets successfully processed it previously will be shown as having no archive points, as there checkpoint file is not needed to be read.

Apparently this is being looked into for a future service pack release, and from there Etrack it will not be in SP2.

The current suggested workaround is to perform the following steps,

1. Delete any checkpoint.xml files present in the \program files\enterprise vault\FSATaskCheckPoint\ folder or a folder you specified

2. Disable checkpointing
2.1 On the SQL Server open the enterprisevaultdirectory database
2.2 Locate and open the FileSystemArchivalTask table for editing
2.3 Find the column called UseCheckPointing and change the value from 1 to 0
2.4 Restart the Enterprise Vault Admin service on the EV Server and the placeholder service on the fileservers

3. Run the FSA task and monitor for any errors.

This appears to have resolved my problems, will keep you posted and will mark as the solution if all goes well.

Thanks for all the help,

Dan 

SOLUTION
Liam Finn's picture

 Good to hear you have it sorted

Please mark the post as solved so others know to use it to help them

dfwood's picture

Will do.

Symantec are monitoring the situation for the next 24/48Hrs before turning the CheckPointing back on.

Will keep you posted.

Dan

dfwood's picture

As yesterdays archiving task completed without any errors, I have enabled CheckPointing as per Symantec's request.

Marking as solved.

dfwood's picture

A quick update, this happened to me again as EV ran out of space on the temporary files disk.

To sort this out quickly do the following:

  1. Stop the File Archiving Task
  2. Then delete the check point xml files found in the C:\program files\enterprise vault\FSATaskCheckPoint\ folder
  3. Now restart the File Archiving Task and run the archiving job again.

Oddly enough the day after I logged this with Symantec someone else called them with the same issue.

Dan

Liam Finn's picture

Hmm maybe a bug somewhere in the software. Maybe you should consider upgrading to SP2 

dfwood's picture

Unfortunately Symantec have confirmed this wasn't fixed in SP2, maybe SP3?

Liam Finn's picture

Lets hope. Looks like it is a more common issue so they will try to get it fixed and add it to the next SP release.