Unable To Restart MSSQL Server After Changing My NT Password
Nov 22, 2000
I have recently changed my NT password and since then one of my machines has not been able to start MSSQL server. When I re-boot the machine it lets me know that it was unable to start MSSQL server. If I right click on the SQL server group in EM and try to manually start the service, it tells me that I have a login failure. I don't understand how changing my NT password would affect one machine and not the others. When I right click on the "edit SQL service registration properties" tab, all of the machines are using the NT password selection as opposed to the SQL server authentication password. Any ideas would be greatly appreciated
I have SQL Server 2000 the Microsoft SQL Enterprise Mangaer version 8.0 and I don't know the password of sa account and I found this page where it shows how to change it and I tried it but it didnt work for me. Password didnt change So what to do? Is there any way to see the current pw?
We have been having a problem with on of our servers, applications connecting to it are experiencing poor performance, even though the server is only running at a peak of 50%.
The odd thing is that after a sql service restart we couldnt connect at all on the SQL port. We were only able to re-connect after rebooting the actuall box. Is there anything that can be done about this? Its strting to look like a network related problem instead of SQL
I'm having trouble with restoring the master db on w2k3 sql2000 sp3a to a Secondary Standby server. Firstly, I place the server in Single user mode and then restore the master db. The sql server then tries to restart sql services but immediately stops as soon as it starts up.
i have a few ssis packages which are scheduled as sql server agent jobs. now after a reboot of the server all the packages jobs don't work anymore. i had to reenter all the passwords for the connection manager in order to make them run again. ist there a way to store the passwords so that the keep available even after a reboot? because it's necessary to restart the server for maintenance resasons.
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"); }
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; }
I have a problem that has happened a couple of times now. I'm in the process of testing our 2005 deployment - Standard edition on 2003 x64 servers for principal and mirror and 2005 express witness. All are pre SP1. Two databases are being mirrored.
I have successfully set up mirroring which seems to work fine - but when I restart the MSSQL service on the principal, spurious things happen:
The server that *was* the principal before restart
database A is in (Mirror, Disconnected / In Recovery) state database B is in (In Recovery)
The server that *was* the mirror:
database A is in (Principal, Disconnected) database B is in (Principal, Disconnected)
I can connect to both servers via Studio Manager and when I try to go to the current principal database to stop mirroring, the Studio Manager hangs and becomes non-responsive.
I deployed a package on mssql-server. How can I save passwords for OLEDB connections of the package? I want to launch the package from server agent according to the schedule, but I don't know how can I save passwords for connectons?
I installed Sqlexpress server 2005 and am able to connect to the server using the sqlexpress manager.
The connection parameters are:
server: 127.0.0.1 (This is an alias name pointing to TMD03SQLEXPRESS) username:sa password:test mode: sql server and windows authentication mode TCP/IP : enabled and listening on port number 1433.
But I am not able to connect to the server using PHP's mssql_connect function.
but none of them works. I also tried OSQL and SQLCMD and they don't work either. They give me the following error message.
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQL Native Client]Login timeout expired [SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Can anyone please let me know what am doing wrong here?
I think my description says it all. I have just installed Studio Express for the first time.
I want to attach a database. When the connect to server dialog is displayed the user name and password text box is greyed out. The Password box is blank and I need to edit this. I switch to SQL authentication they are enabled but if I switch back to Windows authentication they are both greyed out.
I have uninstalled and reinstalled but still no luck,
I`m running SQL 6.5 with standard security. We`re running NT 4.0. I am a member of the NT Admin group - which, of course, has sa privileges in SQL Server. I changed the sa password (via Enterpise Manager on my client machine); and it worked. I tested the password change by connecting to ISQL/w - both on my client machine and at the server machine.
However, when I attempted to connect to the server via Enterprise Manager (SEM) - on my client machine - my login attempt failed. But at the server machine, I connected just fine.
Somehow, even though we`re using standard security, I`m getting locked out of SEM because of the new password. Changing the sa password back to what it had been resolved the problem; but the old password was only meant to be temporary.
2.Web app: ================ a.Hard coded into .asp and .aspx b..inc files that have collective connection strings. c.Possible use of file DSNs d.Possibly use of system DSNs
3.Ad-hoc Queries by Users ===============================
4.Maintenance Plans and Jobs etc. ======================================= a. DTS packages b. Replication
Is there anything else that you can add to this list will be helpful. Regards Paresh
After I have changed the SA password and attempt to login I get the following 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.) (Microsoft SQL Server, Error:233)
If I change the password back I can login without any problems. I need to change the SA password.
When I changed the SQL sa account password (it was blank) and then tried to connect to SMS remotely via SMS Administrator Console, I get Connection Failed. It seemed to work for a about 20 minutes and then I get "Connection Failed" when I try to run the console remotely. I used the SQL Enterprise Manager to change the sa password and then I used the SMS Administrator Console to set its SQL Server account to sa with the new password under Site Properties. When I switched it to a blank password in SQL and SMS, it started working again.
From the Application Event Log I seem to be getting a lot of these messages (even now - and it's working): "The description for Event ID ( 1001 ) in Source ( SQLCTR70 ) could not be found. It contains the following insertion string(s): SQL Server not running."
I have also gotten: "The Open Procedure for service "NM" in DLL "nmperf.dll" failed. Performance data for this service will not be available. Status code returned is DWORD 0. "
I don't see any messages from SMS in Event Viewer.
Can the user change their password in Enterprise Manager? When they follow the documentation, this does not seem to work unless they are sa: (I know about sp_password....we are trying to find a GUI method for typical user.)
Expand a server group; then expand a server. Expand Security; then click Logins. In the details pane, right-click the login to modify, and then click Properties. In Password, on the General tab, enter a new password. Confirm the password.
I am using Administrator to log in the WinNT and I have just changed the password of the Administrator. After that, I discover that I cannot use all function in the sql server. Althougt the server is still running, I cannot open the database, login the security manager.
I have checked that the SQL Executive in NT service is assigned to local system account. As you know, there is no place for inputting password. Where can I change the password in order to let the function of sql server run again?
I am working with MSDE, but some how the password for sa keep changing by itself. I can reset it by logging in windows authentication mode using osql, but the next day the password does not work again. Please give me some suggestions
A client of mine changed his SA password "because it hadn't been changed in a while". :mad: Now nobody can get into Enterprise Manager - opening EM or trying to right-click > Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into Query Analyzer, which I thouhght was weird. But no luck with Enterprise Manager. It's just trying to log in as sa without prompting for a pw.
I already tried running sp_Password in Query Analyzer to change the pw back to what it was. Still can't connect to the SQL Server via Enterprise Manager.
Hi, I know this seems odd but is there any way to change the guest's password? I know this is paradoxical regarding the nature of guest user but if there is any way please clarify me! -Thanks
I just started a new job and no one seems to know the SA password.Here's my plan to change it:1. I've run a trace for a couple of days to verify that there are nojobs or processes that are connecting as SA and that would break if Ichanged the password.2. Before the changing the password I am going to bulk copy out thesysxlogins row for SA so that if things go wrong I can reinset the olddata with the old unknown password (will that work?).3. Log on to the console as Windows administrator and changing the SApassword.Does that make sense? Anyone have any other suggestions?Thanks.
that sounds obvious but I'm stuck... I have an ASP.net application which someone else started and I continue. on the SQL server there was a user X which was used to access the database from the ASP website. I accidently changed the password in the SQL server and now I cant restore the prior settings (trying to reset password to blank or embedding the username and password in the connection string didnt work). it stops on "connection.open" with - "SQLException Login failed for user 'X'" any ideas why that happens and how I can fix it?
Is there an automatic way of changing the Domain user password getting used for running the SQL Server as a Domain user account? I'm taking about EM---Security----Domain User name and the password getting used for running the SQL Server?
We are currently using continuous transactional replication from an OLTP type database to a Reporting database. We recently changed the 'sa' password for the first time since replication was introduced and now the Replication Log Reader job fails to start.
This is the error from the Job Log:
Message 2008-04-14 15:18:24.894 Copyright (c) 2005 Microsoft Corporation 2008-04-14 15:18:24.894 Microsoft SQL Server Replication Agent: logread 2008-04-14 15:18:24.894 2008-04-14 15:18:24.894 The timestamps prepended to the output lines are expressed in terms of UTC time. 2008-04-14 15:18:24.894 User-specified agent parameter values: -Publisher OASV-SQL1 -PublisherDB georgiaoas -Distributor OASV-SQL1 -DistributorSecurityMode 1 -Continuous -XJOBID 0xCE146F975BC43043AB1ECBF42F801C43 -XJOBNAME OASV-SQL1-georgiaoas-1 -XSTEPID 2 -XSUBSYSTEM LogReader -XSERVER OASV-SQL1 -XCMDLINE 0 -XCancelEventHandle 00000730 -XParentProcessHandle 0000075C 2008-04-14 15:18:25.034 Status: 0, code: 20015, text: 'Login failed for user 'sa'.'. 2008-04-14 15:18:25.034 Login failed for user 'sa'.
When we change the 'sa' password back to the previous value, we can start the Log Reader without issue.
We have tried restarting the SQL Server Agent process without success. We have not restarted the SQL Server process due to the server hosting production databases.
I have changed my windows password on my workstation, and the result is that I cannot now access the local databases and services resident on my workstation. I can still access all remote servers, but all attempts to access the local machine have failed. I even changed the password back to the original password, but this has had no effect.
Has anyone had any experience similar to this one? I am at a loss for things to try at this point.
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 tried to change / add password in SQL Server Compact Edition 2005 (in Mobile 5.0) via SQL Server Management Studio. As a result I got an error: "The specified module could not be found." I wonder why and how can I change the (blank) password to a new one?
I installed SQL Server 2005 Express Edition. When I try changing the account name, password in the SQL Server Configuration Manager, i.e. by clicking on Apply, the SQLEXPRESS restarts and the password gets replaced by a longer password. Also the user name gets prefixed with "./". Any help on this will be highly appreciated.
Another query: Do we have the query analyser (gui or command line) kind of thing in Express Edition? Also where can I get a proper documentation of doing elementary things in setting up a database, like creating a database, adding a user, etc)
I tried to cahnge this account option to built in account option in SQL ( MSSQLSERVER) properties box. Then SQL Server was log on as Local system. But then I can not view my reports which i created. Now I changed it again to this account option. but I dont exaclty remember the password. Is there anyway I can get to know the password I created.
