We have a SQL 2005 installation using SQL and Windows Authentication. We
have a login that is mapped to a active directory group and has the
appropriate permissions to the database. However, when we try to create
an ODBC connection to the server from an XP client (and the user is a
member of the appropriate domain group) we get the above mentioned error.
Also logged on the SQL server is the following error:
SSPI handshake failed with error code 0x8009030c...
The only info I can find on this error has to do with IIS
configurations, but I don't see what IIS has to do with this as we are
only trying to make an ODBC connection.Maybe your service account is Local System.
You can change to AD Service account.
"Jan Leste"?? ??? ??:
> We have a SQL 2005 installation using SQL and Windows Authentication. We
> have a login that is mapped to a active directory group and has the
> appropriate permissions to the database. However, when we try to create
> an ODBC connection to the server from an XP client (and the user is a
> member of the appropriate domain group) we get the above mentioned error.
> Also logged on the SQL server is the following error:
> SSPI handshake failed with error code 0x8009030c...
> The only info I can find on this error has to do with IIS
> configurations, but I don't see what IIS has to do with this as we are
> only trying to make an ODBC connection.
>
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Tuesday, March 27, 2012
Thursday, March 22, 2012
Error 15401: Windows NT group or group not found
I had an NT account in SQL Server named: gvv\molly...we then had to change her NT account to mring...so now 2 questions:
1. How can I tell SQL Server that gvv\molly is really gvv\mring..and have gvv\mring inherit all of molly's permissions ?
2. I deleted gvv\molly and tried re-adding gvv\mring...and it gave me my subject errror ?
What to do ?
Thank youHowdy,
Every user has a unique SUID in SQL Server - dont complicate your life -remove the original user & re-add the new user, then re-do all the security as required.
Be careful too - an NT login ( or even a SQL login ) is mapped to a unique username in each database. If your original NT username owned objects in a database, then you wont be able to remove the username from the database until all object ownerships have been transferred to sa or dbo. But this could cause problems with any application you are running, so if this is an issue, you may need to carefully work through it.
(By the way - its a big no-no to have a user owning objects - all objects in a database should be owned by dbo or sa and then you dont have a problem.)
Post back if problems.
Cheers
SG|||(By the way - its a big no-no to have a user owning objects - all objects in a database should be owned by dbo or sa and then you dont have a problem.)
I wouldnt recommend that SG !!!!
Having a single user owning all the objects (DBO) should be a big no - no . How do you take care of all the security problems then ????|||Howdy Enigma,
Part of the reasons for the questions I'm asking are to flesh out the actual problem, hence the comments about dbo & sa owning all objects.
In most situations, I would always have dbo or sa owning all objects. Good security setup in the database ( if professionally configured ) will always be secure. I dont tolerate people that leave sa blank nor should anyone else - good for a pink slip in my book.
In some cases e.g. an application during its operation or installation may create objects in the database, that would be valid case for non-dbo/sa ownership ( but still not a great state of affairs - especially if its an internet exposed app).
If there is a bonafide reason for it, I'm open to suggestion. But in most cases, not good practice.
Cheers,
SG.|||SQLguy,
you wrote: "dont complicate your life -remove the original user & re-add the new user, then re-do all the security as required."
I tried that, but it still gave me the same msg...is that because my previous NT login owned an object ?...Im pretty sure that she did not.
Also, I cannot add her new NT login on a complete new server, one that she was never configured on with old or new NT account name.
Could this have anything to do with DNS settings ?
Thank you for your feedback|||I agree with SQLGuy. users owning objects will lead to more problems than solutions. Consider if you have two users that create tables with the same name. Now there is no telling what results either user would get from queries that reference either table (unless they fully qualify the names in those queries/stored procs). Then there are all the problems around the fact that a user can now drop a table in your database. Or create 200 indexes on the table. It is too much of a potential problem.|||Howdy kohln5,
I am surprised you get the same issue with the new user.
Some suggestions as we work this out:
(1) Lets test whether you have a DNS probem - see if you can ping the domain controller by name and TCPIP address from the SQL box.
(2) If you can ping the domain controller by name, open a dos box & type: ipconfig /all and look for the WINS & DNS server entries. If you dont have any that will probably be the reason. Speak to your networking guys about that.
(3) If you can ping the domain controller & you have correct WINS & DNS entries under ipconfig /all try going to your NT security and try & add the user under NT security to the local Users group on the box. At this point if you cant do this, you have a general networking issue & will need to fix it before we can progress the problem.
Post back if probs
Cheers
SG.sql
1. How can I tell SQL Server that gvv\molly is really gvv\mring..and have gvv\mring inherit all of molly's permissions ?
2. I deleted gvv\molly and tried re-adding gvv\mring...and it gave me my subject errror ?
What to do ?
Thank youHowdy,
Every user has a unique SUID in SQL Server - dont complicate your life -remove the original user & re-add the new user, then re-do all the security as required.
Be careful too - an NT login ( or even a SQL login ) is mapped to a unique username in each database. If your original NT username owned objects in a database, then you wont be able to remove the username from the database until all object ownerships have been transferred to sa or dbo. But this could cause problems with any application you are running, so if this is an issue, you may need to carefully work through it.
(By the way - its a big no-no to have a user owning objects - all objects in a database should be owned by dbo or sa and then you dont have a problem.)
Post back if problems.
Cheers
SG|||(By the way - its a big no-no to have a user owning objects - all objects in a database should be owned by dbo or sa and then you dont have a problem.)
I wouldnt recommend that SG !!!!
Having a single user owning all the objects (DBO) should be a big no - no . How do you take care of all the security problems then ????|||Howdy Enigma,
Part of the reasons for the questions I'm asking are to flesh out the actual problem, hence the comments about dbo & sa owning all objects.
In most situations, I would always have dbo or sa owning all objects. Good security setup in the database ( if professionally configured ) will always be secure. I dont tolerate people that leave sa blank nor should anyone else - good for a pink slip in my book.
In some cases e.g. an application during its operation or installation may create objects in the database, that would be valid case for non-dbo/sa ownership ( but still not a great state of affairs - especially if its an internet exposed app).
If there is a bonafide reason for it, I'm open to suggestion. But in most cases, not good practice.
Cheers,
SG.|||SQLguy,
you wrote: "dont complicate your life -remove the original user & re-add the new user, then re-do all the security as required."
I tried that, but it still gave me the same msg...is that because my previous NT login owned an object ?...Im pretty sure that she did not.
Also, I cannot add her new NT login on a complete new server, one that she was never configured on with old or new NT account name.
Could this have anything to do with DNS settings ?
Thank you for your feedback|||I agree with SQLGuy. users owning objects will lead to more problems than solutions. Consider if you have two users that create tables with the same name. Now there is no telling what results either user would get from queries that reference either table (unless they fully qualify the names in those queries/stored procs). Then there are all the problems around the fact that a user can now drop a table in your database. Or create 200 indexes on the table. It is too much of a potential problem.|||Howdy kohln5,
I am surprised you get the same issue with the new user.
Some suggestions as we work this out:
(1) Lets test whether you have a DNS probem - see if you can ping the domain controller by name and TCPIP address from the SQL box.
(2) If you can ping the domain controller by name, open a dos box & type: ipconfig /all and look for the WINS & DNS server entries. If you dont have any that will probably be the reason. Speak to your networking guys about that.
(3) If you can ping the domain controller & you have correct WINS & DNS entries under ipconfig /all try going to your NT security and try & add the user under NT security to the local Users group on the box. At this point if you cant do this, you have a general networking issue & will need to fix it before we can progress the problem.
Post back if probs
Cheers
SG.sql
Error 15401 windows NT user or group not found+sql 2000
hi all,
i'm doing replication now ...when i add a new login to sqlserver i got
the message if i click ok..."Error 15401 windows NT user or group not
found"...i don't understand......why the error happens.......any one
pls help me!!
--thank youSQL Server cannot resolve the name of the login you specified. The name may
be incorrect, or it may belong to a different domain to which your current
domain does not have access.
Thanks
Laurentiu
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"nafi" <hnbnafisha@.gmail.com> wrote in message
news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...
> hi all,
> i'm doing replication now ...when i add a new login to sqlserver i got
> the message if i click ok..."Error 15401 windows NT user or group not
> found"...i don't understand......why the error happens.......any one
> pls help me!!
> --thank you
>|||hi Mr.Laurentiu Cristofor,
thank u very much....yeh.. correct...my computer doesn't have access
to that domain
Laurentiu Cristofor [MSFT] wrote:[vbcol=seagreen]
> SQL Server cannot resolve the name of the login you specified. The name ma
y
> be incorrect, or it may belong to a different domain to which your current
> domain does not have access.
> Thanks
> Laurentiu
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "nafi" <hnbnafisha@.gmail.com> wrote in message
> news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...
i'm doing replication now ...when i add a new login to sqlserver i got
the message if i click ok..."Error 15401 windows NT user or group not
found"...i don't understand......why the error happens.......any one
pls help me!!
--thank youSQL Server cannot resolve the name of the login you specified. The name may
be incorrect, or it may belong to a different domain to which your current
domain does not have access.
Thanks
Laurentiu
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"nafi" <hnbnafisha@.gmail.com> wrote in message
news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...
> hi all,
> i'm doing replication now ...when i add a new login to sqlserver i got
> the message if i click ok..."Error 15401 windows NT user or group not
> found"...i don't understand......why the error happens.......any one
> pls help me!!
> --thank you
>|||hi Mr.Laurentiu Cristofor,
thank u very much....yeh.. correct...my computer doesn't have access
to that domain
Laurentiu Cristofor [MSFT] wrote:[vbcol=seagreen]
> SQL Server cannot resolve the name of the login you specified. The name ma
y
> be incorrect, or it may belong to a different domain to which your current
> domain does not have access.
> Thanks
> Laurentiu
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "nafi" <hnbnafisha@.gmail.com> wrote in message
> news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...
Error 15401 Adding Domain Group to SQL Server
I have tried rebooting the system, I have ran the script to look for duplicate sids and am still having the issue when trying to add a domain group to SQL. I get the Error 15401: Windows NT user or group'mi\Trust Legal' not found. Check the name again. Running SQL 2000 Std, with SP3a, and the collation is set to SQL_Latin1_General_CP850_BIN, which makes this instance case sensitive, and the group name is spelt right and am following the case sensitivity of the name as well.
This is most likely an issue due to using a different casing. You could use a tool like sid2name, to obtain the correct casing of the group name from Windows. Then use that same casing and the statement should succeed. You might want to quickly try and capitalize the domain name: MI instead of mi; if this doesn't work then look for a sid2name tool and use it to determine the correct casing. If you cannot find such tool, you could write one easily by calling the LookupAccountSid WinAPI. You could use this post as an example: http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.
Thanks
Laurentiu
Most likely the cause of such failure is because the SQL Server cannot gather the information for this account from the domain controller.
Please make sure that the service account used to run SQL Server has permission to query the domain controller (in most cases being a member of the domain is sufficient to query the domain controller), and that the machine has access to the domain controller.
-Raul Garcia
SDE/T
SQL Server Engine
|||OK, so you've got two suggestions. To quickly discern between these, try to ACL something to the group, on the machine on which the server is installed. If you can, then the issue is not with reaching the DC; if you cannot, then it is a DC issue.
Thanks
Laurentiu
Apprciate all the great advice, but nothing seemed to help.
1) I am able to login into server using the account in which sql is running under, and am able to add the group to a folder on the box
2) ran the groups sid up against sid2name, and found the following:
MI\Trust Legal, is a group
enter the username just like that when adding another user to SQL and get the same message?
What command are you executing? sp_addlogin or sp_adduser?
Thanks
Laurentiu
Neither actually:
use IMCEXCLUSIVE
exec sp_grantlogin 'MI\Trust Legal'
since its a domain group, from what I read grantlogin was the proper SP to use, am I wrong?
|||No, you're right. sp_grantlogin is the right command.
You're using the right command and what appears to be the correct group name. So the issue is probably elsewhere. Does the command work for other groups or users in the same domain or does it consistently fail? What about users or groups from another domain? Does it work for local accounts? We need to try to identify the extent of this issue - it might hopefully lead us to its cause. If this is a blocking issue for you, I suggest to contact customer support as well.
Thanks
Laurentiu
The group must be different in some way from the others. You might want to try downloading SQL Server 2005 Express SP1 and trying this command out on it, to see if you get the same issue.
Thanks
Laurentiu
Error 15023: User already exists in current database
Dear Group,
Can someone please help me with this problem.
I'm trying to add a new User to a particular database but
keep getting the above error, telling me that the user
already exists in the current database. When I look in
the Permissions in the database Properties, the only
user/role is public.
What can I do?
Maree.You have orphaned users to the syslogins table in the master database (EM doesn't show such). I
assume you did an attach or restore of the database...
Read about sp_change_users_login and/or use a GUI on top of the proc available at www.dbmaint.com,
free utilities.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Maree" <eeramstu@.yahoo.com.au> wrote in message news:0f8001c387b9$7d459ec0$a101280a@.phx.gbl...
> Dear Group,
> Can someone please help me with this problem.
> I'm trying to add a new User to a particular database but
> keep getting the above error, telling me that the user
> already exists in the current database. When I look in
> the Permissions in the database Properties, the only
> user/role is public.
> What can I do?
> Maree.|||Thank you so much Tibor!!
>--Original Message--
>You have orphaned users to the syslogins table in the
master database (EM doesn't show such). I
>assume you did an attach or restore of the database...
>Read about sp_change_users_login and/or use a GUI on top
of the proc available at www.dbmaint.com,
>free utilities.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Maree" <eeramstu@.yahoo.com.au> wrote in message
news:0f8001c387b9$7d459ec0$a101280a@.phx.gbl...
>> Dear Group,
>> Can someone please help me with this problem.
>> I'm trying to add a new User to a particular database
but
>> keep getting the above error, telling me that the user
>> already exists in the current database. When I look in
>> the Permissions in the database Properties, the only
>> user/role is public.
>> What can I do?
>> Maree.
>
>.
>sql
Can someone please help me with this problem.
I'm trying to add a new User to a particular database but
keep getting the above error, telling me that the user
already exists in the current database. When I look in
the Permissions in the database Properties, the only
user/role is public.
What can I do?
Maree.You have orphaned users to the syslogins table in the master database (EM doesn't show such). I
assume you did an attach or restore of the database...
Read about sp_change_users_login and/or use a GUI on top of the proc available at www.dbmaint.com,
free utilities.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Maree" <eeramstu@.yahoo.com.au> wrote in message news:0f8001c387b9$7d459ec0$a101280a@.phx.gbl...
> Dear Group,
> Can someone please help me with this problem.
> I'm trying to add a new User to a particular database but
> keep getting the above error, telling me that the user
> already exists in the current database. When I look in
> the Permissions in the database Properties, the only
> user/role is public.
> What can I do?
> Maree.|||Thank you so much Tibor!!
>--Original Message--
>You have orphaned users to the syslogins table in the
master database (EM doesn't show such). I
>assume you did an attach or restore of the database...
>Read about sp_change_users_login and/or use a GUI on top
of the proc available at www.dbmaint.com,
>free utilities.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Maree" <eeramstu@.yahoo.com.au> wrote in message
news:0f8001c387b9$7d459ec0$a101280a@.phx.gbl...
>> Dear Group,
>> Can someone please help me with this problem.
>> I'm trying to add a new User to a particular database
but
>> keep getting the above error, telling me that the user
>> already exists in the current database. When I look in
>> the Permissions in the database Properties, the only
>> user/role is public.
>> What can I do?
>> Maree.
>
>.
>sql
Sunday, March 11, 2012
Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER
On manually starting SQLSERVERAGENT service, it gives the following
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprj
Start > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into an
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprj
Start > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into an
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER
On manually starting SQLSERVERAGENT service, it gives the following
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprjStart > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into a
n
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprjStart > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into a
n
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER
On manually starting SQLSERVERAGENT service, it gives the following
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprjStart > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into an
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
error:
error 1068: The depending service for group failed to start.
Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
services.
Thanks,
misecprjStart > Run > services.msc > SLSERVERAGENT > Properties > Dependencies
See which dependant services are not running.
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>|||Hi
In the services applet in control panel you can view the dependencies of a
service and start the services as well. Make sure that you are logged into an
account that has permissions to start services.
John
"misecprj@.hotmail.com" wrote:
> On manually starting SQLSERVERAGENT service, it gives the following
> error:
> error 1068: The depending service for group failed to start.
> Can anybody tell me how to restart these SQLSERVERAGENT and MSSQLSERVER
> services.
> Thanks,
> misecprj
>
Friday, March 9, 2012
Error 0X8007042B while restarting SQLServer Agent 2005
Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx
Error 0X8007042B while restarting SQLServer Agent 2005
Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
Error 0X8007042B while restarting SQLServer Agent 2005
Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitI
n\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while startin
g
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
>|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft.com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft.com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator grou
p
and then added this user to serverAdmin/Sysadmin group in SQL Server. I stil
l
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitI
n\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while startin
g
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
>|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft.com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft.com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator grou
p
and then added this user to serverAdmin/Sysadmin group in SQL Server. I stil
l
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx
Error 0X8007042B while restarting SQLServer Agent 2005
Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx
Friday, February 17, 2012
error
create #table
insert into #table
select A,b,c,d
from x,y,z
group by a,b,c,d
select *,(select max(d) from #table t
where t.a = d.a and t.b = d.b and
t.c like 'm%') as mx1
drop #table
go
when there is such data as t.c like 'm%',
it works OK but otherwise, i get error:
not supported,
details:
cannot obtain error message from server.
--
Sent by 3 from yahoo within field com
This is a spam protected message. Please answer with reference header.
Posted via http://www.usenet-replayer.comHi alex.
Your script really looks off the map in a few ways:
(a) create #table.. (what about columns?)
(b) insert into #table (what about values?)
(c) select ... from x,y,z (no join clauses - likely a major cartesian
product)
(d) select *... where t.a = d.a ... (there's no table / derived table
aliased as "d", although you do have a column aliased as "d")
Please post a better attempt at communicating your query so we've got at
least some chance of establishing what you're trying to achieve / what's
going wrong.
Regards,
Greg Linwood
SQL Server MVP
"alexqa2003@.yahoo.com" <u128845214@.spawnkill.ip-mobilphone.net> wrote in
message news:l.1066069486.1257385253@.[63.127.215.130]...
> create #table
> insert into #table
> select A,b,c,d
> from x,y,z
> group by a,b,c,d
> select *,(select max(d) from #table t
> where t.a = d.a and t.b = d.b and
> t.c like 'm%') as mx1
> drop #table
> go
>
> when there is such data as t.c like 'm%',
> it works OK but otherwise, i get error:
> not supported,
> details:
> cannot obtain error message from server.
>
>
> --
> Sent by 3 from yahoo within field com
> This is a spam protected message. Please answer with reference header.
> Posted via http://www.usenet-replayer.com
insert into #table
select A,b,c,d
from x,y,z
group by a,b,c,d
select *,(select max(d) from #table t
where t.a = d.a and t.b = d.b and
t.c like 'm%') as mx1
drop #table
go
when there is such data as t.c like 'm%',
it works OK but otherwise, i get error:
not supported,
details:
cannot obtain error message from server.
--
Sent by 3 from yahoo within field com
This is a spam protected message. Please answer with reference header.
Posted via http://www.usenet-replayer.comHi alex.
Your script really looks off the map in a few ways:
(a) create #table.. (what about columns?)
(b) insert into #table (what about values?)
(c) select ... from x,y,z (no join clauses - likely a major cartesian
product)
(d) select *... where t.a = d.a ... (there's no table / derived table
aliased as "d", although you do have a column aliased as "d")
Please post a better attempt at communicating your query so we've got at
least some chance of establishing what you're trying to achieve / what's
going wrong.
Regards,
Greg Linwood
SQL Server MVP
"alexqa2003@.yahoo.com" <u128845214@.spawnkill.ip-mobilphone.net> wrote in
message news:l.1066069486.1257385253@.[63.127.215.130]...
> create #table
> insert into #table
> select A,b,c,d
> from x,y,z
> group by a,b,c,d
> select *,(select max(d) from #table t
> where t.a = d.a and t.b = d.b and
> t.c like 'm%') as mx1
> drop #table
> go
>
> when there is such data as t.c like 'm%',
> it works OK but otherwise, i get error:
> not supported,
> details:
> cannot obtain error message from server.
>
>
> --
> Sent by 3 from yahoo within field com
> This is a spam protected message. Please answer with reference header.
> Posted via http://www.usenet-replayer.com
Subscribe to:
Posts (Atom)