Hi;
I have VMWare on a test computer and installed the dev version of SqlServer
2005 fine on the frist VM partition.
However, on the second it won't let me check the reporting services and
requires a strong password. Why?
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htmHi,
For further research, I would like to know:
1. Do your two VMWare partions have the same version of Windows OS?
2. What's the Windows OS edition?
3. What will happen if you specify a strong password for it?
4. Could you send me related system event logs to me
(changliw@.microsoft.com) ?
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||Hi;
1. Yes - same everything.
2. Windows 2003 with all service packs.
3. I did not do that as I want the same p/w we use for everything on the
test system.
4. Will get tomorrow (I'm home now).
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Charles Wang[MSFT]" wrote:
> Hi,
> For further research, I would like to know:
> 1. Do your two VMWare partions have the same version of Windows OS?
> 2. What's the Windows OS edition?
> 3. What will happen if you specify a strong password for it?
> 4. Could you send me related system event logs to me
> (changliw@.microsoft.com) ?
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
>|||Hi;
For question 4 all it has is:
MsiInstaller - SQL Server 2005 - Install started.
MsiInstaller - SQL Server 2005 - Installation failed.
And the failed is because I cancelled it.
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Charles Wang[MSFT]" wrote:
> Hi,
> For further research, I would like to know:
> 1. Do your two VMWare partions have the same version of Windows OS?
> 2. What's the Windows OS edition?
> 3. What will happen if you specify a strong password for it?
> 4. Could you send me related system event logs to me
> (changliw@.microsoft.com) ?
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
>|||BTW - the big problem is it requiring a strong password for the SqlServer sa
user. That will break all of our unit tests.
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Charles Wang[MSFT]" wrote:
> Hi,
> For further research, I would like to know:
> 1. Do your two VMWare partions have the same version of Windows OS?
> 2. What's the Windows OS edition?
> 3. What will happen if you specify a strong password for it?
> 4. Could you send me related system event logs to me
> (changliw@.microsoft.com) ?
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
>|||Hi Dave,
Thanks for your response.
By default, strong password is a policy in Windows 2003. From your
description, I understand that your SQL Server 2005 ran with mixed
authentication mode and you log on the SQL 2005 with sa account.
I would like to know whether or not you can log on the SQL Server 2005 with
sa account which password is weak. Which place did this issue occurs?
To let me better understand this issue, I would like you could mail me
(changliw@.microsoft.com) a screenshot of your issue.
In SQL Server 2005, you can modify sa password and cancel the strong
password policy via:
Log on into Microsoft SQL Server Management Studio with sysadmin;
Expand the Security folder;
Expand the Logins folder;
Right click sa account and click Properties on the pop menu;
Cancel the selection of "Enforce password policy";
Modify the sa password if you want to.
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||Hello;
Not exactly. I have not installed Sql Server 2005 yet because of these two
problems.
1) It has greyed out reporting services and I need to install that.
2) It wants a strong password during install. How can I set it to not
require that during install?
What is weird is this is a Windows 2003 test system and I have another
identical test system that did not have these problems. The only difference
is the other system has IIS installed.
So, how can I fix this?
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Charles Wang[MSFT]" wrote:
> Hi Dave,
> Thanks for your response.
> By default, strong password is a policy in Windows 2003. From your
> description, I understand that your SQL Server 2005 ran with mixed
> authentication mode and you log on the SQL 2005 with sa account.
> I would like to know whether or not you can log on the SQL Server 2005 with
> sa account which password is weak. Which place did this issue occurs?
> To let me better understand this issue, I would like you could mail me
> (changliw@.microsoft.com) a screenshot of your issue.
> In SQL Server 2005, you can modify sa password and cancel the strong
> password policy via:
> Log on into Microsoft SQL Server Management Studio with sysadmin;
> Expand the Security folder;
> Expand the Logins folder;
> Right click sa account and click Properties on the pop menu;
> Cancel the selection of "Enforce password policy";
> Modify the sa password if you want to.
>
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
>
>|||David Thielen wrote:
> Hello;
> Not exactly. I have not installed Sql Server 2005 yet because of these two
> problems.
> 1) It has greyed out reporting services and I need to install that.
> 2) It wants a strong password during install. How can I set it to not
> require that during install?
> What is weird is this is a Windows 2003 test system and I have another
> identical test system that did not have these problems. The only difference
> is the other system has IIS installed.
> So, how can I fix this?
>
Reporting Services requires IIS - that's how it delivers the reports...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, Reporting Service is a web-based application. I recommend that Install
IIS 6.0 first and then try again.
You can install the component via "Add/Remove Components" from control
panel or "Add or remove a role" from "Manage Your Server" in the start menu.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Any idea on the strong password requirement?
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Charles Wang[MSFT]" wrote:
> Yes, Reporting Service is a web-based application. I recommend that Install
> IIS 6.0 first and then try again.
> You can install the component via "Add/Remove Components" from control
> panel or "Add or remove a role" from "Manage Your Server" in the start menu.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>|||Hi Dave,
That's due to your windows security policy on password.
You can try executing the statement ALTER LOGIN sa WITH CHECK_POLICY=OFF.
For more information on password policy, you can refer to:
Strong Passwords
http://msdn2.microsoft.com/en-us/library/ms161962.aspx
Password Policy
http://msdn2.microsoft.com/en-us/library/ms161959.aspx
If you have any other questions or concerns, please let me know. It's my
pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support|||Hi;
Let me ask the question a little differently:
1) Why does this copy of Windows 2003 have a strong password policy when
another test system that I installed the same does not?
2) The password it will not allow for Sql Server it did allow as the
administrator password for Windows itself. How is it there is a policy that
requires the strong password only from Sql Server?
3) How can I turn off this policy for all of Windows on this system? It's a
test system so we don't want strong passwords required.
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Charles Wang[MSFT]" wrote:
> Hi Dave,
> That's due to your windows security policy on password.
> You can try executing the statement ALTER LOGIN sa WITH CHECK_POLICY=OFF.
> For more information on password policy, you can refer to:
> Strong Passwords
> http://msdn2.microsoft.com/en-us/library/ms161962.aspx
> Password Policy
> http://msdn2.microsoft.com/en-us/library/ms161959.aspx
> If you have any other questions or concerns, please let me know. It's my
> pleasure to be of assistance.
> Charles Wang
> Microsoft Online Community Support
>
>|||Hi Dave,
Appreciate your response.
For your first question, Windows Server 2003 has strong password policy by
default, so if another test system doesn't have that policy, it may be
changed.
For your seconde question, SQL Server doesn't force a database to have
strong password even Windows 2003 has that policy. However this is decided
by authentication mode of SQL Server 2005. If you log on your SQL Server
2005 with Windows Authentication, your SQL Server password policy is based
on Windows policy and should be changed in Windows security policy;
otherwise, if you log on SQL Server 2005 with SQL Authentication, you can
modify the password policy in SQL Server 2005 Management Studio:
1. Expand the the Login of Security node;
2. Right click the login account and click Properties;
3. Cancel the selection of "Enforce password policy".
For your third question, if your computer is in domain, you need cancel the
policy in your domain contrller first. For local configuration, you can do
via "Start->Administrative Tools->Local Security Policy->Account
Policy->Password Policy". Please refer to the following articles to change
the policy:
Account Policy Settings
http://technet2.microsoft.com/WindowsServer/en/library/353f7ad9-b53d-41d0-98
67-199f6595a01b1033.mspx?mfr=true
Step-by-Step Guide to Enforcing Strong Password Policies
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/
directory/activedirectory/stepbystep/strngpw.mspx
Sincerely yours,
Charles Wang
Microsoft Online Community Support
C) [16:38:05:436]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI597.tmp, Entrypoint: InstallPerfCounters
C) [16:38:05:436]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI597.tmp, Entrypoint: InstallPerfCounters