12-14-2018 09:32 AM
I'm trying to move Act from a desktop PC to a server.
Act version 20.1.120 (update8)
The server is SBS2011 (effectively 2008 R2)
Older versions of SQL Server are already present and are being used.
Therefore I cannot follow the guidance here: https://community.act.com/t5/Act-Premium/Login-failed-for-user-ACTADMIN/td-p/20195
which pretty much says destroy the entire universe and start afresh!
Using a Hyper-V instance might work (a blunt instrument for a seemingly simple task) but the server isn't really beefy enough to start running Hyper-V.
In my case, installing Act! does not install a fresh instance of SQL Server 2014 Express as I would expect. It seems to see the existing SQL instances and just skip the SQL part of the installation, and then complain when you try to run Act!.
So, I install SQL Server 2014 Express manually, as directed here...
The instructions are clear. I have tried both options. i.e. Act Installed first, or Act installed after SQL Server. Both produce the same error.
Login failed for user 'ACTADMIN'
How can this be so difficult? Act! gets it's own SQL Server instance, nothing else is using it. So why can't the installer just get it right?
I've wasted an entire day on this, install, reboot, test, uninstall, reboot, repeat.
Therefore any useful info would be very much appreciated.