I have forgotten password of user sa in sql server 2005.
But if authentication is window . I still login, and do work normal.
So how to solve problem ,if authentication is sql server.
Thank you very much.
I create a connection to an OLE db source and use SQL Server authorization and save the password, the connection manager seems to "forget" the password. That is, when I click the 'save password' check box, and do a test connection, it connects fine. But as soon as I close that connection window, and reopen it, the password box is empty, and the 'save password' box is still checked.
While using the connection manager name in the SSIS component (say script task) the connection is failing . As a workaround, the whole connection string has been put in a variable and used that variable in the SCRIPT task.
Is it a bug or some other property need to be set to use ConnectionManager Name .
Using BIDS 2008
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.
Any ideas as to a root cause?
I am designing an application using service broker, and to increase performance of the application, sometimes I will be sending messages without waiting for a reply. After reading the article by Remus at http://blogs.msdn.com/remusrusanu/archive/2006/04/06/570578.aspx regarding fire and forget messages I realised I should always let the target end the conversation first so I can catch any errors. However, other times when i send a message from the initiator queue, I will want to wait for a reply.
If I have an activated stored procedure attached to the initator queue (as suggested in the article) would it mean that I would not be able to handly ANY replies manually (ie from the code that originally started the conversation).
If this is the case, should I have two initiating queues, one that handles fire and forget type requests and another where it waits for a reply, or should I just have some sort of clean up routine scheduled which checks for error replies and ends any other conversations that have been ended by the target?
Hi guys,anybudy know the thing as title?And does sql server has the func. to transfer plain txt to encryt. text? Cheers, Elton
View 2 Replies View RelatedHow do you change the SA password in SQL Server 2005?
Thanks.
Doug
12 months since last use!
Is there any way to open server without re-installing to reset password.
after upgrading from sql 2000 to 2005 - many users have issues loging on due to case sensitivity
is this something I can turn off ?
sql 2005 passwords are case sensitive - sql 2000 are not (for SQL Accounts)
any suggestions would help greatly
Hi there .NET community.
I was wondering if there was a way to launch a stored procedure froman aspx page without the sqlCommand object sitting waiting for the sproc to return something.The procedure takes about 10 minutes to execute and the page timeouts.Is there a way to just execute the procedure and procede to the next line of script?
Thanks.
CaptainCrabs
Hi All
I am running SQL Server 2005 SP2 on Windows Server 2003 R2 machines.
I am running the SQL Server service under a domain account. This account has the common sense options ticked/unticked.. i.e. password never expires, don't force user to change password at first login.
I find the SQL Server will start fine under this account.. and run continuously without a problem. Then when the machine is reboot, the SQL Server service has not started. So I go to the "Services" app in the administrative tools and click Start. I immediately get the message that "The service could not start due to a logon failure".
The username still appears to be there, and the password appears to be there too but I obviously cannot tell what it is as its masked. The password has not been changed. But for some reason the authentication details are not correct - so when I re-enter them and click Apply it says "account has been granted Log On As A Service right" and I can click Start and SQL server will start up.
Next reboot... and it happens again. Any ideas why this would be? This occurred when we were running SQL Server 2005 with no SP, and with SP1 too. It happens on all our machines, both x86 and x64.
Adam
Hi!
How to install sql server 2005 automatically with sa password
I want to know that i am creating a setup in visual studio 2005, i have set up sql server as prerequsite, by default the sql server installation is silent, it does not ask anything, in MSDE we had the facility of setyp.ini file which automatically creates the database with the settings provided in the ini file. Is there any option like this in sql server 2005 express editon.
[Options]
INSTANCENAME="MSDE"
SECURITYMODE=SQL
SAPWD="admin"
now what can be done in sql server 2005 express edtion
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,
My application supports both SQL Server 2005 and Oracle. Now, while chaging the password for the user WHOSE PASSWORD IS ALREADY EXPIRED .... the following code works fine for Oracle , but I dont know how to handle the same thing in SQL Server 2005.Please reply at your earliest.I am posting the code below which is creating the problem.
public static boolean changeExpiredPassword(User user, User newUser) throws SQLException, Exception
{
if (_logger.isDebugEnabled())
{
_logger.debug("changeExpiredPassword(User user=" + user + ", User newUser=" + newUser + ") - start");
}
boolean passwordChanged = false;
String url = null;
Properties dalProps = null;
Connection conn = null;
String sysIdentifier = null;
try
{
dalProps = DALManager.getInstance().getProperties();
url = dalProps.getProperty(DALConfigurator.URL);
if (url != null && url.indexOf("thin") > -1 && url.lastIndexOf(":") > -1)
{
int index = url.lastIndexOf(":");
sysIdentifier = url.substring(index+1, url.length());
url = "jdbcracleci" + sysIdentifier;
}
Properties props = new Properties();
props.put("user", user.getUsername());
props.put("password", user.getDecryptedPassword());
props.put("OCINewPassword", newUser.getDecryptedPassword());
if (DALManager.getInstance().isOracle() &&
url != null)
{
conn = DriverManager.getConnection(url, props);
if(conn != null && !conn.isClosed())
{
passwordChanged = true;
conn.close();
}
}
if (DALManager.getInstance().isSqlServer() &&
url != null) // This condition becomes true if we are connected to SQL Server 2005
{
/// Over here , the connection object is Returning the NULL value since the I have loaded the Properties ( props.put ) with Oracle specifice syntax it ( i.e. OCINewPassword ) . I dont know what to code if its connected to the SQL Server 2005 itstead of Oracle.
conn = DriverManager.getConnection(url,props); // This part fails
if(conn != null && !conn.isClosed())
{
UsersQueryModule.changePassword(user.getUsername(), user.getDecryptedPassword(), newUser.getDecryptedPassword(), false);
passwordChanged = true;
conn.close();
}
}
}
catch (SQLException e)
{
_logger.error("changeExpiredPassword(user=" + user + ", newUser=" + newUser + ")", e);
throw new AxisFault("Expired password cannot be changed. Possible cause may be TNS Name does not match with Oracle SID. Please consult the System Administrator.");
}
catch (Exception e)
{
_logger.error("changeExpiredPassword(user=" + user + ", newUser=" + newUser + ")", e);
throw e;
}
finally
{
if (conn != null && !conn.isClosed())
conn.close();
}
if (_logger.isDebugEnabled())
{
_logger.debug("changeExpiredPassword(User, User) - end - return value=" + passwordChanged);
}
return passwordChanged;
}
Is there a way to do this at the server level?
Thanks
Please Help!!
We have an application using SQLOLEDB connection to a SQL Server 2005 database. Per domain policy, the users are required to change their password every 60 days.
The accounts are established to 'Enforce password policy'.
When we try to execute the 'ALTER LOGIN' command to change the password, locks are being established and will not free the account without bouncing the instance.
After issuing the command, any interaction with the server using this UserID results in a "lock request time out" error 1222.
I have tried issuing this command using both the application and through SQLServer Mgmt Studio Express and the results are the same.
Any idea would be greatly appreciated.
Rusty Rickmon
I am trying to do an upgrade in place from SQL Server 2000 SP3a to SQL Server 2005. I am encountering the following error. SQL Server Setup has encountered the following problem:[Microsoft][SQL Native Client][SQL Server] Password validation failed. The password does not meet Windows policy requirements because it is too short...To continue, correct the problem and then SQL Server setup again. I read the other posting and it mentioned that the sa account needs to be changed. I have changed the sa account to meet the passowrd requirements for our system and have changed the following services I could find over to my domain account which I know meets the password restrictions. If I do a new install, everything seems to load correctly. What options do I have to do this upgrade in place?
Thanks for your help,
Bill
How can I execute a long running transaction using something similar to the fire and forget pattern?
I intend to start the execution of a very long stored proc from within IIS. I would like to execute a sql script that will start the job and return immediately so that it doesn't hold an IIS thread.
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
My PC is Window XP Pro and I'm using Microsoft SQL Server 2005 Express and Microsoft SQL Server Management Studio Express.
My question is how to create a login userid and password under "SQL Server Authentication"? (as shown in http://www.findingsteve.net/print_screen.jpg)
Any tutorial about this I can read?
During an install of SQL Server 2005 Express setting the sa password does not work consistently. The install is being run as administrator and I am using an .ini file to pass the settings,
SECURITYMODE=SQL
ADDLOCAL=ALL
SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
INSTANCENAME=DBSERVER
SAPWD=Westtech#1
and while most times it works correctly, occasionally, maybe 4 out of 10 times it fails to set the password and I have been unable to find any warnings or errors in the logs it generates.
We are coming up on release and this is causing us some real problems. Does anyone have any ideas, something I could look at?
Thank you,
Kathy Mook
Westbrook Technologies, Inc.
SQL Server 2005 Express keeps putting in a different password than the one I chose. I would check the properties on the login I want to change. Then I change the password and it gets accepted. When I try my web application, I get the dreaded "login failed for <loginname>". I look at the properties again and see my password never change. Is this a bug? I ever tried this syntax to no avail:
CREATE LOGIN <loginname> WITH PASSWORD='<mypassword>' CHECK_EXPIRATION = OFF, CHECK_POLICY = OFF
Hi,
I was wondering if someone could help me as this is a bit of a puzzle.
I have created a database using a password, the create table scripts are executed successfully using the connection string however when I try and use the same connection string to insert some data into the database an error is produced, with the following message 'The specified password does not match the database password'.
I have opened the database using the SQL Server 2005 Management Studio and provide the password and I can access the database without a problem.
When the connection object is first instantiated all the Connection String property, the connStr variable and the modifiedConnStr are all correct (by this I mean that the data source and the password are present). However when the connection object is accessed again the Connection String property and the connStr variable are both set incorrectly (by this I mean that the password= section of the string is missing) however the modifiedConnStr is set correctly (by this I mean that the password= section is present in the string).
The connection object does not get set in between creating and accessing the connection object.
I have resorted to using no password, however I really need to be able to use a password.
Here is a copy of the connection string I am using (Copied directly from the quick watch window):
"Data Source = '\Program Files\Application\DataBase\MyDatabase.sdf'; password="Pa55word";"
I am sorry this a little long winded however I would like to provide as much information as possible. I hope someone can help me with this problem.
Thank you for reading.
Paul Diston
Hi. I've looked all over MSDN, newsgroups and the web but I can't find the answer to a problem that I am having.
The application that I am working on used both transactional and merge replication. I want to avoid hard coding passwords into an application that kicks off the pull replication on the client machine.
The client machines are all using SQL Server 2005 Express. The other machine is running SQL Server Standard. The passwords and login details are specified in the subscription properties in the Management Studio.
A fragment of the code is posted below. The transactional sychronization works fine without having to specify any passwords - however the merge replication does not work if both of the passwords are not specified.
private void SynchButton_Click(object sender, EventArgs e) { // Set up the subscriber connection details. subscriberConnection = new ServerConnection(subscriberName); try { // Connect to the Subscriber. subscriberConnection.Connect(); // Do the transactional subscription synchronisation independantly of the // merge subscription replication. try { transPullSubscription = new TransPullSubscription(subscriptionDbName, publisherName, publicationDbName, transPublicationName, subscriberConnection); // If the pull subscription and the job exists, start the agent job. if (transPullSubscription.LoadProperties() && transPullSubscription.AgentJobId != null) { TransSynchronizationAgent transSyncAgent = transPullSubscription.SynchronizationAgent; transSyncAgent.Synchronize(); } else { } } catch (Exception ex) { } // Do the merge subscription synchronisation independantly of the // transactional subscription replication. try { // Set up the subscription details for the merge subscription (bi-directional data) mergePullSubscription = new MergePullSubscription(subscriptionDbName, publisherName, publicationDbName, mergePublicationName, subscriberConnection); // If the pull subscription and the job exists, start the agent job. if (mergePullSubscription.LoadProperties() && mergePullSubscription.AgentJobId != null) { MergeSynchronizationAgent mergeSyncAgent = mergePullSubscription.SynchronizationAgent; mergeSyncAgent.DistributorPassword = "<<password>>"; mergeSyncAgent.PublisherPassword = "<<password>>"; mergeSyncAgent.Synchronize(); }etc etc..
Any help or suggestions will be greatly appeciated. Thanks.
We have a need to have separate password policies for different groups of logins. For example: Those IDs that have greater privileges should be rquired to have more complex passwords that expire more frequently than IDs with lesser privileges.
It appears to me that SQL Server pulls the password policy from the default Active Directory domain group. Is there a way to create/utilize multiple policies for SQL Server authenticated IDs?
Thanks for your assistance.
I have a package protected by a password - I am already unhappy that to get it to use the configuration file to change connection strings for the production servers I have had to hardcode the password into the config file - very insecure!
However, the package now deploys correctly to the production server and will run from there OK, but NOT if scheduled as a SQL Server Agent Job. Thus is because however often I edit the command line to include the password after the DECRYPT switch (which it has prompted me for when I click on the command line tab), the Job Step will not retain it.
If I open it up after I have edited it and closed it, the password has disappeared.
I know that if I run dtexec plus the code in the Command Line tab (with the password), the package runs OK.
This is driving me insane!
I have read all the other posts and so I tried replacing the SSIS package step with a CmdExec step and pasting that code into there - then I get an OLEDB error..
The code I use is:
DTEXEC /SQL "ImportRateMonitoringTables" /SERVER servername /DECRYPT password /CONFIGFILE "D:Microsoft SQL ServerSSISDeploymentsRateMonitoringImportTasksDeploymentImportRateMonitoringTables_Production.dtsConfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
and I get
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8000FFFF
although the same code executes perfectly from a command prompt.
Please does anyone have any experience with a similar problem and if so, how did you get round it?
Thank you
When installing SQL Server 2005 Express and using an .ini file that looks like this,
SECURITYMODE=SQL
ADDLOCAL=ALL
SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
INSTANCENAME=DBSERVER
SAPWD=Westtech#1
sometimes the sa password is set correctly, while other times it is not. There does not appear to be any particular environment or system setting when it fails vs. when it works.
We are coming up on a release date and this is causing us a serious problem. Can anyone help?
Thank you,
Kathy Mook
Westbrook Technologies, Inc.
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.
Thanks,
Amilcar
Hi there ,1. i have a database and i want to encrypt my passwords before storing my records in a database plus i will later on would require to authenticate my user so again i have to encrypt the string provided by him to compare it with my encrypted password in database below is my code , i dont know how to do it , plz help 2. one thing more i am storing IP addresses of my users as a "varchar" is there a better method to do it , if yes plz help me try { SqlConnection myConnection = new SqlConnection(); myConnection.ConnectionString = ConfigurationManager.ConnectionStrings["projectConnectionString"].ConnectionString; SqlDataAdapter myAdapter = new SqlDataAdapter("SELECT *From User_Info", myConnection); SqlCommandBuilder builder = new SqlCommandBuilder(myAdapter); DataSet myDataset = new DataSet(); myAdapter.Fill(myDataset, "User_Info"); //Adding New Row in User_Info Table DataRow myRow = myDataset.Tables["User_Info"].NewRow(); myRow["user_name"] = this.user_name.Text; myRow["password"] = this.password.Text; // shoule be encrypted //not known till now how to do it myRow["name"] = this.name.Text; myRow["ip_address"] = this.ip_address.Text; myDataset.Tables["User_Info"].Rows.Add(myRow); myAdapter.Update(myDataset, "User_Info"); myConnection.Close(); myConnection.Dispose(); } catch (Exception ex) { this.error.Text = "Error ocurred in Creating User : " + ex.Message; }
View 3 Replies View RelatedAll:
I am attempting to install SQL Server 2005 Enterprise Edition. The install stalls permanently, the SQL Server's memeory usage and CPU usage plummets to nothing and the SQL Server 2005 Setup Dialogue's status stops at "Validating Database Password." This occurs on the SQL Server Database Services portion of the install. The last line in the SQL Server Setup.log says "<Func Name = 'SAPaswwordPolicyCheck'>
I have verified that the sa password that I am entering when prompted for it in the install setup is valid with respect to SQL Server and Windows Server 2003 SP 1 (13 chars, at least one symbol, at least one upper and at least one lower). What else could be causing this problem? Any ideas or stabs would be greatly appreciated.
Thanks,
NubbyDBA
Just like with Access DB, can we set password for database in SQL Server 2005 Express ?
Reason to do so is, user with Login having sysadmin previliage can acess all databases in SQL server.
so just want to restrict database access to only those users who knows the password.
Is there any possible solution ? Pls comment.
Thanks.
All --
Please help.
I have some questions about connection strings.
BACKGROUND...
Note that I am using the "SQL Native Client OLE DB Provider", SQL Sever 2005 Express, ASP.NET, C#.NET, and VS.NET 2005.
Note that I do not want to use the "Attach a database file" type of connection string.
Note that I am using the site http://www.ConnectionStrings.com as a reference.
Note that this "Standard security" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Uid=MyDatabaseUser;Pwd=MyDatabasePassword;" />...does not work and causes the following run-time error...A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
Note that this "Trusted connection" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Trusted_Connection=yes;" />...works but is less-than ideal because it uses a Trusted Connection rather than a Username/Password combination.
QUESTIONS...
(A) What exactly does the error in Item 4 mean?
(B) Do 4 and 5 imply that one must use a Trusted_Connection for all SQL Server 2005 Express connection strings when the database does not reside in the web application's App_Data folder or use a "Attach a database file" type of connection string?
(C) Are there any alternatives?
(D) What do you suggest?
Please advise.
Thank you.
-- Mark Kamoski
Hi,
I am using SQL Server 2005 at home.
My problem is I forgot my password to log in to my server.
I only remember user name is 'sa'.
I haven't used it for two to three months. So I forgot password.
Previously, When I used sql server 2000, my login is as windows login. so no problem.
But this time, I set seperate log in and I got this problem.
Any help will be appreciated.
Thanks
George
I have an internal Project Management and Scheduling app that I wrote internally for my company. It was written to use MySQL running on a Debian server, but I am going to move it to SQL Server 2000 and integrate it with our Accounting software. The part I am having trouble with is the user login portion. I previously used this:
PHP Code:
$sql = "SELECT * FROM users WHERE username = "$username" AND user_password = password("$password")";
Apparently the password() function is not available when accessing SQL Server via ODBC. Is there an equivalent function I could use isntead so the passwords arent plaintext in the database? I only have 15 people using the system so a blank pwd reset wouldn't be too much trouble.