Question : Sage ACT 2008 install corrupted existing SQL 2000 program

Our server operating system is SBS 2003 and it has SQL 2000 installed which is utilised by our main (critical) software application.  This has always worked absolutely fine with no problems until today when we attempted to install ACT 2008 which also installs SQL Express 2005.  I was concerned prior to install and telephoned Sage to confirm that the install would not affect our existing SQL 2000 install and was told categorically that it would not.

However, since installing ACT my users, on attempting to log into the program, have received the error Error occurred initializing security.  Execution ending.  However, should an administrator run the same program there is no problem and it works fine.    

I have spoken to ACT technical support and they told me to carry out both an automatic and manual uninstall of ACT and that this would revert the system to as it was previously.   It doesnt however appear to have removed the SQL Express 2005 install and there is no option within add/remove programs to do this. (At this stage would even removing SQL Express 2005 resolve the issue anyway?)

I have temporarily given a couple of users administrator rights to allow them to carry on working but this cannot (for obvious reasons) be a permanent solution.

I am pretty much a novice when it comes to all things SQL so assistance in resolving this would be greatly appreciated.  I am assuming that from what I can tell it is a rights issue somewhere along the way  but other than that I am stumped!!  Oh, and ACT technical support have washed their hands of me as they don't support SQL server issues which seems a little harsh under the circumstance but......

Thank you very much in advance for your time and assistance  it will be most appreciated :)

Answer : Sage ACT 2008 install corrupted existing SQL 2000 program

I found what appears to be the problem and resolution today in that somehow the TCP port that SQL was listening on had been changed from 1433 within the SQL instance.  The client PC's were still looking to connect on 1433.  This does not, as far as i am aware, explain how some users were still able to connect though.   However I have reset the port number to 1433 and everything is now (or was when i left the office!) working as it should.    I have no idea why this would have happened but assume that it must have been what was causing the connection problems.

Thank you for your time in trying to help me resolve the problem.    Regards, Sarah