GeekyGav Posted August 9, 2012 Posted August 9, 2012 Hi all, Hope someone can advise here... Since doing a bit of maintenance on our SQL server yesterday, I'm getting this error when trying to log in to FMS with the 'sysman' account. Cutting a long story short... The SIMS and FMS databases needed to be moved due to lack of HD space. This was done successfully, or so I thought! We have two FMS databases... One prior to becoming an academy and one since becoming an academy. Both were working perfectly well before the move and now only the academy database works. All of the other SIMS databases work fine. When logging into SQL Management Studio, I can see the users for that database and also the logins that tally up with them. I have tried logging on to the database in question with a standard user account and I get 'Invalid user id/password or database name error' Have also tried manually resetting the user password within Management Studio and still get the 'Invalid user id message. Trying to give as much information as I can without waffling. Hope someone can point me in the right direction...
6Foot2 Posted August 9, 2012 Posted August 9, 2012 There is an old thread on this error here: Link: http://www.edugeek.net/forums/mis-systems/25956-fms-problem.html Thread date: 31st October 2008. The reported fault is the same: @Hecate says that Capita sorted it.
matt40k Posted August 9, 2012 Posted August 9, 2012 Have you tried deattaching and reattaching the affected database?
GeekyGav Posted August 9, 2012 Author Posted August 9, 2012 There is an old thread on this error here: Link: http://www.edugeek.net/forums/mis-systems/25956-fms-problem.html Thread date: 31st October 2008. The reported fault is the same: @Hecate says that Capita sorted it. Thanks for the link... I did see this but with it being 4 years old, I wasn't sure if there would be any fresh information on this particular fault.
GeekyGav Posted August 9, 2012 Author Posted August 9, 2012 Yes, I've tried detaching and reattaching and also restoring from really old backups too to see how far the fault goes back. Either way, the problem remains. :/ Have you tried deattaching and reattaching the affected database?
matt40k Posted August 9, 2012 Posted August 9, 2012 Yes, I've tried detaching and reattaching and also restoring from really old backups too to see how far the fault goes back. Either way, the problem remains. :/ Did you attach it with a different name? Did you move the mdf\ldf out of the data directory first? I assume you used dbattach to attach?
TheScarfedOne Posted August 9, 2012 Posted August 9, 2012 That's odd... I had the very same error last week with this. @PhilNeal...something we can get support to look at? My fix was a detach reattach. There is also a script that I can post up which captures all you SQL login det,ails so you don't have to recreate them. PM me if you need anything
PhilNeal Posted August 10, 2012 Posted August 10, 2012 @theScafedOne - our desk will always try to reslove these issues. Your support unit should be your first port of call and that could be your LA or us.
HannahBuist Posted August 14, 2012 Posted August 14, 2012 I've got the same problem at one of my schools - I'm so glad I'm not the only one! If I take a copy of the data and load in the office it works fine. Call logged with Capita.....
TheScarfedOne Posted August 15, 2012 Posted August 15, 2012 @PhilNeal, Ive put a post about this on my blog - hope thats ok.
matt40k Posted August 15, 2012 Posted August 15, 2012 Am I missing something, what you've described is (or similar to) the sims install store procedure - as far as I can make out. This creates the SQL users in the MASTER database and links to them to the database - you sometimes have issues if you have a very old database, say called fms, then to deattach\restore it as say, fmsold. Running the install procedure updates the sql logins so they become fmsold_username, rather then fms_username. Do I understand right?
TheScarfedOne Posted August 15, 2012 Posted August 15, 2012 It is kind of. It is more a fix for those who forget to do a DBAttach if moving a database between servers; but you can apply it to the "Atomic" error - where the recomendation is to do the Dettach Re-attach.
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