11-17-2010 08:24 AM
I'm currently setting up a test SLX database. I think I'm nearly finished - but I can' t get past this one error. Hoping someone can help!
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 108
Msg 15291, Level 16, State 1, Procedure sp_change_users_login, Line 108Terminating this procedure. The User name 'sysdba' is absent or invalid.
I receive this error when I try to run the sysdbafix_script.
* Windows Server 2008 R2
* Microsoft SQL Server 2005 set up with mixed authentication on same server
* SLX 7.5.1 installed - mostly
I had to attach the Saleslogix blank database manually, which went fine - and I understand that I need to run this script, but I can't get past that error. I have tried running the script logged in using Windows authentication as a domain admin, and also as the local SA user.
I'd call Sage directly, but I'm still waiting for them to quote me on a Support contract, we're just on maintenance right now.
Can anyone point me in the right direction?
Solved! Go to Solution.
11-17-2010 08:36 AM
Saw that you had posted that on another thread -- but I couldn't get that to work. For the newly attached database, there is a sysdba login already existing, and I can't delete it - "the database principle owns a schema in the database, and cannot be dropped". So I try removing the schema, but I can't do that either because the user isn't created properly and is missing a login name - and I can't provide one, field isn't available. So any changes I try to make - no dice, won't save.
11-17-2010 08:44 AM
You wont have any luck with Sage anyway on this one Im afraid - Windows Server 2008 R2 is not supported (qualified) with v7.5.1
11-17-2010 08:48 AM
Naturally. I'll have to look up and see what IS OK. Seems to me this is an issue within SQL 2005 though, not Server 2008 R2?
Well thanks for your help - if you can think of anything else I'd love to hear it, but it sounds like I may just need to start over with a supported OS and hope it doesn't happen again.
11-17-2010 09:01 AM
figured out how to delete the existing sysdba user and recreate - had to reassign the sysdba schema to another user temporarily, delete the old sysdba, and then recreate.
I still can't run the script, but from the response earlier it seems I may not have to?
11-17-2010 09:27 AM
Are you running the sysdba script against the SalesLogix database? no doubt it defaults to the master database and i suspect you are running it against that..?
11-17-2010 09:30 AM
Ahhh, there we go. See, I had thought of that - and I *thought* I had tried both.. but obviously I mis-clicked because when I just tried again. it worked. Thanks so much!