ACTdiag Errors

[J G]

Running as Administrator, window pops up with this error 

Press "OK", and receive Act! Diag has stopped working.

[Gary W · Accepted solution]

Hi J G,

Unfortunately the next troubleshooting step would be to manually uninstall SQL and reinstall using the instructions in the following Knowledgebase article: http://kb.act.com/app/answers/detail/a_id/38099

Seeing as Act! is still working correctly, I would not recommend doing this for the sole purpose of accessing ActDiag.

If you goal is to rename a database, you can do this from within Act! by clicking File > Save Copy As. This will let you save a copy of the database with a different name. After confirming the copy is correct, you could then discard the old database.

[Gary W]

Hi J G,

Are you receiving any errors when using Act! itself?

Try following the solution in the following Knowledgebase article, then test accessing ActDiag again: http://kb.act.com/app/answers/detail/a_id/28879

[J G]

No, no errors while running Act!, well...none that I have created yet. ha

After running the ResetSQL.bat, I am receiving this.

And after pressing any key, I still receive the same error above when trying to run ActDiag.

[Gary W]

Try moving the ResetSQL.bat file to the C:\Program Files\Act\Act for Windows folder (or your alternate install location) and run it from there.

[J G]

Fixed the securitycmdlnapp error but still no luck with ActDiag

[ssanth13]

What is the version of SQL server?? Have you recently installed or reinstalled SQL??

[J G]

SQL Server 2012 Standard, No we haven't.

[JonTaylor]

Hi J G,

You're saying that Act! itself is working currently, is that right? 

Is this the machine that hosts your database(s)?

If so, are you able to create a new database on that machine?

[J G]

You're saying that Act! itself is working currently, is that right? - Yes
Is this the machine that hosts your database(s)? - Yes

If so, are you able to create a new database on that machine? - Yes

[Gary W]

Hi J G,

What version of Act! are you using?
What are you trying to access ActDiag for?

There are further troubleshooting steps you can try, however these may have unintentional side-effects as Act! is currently working correctly. This is not usually the case when the ActDiag error you are receiving occurs.

Another solution you could try would be running the SQLUSERS.bat file in the following Knowledgebase article. This should recreate the SQL user accounts that Act! and ActDiag uses to access the SQL instance.