I maintain: user error.
I've certainly never had an issue with it!
Some things to try
First of all, depends on the way you selected the options.
As stated previously, if you selected windows authentication then "sa" is disabled. If you have mixed you still might have to enable the "sa" and "sa" can not be blank. There is no default password for "sa", if SQL express comes with a applications ask the applications support team.
You can put the SQL Server in single user mode and then any member of computer's local administrator can gain access to SQL server as sysadmin.
Go to SQL Server Properties/Security tab and change the mode to SQL Server authentication mode
Go to security/logins, open SA login properties
Uncheck "Enforce password policy" and "Enforce password expiration" check box there if you decide to use weak password
Assign password to SA user
If you get "Cannot set a credential for principal 'sa' . (Microsoft SQL Server, Error: 15535)" then "Map To Credential" check box on the General tab of the Login Properties - sa dialog box.
If “User is not associated with a trusted sql server connection"
In SQL Server Management Studio, Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect.
Make sure the sa (at status tab of sa properties) is enabled after restart the server.
as I stated before- any attempt to change anything in SQL property end up same way - user not authorize to perform this action.
I going to reinstall entire package one more time (already did this 3 times) to see if I missed anything where I can setup password for SA or any user at all for database.
And if it is not there I am going to report this as a bug to Microsoft on MSDN.
I'd be interested to know what particular package is giving you so much trouble.
Alexsts, did you find a solution to this? I've experienced the same problem for the last month when trying multiple times to install DotNetNuke. It downloaded SQLExpress as part of the installation, then asks me for the password which I've not given. If you found the solution, please share. Thanks.
Again, read my post on 6/8
I explained how to gain access using single user mode or at least point you to the resources. Since this is part of installing a package you should talk with their support because they configure the user accounts. If you do get in with Single user mode, my post also points out where to look to make sure "sa" is configured, correctly. Althought your probably better off creating a new account as the "sa" user might be tied to the application and changing anything could break the app. Some SQL 2005 include the local admin's as a SQL Administrator so that is one thing to always try. You can also try logging in as the service account that is commonly used as a SQL Administrator assuming not local system or network service .
Just a FYI...
Now if you are having issues connecting you might have to do some digging to find out what the instance name and port settings are. I had one a month ago that was using Named Pipes which has a funky connection string. Took me a few hours to break in but once I relized it was named pipes took me a few minutes LoL.
I don't know if this will help, but I also was not asked to set a user and when I opened management studio was just connected. But, when I went to add a database my login was denied. I exited management studio and restarted it by right clicking and doing the run as administrator option. I retried creating the database and it then worked.
I ended up resolving the issue about an hour after my last post. Although I'd previously uninstalled all SQL programs/modules and tried reinstalling, I did it one more time and then attempted to reinstall DotNetNuke (which is what needed SQL Express and had been trying to install it as part of the DNN installation) and it installed perfectly.
Sometimes when you install SQL Express 2005, a component of another product, that will install the application to configure the environment, and reduce the effectiveness of your access to the SQL database. This is primarily due to the application set the SA password and not tell you what it is.
yes, it is sometimes difficult to argue with MS die hard defenders. for anyone who arrives to these pages....
Originally Posted by alexsts
i do not think there is a default SA password. if you do not get an option to specify it during the install, it is probably set to "undefined" or something like that.
your most promising option is to install SQL Server Management Studio and change the SA password when the application custom installer prompts for it.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)