Community
Showing results for 
Search instead for 
Do you mean 
Reply

Large Index Files Created in Act Program Data Directory

Tuned Listener
Posts: 51
Country: United States

Large Index Files Created in Act Program Data Directory

Once in a while, I will notice my hard drive has gone from less than half full to almost completely full.  It appears huge temporary index files are being created in the Program Data/ACT directory.  Why does this happen and what is the protocol to free up this significant amount of drive space?

Thanks.

Paul

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Large Index Files Created in Act Program Data Directory

If you are running Sage ACT! 2012 or 2013, you are most likely referring to the 'Indices' folder.  This folder and its files are used by the Universal Search function.  These files will generally be slightly larger than the database 'Attachments' folder. 

 

If the files seem abnormally larger than the Attachments folder, you can delete the files and they will be rebuilt upon opening the database.  Another option is to relocate the Indices to a different hard drive on the computer; here is an article with instructions: KB Article 28454

Greg Martin
Sage
Tuned Listener
Posts: 51
Country: United States

Re: Large Index Files Created in Act Program Data Directory

Thanks for the advice.  I am doing the relocating suggestion.

Paul

New Member
Posts: 15
Country: USA

Re: Large Index Files Created in Act Program Data Directory

I am having the same issue     I have a new desktop computer with a very large hard drive and in just a few weeks these files have taken over 97% of my hard drive    There are two of them and they are "ix" files.   One is 621 GB and the other is 741GB.    I cannot relocate them (don't have another hard drive).    Are you sure I can delete them without causing any issues?    Also, how do I keep this from happening again since you say they will rebuild themselves.   I have used ACT! for more than 20 years and have never had this problem before.     

 

Thanks in advance for your answer

Copper Contributor
Posts: 25
Country: USA

Re: Large Index Files Created in Act Program Data Directory

Woud love to hear the latest options on these questions re you can stop it from occuring

 

What impact it would create

 

http://kb.swiftpage.com/app/answers/detail/a_id/28454/kw/28454 

 

 

 

Kind regards

Bron

Bronwyn Clarke

Eyecatchers Solutions Pty Ltd
Sydney, Australia

 

T 02 9543 3472 | M 0412 612 938 | F 61 2 9532 0681 | E bronwyn@eyecatchers.net.au


CRM Specialists, Consultants, Project Implementations

Contacts & Customers for Life


"You meet people in life for a season, a reason, a moment or a lifetime

 

 

Copper Contributor
Posts: 25
Country: USA

Re: Large Index Files Created in Act Program Data Directory

Especially interested if you stop permanently the ACT Server Host Service

 

Recall seeing this mentioned previously

 

as per this KB

http://kb.swiftpage.com/app/answers/detail/a_id/30322/kw/28454/related/1

 

  1. Under the Processes tab in your Windows® Task Manager, locate and end process for the Act.Server.Host.exe service

 

 

Kind regards

Bron

Bronwyn Clarke

Eyecatchers Solutions Pty Ltd
Sydney, Australia

 

T 02 9543 3472 | M 0412 612 938 | F 61 2 9532 0681 | E bronwyn@eyecatchers.net.au


CRM Specialists, Consultants, Project Implementations

Contacts & Customers for Life


"You meet people in life for a season, a reason, a moment or a lifetime

New Member
Posts: 15
Country: USA

Re: Large Index Files Created in Act Program Data Directory

I deleted the Act! related files on my computer that were causing the problem.   That was just after I reported the problem and it hasn't reoccurred or caused any problems.    Good luck!

Administrator
Posts: 4,024
Country: United_Kingdom

Re: Large Index Files Created in Act Program Data Directory

Bron,
You can stop the service running, but then universal search stops working.
The indices folders as default is still just slightly larger than the attachments folder of the database.
If the indices get larger than this, you can stop the service, delete the indices, detach and reattach the database and then run full maintenance. Restart the service, and check if there is still an issue.