How to Fix the ACT 5.5 Persistence_FlushSqlError


I’ve seen this error come up a few times now, and there’s a (dirty, ugly) hack you can use to fix it. So, for those who are fans of dirty, ugly hacks, here you go.

If you see the error:

ACM encountered the following error while performing synchronization:

Persistence_FlushSqlError
Violation of PRIMARY KEY constraint ‘IssueSolution_PrimaryKey’.
Cannot insert duplicate key in object ‘dbo.IssueSolution’.
Stale Data
The statement has been terminated.

Would you like to retry?

You can fix it by (remember, I said it was a dirty, ugly hack) removing the constraint:

ALTER TABLE [dbo].[IssueSolution] DROP CONSTRAINT [IssueSolution_PrimaryKey]

Good luck, and sorry for the bug.

Comments (5)

  1. XYZ says:

    Hi Chris,

    I have one application oracle-10g. Installation is fine and it does not have any issues.

    But I launched shortcuts few of them are asking for the adimn credentials in standard user. Where as shortcuts were launched without any admin credentials in XP. I just suprised why it is asking for?

    I tried disabling the UAC feature then all the shortcuts were launched without admin credentials in Vista also. But turning off the UAC is not at all recommended soltution.

    So please could you guide me, is there any workarounds(shims,etc) to resolve this issue?…..

    I hope this will catch u in your best of time and will be waiting for your reply as it is urgent to me..

    Thanks in advance..

    XYZ

  2. cjacks says:

    XYZ-

    There are 3 reasons why we would prompt for admin credentials on Windows 7:

    – the developer asked us to

    – the it pro asked us to

    – we think it’s a setup

    If we’re falsely believing it’s a setup, then you can turn off that setup detection by shimming these applications with SpecificNonInstaller.

  3. XYZ says:

    Hi CHris,

    Thanks for your advise.

    I had applied "SpecificNonInstaller" shim, but still it is asking for the admin credentials in standard user.

    Is there any other work around to resolve this issue.

    Since the Vista security layer has designed to prompt for admin credentials, can we treat it as an issue or not?….

    we are facing the same issue for 4 to 5 applications.

    If we find solution for it, we can easily push out all the other applications to deployment…….

    Help me in this regard

    Thanks in advance

    XYZ

  4. XYZ says:

    Hi CHris,

    Thanks for your advise.

    I had applied "SpecificNonInstaller" shim, but still it is asking for the admin credentials in standard user.

    Is there any other work around to resolve this issue.

    Since the Vista security layer has designed to prompt for admin credentials, can we treat it as an issue or not?….

    we are facing the same issue for 4 to 5 applications.

    If we find solution for it, we can easily push out all the other applications to deployment…….

    Help me in this regard

    Thanks in advance

    XYZ

  5. cjacks says:

    XYZ – I pointed out the logic above. If SpecificNonInstaller doesn’t make it stop prompting, then there are only 2 other reasons why it would prompt. If it’s because the developer asked for it, then you can override that choice with RunAsInvoker. If it’s because you asked for it, then, well, stop asking for it.