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

|||Interesting idea, now when I try to add a user MI\15451a it works fine, when I try to add another group MI\Trust Technology Services it works just fine, just an issue so far with this one group MI\Trust Legal, arrgghhhhh this sucks. @. this point, if I cant get it fixed, I might just create a new group and go that route.|||

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 after restore db on different server (user dbo)

That is a user role, or user account error, and it probably already exists in the current system.

If you go to the user section of the db that you just restored, and delete all of the users, then go to the security options and allow these users to see it again, it should fix your problem.

There is a script somewhere that will resolve this, i will try to find and post.

Scooter McFlyhi,
but how i ll remove dbo in database.it is not removing anyway showing error that:
The selected use canot be dropped because the user owns objects
-Ashwini
Originally posted by scootermcfly
That is a user role, or user account error, and it probably already exists in the current system.

If you go to the user section of the db that you just restored, and delete all of the users, then go to the security options and allow these users to see it again, it should fix your problem.

There is a script somewhere that will resolve this, i will try to find and post.

Scooter McFly|||http://support.microsoft.com/default.aspx?scid=kb;en-us;819261 to resolve the issue.|||I would suggest EXECUTE sp_change_users_login 'Auto_Fix' (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_ca-cz_8qzy.asp) myself.

-PatP|||If you want to drop a user from a db where it owns objects, you can change object ownership to dbo (or any other user - NOT RECOMMENDED) and go on with the drop.|||yaa,solved

Error 14258

Hi,

I am new to the organization that I am working and we are running SQL Server 200O server. System has been working fine till last couple of days (It running for past two years).

SQLAGENT.exe has been using almost 50% of the CPU time so yesterday I started the SQL server. I want to modify some of the SQL server JOB but when I click on the properties of any job it gives me the following error:

"Error 14258 - Cannot perform this operation while SQL server agent is starting. Try again later."

I checked SQLAGENTSERVICE service and it is started also in the service manager it shows as started. We have a backup job scheduled for 5 days of the weeks but since last 10-12 days it is not running.

Our SQL Server is configured for thread mode processing. I checked for this error in www.support.microsoft.com but the solution given there is something to do with the fiber mode processing.

Could any body tell me why am I getting this error and what is the work around. Everything has been working fine till last two weeks back. Off course SQL server is running as the base product and no service packs have been applied. Other than applying the service pack is there any other solution, since things have been working fine.

Regards

VbabsDid you restart the MSSQLServer service as well ? Have you rebooted the server ? What version of sql are you using including service pack ? What do the logs report back to when this first started (look at both sql server and event logs) ?|||Originally posted by rnealejr
Did you restart the MSSQLServer service as well ? Have you rebooted the server ? What version of sql are you using including service pack ? What do the logs report back to when this first started (look at both sql server and event logs) ?

Hi,

I have rebooted server twice and all the service including SQLAGENTSERVICE show started. MSSSQLSERVER service stopped and restarted and server is working fine. As I have written erlier, NO SERVICE packs have been applied so far, it is running on the base product (ORIGINAL SQL SERVER 2000). This has been working for past two years (from 2001 onwards) and just last two days back this error poped up.

Also after now 72 hours of restart the agent service shows the same status (STARTED) but in the enterprise manager it still gives the same error.

Help!!!

Cheers

Vinod|||What is displayed in the sql server agent log (as well as the sql logs) when this error is returned ? Also, update your ss to the highest service pack that you can.sql

Error 1105

Following is the error message that we get when we try to
do some process:
Error No:1105
==========
Could not allocate space for object '(System table id:3)'
in database 'database name' because primary filegroup is
full.
sometimes we do get error like the one following:
Could not allocate new page for database 'database
name'.There are no more pages available in filegroup
Primary.
Space can be created by dropping objects,adding additional
files , or allowing filegrowth.
How do I handle this programatically.
I'm not sure exactly what you mean by 'handle programmatically' but, as the
error message states, you can set your data file to autogrow. This will
automatically expand the data file as needed, assuming you have available
disk space. However, for performance reasons, it is better to anticipate
space requirements and size the file accordingly.
Hope this helps.
Dan Guzman
SQL Server MVP
"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
> Following is the error message that we get when we try to
> do some process:
> Error No:1105
> ==========
> Could not allocate space for object '(System table id:3)'
> in database 'database name' because primary filegroup is
> full.
> sometimes we do get error like the one following:
> Could not allocate new page for database 'database
> name'.There are no more pages available in filegroup
> Primary.
> Space can be created by dropping objects,adding additional
> files , or allowing filegrowth.
> How do I handle this programatically.
>
|||We are using JDBC to connect SQL server.
JDBC driver provided in SQL server.
We create database from JDBC and specify initial size
while creating database.
Using JDBC driver autogrow option fails. All transaction
fails with auto grow option.
This is the reason we specify initial value.
When the more record are added to tables and grows to
size specified it works fine. After exceeding the
specified size or just before that
it gives Error 1105
Thanks in advance
Lakshmi.
>--Original Message--
>I'm not sure exactly what you mean by 'handle
programmatically' but, as the
>error message states, you can set your data file to
autogrow. This will
>automatically expand the data file as needed, assuming
you have available
>disk space. However, for performance reasons, it is
better to anticipate
>space requirements and size the file accordingly.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
to
id:3)'
additional
>
>.
>
|||You might try to use the
alter database alte file
command... It allows you to change file growth paramters for the database
programmatically.
"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
> Following is the error message that we get when we try to
> do some process:
> Error No:1105
> ==========
> Could not allocate space for object '(System table id:3)'
> in database 'database name' because primary filegroup is
> full.
> sometimes we do get error like the one following:
> Could not allocate new page for database 'database
> name'.There are no more pages available in filegroup
> Primary.
> Space can be created by dropping objects,adding additional
> files , or allowing filegrowth.
> How do I handle this programatically.
>
|||In addition to the initial size, you can specify the growth increment and
max size so that the file can grow automatically if needed. You can specify
this in your CREATE DATABASE statement or after database creation with ALTER
DATABASE as Wayne suggested.
Hope this helps.
Dan Guzman
SQL Server MVP
"lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:1882f01c42095$f8e54f10$a601280a@.phx.gbl...[color=darkblue]
> We are using JDBC to connect SQL server.
> JDBC driver provided in SQL server.
> We create database from JDBC and specify initial size
> while creating database.
> Using JDBC driver autogrow option fails. All transaction
> fails with auto grow option.
> This is the reason we specify initial value.
> When the more record are added to tables and grows to
> size specified it works fine. After exceeding the
> specified size or just before that
> it gives Error 1105
> Thanks in advance
> Lakshmi.
> programmatically' but, as the
> autogrow. This will
> you have available
> better to anticipate
> message
> to
> id:3)'
> additional

Error 1105

Following is the error message that we get when we try to
do some process:
Error No:1105
========== Could not allocate space for object '(System table id:3)'
in database 'database name' because primary filegroup is
full.
sometimes we do get error like the one following:
Could not allocate new page for database 'database
name'.There are no more pages available in filegroup
Primary.
Space can be created by dropping objects,adding additional
files , or allowing filegrowth.
How do I handle this programatically.I'm not sure exactly what you mean by 'handle programmatically' but, as the
error message states, you can set your data file to autogrow. This will
automatically expand the data file as needed, assuming you have available
disk space. However, for performance reasons, it is better to anticipate
space requirements and size the file accordingly.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
> Following is the error message that we get when we try to
> do some process:
> Error No:1105
> ==========> Could not allocate space for object '(System table id:3)'
> in database 'database name' because primary filegroup is
> full.
> sometimes we do get error like the one following:
> Could not allocate new page for database 'database
> name'.There are no more pages available in filegroup
> Primary.
> Space can be created by dropping objects,adding additional
> files , or allowing filegrowth.
> How do I handle this programatically.
>|||We are using JDBC to connect SQL server.
JDBC driver provided in SQL server.
We create database from JDBC and specify initial size
while creating database.
Using JDBC driver autogrow option fails. All transaction
fails with auto grow option.
This is the reason we specify initial value.
When the more record are added to tables and grows to
size specified it works fine. After exceeding the
specified size or just before that
it gives Error 1105
Thanks in advance
Lakshmi.
>--Original Message--
>I'm not sure exactly what you mean by 'handle
programmatically' but, as the
>error message states, you can set your data file to
autogrow. This will
>automatically expand the data file as needed, assuming
you have available
>disk space. However, for performance reasons, it is
better to anticipate
>space requirements and size the file accordingly.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
>> Following is the error message that we get when we try
to
>> do some process:
>> Error No:1105
>> ==========>> Could not allocate space for object '(System table
id:3)'
>> in database 'database name' because primary filegroup is
>> full.
>> sometimes we do get error like the one following:
>> Could not allocate new page for database 'database
>> name'.There are no more pages available in filegroup
>> Primary.
>> Space can be created by dropping objects,adding
additional
>> files , or allowing filegrowth.
>> How do I handle this programatically.
>
>.
>|||You might try to use the
alter database alte file
command... It allows you to change file growth paramters for the database
programmatically.
"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
> Following is the error message that we get when we try to
> do some process:
> Error No:1105
> ==========> Could not allocate space for object '(System table id:3)'
> in database 'database name' because primary filegroup is
> full.
> sometimes we do get error like the one following:
> Could not allocate new page for database 'database
> name'.There are no more pages available in filegroup
> Primary.
> Space can be created by dropping objects,adding additional
> files , or allowing filegrowth.
> How do I handle this programatically.
>|||In addition to the initial size, you can specify the growth increment and
max size so that the file can grow automatically if needed. You can specify
this in your CREATE DATABASE statement or after database creation with ALTER
DATABASE as Wayne suggested.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:1882f01c42095$f8e54f10$a601280a@.phx.gbl...
> We are using JDBC to connect SQL server.
> JDBC driver provided in SQL server.
> We create database from JDBC and specify initial size
> while creating database.
> Using JDBC driver autogrow option fails. All transaction
> fails with auto grow option.
> This is the reason we specify initial value.
> When the more record are added to tables and grows to
> size specified it works fine. After exceeding the
> specified size or just before that
> it gives Error 1105
> Thanks in advance
> Lakshmi.
> >--Original Message--
> >I'm not sure exactly what you mean by 'handle
> programmatically' but, as the
> >error message states, you can set your data file to
> autogrow. This will
> >automatically expand the data file as needed, assuming
> you have available
> >disk space. However, for performance reasons, it is
> better to anticipate
> >space requirements and size the file accordingly.
> >
> >--
> >Hope this helps.
> >
> >Dan Guzman
> >SQL Server MVP
> >
> >"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:16c9101c4208d$d56c5220$a001280a@.phx.gbl...
> >> Following is the error message that we get when we try
> to
> >> do some process:
> >>
> >> Error No:1105
> >> ==========> >> Could not allocate space for object '(System table
> id:3)'
> >> in database 'database name' because primary filegroup is
> >> full.
> >> sometimes we do get error like the one following:
> >> Could not allocate new page for database 'database
> >> name'.There are no more pages available in filegroup
> >> Primary.
> >> Space can be created by dropping objects,adding
> additional
> >> files , or allowing filegrowth.
> >>
> >> How do I handle this programatically.
> >>
> >
> >
> >.
> >

Error 1105

Following is the error message that we get when we try to
do some process:
Error No:1105
==========
Could not allocate space for object '(System table id:3)'
in database 'database name' because primary filegroup is
full.
sometimes we do get error like the one following:
Could not allocate new page for database 'database
name'.There are no more pages available in filegroup
Primary.
Space can be created by dropping objects,adding additional
files , or allowing filegrowth.
How do I handle this programatically.I'm not sure exactly what you mean by 'handle programmatically' but, as the
error message states, you can set your data file to autogrow. This will
automatically expand the data file as needed, assuming you have available
disk space. However, for performance reasons, it is better to anticipate
space requirements and size the file accordingly.
Hope this helps.
Dan Guzman
SQL Server MVP
"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:16c9101c4208d$d56c5220$a001280a@.phx
.gbl...
> Following is the error message that we get when we try to
> do some process:
> Error No:1105
> ==========
> Could not allocate space for object '(System table id:3)'
> in database 'database name' because primary filegroup is
> full.
> sometimes we do get error like the one following:
> Could not allocate new page for database 'database
> name'.There are no more pages available in filegroup
> Primary.
> Space can be created by dropping objects,adding additional
> files , or allowing filegrowth.
> How do I handle this programatically.
>|||We are using JDBC to connect SQL server.
JDBC driver provided in SQL server.
We create database from JDBC and specify initial size
while creating database.
Using JDBC driver autogrow option fails. All transaction
fails with auto grow option.
This is the reason we specify initial value.
When the more record are added to tables and grows to
size specified it works fine. After exceeding the
specified size or just before that
it gives Error 1105
Thanks in advance
Lakshmi.
>--Original Message--
>I'm not sure exactly what you mean by 'handle
programmatically' but, as the
>error message states, you can set your data file to
autogrow. This will
>automatically expand the data file as needed, assuming
you have available
>disk space. However, for performance reasons, it is
better to anticipate
>space requirements and size the file accordingly.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in
message
> news:16c9101c4208d$d56c5220$a001280a@.phx
.gbl...
to
id:3)'
additional
>
>.
>|||You might try to use the
alter database alte file
command... It allows you to change file growth paramters for the database
programmatically.
"Lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:16c9101c4208d$d56c5220$a001280a@.phx
.gbl...
> Following is the error message that we get when we try to
> do some process:
> Error No:1105
> ==========
> Could not allocate space for object '(System table id:3)'
> in database 'database name' because primary filegroup is
> full.
> sometimes we do get error like the one following:
> Could not allocate new page for database 'database
> name'.There are no more pages available in filegroup
> Primary.
> Space can be created by dropping objects,adding additional
> files , or allowing filegrowth.
> How do I handle this programatically.
>|||In addition to the initial size, you can specify the growth increment and
max size so that the file can grow automatically if needed. You can specify
this in your CREATE DATABASE statement or after database creation with ALTER
DATABASE as Wayne suggested.
Hope this helps.
Dan Guzman
SQL Server MVP
"lakshmi" <anonymous@.discussions.microsoft.com> wrote in message
news:1882f01c42095$f8e54f10$a601280a@.phx
.gbl...
> We are using JDBC to connect SQL server.
> JDBC driver provided in SQL server.
> We create database from JDBC and specify initial size
> while creating database.
> Using JDBC driver autogrow option fails. All transaction
> fails with auto grow option.
> This is the reason we specify initial value.
> When the more record are added to tables and grows to
> size specified it works fine. After exceeding the
> specified size or just before that
> it gives Error 1105
> Thanks in advance
> Lakshmi.
> programmatically' but, as the
> autogrow. This will
> you have available
> better to anticipate
> message
> to
> id:3)'
> additional

error 1069

I have been running my SQL under Local System a/c. I
wanted to change it to run under my NT a/c. I went to
control panel, services and tried changing the account to
this account and gave my NT credentials. It wouldn't start
and I get logon failure error 1069.
Am I missing anything here?
thanks,
balaYou can change it in Enterprise manager (Properties of the Server).
What rights does the new account have on the domain? You need log on locally
rights.
Is it your personal account or an account specific for SQL Server only? It
is best to use a dedicated account as SQL will stop working if your password
expires.
Look at http://support.microsoft.com/defaul...kb;en-us;283811
(HOW TO: Change the SQL Server or SQL Server Agent Service Account Without
Using SQL Enterprise Manager in SQL Server 2000)
Regards
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"bala" <balal@.microsoft.com> wrote in message
news:00ff01c3d613$d8533400$a401280a@.phx.gbl...

quote:

---

> I have been running my SQL under Local System a/c. I
> wanted to change it to run under my NT a/c. I went to
> control panel, services and tried changing the account to
> this account and gave my NT credentials. It wouldn't start
> and I get logon failure error 1069.
> Am I missing anything here?
> thanks,
> bala

---

Error 1068 Can't start SQLSERVERAGENT and MSSQLSERVER

I was rebuilding my index and my system admin rebooted the system without
shutting down the database first. After the reboot the SQLSERVERAGENT and
MSSQLSERVER services won't start and I received ERROR 1068:The dependency
service or group failed to start error while trying to start the two services.
In the Enterprise Manger screen I saw:
Connection failed, check SQL Server Registration Properties
I am not sure how to fix this problem. Can I rebuild my SQL Server
registery, and if so, how? Please advise. Thanks in advance.
Hi,
Could you please open the SQL server errorlog in program files\microsoft sql
server\log folder and investigate more on this error.
Thanks
Hari
MCDBA
"Ling" wrote:

> I was rebuilding my index and my system admin rebooted the system without
> shutting down the database first. After the reboot the SQLSERVERAGENT and
> MSSQLSERVER services won't start and I received ERROR 1068:The dependency
> service or group failed to start error while trying to start the two services.
> In the Enterprise Manger screen I saw:
> Connection failed, check SQL Server Registration Properties
> I am not sure how to fix this problem. Can I rebuild my SQL Server
> registery, and if so, how? Please advise. Thanks in advance.
|||There's only one line in the errorlog:
2004-09-22 11:28:07.03 server The system is older than SQL Server 7.0 RTM
version and is not supported by this server
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Could you please open the SQL server errorlog in program files\microsoft sql
> server\log folder and investigate more on this error.
> Thanks
> Hari
> MCDBA
>
> "Ling" wrote:
|||What exact messages do you get if you from a DOS prompt type below?
NET START MSSQLSERVER
(Adjust server name of it is a named instance.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ling" <Ling@.discussions.microsoft.com> wrote in message
news:F823DF33-6210-4E2D-AA98-37E2FEFD1659@.microsoft.com...
> I was rebuilding my index and my system admin rebooted the system without
> shutting down the database first. After the reboot the SQLSERVERAGENT and
> MSSQLSERVER services won't start and I received ERROR 1068:The dependency
> service or group failed to start error while trying to start the two services.
> In the Enterprise Manger screen I saw:
> Connection failed, check SQL Server Registration Properties
> I am not sure how to fix this problem. Can I rebuild my SQL Server
> registery, and if so, how? Please advise. Thanks in advance.

error 1053 when try to start mssqlserver service

I have a two node cluster. When I try to failover from active node which is
node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely
fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group
'006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is
unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode
processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed
Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'S:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog _200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin
user account. What possibly could be the issue here?
Thanks
You could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/224071/en-us for
some info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>I have a two node cluster. When I try to failover from active node which is
> node2 to node1 I get the following errors in the event viewer/ system logs
>
> The MSSQLSERVER service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
> Cluster resource 'SQL Cluster Group Server Service' in Resource Group
> '006-PM2-DBASQL' failed.
>
> SQL Server Error Logs dont show any error either execpt one which i think is
> unrelated to this issue:
> 2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2006-04-05 09:51:43.86 server All rights reserved.
> 2006-04-05 09:51:43.86 server Server Process ID is 5508.
> 2006-04-05 09:51:43.86 server Logging SQL Server messages in file
> 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2006-04-05 09:51:43.86 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2006-04-05 09:51:44.00 server SQL Server configured for thread mode
> processing.
> 2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-04-05 09:51:44.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
> 2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
> 2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
> 2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
> 2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
> 2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
> 2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
> 2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connections
> 2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
> 2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
> 2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
> 2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
> 2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
> 2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
> 2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
> 2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
> complete (approximately 0 more seconds)
> 2006-04-05 09:51:53.63 spid3 Recovery complete.
> 2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
> created.
> 2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlmaint'.
> 2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
> creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
> 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog _200604050952.TRN'}).
> 2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'sp_MSgetversion'.
> 2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
> 2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_msver'.
> 2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
>
> MSSQLServer and SQLServerAgent services are running under a system admin
> user account. What possibly could be the issue here?
> Thanks

error 1053 when try to start mssqlserver service

I have a two node cluster. When I try to failover from active node which is
node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely
fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group
'006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is
unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode
processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed
Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433
.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'S:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\TransactionLogs\Nort
hwind_tlog_200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin
user account. What possibly could be the issue here?
ThanksYou could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/
224071/en-us for
some info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>I have a two node cluster. When I try to failover from active node which is
> node2 to node1 I get the following errors in the event viewer/ system logs
>
> The MSSQLSERVER service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connec
t.
> Cluster resource 'SQL Cluster Group Server Service' in Resource Group
> '006-PM2-DBASQL' failed.
>
> SQL Server Error Logs dont show any error either execpt one which i think
is
> unrelated to this issue:
> 2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2006-04-05 09:51:43.86 server All rights reserved.
> 2006-04-05 09:51:43.86 server Server Process ID is 5508.
> 2006-04-05 09:51:43.86 server Logging SQL Server messages in file
> 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2006-04-05 09:51:43.86 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2006-04-05 09:51:44.00 server SQL Server configured for thread mode
> processing.
> 2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500]
Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-04-05 09:51:44.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
> 2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 14
33.
> 2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
> 2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
> 2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
> 2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
> 2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
> 2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memor
y,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connection
s
> 2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
> 2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
> 2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
> 2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
> 2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
> 2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
> 2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
> 2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
> complete (approximately 0 more seconds)
> 2006-04-05 09:51:53.63 spid3 Recovery complete.
> 2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
> created.
> 2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.203
9'
> to execute extended stored procedure 'xp_qv'.
> 2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlmaint'.
> 2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
> creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
> 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DIS
K:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Nort
hwind_tlog_200604050952.TRN'}).
> 2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'sp_MSgetversion'.
> 2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
> 2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039
'
> to execute extended stored procedure 'xp_msver'.
> 2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
>
> MSSQLServer and SQLServerAgent services are running under a system admin
> user account. What possibly could be the issue here?
> Thanks

error 1053 when try to start mssqlserver service

I have a two node cluster. When I try to failover from active node which is
node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely
fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group
'006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is
unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode
processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed
Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'S:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog_200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin
user account. What possibly could be the issue here?
ThanksYou could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/224071/en-us for
some info.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>I have a two node cluster. When I try to failover from active node which is
> node2 to node1 I get the following errors in the event viewer/ system logs
>
> The MSSQLSERVER service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
> Cluster resource 'SQL Cluster Group Server Service' in Resource Group
> '006-PM2-DBASQL' failed.
>
> SQL Server Error Logs dont show any error either execpt one which i think is
> unrelated to this issue:
> 2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2006-04-05 09:51:43.86 server All rights reserved.
> 2006-04-05 09:51:43.86 server Server Process ID is 5508.
> 2006-04-05 09:51:43.86 server Logging SQL Server messages in file
> 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2006-04-05 09:51:43.86 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2006-04-05 09:51:44.00 server SQL Server configured for thread mode
> processing.
> 2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-04-05 09:51:44.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
> 2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
> 2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
> 2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
> 2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
> 2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
> 2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
> 2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connections
> 2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
> 2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
> 2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
> 2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
> 2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
> 2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
> 2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
> 2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
> complete (approximately 0 more seconds)
> 2006-04-05 09:51:53.63 spid3 Recovery complete.
> 2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
> created.
> 2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlmaint'.
> 2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
> creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
> 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog_200604050952.TRN'}).
> 2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'sp_MSgetversion'.
> 2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
> 2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_msver'.
> 2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
>
> MSSQLServer and SQLServerAgent services are running under a system admin
> user account. What possibly could be the issue here?
> Thanks

error 1053 when I try to start SQLagent

I also get and error of unable to complete the operation
on "system Log" The interface is unknown.
Hi,
I feel that Service startup account for SQL Agent do not have previlages in
registry. Can you add that user in Administarter group and try starting
the SQL agent service.
Verify, what is there in SQLAGENT.OUT file ?
Thanks
Hari
MCDBA
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:19cb101c41cc2$1bc4ec20$a101280a@.phx.gbl...
> I also get and error of unable to complete the operation
> on "system Log" The interface is unknown.

error 1053 when I try to start SQLagent

I also get and error of unable to complete the operation
on "system Log" The interface is unknown.Hi,
I feel that Service startup account for SQL Agent do not have previlages in
registry. Can you add that user in Administarter group and try starting
the SQL agent service.
Verify, what is there in SQLAGENT.OUT file ?
Thanks
Hari
MCDBA
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:19cb101c41cc2$1bc4ec20$a101280a@.phx.gbl...
> I also get and error of unable to complete the operation
> on "system Log" The interface is unknown.|||sqlagent.out => startup erroe: The event log service has
not been started.
>--Original Message--
>I also get and error of unable to complete the operation
>on "system Log" The interface is unknown.
>.
>|||Here is how I got around the problem, trying to put a program to run as a Servic
in Windows
How to setup the Morning Negotiation Tool(MNTOOL), so it wil
Run as a Service in Windows 2003 Server.
1.) You must have the following programs, which you can fin
in the Microsoft NT/2000 resource kit
a.) srvany.exe
b.) instsrv.exe
2. Put the MNTOOL execution file in the directory D:\smt_tool as pass.exe
3. Copy INSTSRV.EXE and SRVANY.EXE, on Windows 2003 Server, unde
the directory C:\windows\.
4. Run "C:\Windows\INSTSRV MNTOOL C:\Windows\srvany.exe"
5. Using REGEDT32 find the following key:-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MNTOOL
6. Create a new key called "Parameters" , under MNTOOL
7. Create a new REG_SZ value, under Parameters, called "Application" and give i
the value d:\smt_tool\pass.exe.
8. Run Control Panel, Services, find the MNTOOL service and change the Startu
settings for this service to log on account smt, which should have Administrato
permissions
9. Start the MNTOOL service, from the Service menu, and it should remai
running. Do a Cntrl/Alt/Delete to get the TASK Manager ICON and mak
sure it says that PASS.exe is running
Note
To delete the MNTOOL, from running as a service, you can use the followin
DOS command, which is only available in Windows XP PRO and Window
2003 Service software: â'sc delete MNTOOLâ?
© NJC 4/08/200

error 1053 when I try to start SQLagent

I also get and error of unable to complete the operation
on "system Log" The interface is unknown.Hi,
I feel that Service startup account for SQL Agent do not have previlages in
registry. Can you add that user in Administarter group and try starting
the SQL agent service.
Verify, what is there in SQLAGENT.OUT file ?
Thanks
Hari
MCDBA
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:19cb101c41cc2$1bc4ec20$a101280a@.phx
.gbl...
> I also get and error of unable to complete the operation
> on "system Log" The interface is unknown.

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error = Arithmetic overflow error converting expression to data type smalldatetim

$exception {"Arithmetic overflow error converting expression to data type smalldatetime.\r\nThe statement has been terminated."} System.Exception {System.Data.SqlClient.SqlException}

occurs

here is my code

protectedvoid EmailSubmitBtn_Click(object sender,EventArgs e)

{

SqlDataSource NewsletterSqlDataSource =newSqlDataSource();

NewsletterSqlDataSource.ConnectionString =

ConfigurationManager.ConnectionStrings["NewsletterConnectionString"].ToString();

//Text version

NewsletterSqlDataSource.InsertCommandType =

SqlDataSourceCommandType.Text;

NewsletterSqlDataSource.InsertCommand =

"INSERT INTO NewsLetter (EmailAddress, IPAddress, DateTimeStamp) VALUES (@.EmailAddress, @.IPAddress, @.DateTimeStamp)";

//storeprocedure version//NewsletterSqlDataSource.InsertCommandType = SqlDataSourceCommandType.StoredProcedure;//NewsletterSqlDataSource.InsertCommand = "EmailInsert";

NewsletterSqlDataSource.InsertParameters.Add(

"EmailAddress", EmailTb.Text);

NewsletterSqlDataSource.InsertParameters.Add(

"IPAddress", Request.UserHostAddress.ToString());

NewsletterSqlDataSource.InsertParameters.Add(

"DateTimeStamp",DateTime.Now.ToString());int rowsAffected = 0;try

{

rowsAffected = NewsletterSqlDataSource.Insert();

}

catch (Exception ex)

{

Server.Transfer(

"NewsletterProblem.aspx");

}

finally

{

NewsletterSqlDataSource =

null;

}

if (rowsAffected != 1)

{

Server.Transfer(

"NewsletterProblem.aspx");

}

else

{

Server.Transfer(

"NewsletterSuccess.aspx");

}

Do not pass the Value asDateTime.Now.ToString() . Just pass the value asDateTime.Now if the db datatype is smalldatetime. If the input datatype for stored procedure is string , try

DateTime

.Now.ToShortDateString(); . Let me know if you need any clarifications

Error : insufficient system memory

Hi,
We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
issues. As soon as we installed the Database on Windows 2003 we are getting
the error saying that there is insufficient system memory. We get this at
least twice every week. Once this error happens most of SQL statements give
similar error message.
Kindly provide some help on this.
Here is the error message
SQLState: 42000, ErrorCode:701
[Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system
memory to run this query.
--
Thanks,
Mr GeekWithout seeing a stack dump file , it is hard to say exactly what is causing
the problem.
Are the queries that trigger this problem , dealing with UNION ALL or IN
with largae data sets?
Have you thought about upgarding to sp4?
--
Jack Vamvas
__________________________________________________________________
"LSolve" <L0L@.newsgroups.nospam> wrote in message
news:F4561270-E1BA-4B4C-9841-DA55FE250789@.microsoft.com...
> Hi,
> We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
> issues. As soon as we installed the Database on Windows 2003 we are
getting
> the error saying that there is insufficient system memory. We get this at
> least twice every week. Once this error happens most of SQL statements
give
> similar error message.
> Kindly provide some help on this.
> Here is the error message
> SQLState: 42000, ErrorCode:701
> [Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient
system
> memory to run this query.
> --
> Thanks,
> Mr Geek|||Hello,
Please refer to the following article which describes how to troubleshoot
the slow performance of many concurrent ad-hoc queries:
243588 HOW TO: Troubleshoot the Performance of Ad-Hoc Queries
http://support.microsoft.com/?id=243588
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lsolve,
If u want to check that ur sql server need more merory then check this
artical .
http://www.computerperformance.co.uk/HealthCheck/Memory_Health.htm
from
Doller

Error : insufficient system memory

Hi,
We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
issues. As soon as we installed the Database on Windows 2003 we are getting
the error saying that there is insufficient system memory. We get this at
least twice every week. Once this error happens most of SQL statements give
similar error message when run from query analyzer.
Kindly provide some help on this.
Here is the error message
SQLState: 42000, ErrorCode:701
[Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system
memory to run this query.You might want to give MS PSS a call:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"LSolve" <LSolve@.discussions.microsoft.com> wrote in message
news:42FBA2DD-8B32-48E2-9CFD-805E88A6DCDA@.microsoft.com...
> Hi,
> We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
> issues. As soon as we installed the Database on Windows 2003 we are
> getting
> the error saying that there is insufficient system memory. We get this at
> least twice every week. Once this error happens most of SQL statements
> give
> similar error message when run from query analyzer.
> Kindly provide some help on this.
> Here is the error message
> SQLState: 42000, ErrorCode:701
> [Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient
> system
> memory to run this query.
>

Error : insufficient system memory

Hi,
We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
issues. As soon as we installed the Database on Windows 2003 we are getting
the error saying that there is insufficient system memory. We get this at
least twice every week. Once this error happens most of SQL statements give
similar error message when run from query analyzer.
Kindly provide some help on this.
Here is the error message
SQLState: 42000, ErrorCode:701
[Microsoft][ODBC SQL Server Driver][SQL Server]There is insuffic
ient system
memory to run this query.You might want to give MS PSS a call:
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"LSolve" <LSolve@.discussions.microsoft.com> wrote in message
news:42FBA2DD-8B32-48E2-9CFD-805E88A6DCDA@.microsoft.com...
> Hi,
> We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
> issues. As soon as we installed the Database on Windows 2003 we are
> getting
> the error saying that there is insufficient system memory. We get this at
> least twice every week. Once this error happens most of SQL statements
> give
> similar error message when run from query analyzer.
> Kindly provide some help on this.
> Here is the error message
> SQLState: 42000, ErrorCode:701
> [Microsoft][ODBC SQL Server Driver][SQL Server]There is insuff
icient
> system
> memory to run this query.
>