We have a SQL installation that was setup with Windows Authentication.
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?
I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?
Showing posts with label mode. Show all posts
Showing posts with label mode. Show all posts
Thursday, March 29, 2012
Can't Switch to SQL Authentication (Mixed Mode)
We have a SQL installation that was setup with Windows Authentication.
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?
Can't Switch to SQL Authentication (Mixed Mode)
We have a SQL installation that was setup with Windows Authentication.
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?
Sunday, March 25, 2012
Can't start a cloned connection while in manual transaction mode.
I got this error recently using SQL Server, and I found a microsoft site
which gives a solution by setting the SelectMethod property to Cursor but I
don't understand why. We've run this app before with no problems, yet now all
of a sudden we need to customize the URL string of the driver connection.
Can anyone explain what this means exactly and why this might have become a
problem now but was not before?
Most appreciated,
ol,
add "SelectMethod=cursor" your URL connection
ex:
Connection conn =
DriverManager.getConnection("jdbc:microsoft:sqlser ver://localhost:1433;SelectMethod=cursor");
newton
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message1022266.html
|||| Thread-Topic: Can't start a cloned connection while in manual transaction
mode.
| thread-index: AcVBMGMZaFbT7Q3cQUeyebz5WmA8JQ==
| X-WBNR-Posting-Host: 66.114.64.114
| From: "=?Utf-8?B?TXJOb2JvZHk=?=" <MrNobody@.discussions.microsoft.com>
| Subject: Can't start a cloned connection while in manual transaction mode.
| Date: Thu, 14 Apr 2005 13:27:32 -0700
| Lines: 11
| Message-ID: <120F0C3C-9AAD-4B6A-B7F4-3F966E95E4DD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6826
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I got this error recently using SQL Server, and I found a microsoft site
| which gives a solution by setting the SelectMethod property to Cursor but
I
| don't understand why. We've run this app before with no problems, yet now
all
| of a sudden we need to customize the URL string of the driver connection.
|
| Can anyone explain what this means exactly and why this might have become
a
| problem now but was not before?
|
| Most appreciated,
|
|
|
Hello,
You will definitely need to use cursor mode to allow cloned connections to
be spawned on your behalf in a transaction. The behavior of SelectMethod
has been the same for the last several years.
If your code always used SelectMethod=direct, then the only thing I can
think of is that your app never entered the codepath that required a new
connection to be spawned.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
which gives a solution by setting the SelectMethod property to Cursor but I
don't understand why. We've run this app before with no problems, yet now all
of a sudden we need to customize the URL string of the driver connection.
Can anyone explain what this means exactly and why this might have become a
problem now but was not before?
Most appreciated,
ol,
add "SelectMethod=cursor" your URL connection
ex:
Connection conn =
DriverManager.getConnection("jdbc:microsoft:sqlser ver://localhost:1433;SelectMethod=cursor");
newton
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message1022266.html
|||| Thread-Topic: Can't start a cloned connection while in manual transaction
mode.
| thread-index: AcVBMGMZaFbT7Q3cQUeyebz5WmA8JQ==
| X-WBNR-Posting-Host: 66.114.64.114
| From: "=?Utf-8?B?TXJOb2JvZHk=?=" <MrNobody@.discussions.microsoft.com>
| Subject: Can't start a cloned connection while in manual transaction mode.
| Date: Thu, 14 Apr 2005 13:27:32 -0700
| Lines: 11
| Message-ID: <120F0C3C-9AAD-4B6A-B7F4-3F966E95E4DD@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.jdbcdriver:6826
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I got this error recently using SQL Server, and I found a microsoft site
| which gives a solution by setting the SelectMethod property to Cursor but
I
| don't understand why. We've run this app before with no problems, yet now
all
| of a sudden we need to customize the URL string of the driver connection.
|
| Can anyone explain what this means exactly and why this might have become
a
| problem now but was not before?
|
| Most appreciated,
|
|
|
Hello,
You will definitely need to use cursor mode to allow cloned connections to
be spawned on your behalf in a transaction. The behavior of SelectMethod
has been the same for the last several years.
If your code always used SelectMethod=direct, then the only thing I can
think of is that your app never entered the codepath that required a new
connection to be spawned.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Thursday, March 8, 2012
Can't remove SA account or delete xp_cmdshell ext stored proc?
I'm trying to make my SQL Server a tad more secure, but I'm unable to remove
SA (I'm running Mixed mode) -- can the SA account only be removed when using
windows Authentication? When I try to remove SA I get "selected user
cannot be dropped because the user owns objects". When I try to delect
xp_cmdshell I get the following error "You tried to delete one or more
system objects. They were not deleted."
I must admit, I'm a little confused, I'm trying to implement Microsofts
security recommendations, but either the documention is not
detailed/accurate or I'm missing something?
Any suggestions?
Thanks, Rob.Hi
You can not remove the SA account. Set a very complicated password for it,
write it down and put it in a safe.
For the xp_ look at
http://support.microsoft.com/defaul...kb;en-us;891984
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rob R. Ainscough" wrote:
> I'm trying to make my SQL Server a tad more secure, but I'm unable to remo
ve
> SA (I'm running Mixed mode) -- can the SA account only be removed when usi
ng
> windows Authentication? When I try to remove SA I get "selected user
> cannot be dropped because the user owns objects". When I try to delect
> xp_cmdshell I get the following error "You tried to delete one or more
> system objects. They were not deleted."
> I must admit, I'm a little confused, I'm trying to implement Microsofts
> security recommendations, but either the documention is not
> detailed/accurate or I'm missing something?
> Any suggestions?
> Thanks, Rob.
>
>
>|||> I'm trying to make my SQL Server a tad more secure, but I'm unable to
> remove SA (I'm running Mixed mode) -- can the SA account only be removed
> when using windows Authentication? When I try to remove SA I get
> "selected user cannot be dropped because the user owns objects". When I
> try to delect xp_cmdshell I get the following error "You tried to delete
> one or more system objects. They were not deleted."
The sa login account cannot be deleted or renameed, nor it can't be revoked
any permission.
> I must admit, I'm a little confused, I'm trying to implement Microsofts
> security recommendations, but either the documention is not
> detailed/accurate or I'm missing something?
I don't think MS ever mentioned droping the sa account (as it can't be
done). Here are recommendations from Operations Guide: "
The sa account in a production environment should be given a complex
password, made up of uppercase and lowercase letters, symbols, spaces, and
numbers. The sa account should have a complex password, even if the SQL
Server is running in only Windows Authentication Mode. A complex password
protects SQL Server from someone easily getting administrative access to SQL
Server. This also protects the server in the event that an administrator
changes the security authentication mode to Mixed Mode.
Do not use the sa login account in a production environment. Instead, place
each DBA's network user account into a Windows group, create a single SQL
Server login account for the group then add the login account to the
sysadmin fixed server role. "
(http://www.microsoft.com/technet/pr...in/sqlops3.mspx
).
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||Thank you for the information.
The book I was reading is Microsoft Press and the authors are Ed Robinson
and Michael James Bond.
I have the SA password complex so no worries there.
I guess I'll leave the xp_cmdshell alone as it seems to be more trouble that
it is worth to remove it.
Should I think about installing URLScan ?
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:%23BAAU89pFHA.3112@.TK2MSFTNGP12.phx.gbl...
> The sa login account cannot be deleted or renameed, nor it can't be
> revoked any permission.
>
> I don't think MS ever mentioned droping the sa account (as it can't be
> done). Here are recommendations from Operations Guide: "
> The sa account in a production environment should be given a complex
> password, made up of uppercase and lowercase letters, symbols, spaces, and
> numbers. The sa account should have a complex password, even if the SQL
> Server is running in only Windows Authentication Mode. A complex password
> protects SQL Server from someone easily getting administrative access to
> SQL Server. This also protects the server in the event that an
> administrator changes the security authentication mode to Mixed Mode.
> Do not use the sa login account in a production environment. Instead,
> place each DBA's network user account into a Windows group, create a
> single SQL Server login account for the group then add the login account
> to the sysadmin fixed server role. "
> (http://www.microsoft.com/technet/pr...ityLearning.com
>|||> Should I think about installing URLScan ?
Why don't you ask this in some IIS group, with explanation why do you think
you need it?
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
SA (I'm running Mixed mode) -- can the SA account only be removed when using
windows Authentication? When I try to remove SA I get "selected user
cannot be dropped because the user owns objects". When I try to delect
xp_cmdshell I get the following error "You tried to delete one or more
system objects. They were not deleted."
I must admit, I'm a little confused, I'm trying to implement Microsofts
security recommendations, but either the documention is not
detailed/accurate or I'm missing something?
Any suggestions?
Thanks, Rob.Hi
You can not remove the SA account. Set a very complicated password for it,
write it down and put it in a safe.
For the xp_ look at
http://support.microsoft.com/defaul...kb;en-us;891984
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rob R. Ainscough" wrote:
> I'm trying to make my SQL Server a tad more secure, but I'm unable to remo
ve
> SA (I'm running Mixed mode) -- can the SA account only be removed when usi
ng
> windows Authentication? When I try to remove SA I get "selected user
> cannot be dropped because the user owns objects". When I try to delect
> xp_cmdshell I get the following error "You tried to delete one or more
> system objects. They were not deleted."
> I must admit, I'm a little confused, I'm trying to implement Microsofts
> security recommendations, but either the documention is not
> detailed/accurate or I'm missing something?
> Any suggestions?
> Thanks, Rob.
>
>
>|||> I'm trying to make my SQL Server a tad more secure, but I'm unable to
> remove SA (I'm running Mixed mode) -- can the SA account only be removed
> when using windows Authentication? When I try to remove SA I get
> "selected user cannot be dropped because the user owns objects". When I
> try to delect xp_cmdshell I get the following error "You tried to delete
> one or more system objects. They were not deleted."
The sa login account cannot be deleted or renameed, nor it can't be revoked
any permission.
> I must admit, I'm a little confused, I'm trying to implement Microsofts
> security recommendations, but either the documention is not
> detailed/accurate or I'm missing something?
I don't think MS ever mentioned droping the sa account (as it can't be
done). Here are recommendations from Operations Guide: "
The sa account in a production environment should be given a complex
password, made up of uppercase and lowercase letters, symbols, spaces, and
numbers. The sa account should have a complex password, even if the SQL
Server is running in only Windows Authentication Mode. A complex password
protects SQL Server from someone easily getting administrative access to SQL
Server. This also protects the server in the event that an administrator
changes the security authentication mode to Mixed Mode.
Do not use the sa login account in a production environment. Instead, place
each DBA's network user account into a Windows group, create a single SQL
Server login account for the group then add the login account to the
sysadmin fixed server role. "
(http://www.microsoft.com/technet/pr...in/sqlops3.mspx
).
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||Thank you for the information.
The book I was reading is Microsoft Press and the authors are Ed Robinson
and Michael James Bond.
I have the SA password complex so no worries there.
I guess I'll leave the xp_cmdshell alone as it seems to be more trouble that
it is worth to remove it.
Should I think about installing URLScan ?
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:%23BAAU89pFHA.3112@.TK2MSFTNGP12.phx.gbl...
> The sa login account cannot be deleted or renameed, nor it can't be
> revoked any permission.
>
> I don't think MS ever mentioned droping the sa account (as it can't be
> done). Here are recommendations from Operations Guide: "
> The sa account in a production environment should be given a complex
> password, made up of uppercase and lowercase letters, symbols, spaces, and
> numbers. The sa account should have a complex password, even if the SQL
> Server is running in only Windows Authentication Mode. A complex password
> protects SQL Server from someone easily getting administrative access to
> SQL Server. This also protects the server in the event that an
> administrator changes the security authentication mode to Mixed Mode.
> Do not use the sa login account in a production environment. Instead,
> place each DBA's network user account into a Windows group, create a
> single SQL Server login account for the group then add the login account
> to the sysadmin fixed server role. "
> (http://www.microsoft.com/technet/pr...ityLearning.com
>|||> Should I think about installing URLScan ?
Why don't you ask this in some IIS group, with explanation why do you think
you need it?
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
Friday, February 24, 2012
Can't make a connection to SQL Express as Server does not exist or access denied...
Hi
I have recently downloaded SQL Server Express which I have installed using Windows authentication mode. I cannot seem to be able to make a connection to SQL Server from Dreamweaver or Microsoft Visual Web Developer as I am getting an error Server does not exist or access is denied....
I am relatively new to all of this, so would appreciate any advice....
When I installed SQL Server Express I chose Windows Authentication. When I fire up SQL Express and view Security option - the installation program has set up an sa login with a random password. I did not set this password, but think this might be a reason why I can't connect. To rectify the problem I tried creating a new user in SQL Server Express with a password that I specified. On going in to check the settings, I notice SQL Server Express has gone and changed it from the password that I set up.
Now when I try and connect to SQL Server Express I specify the following in the connection paramaters
Server: BGIRL\SQLEXPRESS
Database The database name that I've created
User: the new user that I created
Password: the password I created as part of new user setup
Now I get error message Server does not exist or access denied
Is the problem to do with passwords or perhaps one of the many parameters one seems to have to set up? How can I change a password if I didn't create it? Is there anywhere I can reset it?
PLEASE HELP - I have literally spent 3 days attempting to get this working and am about to give up entirely. Due to my lack of experience, I need very specific step by step instructions..
DId you enable remote connections ? For a step by step guide, visit my site on the link below and visit the Screencast section, you will find the Enable Remote Connection on the list. Feel free to put a comment in there if you find it useful.
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de|||
Thank you for your quick response. I viewed some of your screencasts, and they are very useful...
I had already enabled remote connections so this was not the problem, started up the SQL Browser too, and no luck.
I believe my problem is to do with SQL Express automatically setting up an sa password for me, I can't seem to be able to change this - any ideas as to how I can get around it? Also, when I create my own user in SQL Express, the software automatically changes the password so that I can't use the new user either. Is there a setting I need to change?
Regards Bron
|||There might be a firewall issue with your computer. By default SQL Server is listening on 1433 and uses 1434 additionally. Make sure these ones are not blocked. SQL Server won′t chnage the passwords for you, if you mean that after creating a new user the numbers of stars / dots in the password field differs from the one you entered, that is just for obfuscating the real length of the password and just means that there i something secure store, you don′t need to care about that.HTH; Jens Suessmeyer.
http://www.sqlserver2005.de
cant login to SQL Server anymore
Hi guys-
I can't seem to be able to login into SQL Server anymore ever since I c hanged my password for my Win 2k login. the authentication mode (i checked in the properties section ) is set to SQL Server authentication, but i know originally i set it up as Win 2k authentication, and then changed that to SQL Server authentication...the local server (its set up on my machine) will not start up any more, and I am clueless as to how to fix it. I've tried to login using my other ids ( that i've created) but i don't think those id's had sa rights, so it won't let me.
Please help!Hi Indigo4267,
Try the checking the following:
1). Using the 'Client Network Utility' in the MS Menu, click on the
'Alias' tab.
2). If you don't see your DB server in this list, add it as a Named Pipes
alias.
You should be able to logon direct now, since the DB is on your
local workstation.
3). Check to see what domain/user privileges you have as a user in
the domain that is running the MSSqlServer process. You may not
be able to 'see' the domain running the server.
Good luck!|||thanks for the advice. i'm really new to this db admin stuff (and sql server in general) so i only understood part 1 of what you wrote, and i followed your steps, but it still doesn't work...<sigh>
i guess the real underlying problem is "is there a way to change your win 2k password (if you are the db admin) and still be able to login into sql server (if its set up on your machine) regardless of what authentication mode is set up?" even when i switched to win authentication from sql authentication/mixed mode authentication it still failed!
:( i always get weird problems like this in everything i touch :(|||I actually managed to solve this problem...i think my SQL Server was set to mixed mode which is why i was having problems with my new win2k password--
here's how i did it (for others who are facing teh same problem)
in win2k-
-go to the control panel
-click on administrative tools
-click on services
-right click on MSSQLServer and choose properties
-click on logon tab
-enter and confirm new password
-restart SQL Server
its actually in the help section (for SQL Server 2k) under the heading "Changing Passwords and User Accounts" and there also is info there for win 4.0 NT.
I can't seem to be able to login into SQL Server anymore ever since I c hanged my password for my Win 2k login. the authentication mode (i checked in the properties section ) is set to SQL Server authentication, but i know originally i set it up as Win 2k authentication, and then changed that to SQL Server authentication...the local server (its set up on my machine) will not start up any more, and I am clueless as to how to fix it. I've tried to login using my other ids ( that i've created) but i don't think those id's had sa rights, so it won't let me.
Please help!Hi Indigo4267,
Try the checking the following:
1). Using the 'Client Network Utility' in the MS Menu, click on the
'Alias' tab.
2). If you don't see your DB server in this list, add it as a Named Pipes
alias.
You should be able to logon direct now, since the DB is on your
local workstation.
3). Check to see what domain/user privileges you have as a user in
the domain that is running the MSSqlServer process. You may not
be able to 'see' the domain running the server.
Good luck!|||thanks for the advice. i'm really new to this db admin stuff (and sql server in general) so i only understood part 1 of what you wrote, and i followed your steps, but it still doesn't work...<sigh>
i guess the real underlying problem is "is there a way to change your win 2k password (if you are the db admin) and still be able to login into sql server (if its set up on your machine) regardless of what authentication mode is set up?" even when i switched to win authentication from sql authentication/mixed mode authentication it still failed!
:( i always get weird problems like this in everything i touch :(|||I actually managed to solve this problem...i think my SQL Server was set to mixed mode which is why i was having problems with my new win2k password--
here's how i did it (for others who are facing teh same problem)
in win2k-
-go to the control panel
-click on administrative tools
-click on services
-right click on MSSQLServer and choose properties
-click on logon tab
-enter and confirm new password
-restart SQL Server
its actually in the help section (for SQL Server 2k) under the heading "Changing Passwords and User Accounts" and there also is info there for win 4.0 NT.
Thursday, February 16, 2012
Can't install SQL Server Express 2005 in quiet mode
I'm trying to use a bootstrapper with SQL Server Express 2005, but I'm having difficulty with the installation. I'm using the command line:
SQLEXPR.EXE /qb INSTANCENAME=myInstanceName SAPWD=mySaPassword
SQLEXPR.EXE /qb INSTANCENAME=myInstanceName SAPWD=mySaPassword
and it seems to fail right at the system configuration check. One of the log files says "Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 0"
I can post the contents of the log files if anyone needs them.Try this. Please also check the file template.ini located at the same directory for setup.exe. You can find sample command line to install SQL Server 2005 in silent mode.
start /wait setup.exe /qb ADDLOCAL=SQL_Engine INSTANCENAME="OneExpress" SQLACCOUNT="<domain\user>" SQLPASSWORD="<strong password>" SQLBROWSERACCOUNT="<domain\user>" SQLBROWSERPASSWORD="<strong password>" SQLAUTOSTART=1 SQLBROWSERAUTOSTART=1|||The following command line installs SQL Server Express 2005 in quiet mode (without any user input):
SQLEXPR.EXE /qb ADDLOCAL=ALL INSTANCENAME=myInstanceName SAPWD=mySaPassword
As you can see, the original command line I was having problems with did not include the "ADDLOCAL=ALL" option.
Tuesday, February 14, 2012
Cant install msde on server2000
Anybody out there know why i can't install MSDE on a win2000 server. I start
setup in dos mode with sapwd ="password" but it dies without error
messages.
Thanks in advance
hi,
news wrote:
> Anybody out there know why i can't install MSDE on a win2000 server.
> I start setup in dos mode with sapwd ="password" but it dies without
> error messages.
> Thanks in advance
please add verbose logging of the installation process providing the
/L*v "c:\msde.log"
parameter to your call to setup.exe boostrap installer... this will output
an about 2mb text file (for a succesfull installation) you can later inspect
for
RETURN VALUE 3
entries... about 10/15 lines before each entry som (sometime cryptic)
description of the problem will be reported..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi thanks for the reply i tried it nut cant read the cryptic merror report
or rather cant understand it
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ii0fpFljhkoU1@.individual.net...
> hi,
> news wrote:
> please add verbose logging of the installation process providing the
> /L*v "c:\msde.log"
> parameter to your call to setup.exe boostrap installer... this will output
> an about 2mb text file (for a succesfull installation) you can later
> inspect for
> RETURN VALUE 3
> entries... about 10/15 lines before each entry som (sometime cryptic)
> description of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||him
news wrote:
> Hi thanks for the reply i tried it nut cant read the cryptic merror
> report or rather cant understand it
perhaps we can help you...
try reporting the lines indicating the problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||See my post "Corrupted MSDE files encountered" posted 7/2/2005. Maybe you
have the same problem I did.
Axel Larson,
Share What You Know,
Learn What You Don't
"news" <news@.c.com> wrote in message
news:HL-dnaakovg48F7fRVn-ow@.rogers.com...
> Anybody out there know why i can't install MSDE on a win2000 server. I
start
> setup in dos mode with sapwd ="password" but it dies without error
> messages.
> Thanks in advance
>
|||Hi, I don't know if I have the same problem as News.
This is just the last part of the log file.
Thanks!
MSI (c) (58:60) [09:49:42:814]: Note: 1: 1708
MSI (c) (58:60) [09:49:42:814]: Product: Microsoft SQL Server Desktop
Engine -- Installation operation failed.
MSI (c) (58:60) [09:49:42:830]: Grabbed execution mutex.
MSI (c) (58:60) [09:49:42:830]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (58:60) [09:49:42:830]: MainEngineThread is returning 1603
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ij10tFlrda6U1@.individual.net...
> him
> news wrote:
> perhaps we can help you...
> try reporting the lines indicating the problem..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
Gule wrote:
> Hi, I don't know if I have the same problem as News.
> This is just the last part of the log file.
please isolate the relevand part of the log reporting
RETURN VALUE 3
... about 10/15 lines before each entry some (sometime cryptic) description
of the problem will be reported..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Actually, i solved the problem. I run the setup2.msi and installation passed
without problem!?
Thanks anyway!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3jnfloFqq68uU1@.individual.net...
> hi,
> Gule wrote:
> please isolate the relevand part of the log reporting
> RETURN VALUE 3
> ... about 10/15 lines before each entry some (sometime cryptic)
> description of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Hi Andrea,
We are experiencing the same issue while installing MSDE 2K on a Windows 2K
(SP3) machine. It gives out the error: 1603.
Here is the excerpt from the MSDE install verbose log of the 10-15 lines
before the 'Return Value 3' happens (2 occurences in the log)
-----
-----
1.Starting custom action SkuIt
MSI (s) (24:C0): Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
Action 14:03:31: ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B. ..
MSI (s) (24:C0): Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (24:C0): Creating MSIHANDLE (214) of type 790536 for thread 1984
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\D35166.000\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\D35166.000\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\WINNT\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
"SQL_Latin1_General_CP1_CI_AS""
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 14:04:04: InstallFinalize. Return value 3.
-----
2. Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (24:C0): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (24:C0): Error in rollback skipped. Return: 5
MSI (s) (24:C0): FEATURECACHE: Entering Invalidate
MSI (s) (24:C0): Unlocking Server
Action ended 14:04:24: INSTALL. Return value 3.
-----
-----
I will greatly appreciate any direction to help resolve this issue.
Regards,
Srinivas
"Andrea Montanari" wrote:
> hi,
> Gule wrote:
> please isolate the relevand part of the log reporting
> RETURN VALUE 3
> ... about 10/15 lines before each entry some (sometime cryptic) description
> of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Srinivas Rampalli wrote:
> Hi Andrea,
> "SQL_Latin1_General_CP1_CI_AS""
> Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> Action ended 14:04:04: InstallFinalize. Return value 3.
please have a look at
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
setup in dos mode with sapwd ="password" but it dies without error
messages.
Thanks in advance
hi,
news wrote:
> Anybody out there know why i can't install MSDE on a win2000 server.
> I start setup in dos mode with sapwd ="password" but it dies without
> error messages.
> Thanks in advance
please add verbose logging of the installation process providing the
/L*v "c:\msde.log"
parameter to your call to setup.exe boostrap installer... this will output
an about 2mb text file (for a succesfull installation) you can later inspect
for
RETURN VALUE 3
entries... about 10/15 lines before each entry som (sometime cryptic)
description of the problem will be reported..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi thanks for the reply i tried it nut cant read the cryptic merror report
or rather cant understand it
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ii0fpFljhkoU1@.individual.net...
> hi,
> news wrote:
> please add verbose logging of the installation process providing the
> /L*v "c:\msde.log"
> parameter to your call to setup.exe boostrap installer... this will output
> an about 2mb text file (for a succesfull installation) you can later
> inspect for
> RETURN VALUE 3
> entries... about 10/15 lines before each entry som (sometime cryptic)
> description of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||him
news wrote:
> Hi thanks for the reply i tried it nut cant read the cryptic merror
> report or rather cant understand it
perhaps we can help you...
try reporting the lines indicating the problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||See my post "Corrupted MSDE files encountered" posted 7/2/2005. Maybe you
have the same problem I did.
Axel Larson,
Share What You Know,
Learn What You Don't
"news" <news@.c.com> wrote in message
news:HL-dnaakovg48F7fRVn-ow@.rogers.com...
> Anybody out there know why i can't install MSDE on a win2000 server. I
start
> setup in dos mode with sapwd ="password" but it dies without error
> messages.
> Thanks in advance
>
|||Hi, I don't know if I have the same problem as News.
This is just the last part of the log file.
Thanks!
MSI (c) (58:60) [09:49:42:814]: Note: 1: 1708
MSI (c) (58:60) [09:49:42:814]: Product: Microsoft SQL Server Desktop
Engine -- Installation operation failed.
MSI (c) (58:60) [09:49:42:830]: Grabbed execution mutex.
MSI (c) (58:60) [09:49:42:830]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (58:60) [09:49:42:830]: MainEngineThread is returning 1603
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ij10tFlrda6U1@.individual.net...
> him
> news wrote:
> perhaps we can help you...
> try reporting the lines indicating the problem..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
Gule wrote:
> Hi, I don't know if I have the same problem as News.
> This is just the last part of the log file.
please isolate the relevand part of the log reporting
RETURN VALUE 3
... about 10/15 lines before each entry some (sometime cryptic) description
of the problem will be reported..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Actually, i solved the problem. I run the setup2.msi and installation passed
without problem!?
Thanks anyway!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3jnfloFqq68uU1@.individual.net...
> hi,
> Gule wrote:
> please isolate the relevand part of the log reporting
> RETURN VALUE 3
> ... about 10/15 lines before each entry some (sometime cryptic)
> description of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Hi Andrea,
We are experiencing the same issue while installing MSDE 2K on a Windows 2K
(SP3) machine. It gives out the error: 1603.
Here is the excerpt from the MSDE install verbose log of the 10-15 lines
before the 'Return Value 3' happens (2 occurences in the log)
-----
-----
1.Starting custom action SkuIt
MSI (s) (24:C0): Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
Action 14:03:31: ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B. ..
MSI (s) (24:C0): Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (24:C0): Creating MSIHANDLE (214) of type 790536 for thread 1984
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\D35166.000\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\D35166.000\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\WINNT\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
"SQL_Latin1_General_CP1_CI_AS""
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 14:04:04: InstallFinalize. Return value 3.
-----
2. Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (24:C0): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (24:C0): Error in rollback skipped. Return: 5
MSI (s) (24:C0): FEATURECACHE: Entering Invalidate
MSI (s) (24:C0): Unlocking Server
Action ended 14:04:24: INSTALL. Return value 3.
-----
-----
I will greatly appreciate any direction to help resolve this issue.
Regards,
Srinivas
"Andrea Montanari" wrote:
> hi,
> Gule wrote:
> please isolate the relevand part of the log reporting
> RETURN VALUE 3
> ... about 10/15 lines before each entry some (sometime cryptic) description
> of the problem will be reported..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Srinivas Rampalli wrote:
> Hi Andrea,
> "SQL_Latin1_General_CP1_CI_AS""
> Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> Action ended 14:04:04: InstallFinalize. Return value 3.
please have a look at
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Sunday, February 12, 2012
Cant get windows authentication in Mixed Mode to work .... any ideas?
Hey all,
I've got SQL 2K running in mixed mode. I created a windows acct (mytest) in the administrator group, and then created a corresponding SQL account (mytest) using the windows authentication. In the EM it comes up as a "Windows User" type of acct. (The account is not a domain account but a workstation one).
I've configured my app to use that account for access to the database but I get the following error message when I send the connection request to the datasource:
Connection Failed:
SQL State:28000
SQL Server Error: 18456
Login failed for user myworkstation\mytest
I can connect just fine using the sql accounts, but it doesn't want to play nice when I need the windows authentication portion to work.
What exactly am I doing wrong?
Any input is greatly appreciated !
Regards,
TammyA couple of things come to mind...
1. If mytest is a member of the workstation Administrators group, then you do not (necessarily) need a separate SQL account for it. The BUILTIN\Administrators account permits all members of the local Administrators group to have access (in the default config anyway).
2. If you have denied access to the BUILTIN\Administrators group, then myWorkstation\mytest will not have access (Deny trumps permit).
3. Just a head check: you said that myworkstation\mytest was NOT a domain account (when you set it up). You didn't by chance login under the domain?
Just my $ .02. It's not much, I'll grant you, but it was what I could come up with.
hmscott|||Mr. Scott !
I'm such an idiot ....
I had forgotten that I denied access to the builtin Administrator account. I turned it back on and VOILA !
Mr. Scott - 1
Tammy - 0
Gracias !
Originally posted by hmscott
A couple of things come to mind...
1. If mytest is a member of the workstation Administrators group, then you do not (necessarily) need a separate SQL account for it. The BUILTIN\Administrators account permits all members of the local Administrators group to have access (in the default config anyway).
2. If you have denied access to the BUILTIN\Administrators group, then myWorkstation\mytest will not have access (Deny trumps permit).
3. Just a head check: you said that myworkstation\mytest was NOT a domain account (when you set it up). You didn't by chance login under the domain?
Just my $ .02. It's not much, I'll grant you, but it was what I could come up with.
hmscott
I've got SQL 2K running in mixed mode. I created a windows acct (mytest) in the administrator group, and then created a corresponding SQL account (mytest) using the windows authentication. In the EM it comes up as a "Windows User" type of acct. (The account is not a domain account but a workstation one).
I've configured my app to use that account for access to the database but I get the following error message when I send the connection request to the datasource:
Connection Failed:
SQL State:28000
SQL Server Error: 18456
Login failed for user myworkstation\mytest
I can connect just fine using the sql accounts, but it doesn't want to play nice when I need the windows authentication portion to work.
What exactly am I doing wrong?
Any input is greatly appreciated !
Regards,
TammyA couple of things come to mind...
1. If mytest is a member of the workstation Administrators group, then you do not (necessarily) need a separate SQL account for it. The BUILTIN\Administrators account permits all members of the local Administrators group to have access (in the default config anyway).
2. If you have denied access to the BUILTIN\Administrators group, then myWorkstation\mytest will not have access (Deny trumps permit).
3. Just a head check: you said that myworkstation\mytest was NOT a domain account (when you set it up). You didn't by chance login under the domain?
Just my $ .02. It's not much, I'll grant you, but it was what I could come up with.
hmscott|||Mr. Scott !
I'm such an idiot ....
I had forgotten that I denied access to the builtin Administrator account. I turned it back on and VOILA !
Mr. Scott - 1
Tammy - 0
Gracias !
Originally posted by hmscott
A couple of things come to mind...
1. If mytest is a member of the workstation Administrators group, then you do not (necessarily) need a separate SQL account for it. The BUILTIN\Administrators account permits all members of the local Administrators group to have access (in the default config anyway).
2. If you have denied access to the BUILTIN\Administrators group, then myWorkstation\mytest will not have access (Deny trumps permit).
3. Just a head check: you said that myworkstation\mytest was NOT a domain account (when you set it up). You didn't by chance login under the domain?
Just my $ .02. It's not much, I'll grant you, but it was what I could come up with.
hmscott
Subscribe to:
Posts (Atom)