Using Actdiag – Act’s diagnostic tool

By Patricia Egen • May 12th, 2017

For years, there has been a diagnostics tool included with Act. It’s called Actdiag. While it’s not a tool that everyone will want to use, it’s powerful and can get your Act database out of a jam in a crisis.

There are several options that Actdiag can handle. The one I am going to cover today is Reindex.

Within Act, under the Tools menu, there is a database maintenance option that an Administrator can use to Check and Repair a database. This is something that should be done on a regular basis to keep your Act database running smoothly and efficiently. You can set it up to run using the Act scheduler as well. It can be run from a workstation that is connected to the Act server.

If you run check and repair and it gives you an error, then you need to use Actdiag to fix the issue.

Part of the check and repair from within Act is a reindex function. What this does is go through all the tables and reorganize data. When you do adds and deletes in your Act database, over time the indexes get fragmented. A reindex “realigns” them. Running the reindex inside Act does a bit more than just the realignment. It puts things in place so that your searches work fast. If you have done a check and repair and cannot find something via a search, that you know is in your data, then you want to perform a Reindex using Actdiag.

For the most part, running Check and Repair inside Act is sufficient. Running a reindex from Actdiag will be faster because it is doing less other steps. You want to do it from Actdiag if you suspect, like mentioned above, that there is data that is in such a squirrely state (that’s a technical term) it cannot be fixed by the normal check and repair.

The other important thing to realize is Actdiag needs to be run on the server hosting the Act database. And, when you run a reindex from Actdiag, it will disconnect any users currently in the database so you want to use this tool either off hours or let people know there will be a temporary disruption in access to the database.

There are lots of other things you can do with Actdiag, but the reindex feature is the one you may need to turn to if you can’t get to support or your Act consultant and you are stuck.

To use Actdiag, click on the Windows Start button and enter ACTDIAG in the run box.  And remember you need to run it on the server hosting the Act database.

If you want to know additional information about this nifty tool give us a call (423-875-2652) or call your local Act consultant.


Has anyone ever had ACTDIAG freeze at the same point (Analyzing Schedule For/By/With Data) during Scan and Repair? I’ve tried it several times.


By Patricia Egen on August 8th, 2017 at 2:22 pm

Yes. It’s generally a bad activity record. Recurring activities can be “interesting” – not a good word. Typically means using something like SQL Management Studio to track down the offending entry and removing it.

Thank you very much for the speedy response Patricia. I appreciate it.
I need to keep 2 ACT “legacy” db’s running. When ACT is happy life is good. But when it’s unhappy, things get ugly pretty quickly. What’s frustrating is the lack of reliable documentation. As a SW dev firm we can appreciate how hard it is to produce good documentation, but for ACT it seems like they didn’t even try. For instance, I recently had to do some maint( reindexing, scan/repair etc.) After I completed it, 1 DB had 1 “transaction” and the other more than 600,000. Nowhere have I been able to find out what they are other than (I think) being related to synchronization which we do not do nor how to get rid of them. (I tried data cleanup) And I won’t even get into some of the cryptic error messages I’ve gotten.



If an Act! data base is no longer part of a syncing family then sync should be disabled in that data base. That will more often than not make the data base run faster. In the Tools/Synchronization Panel dialog, if you are offered Disable Synchronization at the top of the panel then click Disable Synchronization. If you get an error message at this point you may need to ensure that any remote data base definitions are removed first. Click the Manage Database item and on the screen that comes up click each line and then Disable/Change Sync Status and select Disable on the next screen, then return to the list and click the same line and click Delete Database. You should then be able to do the Disable Synchronization operation.

Hope this helps.
Don Egen

Thank you for your response Don.
I appreciate your time.

The copy of Act I am running is from a prehistoric time – Act 2000 B 5.0.3,423 so those options don’t even appear. I had to build a win98 machine just to run maint since this version has “issues” with anything after XP. So you can imagine the challenges that has posed! The 600K transactions I suspect will remain a mystery and as long as I can keep this thing running, I guess it will have to do. The sw equivalent of duct tape one could say.
Again, thank you for your help! It’s nice to know that there is help out there if we ever hit an iceberg and start to go down.




You had said “legacy”. I did not realize how old that actually meant. The only thing I can suggest is, on the Define Users Send and Receive tabs, is to clear out every setting that you can. It has been over 10 years since we dealt with sync in an Act! 5/6 environment so I definitely don’t remember any other tricks.

Hope this helps.
Don Egen

Thanks Don,
I meant it when I said prehistoric! I tried that and it got rid of 20 of the 600K “transactions”. Oh well, I guess it will remain one of those mysteries of the universe.

The nerd in me hates to admit defeat…

Thanks again.



Leave a Comment

« | Home | »