SQL Server 2005 SP2, Service Password Gets Forgotten
Mar 8, 2007
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
View 5 Replies
ADVERTISEMENT
Jul 24, 2015
I have connected to Database using my credentials by checking remember password option. After few days I forgot my password. How can I recover the password as SQL remember it. Is there any way to recover my password instead of resetting it.
View 3 Replies
View Related
Jul 31, 2000
A user forgot her password, how do I reset her password? sp_password
require a former password to change, and I'm unable to do that since
she forgot her's
thanks!
View 3 Replies
View Related
Jun 18, 2007
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?
View 5 Replies
View Related
Mar 11, 2008
Ok, here is my situation:
I have a table-valued function that, when moved from SQL2000 to SQL2005, is having some performance issues. I have found an appropriate index that fixes the performance issues on a table queried within the function.
For the first day, everything was running wonderfully. Then, I get in the next morning and have a message from a developer saying that performance is bad again. I double check and sure enough, the function is timing out. As a quick test, I dropped and recreated the index and performance was back to normal (~1 sec). The following day, the same thing happened; the execution plan was completely skipping the index I had created. So, I checked any column statistics that may be getting updated that would cause issues and there were none that had been updated for about a week. I tried issuing the DBCC dropcleanbuffers and DBCC freeproccache commands and still, the engine would not recognize the index as the most efficient plan. Also, I have recreated this problem in a test database, so there is no nightly processing (or anyone at all for that matter) hitting the database.
The only thing, to date, that I have found that works is dropping and recreating the index. This is obviously not an acceptable solution. I was curious if anyone here had ever come across this before and if so, what did you do to fix the issue?
Thank you very much in advance!
View 7 Replies
View Related
Jan 22, 2002
Folks,
MSSQLServer and SQL Server Agent services under NT are running under a system account under our domain (setup many moons ago) for which we have lost the passsword. Is there any way we can recover these passwords?
Thanks.
Sam
View 1 Replies
View Related
Mar 12, 2007
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 Related
Dec 14, 2005
How do you change the SA password in SQL Server 2005?
Thanks.
Doug
View 1 Replies
View Related
Jan 29, 2007
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.
View 5 Replies
View Related
Apr 17, 2007
12 months since last use!
Is there any way to open server without re-installing to reset password.
View 1 Replies
View Related
Nov 11, 2007
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
View 5 Replies
View Related
Jul 6, 2000
We have changed NT Administration Password. Now how to reassign the new password setting for sql server service account. As right now all schedule jobs are getting failed & needs to be executed manually.
Thanks in Advance
Manoj
View 1 Replies
View Related
Dec 3, 1999
Ugh! Someone changed the password of our SQL Server service account. It is called syssql, and it is used by the MSSQLServer and SQL Executive services to log in at startup. After the password was changed, we noticed that replication wasn’t running, and since I know that replication uses the Executive service, I restarted that service using the new password. That worked to get replication working again, and since the boxes were production machines I didn’t restart the MSSQLServer service with the new password yet. Now, our syssql account keeps on locking up every so often, and scheduled tasks that use xp_sendmail stopped working, and alerts stopped sending. Is this happening because of the MSSQLServer service still being logged in with the old password? I suspect that the SQL Mail logs in through the MSSQLServer service, which is still using the old password, and the login failures are causing the syssql account to lock. Any other ideas???
Cindy Rutherfurd
cindy.rutherfurd@zcsterling.com
View 2 Replies
View Related
Apr 16, 2008
We are running SQL Server 2000 on two servers and when they were built, the same domain account was used for all installations, and the MSSQLSERVER and SQLServerAgent services run logged in as that same account. That account is also the dbo of all the SQL databases. We now need to change the password and possibly disable that domain account.
What do we need to do to make sure the SQL Servers and databases continue to run without problems after making the password change and/or disabling the account?
I appreciate any advice!
View 6 Replies
View Related
Aug 22, 2006
Wjen sql 2005 is installed a Service Master key is generated using the password of the account under which sql 2005 server runs.
Suppose I use a domain account to run sql server. The account password will change every so often. I presume this change will not impact the validity of the existing Service master key and therefore any data indirectly encrypted by it. Am I correct?
Barkingdog
View 1 Replies
View Related
May 25, 2007
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
View 1 Replies
View Related
Jun 12, 2007
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.
View 1 Replies
View Related
Sep 24, 1999
Hopefully, someone has a clue about this. We recently upgraded from SQL 6.5 to 7.0. Everything was fine until we changed the administrator
password for our NT domain, which has about 26 servers on it. We also changed the local NT domain on the SQL server machine to match the
network NT domain password. This seemed to work until a reboot a couple of days later. No we get a "failure to start do to logon failuer" message.
Anyone experienced this problem?
View 1 Replies
View Related
Jul 20, 2005
Hello,I hope you guys can help me with a problem that I am facing...I have started the MSSqlServer service and SQLServerAgent serviceswith a domain username and password.There are periodic password resets to this user. Security policieswithin the company dictate that the password for this domain accountcannot be permenant.Would there be any way to automatically reset the pwd in theseservices instead of manually changing them each time?Thanks
View 1 Replies
View Related
Oct 10, 2007
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;
}
View 3 Replies
View Related
Jun 20, 2006
Is there a way to do this at the server level?
Thanks
View 4 Replies
View Related
Sep 26, 2006
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
View 5 Replies
View Related
Oct 20, 2006
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
View 5 Replies
View Related
Mar 18, 2008
Hi,
I understand from previous threads that installing SQL Server 2005 Service Pack 2 on the desktop client can speed up the response rate of the Visual Studio 2005 Business Intelligence Tools.
However after logging on as an administrator and installing Service Pack 2, Service Pack 2 returned no errors. However after launching Visual Studio and clicking on the about dialog box the version reported was still €œRTM.050727-4200€? where I was expecting to see €œSP.050727-7600€?.
I understood that I applied the same service pack to my copy of SQL Server on my laptop and the upgrade worked successfully.
Can anyone help?
Thanks in advance,
Kieran.
View 9 Replies
View Related
Jan 14, 2007
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
View 4 Replies
View Related
Oct 30, 2007
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?
View 6 Replies
View Related
Mar 21, 2007
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.
View 6 Replies
View Related
Jan 13, 2006
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
View 3 Replies
View Related
Dec 5, 2006
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
View 4 Replies
View Related
Jan 10, 2007
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.
View 8 Replies
View Related
Sep 12, 2006
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.
View 4 Replies
View Related
Apr 1, 2008
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
View 9 Replies
View Related
Mar 21, 2007
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.
View 1 Replies
View Related
