May 8, 2010 at 11:49 pm
Hi all,
I deleted the builtin administrator from sql server.
When i tried to access msdb dtsx packages, I was prompt the error.
Login failed for user '<Servername>\Administrator'. (Microsoft SQL Native Client)
When the builtin adminstrators account does exists, there is no problem to access packages in MSDB,
please advice.
THanks
May 9, 2010 at 11:11 am
What account is running SQL Server?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 9, 2010 at 6:34 pm
Hi,
You mean SSIS account or sql server?
SSIS-Network Server
SQL -Local System
What can we do on SSIS if we still need to retain Local System as a startup account for SQL Server.
Thanks for the advance.
May 9, 2010 at 6:34 pm
Hi,
You mean SSIS account or sql server?
SSIS-Network Service
SQL -Local System
What can we do on SSIS if we still need to retain Local System as a startup account for SQL Server.
Thanks for the advance.
May 9, 2010 at 9:39 pm
How are the SSIS packages configured to run? Are they setup to use windows authentication?
If so, does the network account have a separate login to SQL Server with the appropriate permissions to run the packages? Most likely SSIS was using the BUILTIN\Administrator permissions to access the system - try adding it separately.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 10, 2010 at 12:34 am
Hi,
There is no sql server authentication available for me to connect to SSIS
That means I am not able to remotely connect to the SSIS through Management Studio.
If so, does the network account have a separate login to SQL Server with the appropriate permissions to run the packages? Most likely SSIS was using the BUILTIN\Administrator permissions to access the system - try adding it separately.
Can you clarify on the statement above.
Appreciate your advice.
May 10, 2010 at 6:47 pm
Hi, can anybody help me on this issue? thanks.
May 10, 2010 at 9:02 pm
Okay, each login to SQL Server has to be defined. Windows logins can be added individually or through group membership. When you run SSIS packages from SQL Server Agent - the account used to login to SQL Server is going to be the same account that is running SQL Server Agent.
The connections in the SSIS package are going to use the login information defined for each connection. If the connection is defined as windows authentication - then it is going to use the same credentials as the SQL Server Agent.
One of those is trying to use the system administrator account to login to SQL Server. That account does not have a login to SQL Server and uses the BUILTIN\Administrators group to access the system. When you removed the group, the package cannot login and fails with the message you are seeing.
You need to validate the connection information in the packages - and validate the users that each service is running under. If those users are not a part of one of the groups added to SQL Server - or is using the system adminstrator account to login, then it needs to be changed.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply