10-15-2012 07:49 PM
ACT! 2012 Pro remote database is having issues where the hard drive is fast filling up.
The Indices folder shows the following file sizes
index_d_1.ix = 424,071,488 KB
index_r_1.ix = 237,547,573 KB
index_di_1.ix = 1,222,336 KB
index_kl_1.ix = 41,824 KB
index_i_47235.ix = 28,183 KB
The same remote has been having constant issues with error 2601 while trying to synch
We thought this had been resolved, but apparently not.
If anyone can throw some light on this that would be great.
The user cannot do anything on his laptop at present.
10-16-2012 08:08 AM
The size of the index files will generally reflect the size of the attachments folder. How many attachments are in the Attachments folder, and what is the size of that folder?
Do these index files reflect the size of the index files for the publisher database?
If there is a secondary hard drive on the computer, the index files can be recreated in a new location. See this article for instructions: KB Article 28454
01-21-2013 08:32 AM
I have moved the index files to a different drive and now that is filling up. 450 gigs in 5 days. Any other suggestions?
01-21-2013 08:37 AM
01-21-2013 08:40 AM
Attachement files are approx 7 gigs.
01-21-2013 02:06 PM
Hi Greg
We resolved the growing size of the index files by simply deleting them.
They are recreated automatically.
The original issue has still not been resolved - as follows:
The same remote has been having constant issues with error 2601 while trying to synch.
ACT! Support has suggested installing SP1 for SQL 2008 R2 - But I can't find a download just for SP1 though
Any ideas on a link?
01-23-2013 05:55 AM
Here is an article which addresses the 2601 error and contains a link to download the SQL 2008 R2 SP1 update: KB Article 28141
01-23-2013 11:01 AM
It seemed to have fixed itself. the file is now only running approx 3 megs. Maybe it needed that much space to complete an index process and once i deleted the files and restarted all was good. It has been at 3 megs for several days now. Thanks for the help.
One last note, this all started with the backups failing and getting the syscommit error as in the last post.