Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
1/1/2011 6:24:31 PM
chromebuster
Gravatar
Total Posts 139
View Posts
"All that is gold does not glitter, not all those who wander are lost;" --J.R.R. Tolkien

Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Hi folks,

Happy newyear to all.  Well anyways, I wish I was only here to say that, but unfortunately I'm not.  I was in the processs of testing with Mojo Portal on my Windows 7 machine with SQL Server 2008 R2 express when things decided to go awry.  I ended up having to change the password of the SA user like a total of three times, and even after that, I still get the "login failure for user SA" message.  I changed the password to something more obscure and then I changed it to @gordon1.  Neither one worked.  What am I doing wrong?  SQL Server is in it's default configuration.  Let me know what I can do to fix this.  Should I just allow Mojo to install and then modify that user later?  (that's if it will allow itself to do so without stalling the whole computer).  Thanks. 

 

Katherine

1/3/2011 10:50:26 AM
Jamie E
Gravatar
Total Posts 1203
View Posts
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Hi Katherine, what does the database connect string in your user.config look like? Do you have the password specified? I think by default SQL server will use Windows authentication, but if you want to use DB authentication you need to make sure the password is included in the connect string.

Jamie

1/4/2011 5:40:20 AM
chromebuster
Gravatar
Total Posts 139
View Posts
"All that is gold does not glitter, not all those who wander are lost;" --J.R.R. Tolkien

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Thanks for getting back to me so quickly.  I can't exactly tell you what that looks like since my goal was to use the Web app gallery to install Mojo Portal with ease.  That's what's failing.  Do you recommend I download it manually and then use IIS's deployment options instead?  What I can tell you though, is that I do use windows authentication since I haven't learned enough about database authentication.  I was presented with the prompts for all of the different passwords, and it was only the super admin one that failed to log in.  Everything else was fine.  let me know what else I should try. 

 

Many thanks,

Katherine

1/4/2011 6:36:29 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Hi Katherine,

Possibly your installation of SQL Server is not configured for mixed mode authentication. What I would try is connecting via SQL Server Management Studio as the sa user using sql authentication. Wen you open SQL Management Studio it pops up a login dialog, by default the dialog is set to use Windows Authentication and your current windows user which is an administrator and is therefore allowed to connect. But you can from this dialog choose SQL Server Authentication from the dropdown and then try to connect with the sa credentials. If that does not work it means either it is not configured for Mixed Mode Authentication or you are not entering the correct credentials. You can then change it back to Windows Authentication to get back in.

To enable Mixed mode, once you connect with SQL Management Studio, right click the topmost node in the left pane and choose Properties, it will open up a dialog window. on the left click Security, then on the Right it will show a set of Radio buttons for Windows Authentication mode and  SQL Server and Windows Authentication mode. You want to make sure it is set to SQL Server and Windows Authentication mode.

Hope it helps,

Joe

1/10/2011 1:37:20 AM
chromebuster
Gravatar
Total Posts 139
View Posts
"All that is gold does not glitter, not all those who wander are lost;" --J.R.R. Tolkien

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

I'll definitely be farting with that tomorrow.  I'm pretty sure that's what it is.  I'll have to try a few times probably to find the correct panel, as there are quite a few nodes in there labeled security, so it's kind of difficult.  And neither JAWS nor System access really like SQL Server management that much.  But thanks for all of your help.  This is so important to me, you have no idea.  I'll be sure to let you know if I break anything else LOL. 

 

katherine

1/10/2011 4:22:28 PM
chromebuster
Gravatar
Total Posts 139
View Posts
"All that is gold does not glitter, not all those who wander are lost;" --J.R.R. Tolkien

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Hi again,

I just tried to find the node you are talking about, but I'm unsure of the name of it.  Which node is it that I'm supposed to right-click on?  Thanks. 

1/11/2011 1:09:49 PM
Penguin360
Gravatar
Total Posts 63
View Posts

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

The very first one in the left panel. It usually says "XXX\SQLEXPRESS (SQL Server 10.0.4000 - YYY", where XXX is your computer name, and YYY is the logon username. Then right-click this node and select "Properties". Then in "Server Properties" window, click on "Security" node from the left panel, then choose "SQL Server and Windows Authentication mode", and then click OK to exist.

1/11/2011 5:35:31 PM
chromebuster
Gravatar
Total Posts 139
View Posts
"All that is gold does not glitter, not all those who wander are lost;" --J.R.R. Tolkien

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Thanks so much.  I really appreciate the clarification.  I'll definitely be taking care of that when I get around to it.  i'm just curious though, why doesn't it say in the documentation that mixed mode auth is required for Mojo Portal to work?

1/12/2011 7:29:01 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Hi Katherine,

I can only imagine how much more difficult it is to do things using a screen reader, I admire your perseverance and tenacity, sometimes I wish I could see over your shoulder and guide you a little.

It is not impossible to use windows authentication for SQL server with mojoPortal but it is a lot more complicated, it requires the web process to run as a windows user with permissions to the database or using impersonation of a specific windows user, all of which is much more complicated to configure. Generally in the world of publicly available hosting you will find sql authentication almost always used and really sql authentication is also the easiest thing to do on your local machine.

One thing that occurred to me is if you somehow have added your connection string in more than one place in your user.config file, the one closest to the bottom of the file wins, so if you accidently did that and then you kept modifying the one at the top of the file with new passwords or users it would have no effect and could lead you to think the credentials you are entering are wrong because the one lower in the file is the one being used and it is not the one you are changing. Just a theory, you might review your user.config and see if you have the connection string in there more than once.

Best,

Joe

1/12/2011 10:42:57 AM
chromebuster
Gravatar
Total Posts 139
View Posts
"All that is gold does not glitter, not all those who wander are lost;" --J.R.R. Tolkien

Re: Testing goes awry after 30 thousandth time changing Super Admin Password in SQL Server 2008 R2

Thanks Joe.  I found it finally.  And it could work very well if the makers of screen readers would stop only taking care of the average uers and leaving us advanced enthusiasts out.  But sorry for the rant.  I tried what you said, and yes, logging in as the sa user failed even when I changed the auth mode to SQL auth.  I did what you suggested and then configured it for mixed mode authentication.  I'll try it from the web app gallery again, see what happens, and if it doesn't work, I'll report back here.  Again, thanks so much everyone for your help. 

You must sign in to post in the forums. This thread is closed to new posts.