We have renamed the 'sa' account on a SQL Server 2005 machine. When
we run
SELECT * FROM syslogins
it appears that 'sa' no longer exists as a valid SQL login. However,
when we look at running processes through sp_who, we see that 'sa' is
still being used in various background operations, even when we shut
down and restart the SQL Server. Can someone explain this?
Bill E.
Hollywood, FL
Had to migrate to new hardware running Server 2003, sql 2005. Databases, logins, two SSIS(DTS) packages working great. But, System and User maintenance plans failing since name change.
So, recreated them, and (with minor problem to be addressed at another time) the recreations are working fine. But, I can't delete (or modify) the old plans or jobs. Get the following error when physically sitting in front of the server logging in "Exception has been thrown by the target of an invocation(mscorlib). An error has occurred while establishing a connection to the server. When connecting to sql server 2005, this failure may be cause by the fact that under the default settings, sql server does not allow remote connecitons. (provider: tcp provider, error: 0 no such host is know) error 11001
As I said, I've disabled both jobs, but would prefer to delete the plan/jobs. But, it won't let me. Any ideas?
During install of SQL Server 2005, we can of course use a domain account or the built-in system account for running the services. I lean toward domain for obvious reaons but would like to know a +/- to each option and why I'd choose one over the other and what consequences or limitations one may encounter if I choose one over the other.
View 6 Replies View RelatedHi Guys
I have sort of a weird problem; we havea sql server 2000 box which was virtualized using VMWare, the virtual server was then renamed and used as another sql server.
there is a simple .net framework 3.5 console application (running on the same sql server box) that reads and deletes data from that sql server, this console application opens 2 connections simultaneously, for some reason after creating the VM and renaming the server this app didn't work, the problem is that when there was one connection open the second connection command always times out though the command only deletes one record from the DB.
After several trials I found that if I ran this app from another server it works without problems and to get it working on the same box as the sql server I have to use the ip address instead of the server name in the connection string.
I had another problem related to editing the sql agent jobs on the renamed server but I found a solution for this one in KB article.
Any ideas?
Hi
I have created a database using the following create database instruction
Create Database SoftwareChange
ON (NAME = 'SoftwareChange',
FILENAME = 'C:DevelopmentSoftwareChangeDatabaseSoftwareChange.mdf',
size = 10mb,
filegrowth = 2mb)
log on (NAME = 'SoftwareChangeLog',
FILENAME = 'C:DevelopmentSoftwareChangeDatabaseSoftwareChangeLog.ldf',
size = 2mb,
filegrowth = 1mb)
go
This shows up fine in Managment Studio, I then connect to the database from VB.net Express and it connects to the database using the following connection string :
Data Source=.SQLEXPRESS;AttachDbFilename=C:DevelopmentSoftwareChangeDatabaseSoftwareChange.mdf;Initial Catalog=C:DevelopmentSoftwareChangeDatabase;Integrated Security=True;Connect Timeout=30;User Instance=False
I don't want it to be a user instance as and without the path in AttachDBfilename it doesn't see the database.
Here's the problem when I go back into Management Studio and click on the SoftwareChange entry under databases it gives me a file not found error then subsequently doesn't let me open it. However another database entry has appeared "C:DevelopmentSoftwareChangeDatabase", this is the path of the database and displays the contents of SoftwareChange. I can detach and re-attach as SoftwareChange but why does VB.net (i assume) change the name of Db in SQL.
Regards
Ian
I recently changed the name of my pc to MYNEWPC ...but in SQL Server 2005 Security/Logins there are a couple of logins pointing to the old name...would i need to add these, change these or do something to make it point to the new pc name?
Here is what I see that needs to be changed from MYOLDPC to MYNEWPC, how do i go about doing this..is this needed?
MYOLDPCSQLServer2005SQLAgentUser$MYOLDPC$MSSQLSERVER
MYOLDPCSQLServer2005MSSQLUser$MYOLDPC$MSSQLSERVER
MYOLDPCSQLServer2005MSFTEUser$MYOLDPC$MSSQLSERVER
Our network people changed our machine name one character without our permission, they say their naming standards can't handle an "underscore" we put in our name...now the SQL Server won't run because it doesn't recognize the name of the machine.
Is there a way of bypassing or telling SQL server that we changed the name without having to reload all of our information?
I have read that if I change "computer name" and then try to startup sql server it will recognize the changes automatically BUT you need to execute sp_dropserver and sp_addserver procedures too in order to set all thing right.But yesterday I tried it on a Personal edition on xp and after reboot sql server came up without any problem and I could connec it without executing sp_dropserver and sp_addserver! Was it a specific situation or no need to those SPs at all?
View 10 Replies View RelatedHere's the scenario -
We had issues with our production database which had 'broker enabled', I restored an older backup and then renamed the Prod database to ProdOld and the Backup database to Prod. We noticed yesterday that the broker service wasn't working and had the error
'The SQL Server Service Broker for the current database is not enabled, and as a result query notifications are not supported. Please enable the Service Broker for this database if you wish to use notifications.
'
I ran the following script against the database
ALTER DATABASE prod SET ENABLE_BROKER
go
GRANT CREATE PROCEDURE to User
GRANT CREATE QUEUE to User
GRANT CREATE SERVICE to User
GRANT REFERENCES on CONTRACT::[http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification] to User
GRANT VIEW DEFINITION to User
And it came back with a message that the broker was already enabled.
I did a disable/enable just for kicks, but we still get the same error message.
I did a check on the sys.databases table and it shows that the 'is_broker_enabled' field set = 0 (should be one)
Any ideas on what's going on here? Could the rename caused the broker to become out of sync?
It would be great if I could just update the bit field, but I don't believe there is an easy way of updatting the system tables.
Thanks in advance
Ran a trace using profiler and found that the CLR is not using the ASPNET windows account to log into SQL 2005, instead using the admin. Some ado.net code does not work properly as a result. Have had to change the connection string to use SQL logins.Spec: Win XP Pro; IIS 5; 2.0.Is this normal? Where security and permissions are concerned, what changes, if any, are there from SQL 2000?
View 5 Replies View RelatedI had a cluster running on 3 nodes (windows failover cluster) with server 2012 and SQL server 2012 running in the cluster. Well, I thought I'd just go ahead and rename all 3 of the hosts with new hostnames and it apparently broke the cluster pretty bad. Now when I open failover cluster manager I cannot see anything nor can I connect to the cluster object in AD. I re-named all of the hosts back to their original names but that didn't work.
View 5 Replies View RelatedI am using SQL 2012 SE and implementing transactional replication. I need to insert the rows from publisher database tables to new tables, drop the old tables and rename the new tables with the old table names.
For example:
Publisher database tables that are being replicated:
Table1
Table2
Table3
and I am going to create new tables in publisher database
Table1_new
Table2_new
Table3_new
Move data from
Table1--->Table1_new
Table2--->Table2_new
Table3--->Table3_new
Drop constraints from and then tables (does this require articles to be removed from replication?)
Table1
Table2
Table3
Rename
Table1_new to Table1
Table2_new to Table2
Table3_new to Table3
Does this require replication to set up from scratch or add the three articles only to replication? Is there a way this can be done without pausing or reinitializing replication or without removing articles and adding them back?
I have been running a script in SQL Server 2000 as sa also as a Active Directory user who has administrator rights (I tested both approaches SQL Server then Windows Authentication) in Query Analyser which grants execute rights to the stored procedures within the database instance and Query Analyser does not give any errors when I run the script. I have made sure that each transaction has a go after it. I then return to Enterprise Manager, check the rights (I apply them to roles so that when we create another SQL Server user we just grant him/her rights to the role) and discover that the role has not been granted the rights. I seems to be occurring only with 2 of the procedures. Is there a known bug that might be causing this?
yours sincerely
Craig Hoy
hi ,
i have a problem :)
my sql server 2005 is instaled on windows xp machine ( i have only remote connection on this computer ) , i made mistake and delete my account on sqlserver it was a admin account , the problem now is i cant log on sqlserver enymore becuse sa account is disabled.
What cann i do now ?
I recenly installed SP1 on 2 servers.
For some strange reason I am unable to run the SQL service or the SQL Agent service using the normal SQL service domain account. It has always worked and is currently running on the other server without a problem.
Has anyone had a similar problem?
can anyone give me step by step instructions as to how I would go about correctly granting the aspnet account access to my sql server 2005 database ??
As far as I can see Ive set it up, but im getting execute permissions errors on stored procedures even though Ive gone into properties and permissions and added the aspnet account with execute permissions.
I have several DTS jobs that runs well as a job with my nt login account for the SQL agent service startup account, but if I use the System account
they fail with this error.
" Error opening datafile: Access is denied. Error source: Microsoft Data Transformation Services Flat File Rowset Provider"
The data has change access to the System account under the NT security.
Thank you in advanced.
Jorge
Hi all, i hope you can help me.
Basically a dts package has been setup that pulls in data from another companies server, this data requires to be on-demand i.e individual users can pull in updates of the data when they require it.
I am using xp_cmdshell and dtsrun to pull in the data. This obviouly works fine for me as i am a member of sysadmin.
Books online quotes " SQL Server Agent proxy accounts allow SQL Server users who do not belong to the sysadmin fixed server role to execute xp_cmdshell"
So i went to the SQL Server Agent Properties 'Job System' tab and unchecked 'Non-sysadmin job step proxy account' and entered a proxy account.
The proxy account has been setup as a Windows user with local administrator privilages and even a member of the sysadmin server role - just in case.
Now when i log onto the db with my test account - a non-sysadmin - and attempt to run the stored proc to import the data i recieved the message 'EXECUTE permission denied on object 'xp_cmdshell', database 'master', owner 'dbo' '
hmm... so basically i have either misunderstood BoL or there is something not quite right in my setup.
I have search the net for a few days now and yet i can find no solution.
Can anyone help?
We have a N+1 SQL 2005 x65 SP2 + 3159 cluster which was running fine until the service account which runs Windows cluster and the SQL services was removed as a login from SQL. This was a new setup so the only SQL accounts are (SA) as SA, Windows Domain GROUP's which one group is configured as SA and the cluster account is added to this group. I cannot start SQL service on the cluster now. I've tried logging into one node as the service account which is member of a AD group which has SA rights to SQL as well as my personal account. If anyone knows a way ot fix this without reinstalling I'd appreciate your help.
View 8 Replies View Related
Bummer. I can't remember the SA password. I had setup a user account, but I can't change anything or add any new accounts using this login. I can't get in using the windows authentication method no matter how I am logged into this machine.
Any suggestions? I have never been able to use Windows Authentication. There must be something I'm missing here. I have spent hours and hours trying to get into this machine. I just want to replicate a database. This is very frustrating.
Thanks guys.
I'm trying to do an unattended install of SQL Express 2005 SP2, and specify that the service runs under the Local Service account. Prior versions of SQL Express worked fine.
With SQL Express 2005 SP2, however, the install fails on XP Pro SP2. It *does* work on Winows 2003 Server.
Here's the command line I'm using:
SQLEXPR.EXE /QB ADDLOCAL=ALL INSTANCENAME=FOO SECURITYMODE=SQL SAPWD=BAR SQLACCOUNT="NT AUTHORITYLOCAL SERVICE"
It fails at the end of the install, saying it can't start the service. If I use "NETWORK SERVICE", it works fine, but that's more privileges than I want the service to have. Is there something else on the command line that I can try to get it to work?
Is this even supported?
-Dave
Who needs to invoke the jobs in SQL05? Manually executing the job import_myteam as a user with dbo privileges fails. So, which user account should be assigned to successfully run scheduled jobs (ie, dbo)?
The package file for the job in question is located in the server€™s C:Documents and SettingsuserxyzMy DocumentsVisual Studio 2005ProjectsIntegration Services Project3Integration Services Project3MyTeam (1).dtsx, but this still fails when the user userxyz is logged on and is executing the job directly from the server console.
Step1 of the package executes as userxyz
Step 2 fails and runs as cpmc-casql02
The user account userxyz has administrator rights to the server as well as being a sysadmin of the SQL2005 database (named cpcasql02).
The account cpmc-casql02 is a €œpublic€? user of the database and is a member of the administrator group on the server itself.
This same scenario carries for tasks as simple as truncating a table and importing the contents of another table in the same database.
All of these jobs exhibit the same behavior whether run directly from the server console on remotely from a workstation connected to the SQL2005 database.
Attempting to get a really simple job working, we also created a very simple SSIS package which does a select from a database table and writes the output to a text file. When running the same package from the user€™s workstation within Visual Studio, the package executes successfully. Once copied to the server, and run from within SQLServer as MyJunePackage however, the execution fails in the same manner as described above. The first step executes successfully as the logged-in user and the second fails executed under the account cpmc-casql02.
So, again we have the same behavior of sequential steps being run as different users with unsatisfactory results. Please advise as to how to set up these jobs to run correctly and consistently.
Thanks very much,Eric W
I want to know if I can debug stored procedures remotely with the SA account.
I can not have Active Directory in my system right now.
Thanks
How would Set permissions Sql Server 2005 so that I can access a asp page created in VWD and Sql Express.
On the production server i have just the one instance of Sql
I have the following connection string in the web config file:
<connectionStrings>
<add name="ConnectionString" connectionString="server=serversNameXPRESS;uid=aspuser;pwd=aspuserPassworkd;database=DATABName" />
</connectionStrings>
The account i setup to access the db in Sql 2005 Proper on the Production serve is Represented by the name in the above example as “aspuser�. I created this user in security, logins. And I gave permissions to this on the Db level “create procedure delete, select, update insert.�
I get a error when i run the page in the browser that says “login failed for aspuser.�
I know virtual directory is configured properly. I can run aspx page in the directory with out a db connection, without and error.
Any help would be greatly appreciated.
Hi all,
I have a problem while i create a proxy account in SQL Sever 2005.The situation is like this...There is a user who has an login in to the server.He has a stored procedure which calls some on the SSIS packages and XP_cmdshell...so this stored procedure basically load some data in to the tables .So for the login in order to execute the stored procedure as he is not a Sys admin I have created a proxy account in my account as Iam an SA and then in the proxies and in principals I selected his login name and this way I have created a credential and a proxy account.
Now the problem is if he logins with his id and password and try to execute the stored procedure it gives an error message
Server: Msg 15153, Level 16, State 1, Procedure xp_cmdshell, Line 1
The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '##xp_cmdshell_proxy_account##' credential exists and contains valid information.
....so this mean the login is not able to see the proxy account.So what I did is I created a job and then in the job owner tab I have selected his login and then created a step with the type operating system (CmdExec) as I need to just execute the stored procedure and used the proxy account that I have created.
so I gave the command -- exec <stored procedure> --.
But this job fails and gives the error message as
[298] SQLServer Error: 536, Invalid length parameter passed to the SUBSTRING function. [SQLSTATE 42000]....
So now ....first My question is am I doing in a right way....if its right then why Iam not able to execute the stored procedure.
If there is any other way through which I can execute the stored procedure using a proxy account for the logins who are not sys admins....please do let me know.....
Thanks
Raja.V
Hi all,
I am running a named instance of SQL Server 2005 Enterprise Edition, side by side with named instance of SQL Server 2000 in Windows Server 2003. When I start the installation. I am unable to proceed from authentication stage.
The error description for Database Services and Reporting Services under both sa and windows authentication mode is: Encryption not supported on client Sqlcmd error: Microsoft SQL Native client: Client Unable to establish connection
In Service Manager, all SQL Server 2005 services are running with Logon as Administrator, and I am also able to connect to SSAS, SSRS, SSIS via Management studio both via Windows authentication and sa account information.
Would you please inform if I have to change any security settings before SP2 installation here.
How to add myself a Sql Server Administrator. The link in Surface Area Configuration to Add new Administrator doesn't work.
Hi all,
I've recently installed SQL-Server 2005 on our production server (win server r2, .net framework 2.0, 3.0 etc ..).
In order to improve the security mechanism I'm allowing only windows authentication (not mixed mode).
If each site and the sql-process is given a specific user account, could it have some bad performance issues ?
Security-wise, which is better ?
Few things to point out:
1. The SQL process was assigned with a local user account (i.e : [machine name]SqlServerUser) and not using NT AUTHORITYNETWORK_SERVICE.
2. Every ASP.Net site on the server assigned with a local account (i.e : [machine name]SomeSiteUser) through the IIS's Directory Security tab and not using IUSR_[machine name].
3. Each "Site User" has the appropriate database authorization in sql.
Any given help will be appreciated, thanks.
Hi there,BOL notes that in order for replication agents to run properly, theSQLServerAgent must run as a domain account which has privledges to loginto the other machines involved in replication (under "SecurityConsiderations" and elsewhere). This makes sense; however, I waswondering if there were any repercussions to using duplicate localaccounts to establish replication where a domain was not available.Anotherwords, create a local windows account "johndoe" on both machines(with the same password), grant that account access to SQL Server onboth machines, and then have SQL Server Agent run as "johndoe" on bothmachines. I do not feel this is an ideal solution but I havecircumstances under which I may not have a domain available; mypreliminary tests seem to work.Also, are there any similar considerations regarding the MSSQLSERVERservice, or can I always leave that as local system?Dave
View 1 Replies View RelatedHi,
I would like to know is it possible to installing sql 2005 express edition on windows xp with limited account. I tried to install it. After installing, the service can not start. Is there any thing that I misconfigured?
Thanks for reading and answering my post.
Greetings,
I receive an error message in event log when i try to connect to the Database Server using ODBC on a client machine. The database server is running on Windows 2003 Server Standard Edition and the client machine is Windows XP Professional. Following is the error message from the event log:
2147467259 - [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa' because the account is currently locked out. The system administrator can unlock it.
What causes the error to occur and how to resolve it?Appreciate for your assistence.
Thanks and regards,
Viknes
I am installing SQL Server 2005 on a server (Windows Server Enterprise Edition 2003 SP2) that is not domain controller and on the screen "Service Account" I checked the box "Customize for each service account" and typed a domain account (it has permission to "logon as a service"), its password and domain, and when I click the "Next" button, I am getting the error below:"SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account. "
View 11 Replies View RelatedHi,
I have a least privileged SQL Login €œClient€? and have granted execute rights on XP_Cmdshell SP at master db. When I execute master.. XP_Cmdshell €˜dir€™ I€™m getting the below error.
Msg 15153, Level 16, State 1, Procedure xp_cmdshell, Line 1
The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '##xp_cmdshell_proxy_account##' credential exists and contains valid information.
Please note it is SQL Login account and not windows account. I have checked everywhere for similar problem and no luck.
Thanks for you help in advance
With regards
GK
Hi all,
I have a SQL Server 2005 Express edition instance set up on one server, and IIS on another server.
The SQL Server process account is a domain user account, which I have added to the local groups that SQL Server created during installation (I originally used a local user account instead of domain account; however, the problem occurs with both).
SQL Server runs fine, and if I set my IIS application pool identity to a domain admin, my web app can access the database and retrieve the data necessary.
However, I have a domain user account that I want to use to run the app pool and retrieve the data. The domain user account is added to the IIS_WPG group on the web server. On the database server, I have created a login for the account, as well as added it to the db_datareader role of the database that is used for the site.
However, the user is not able to connect to the SQL Server. I get the "Login failed for user <user account>" error in ASP.NET. I also tried connecting with SQL Server Management Studio, and I get the same error. I checked and the user has connect permission to the database server.
With admin accounts, there are no problems logging in, etc.
Any pointers are appreciated,
Thanks,
SA.
Edit: I was able to find out that the State is 11 for the error. According to http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx, this indicates "Valid login but server access failure." I am not sure how to resolve this.