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.
Sadly after spending hours upon hours, we've now got act installed again, but it's back at the initial problem about protexis license... I have a feeling that when we reinstall it, it's just going to reproduce the same issues we initially had.
I'm sorry to hear that. If you have a support subscription, you could give us a call and work with a support technician on further in-depth troubleshooting of this issue. I would suggest pointing the technician to this thread so they can see the details of the issue that we've already established.
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 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.
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:
