cf23 Posted April 7, 2008 Posted April 7, 2008 Anybody out there dared doing the latest SIMS/FMS upgrade!! Logging into SOLUS update screen using SQL SA account I receive error - connection failed Reason: 6 - Cannot find what exactly this error is apart from 'Copitall' suggestions 'detaching/reattaching' the DB - done this to death and still no joy! All comments welcome.
Domino Posted April 7, 2008 Posted April 7, 2008 I usually use the system managers account for logging into solus itself, the sa I only really use for dbattach, etc
FragglePete Posted April 7, 2008 Posted April 7, 2008 We did our Feb update today, but got a Capita engineer in to do it. Primarily to have a look at a B2B problem we're having, but also as I'm new in post I wasn't happy about doing the upgrade myself just yet. Damn glad we did, the SIMS upgrade went fine, but it suceeded in breaking our FMS database big time. Eventually they got it sorted, but it took a Senior Engineer to remote in from home to fix it. The helpdesk were useless, in fact their tinkering made it worse. Ended up having to restore the fms database, and the Engineer manually downloaded the files to start the process again. Nightmare, SIMS was offline for more than six hours!! Pete
tech_guy Posted April 7, 2008 Posted April 7, 2008 Did ours over the weekend and touch wood all seems to be well!
cf23 Posted April 8, 2008 Author Posted April 8, 2008 Domino - the fix was in the shortcut - so hands up on our part to that! However, today no one can log in on the client stations: Connection failed...reason: error 2 - ok when logging in on the server.
apeo Posted April 8, 2008 Posted April 8, 2008 Have you tried deleting the SIMS .Net directory and reinstalling on the affected workstations? Doesnt hurt to reinstall SIMS Infrastructure, and check sims.ini.
BlogRat Posted April 8, 2008 Posted April 8, 2008 I had a problem, the first time on SOLUS had to use the SA password to run FMS upgrades. The found I didn’t have permissions to log in to SOLUS and was unable to create users, change passwords and do admin stuff in FMS. Solved it by getting the helpdesk to log on remotely and reset my admin user rights, I can now logon to SOLUS (FMS) using my own password.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now