I have a 3 node cluster running windows 2003 x64 sp1 and SQL Server 2005 version 9.00.2153. My problem is the following...
This Saturday I migrated a web application's database to this server. After restoring the database I created the sql login for the service account, set the password and disabled the password policy for this login. I then ran sp_change_users_login to attach the already existing db user with the same name to the login. I changed the connection string for the application, tested the application connectivity and functionality then detatched the old database on the old server. Everything went like clockwork, no problems at all.
Come Monday morning at 8:35 I started getting alerts that the web site was down. I tested the site and sure enough it was down. I then attempted to connect to the database server using the login that was created for the app and the connection failed. I logged in with my ID and got in fine. Nothing showing to be wrong with the DB, I checked the new login and somehow the "Enable Password Policy" had been set for the new login. I disabled it and still no connection. I went to the database and checked the DB user and somehow the link between it and the login no longer existed. I reran the sp_change_users_login and restested the web site and verified that that web site was back online.
My question is this, is there any stored proc that resets these values back to default for some reason, a series of events that might revert the "Enable Password Policiy" to the default for a login, or is there a particular domain level operation that might occur such as Security Polcies that would affect these settings in SQL?
No one else was on the machine when I went to check it out at 8:40 so it has left me puzzled.
I am building a winforms .net 3.5 application which connects to a SQL Server 2005 database with SQL server authentication. Is it possible to access the SQL Server password policy and expiration through the .NET 3.5 framework? I would like add the following functionality to my login form:
Ensure passwords meet policy standard.
Prompt a user to change their password when it is due to expire in 5 days or less. Thanks in advance.
I am receiving the following error message when attempting to create a new SQL Authenticated login id.
Password validation failed. The password does not meet the requirements of the password filter DLL. (Microsoft SQL Server, Error: 15119)
I have four servers all running SQL Server 2005 SP2 on Windows 2003 Ent. SP1. Of the four servers, only one received the above error message using the same TSQL below.
CREATE LOGIN TEST_LOGIN WITH PASSWORD = 'pvif9dal' MUST_CHANGE, CHECK_EXPIRATION = ON
All four servers are in the same domain, which if I understand correctly, the password policies are therefore inherited at the OS level by the domain. The password being used is within the password policies of the domain.
I tried to install an ALLDATA database which run with SQL Server 2005 express edition. The data base fails to install becase of the following code that come up which is related to AS password requirement. The error that come up is:
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=28001&EvtType=sqlca%5csqlcax.cpp%40SAPasswordPolicyCheck%40SAPasswordPolicyCheck%40x6d61
------------------------------ BUTTONS:
&Retry Cancel ------------------------------
I am trying to install this database in a network server operating under Windows Server 2003 R2 with SP2. If anyone knows how to solve this problem, please let me.
Hi all,We recently started to receive complaints about our install project notworking and giving and shitload of error messages related to SQL. Welater found out that the problem was the users we were trying to bindto we're not created because of the domain password policy featureimplemented into SQL Server 2005.After much dabbling around the SQL scripts that created the databasestructure, we came to the conclusion that only this piece of code couldcorrect our problem :CREATE LOGIN mynewuser WITH PASSWORD = '', CHECK_POLICY = OFF,CHECK_EXPIRATION = OFFThis runs perfectly fine on SQL2005, but not on SQL2000. We have beensearching for a way to have code in SQL files executed on install thatdoesn't fail to compile when run against the server and that willbypass the password policy in case it's a SQL Server 2005...Right now we are testing a feature available in MSI that can filterscripts not matching a database version, but the problem with this, isthat we are missing a lot of features that InstallShield has. In short,we need Help to fix this issue and be able to continue withdevelopment.In hopes to receive a a prompt anwser
We run a few shared hosting servers in the UK, now we used to run mssql 2000 and moved to 2005 in december 2005.
Microsoft SQL 2005 9.00.1399.06 Microsoft SQL Server Management Studio 9.00.1399.00 Microsoft Analysis Services Client Tools 2005.090.1399.00 Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447) Microsoft MSXML 2.6 3.0 6.0 Microsoft Internet Explorer 6.0.3790.1830 Microsoft .NET Framework 2.0.50727.42 Operating System 5.2.3790
We were in the process of improving security on some of our new servers, in the windows password policies settings we enabled the following minimum password length = 6 characters Password must meet complexity requirments = enabled
sql 2005 authentification was set in mixed mode, but we have tried windows authentification only as well.
Now when you try and add a new user even if the password meets all requirments you get an error password is to short etc, we used sql managment studio both manually creating a user and scripting with sql, both with the same result.
In the shared hosting environment we need passwords to be secure, the only way we can get sql users to be created is to disable windows password policies which causes security problems.
We would prefer to use sql authentification not windows but even when we use sql authent it still seems to use the windows password policy and the same error occurs
I am installing SQL Server 2005 Express as part of my setup. On Windows 2003 Servers with password policy enabled, the SQL Server 2005 Express installation fails. Here is the error I am getting - "the sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online.". If I disable the password policy, the SQL Server 2005 Express installation is OK.
Is there a parameter that I can pass to the command line to get around this?
What are the exact requirements implied by the sql 2005 option:
"Password Must Meet Complexity Requirements "
TIA,
Barkingdog
P.S. I found this one:
-Cannot contain all or part of the username -Must be at least 6 characters long -Contain 3 of the 4 following character groups - A to Z - a to z - 0 to 9 - Special Characters i.e. ! ^ $ *
and I have also found
"At least 7 characters in length"
Combines letters. numbners, and symbolds
Is not a dicitonary word, name of a command, person's name or user's account name
I've legacy code that requires a blank password for a SQL Server login. This works fine on 2000 or 7.
How can you allow blank passwords on SQL Server 2005 without changing the windows policy? Is there a stored procedure to do this? I know you can now use CREATE LOGIN and set CHECK_POLICY to no on SQL 2005 when creating logins, but this needs to run on SQL Server 7/2000 and so its using sp_addlogin. (NB: I can't easily change the legacy code to work conditionally on SQL Server 2005)
I have a complicated question that involves the password policy defined within Windows Server 2003 and how it is used in Microsoft SQL Server 2005. I recently installed windows server 2003 on my development system. I am a person that prefers to develop in the same OS that our application runs in production. After installing 2003, then a Domain administrator added my machine to our corporate domain. Now, I cannot change the local password policy to allow a simple password. I believe this is due to policy inheriting from the domain that the machine belongs to.
This ties back into SQL Server 2005 because installing sql server on a Server 2003 causes SQL Server 2005 to follow the password policies defined at the OS level. This breaks our application in a subtle way in that we create login accounts for new client databases with random password. Because the password is random it sometimes conforms to the policy and sometimes not.
In production environments, the password policies are configured differently. So I need to one of the following options:
-change the group policy/inherited policy on my machine to not inherity from the domain I joined (prefered solution but don't know HOW)
-change SQL Server to not use OS password policy
-change code to use CREATE LOGIN statement with CHECK_POLICY=OFF or change password generation code to use a stronger password. (don't want to do this as the code change is only accomodating non-production environments)
If someone has a better place to post this question, I would sure appreciate it.
Hi all,Suppose I have a SQL database table called Customer Info which contains six fields namely Customer ID, Address, First , Last Name , Password, and Time Remaining. The Time Remaining field contains the amount of time that a customer has before his or her password expires. I would like info in this field to be in hours and minutes and when it reaches zero, I would like the password to be deleted from the database. So I have two questions and please take into consideration that I am using dot net 2.0.1) Can this be done without having to write a custom function?2) If this can only be done by creating a custom function, how would I get the function to communicate with the database, in other words how would I let the function know that a customer's time is up? Any suggestions will be greatly appreciated, thank you in advance for your help.
The problem I am facing is related to dynamic configuration of package one of the package connection is DB2 connection, I tried to set the expression connection string for that connection to the variable which contains the connection string to the DB2 but when I set connection the String property then i get the error message in transformation that password is missing, I dont want to write password in connection String for security reasons so I tried to save password in connection which is not helpful I am getting the same error message package security setting I changed to "Encrypt Sensitive Data with User Key" , anywayout to overcome this problem?
I am doing a shopping basket type demo.I have difficulties going from table with fields like (Name,ProductCode) to table(Name, ProductCode, NumberOfItems). One way could be adding just Name and ProductCode fields and let NumberOfItems come automatically. It could have some common value like 1. How should I do this with VB.
When I ran the report from the browser (not from the preview when designing the report), the parameters and the View Report button still displayed. I noticed clicking a double arrow button can hide or show the parameter section . How can I make hiding the parameter section as default? Currently showing the section is the default.
Hi, SELECT UserID, UserName, Password, PublisherID, CurrencyFROM [User]WHERE (Password = 'Anitha') I am using the above mentioned it is working but int the password field i had given it as anitha. Now the querry is retriving the record for anitha, it shouldnot happen. The querry should retrive the record of anitha only for where condition anitha and not for Anitha or ANITHA etc.. Thanks Vishwanath
While installing SQL Server 2000 on my Windows 2000 Advanced Server, i choose Windows Authentication mode, so i was not able to enter a password for sa account. And after installation, in Enterprise Manager i could still see sa account under logins but the account has a password.
So my question is what is the default password for sa account when we choose Windows Authentication mode and is it possible to change the mode from windows Authentication to Mixed Authentication mode after installation, with out re-installaing SQL Server 2000.
i have installed the .net C# 2005 it include the sql express but when i am creating a database in window authoncation it create sucessfully but when i am creating using uid and password it will not accept why ?
We recently downloaded and installed SQL Express as it was a required program for our new database management software. When trying to install my database management software I was asked to Login to the SQL server. I entered the SQLEXPRESS server, however, I do not have the SA password. When SQL Express installed it did not ask for a password only for a user name and company. I am running Windows Small Business Server with the Administrator and no password. We did not assign a password to the Administrator account yet.
I have tried to leave the password blank using the login SA and I get error message 28000 Login failed for user. The user is not associated with a trusted SQL Server Connection.
Is there a default password for SA? Or in the alternative, how do I create a user or associate an exising Windows user with a trusted SQL server connection?
If I install an instance with Windows Only authentication, and then change it to Mixed Mode, if I enable the sa login, the password has already been set. What is the default? If it's generated, how secure is it? Is the password generated? What algorithm is used for that?
Hello,What are the default login/password to access pubs and northwind databases ?I remember the login = "sa", but nothing about the password.ThanksEric
hi, all: I installed a Sql 2000 Personal Edition in my Laptop,now I want to change my Sql 2000 sa account password. but I can not find where I can get the default password for sa account and how to change it .
i have installed windows 2008 evaluation, during installation i was not asked for username and pssword but when i try and start up its asking for administrator password.
I have recently restored an SQL Server 2000 database on SQL Server 2005 A number of constraints on the database had previously been disabled
A monthly process that is carried out, imports data into 'Table A'. This process now crashed, being unable to truncate table as it referenced by 'Table B'
Although when i check the properties of the constraint the 'enforce foreign key constraints' is set to no.
Is there a known issue with restoring databases on 2005,
how to i write a trigger to enforce this constraint..A rental can be made only if the customer is registered with the company and the car is not currently rented out. If not, the rental will not be successful.
