03-09-2017 07:10 AM
While it may be possible to diagnose and fix the issues here, it may end up being easier to simply uninstall the SQL instance and Act! - and then reinstall Act to rebuild the SQL instance.
I'd advise ensuring that you are installing while logged in as a local administrator.
Hopefully a fresh instance of SQL will resolve any issues with database creation/SQL users etc.
03-09-2017 07:35 AM
03-09-2017 08:28 AM
03-10-2017 01:21 AM
03-10-2017 01:46 AM
03-10-2017 07:42 AM
While I appreciate the help I got from here. I do find it kind of disturbing that we would require a subscription just to get the product installed. There is clearly something wrong with this installation process as it is conflicting with something.
We have decided to just setup a VM on the server that is dedicated to ACT and install it there. No issues at all with the install.
I think this should be taken as a last resort.
03-10-2017 08:21 AM
I agree. There it definitely sounds like there is an environmental issue affecting the initial installation. Whether this is related to permissions or third-party software like antivirus affecting the installation routine, It's hard to say.
For reference, here's a list of AV/Firewall exceptions to make for Act!: http://kb.act.com/app/answers/detail/a_id/25125
As an alternate installation, you could try installing Act! without SQL, then manually installing and configuring the SQL instance. Follow these steps to do this: