Counter settings: log

Showing posts with label log. Show all posts

Tuesday, March 20, 2012

Could not start SQL Server

SQL server is not starting, logs following error in
windows log
Error: 9003, Severity: 20,State: 1
The LSN (4:482:1) passed to log scan in database 'model'
is invalid
Is any one having solution for this?Manoj
It looks like the model database has become corrupted due to the power
failure.
Try to start the SQL Server as an application from a command prompt. For
more information, please refer to the topics: 'Starting SQL Server
Manually' and 'Using Startup Options' on Microsoft SQL Server Books Online.
Look if it does not help you so in this situation your best bet is to call
MS PSS
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Hi,
Seems your Model database is corrupt,
1. Stop SQL server
2. Copy the .MDF and .LDF files (Belongs to MODEL database) to a different
ent location
3. From a different SQL Serevr copy the Model databases .MDF and .LDF files
to the same folder. Overwrite the old files
4. Now start the SQL server.
Most probably this will work out.
Thanks
Hari
MCDBA
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> SQL server is not starting, logs following error in
> windows log
> Error: 9003, Severity: 20,State: 1
> The LSN (4:482:1) passed to log scan in database 'model'
> is invalid
> Is any one having solution for this?
>|||Thanks Hari !! I will try this option
>--Original Message--
>Hi,
>Seems your Model database is corrupt,
>1. Stop SQL server
>2. Copy the .MDF and .LDF files (Belongs to MODEL
database) to a different
>ent location
>3. From a different SQL Serevr copy the Model
databases .MDF and .LDF files
>to the same folder. Overwrite the old files
>4. Now start the SQL server.
>
>Most probably this will work out.
>Thanks
>Hari
>MCDBA
>
>"Manoj" <manoj_raheja@.hotmail.com> wrote in message
>news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
>> SQL server is not starting, logs following error in
>> windows log
>> Error: 9003, Severity: 20,State: 1
>> The LSN (4:482:1) passed to log scan in database 'model'
>> is invalid
>> Is any one having solution for this?
>
>.
>|||Make sure that other SQL Server has the same collation. SQL Server does not
support different collations across the system databases.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<anonymous@.discussions.microsoft.com> wrote in message
news:d07801c3eeee$ed440170$a401280a@.phx.gbl...
> Thanks Hari !! I will try this option
> >--Original Message--
> >Hi,
> >
> >Seems your Model database is corrupt,
> >
> >1. Stop SQL server
> >2. Copy the .MDF and .LDF files (Belongs to MODEL
> database) to a different
> >ent location
> >3. From a different SQL Serevr copy the Model
> databases .MDF and .LDF files
> >to the same folder. Overwrite the old files
> >4. Now start the SQL server.
> >
> >
> >Most probably this will work out.
> >
> >Thanks
> >Hari
> >MCDBA
> >
> >
> >"Manoj" <manoj_raheja@.hotmail.com> wrote in message
> >news:d03f01c3eeea$1f354a90$a401280a@.phx.gbl...
> >> SQL server is not starting, logs following error in
> >> windows log
> >>
> >> Error: 9003, Severity: 20,State: 1
> >> The LSN (4:482:1) passed to log scan in database 'model'
> >> is invalid
> >>
> >> Is any one having solution for this?
> >>
> >
> >
> >.
> >|||Hi! Hari Prasad,
Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||What's the error? Could you post the error form the error log?
--
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide SQL Community)
SQLTips, SQL Scripts, SQL Forums, SQL Articles, SQL Radio, SQL Server 2008,
SQL Blogs, SQL Clinic and a lot of SQL Server fun.
"Girish Sharma (QA Engg.)" wrote:
> Hi! Hari Prasad,
> Heartly thanks for your comment. I was stuck with the same problem & after googling for quite sometime i came across your comment. I am all set with my DB now. Thanks again.
>
> From http://www.developmentnow.com/g/118_2004_2_0_0_469115/Could-not-start-SQL-Server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

Could not set working set size to 1168512 KB

hello,
We're running W2000 sp4 fr/ SQL 2000 SP3 fr and get error 17122 in the
application event log every time SQL is brought up. The error text
reads
"initdata: Warning: Could not set working set size to 1168512 KB".
What does
this really mean, is it harmful and how can I correct it? Thanks for
any info.
Thanks
A.S
Hi,
Not a real problem, this is only a warning due to incompatibility with
PAE/AWE !
Just disable the "reserve physical memory for SQLServer" by :
sp_configure 'set working set size',0
go
reconfigure with override
go
See http://support.microsoft.com/kb/822164/en-us
Guillaume.
"Zizou-Real" wrote:

> hello,
> We're running W2000 sp4 fr/ SQL 2000 SP3 fr and get error 17122 in the
> application event log every time SQL is brought up. The error text
> reads
> "initdata: Warning: Could not set working set size to 1168512 KB".
> What does
> this really mean, is it harmful and how can I correct it? Thanks for
> any info.
>
> Thank’s
> A.S
>
>
sql

Monday, March 19, 2012

Could not locate file 'data01_log' in sysfiles

I need to shrink this log file, and setup some maintenance tasks, but I am
getting the above error. Any advice is greatly appreciated.
sp_helpdb output:
DATA01
1 e:\mssql\data\data01.mdf
PRIMARY 4102976 KB Unlimited 10% data only
DATA01_log
2 c:\logfiles\data01_log.ldf
NULL 327296 KB 460800 KB 10% log only
When I run shrinkfile I get this:
dbcc shrinkfile (data01_log,320)
Server: Msg 8985, Level 16, State 1, Line 1
Could not locate file 'data01_log' in sysfiles.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.Hi
If you do a SELECT * from sysfiles , what is the NAME returned ?
Are you then using the exact - case sensitive spelling?
Jack Vamvas
__________________________________________________________________
Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
"Rick Billingsley" <RickBillingsley@.discussions.microsoft.com> wrote in
message news:35983A24-DD51-43EA-A644-BA857A76F29B@.microsoft.com...
> I need to shrink this log file, and setup some maintenance tasks, but I am
> getting the above error. Any advice is greatly appreciated.
> sp_helpdb output:
> DATA01
> 1 e:\mssql\data\data01.mdf
>
> PRIMARY 4102976 KB Unlimited 10% data only
> DATA01_log
> 2
c:\logfiles\data01_log.ldf
>
> NULL 327296 KB 460800 KB 10% log only
> When I run shrinkfile I get this:
> dbcc shrinkfile (data01_log,320)
> Server: Msg 8985, Level 16, State 1, Line 1
> Could not locate file 'data01_log' in sysfiles.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>|||the select query returns the mastlog. This is not the log I am trying to
shrink/backup.
I believe the problem is that the log I want is on a different logical drive
(c vs. e) than the database.
I have tried running the shrinkfile with the exact case-sensitive spelling
with the same results.|||Change your database context to Data01. The select statement
indicates that you are trying to do this from the master
database. Shrinkfile applies to files in the current
database so you need to be in the appropriate database.
-Sue
On Mon, 23 Jan 2006 08:58:03 -0800, "Rick Billingsley"
<RickBillingsley@.discussions.microsoft.com> wrote:
>the select query returns the mastlog. This is not the log I am trying to
>shrink/backup.
>I believe the problem is that the log I want is on a different logical drive
>(c vs. e) than the database.
>I have tried running the shrinkfile with the exact case-sensitive spelling
>with the same results.

Thursday, March 8, 2012

Could not find stored procedure.....SQL 2000

We are setting up a new server to replace a currently running SQL 2000
server. After restoring the database from a backup, when we attempt to log in
using a custom application, we get an error message stating "[Microsoft][ODBC
SQL Server Driver][SQL Server]Cound not find stored procedure
'drs_AuthenticateCurrentUser'. I can see that stored procedure listed in the
Stored Procedures subfolder in the restored database. I ran the restore from
Enterprise Manager just using the wizzard and had no issues when restoring.
Any ideas?
What user are you connecting as? What is that user's default database? Are
you sure you're executing in the right database? (A common problem is that
a connection string without a database specified would default to a user's
default database, but if the database is dropped/re-created/renamed...) Who
is the owner of the stored procedure? If it is dbo, did you try EXEC
dbo.drs_AuthenticateCurrentUser instead of EXEC drs_AuthenticateCurrentUser?
It is always a good idea to prefix object names both when creating and when
executing.
Aaron Bertrand
SQL Server MVP
"Jason Carter" <JasonCarter@.discussions.microsoft.com> wrote in message
news:0A96F5C3-EB54-46B7-A7B2-3EBAD3E9842B@.microsoft.com...
> We are setting up a new server to replace a currently running SQL 2000
> server. After restoring the database from a backup, when we attempt to log
> in
> using a custom application, we get an error message stating
> "[Microsoft][ODBC
> SQL Server Driver][SQL Server]Cound not find stored procedure
> 'drs_AuthenticateCurrentUser'. I can see that stored procedure listed in
> the
> Stored Procedures subfolder in the restored database. I ran the restore
> from
> Enterprise Manager just using the wizzard and had no issues when
> restoring.
> Any ideas?
|||Thanks for the reply Aaron....
I have tried a number of users including sa. sa's default database is
'master', but the other users I have tried have their default databases set
to MTCCashRecon which is where the stored procedure is located. I have also
verified the permissions for each of those users in that database is the same
as the ones on the old server. The owner of the stored procedure is dbo. I
have not tried to manually execute that procedure; I have only lanched this
from the application. I am nowhere near a SQL DBA and kind of got forced into
this one. I do not have access to the code and do not know if the stored proc
is being called as dbo.drs_authenticateCurrentUser or if it is being called
simply by the name; although I can say that the database was simply restored
from a .BAK file and I would have hoped that it would have just worked.
I have considered using the Data Transformation Sets to get the stored
procedures from the old server, but am not sure how that affects the old
server since it is still in use; does it lock the server or move any stored
procedures vs. just copying them.

Could not find stored procedure.....SQL 2000

We are setting up a new server to replace a currently running SQL 2000
server. After restoring the database from a backup, when we attempt to log i
n
using a custom application, we get an error message stating "[Microsoft]
[ODBC
SQL Server Driver][SQL Server]Cound not find stored procedure
'drs_AuthenticateCurrentUser'. I can see that stored procedure listed in the
Stored Procedures subfolder in the restored database. I ran the restore from
Enterprise Manager just using the wizzard and had no issues when restoring.
Any ideas?What user are you connecting as? What is that user's default database? Are
you sure you're executing in the right database? (A common problem is that
a connection string without a database specified would default to a user's
default database, but if the database is dropped/re-created/renamed...) Who
is the owner of the stored procedure? If it is dbo, did you try EXEC
dbo.drs_AuthenticateCurrentUser instead of EXEC drs_AuthenticateCurrentUser?
It is always a good idea to prefix object names both when creating and when
executing.
Aaron Bertrand
SQL Server MVP
"Jason Carter" <JasonCarter@.discussions.microsoft.com> wrote in message
news:0A96F5C3-EB54-46B7-A7B2-3EBAD3E9842B@.microsoft.com...
> We are setting up a new server to replace a currently running SQL 2000
> server. After restoring the database from a backup, when we attempt to log
> in
> using a custom application, we get an error message stating
> "[Microsoft][ODBC
> SQL Server Driver][SQL Server]Cound not find stored procedure
> 'drs_AuthenticateCurrentUser'. I can see that stored procedure listed in
> the
> Stored Procedures subfolder in the restored database. I ran the restore
> from
> Enterprise Manager just using the wizzard and had no issues when
> restoring.
> Any ideas?|||Thanks for the reply Aaron....
I have tried a number of users including sa. sa's default database is
'master', but the other users I have tried have their default databases set
to MTCCashRecon which is where the stored procedure is located. I have also
verified the permissions for each of those users in that database is the sam
e
as the ones on the old server. The owner of the stored procedure is dbo. I
have not tried to manually execute that procedure; I have only lanched this
from the application. I am nowhere near a SQL DBA and kind of got forced int
o
this one. I do not have access to the code and do not know if the stored pro
c
is being called as dbo.drs_authenticateCurrentUser or if it is being called
simply by the name; although I can say that the database was simply restored
from a .BAK file and I would have hoped that it would have just worked.
I have considered using the Data Transformation Sets to get the stored
procedures from the old server, but am not sure how that affects the old
server since it is still in use; does it lock the server or move any stored
procedures vs. just copying them.

Could not find stored procedure.....SQL 2000

We are setting up a new server to replace a currently running SQL 2000
server. After restoring the database from a backup, when we attempt to log in
using a custom application, we get an error message stating "[Microsoft][ODBC
SQL Server Driver][SQL Server]Cound not find stored procedure
'drs_AuthenticateCurrentUser'. I can see that stored procedure listed in the
Stored Procedures subfolder in the restored database. I ran the restore from
Enterprise Manager just using the wizzard and had no issues when restoring.
Any ideas?What user are you connecting as? What is that user's default database? Are
you sure you're executing in the right database? (A common problem is that
a connection string without a database specified would default to a user's
default database, but if the database is dropped/re-created/renamed...) Who
is the owner of the stored procedure? If it is dbo, did you try EXEC
dbo.drs_AuthenticateCurrentUser instead of EXEC drs_AuthenticateCurrentUser?
It is always a good idea to prefix object names both when creating and when
executing.
--
Aaron Bertrand
SQL Server MVP
"Jason Carter" <JasonCarter@.discussions.microsoft.com> wrote in message
news:0A96F5C3-EB54-46B7-A7B2-3EBAD3E9842B@.microsoft.com...
> We are setting up a new server to replace a currently running SQL 2000
> server. After restoring the database from a backup, when we attempt to log
> in
> using a custom application, we get an error message stating
> "[Microsoft][ODBC
> SQL Server Driver][SQL Server]Cound not find stored procedure
> 'drs_AuthenticateCurrentUser'. I can see that stored procedure listed in
> the
> Stored Procedures subfolder in the restored database. I ran the restore
> from
> Enterprise Manager just using the wizzard and had no issues when
> restoring.
> Any ideas?|||Thanks for the reply Aaron....
I have tried a number of users including sa. sa's default database is
'master', but the other users I have tried have their default databases set
to MTCCashRecon which is where the stored procedure is located. I have also
verified the permissions for each of those users in that database is the same
as the ones on the old server. The owner of the stored procedure is dbo. I
have not tried to manually execute that procedure; I have only lanched this
from the application. I am nowhere near a SQL DBA and kind of got forced into
this one. I do not have access to the code and do not know if the stored proc
is being called as dbo.drs_authenticateCurrentUser or if it is being called
simply by the name; although I can say that the database was simply restored
from a .BAK file and I would have hoped that it would have just worked.
I have considered using the Data Transformation Sets to get the stored
procedures from the old server, but am not sure how that affects the old
server since it is still in use; does it lock the server or move any stored
procedures vs. just copying them.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.
|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.
|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

Saturday, February 25, 2012

Could not create tempdb - SQL Server 2005 with SP1

I am receiving the following message within the Application Event Log on one
of my servers.
Could not create tempdb. You may not have enough disk space available. Free
additional disk space by deleting other files on the tempdb drive and then
restart SQL Server. Check for additional errors in the event log that may
indicate why the tempdb files could not be initialized.
I am also receiving this error:
The database 'model' is marked RESTORING and is in a state that does not
allow recovery to be run.
The strange thing about this message is that the server was working
correctly yesterday. The only thing that changed: The server was shut down
and moved to a new data center. Connectivity is in place because I can
connect to the box via Remote Desktop from work and from home.
This error is ONLYhappening on the default instance. There are two other
instances on the server (all three SQL Server installs are running under the
same network account).
There is enough free space on the volumes.
OS: 24GB free
internal array: 650 GB free
external array (MSA 500 G2): 900GB free
I even tried starting that instance in single user mode from the command
prompt via:
sqlservr -smssqlserver -c -f -m -T3608
This worked and I tried moving tempdb to the different volumes that are
available on the box. When I try to start SQL Server I receive the same
errors about model and tempdb and this instance fails to start.
I appreciate any assistance you can provide!
--
Keith KratochvilKeith Kratochvil wrote:
> I am receiving the following message within the Application Event Log on one
> of my servers.
> Could not create tempdb. You may not have enough disk space available. Free
> additional disk space by deleting other files on the tempdb drive and then
> restart SQL Server. Check for additional errors in the event log that may
> indicate why the tempdb files could not be initialized.
> I am also receiving this error:
> The database 'model' is marked RESTORING and is in a state that does not
> allow recovery to be run.
> The strange thing about this message is that the server was working
> correctly yesterday. The only thing that changed: The server was shut down
> and moved to a new data center. Connectivity is in place because I can
> connect to the box via Remote Desktop from work and from home.
>
> This error is ONLYhappening on the default instance. There are two other
> instances on the server (all three SQL Server installs are running under the
> same network account).
>
> There is enough free space on the volumes.
> OS: 24GB free
> internal array: 650 GB free
> external array (MSA 500 G2): 900GB free
> I even tried starting that instance in single user mode from the command
> prompt via:
> sqlservr -smssqlserver -c -f -m -T3608
> This worked and I tried moving tempdb to the different volumes that are
> available on the box. When I try to start SQL Server I receive the same
> errors about model and tempdb and this instance fails to start.
>
> I appreciate any assistance you can provide!
>
Hi
Check your logs(ldf) file size
regards
SW|||In addition to the errors that I mentioned (recorded within the Application
log), this error is within the System log:
The SQL Server (MSSQLSERVER) service terminated with service-specific error
1814 (0x716).
The error is written right after the entry that states:
The SQL Server (MSSQLSERVER) service entered the stopped state.
I tried starting SQL Server normally after telling it where to create tempdb
(via ALTER DATABASE ... MODIFY FILE...).
It would not start -- the same errors on model and tempdb are written to the
log.
Then I started SQL Server via the command line again
(sqlservr -smssqlserver -c -f -m -T3608).
It started (as before).
SQL crashes if I execute these commands:
sp_helpdb tempdb
select * From tempdb..sysfiles
I can execute these commands, however:
select * From master..sysdatabases where name = 'tempdb'
select * From master..sysaltfiles where name like 'temp%'
Here are the results:
name dbid sid mode status status2 crdate reserved category cmptlevel
filename version
tempdb 2 0x01 0 8 1090520064 2006-10-26 09:26:35.027 1900-01-01 00:00:00.000
0 90 E:\mssql\data\tempdb.mdf NULL
fileid groupid size maxsize growth status perf dbid name filename
1 1 1024 -1 10 1048578 0 2 tempdev E:\mssql\data\tempdb.mdf
2 0 64 -1 10 1048642 0 2 templog E:\mssql\data\templog.ldf
However tempdb's data and log files are are not on the disk. I searched for
them using Agent Ransack (as well as Windows Explorer).
--
Keith Kratochvil
"Sebastian" <sebastian@.waksmundzcy.com.pl> wrote in message
news:%23Bnb$FJGHHA.2456@.TK2MSFTNGP06.phx.gbl...
> Keith Kratochvil wrote:
>> I am receiving the following message within the Application Event Log on
>> one of my servers.
>> Could not create tempdb. You may not have enough disk space available.
>> Free additional disk space by deleting other files on the tempdb drive
>> and then restart SQL Server. Check for additional errors in the event log
>> that may indicate why the tempdb files could not be initialized.
>> I am also receiving this error:
>> The database 'model' is marked RESTORING and is in a state that does not
>> allow recovery to be run.
>> The strange thing about this message is that the server was working
>> correctly yesterday. The only thing that changed: The server was shut
>> down and moved to a new data center. Connectivity is in place because I
>> can connect to the box via Remote Desktop from work and from home.
>>
>> This error is ONLYhappening on the default instance. There are two other
>> instances on the server (all three SQL Server installs are running under
>> the same network account).
>>
>> There is enough free space on the volumes.
>> OS: 24GB free
>> internal array: 650 GB free
>> external array (MSA 500 G2): 900GB free
>> I even tried starting that instance in single user mode from the command
>> prompt via:
>> sqlservr -smssqlserver -c -f -m -T3608
>> This worked and I tried moving tempdb to the different volumes that are
>> available on the box. When I try to start SQL Server I receive the same
>> errors about model and tempdb and this instance fails to start.
>>
>> I appreciate any assistance you can provide!
> Hi
> Check your logs(ldf) file size
> regards
> SW|||Does that directory structure exist on the E Drive? Does the E: Drive
even exist'
What other databases were supposed to be on your E Drive?
Keith Kratochvil wrote:
> In addition to the errors that I mentioned (recorded within the Application
> log), this error is within the System log:
> The SQL Server (MSSQLSERVER) service terminated with service-specific error
> 1814 (0x716).
> The error is written right after the entry that states:
> The SQL Server (MSSQLSERVER) service entered the stopped state.
>
> I tried starting SQL Server normally after telling it where to create tempdb
> (via ALTER DATABASE ... MODIFY FILE...).
> It would not start -- the same errors on model and tempdb are written to the
> log.
> Then I started SQL Server via the command line again
> (sqlservr -smssqlserver -c -f -m -T3608).
> It started (as before).
> SQL crashes if I execute these commands:
> sp_helpdb tempdb
> select * From tempdb..sysfiles
>
> I can execute these commands, however:
> select * From master..sysdatabases where name = 'tempdb'
> select * From master..sysaltfiles where name like 'temp%'
> Here are the results:
> name dbid sid mode status status2 crdate reserved category cmptlevel
> filename version
> tempdb 2 0x01 0 8 1090520064 2006-10-26 09:26:35.027 1900-01-01 00:00:00.000
> 0 90 E:\mssql\data\tempdb.mdf NULL
>
> fileid groupid size maxsize growth status perf dbid name filename
> 1 1 1024 -1 10 1048578 0 2 tempdev E:\mssql\data\tempdb.mdf
> 2 0 64 -1 10 1048642 0 2 templog E:\mssql\data\templog.ldf
>
> However tempdb's data and log files are are not on the disk. I searched for
> them using Agent Ransack (as well as Windows Explorer).
> --
> Keith Kratochvil
>
> "Sebastian" <sebastian@.waksmundzcy.com.pl> wrote in message
> news:%23Bnb$FJGHHA.2456@.TK2MSFTNGP06.phx.gbl...
> > Keith Kratochvil wrote:
> >> I am receiving the following message within the Application Event Log on
> >> one of my servers.
> >> Could not create tempdb. You may not have enough disk space available.
> >> Free additional disk space by deleting other files on the tempdb drive
> >> and then restart SQL Server. Check for additional errors in the event log
> >> that may indicate why the tempdb files could not be initialized.
> >>
> >> I am also receiving this error:
> >> The database 'model' is marked RESTORING and is in a state that does not
> >> allow recovery to be run.
> >>
> >> The strange thing about this message is that the server was working
> >> correctly yesterday. The only thing that changed: The server was shut
> >> down and moved to a new data center. Connectivity is in place because I
> >> can connect to the box via Remote Desktop from work and from home.
> >>
> >>
> >>
> >> This error is ONLYhappening on the default instance. There are two other
> >> instances on the server (all three SQL Server installs are running under
> >> the same network account).
> >>
> >>
> >> There is enough free space on the volumes.
> >> OS: 24GB free
> >> internal array: 650 GB free
> >> external array (MSA 500 G2): 900GB free
> >>
> >> I even tried starting that instance in single user mode from the command
> >> prompt via:
> >> sqlservr -smssqlserver -c -f -m -T3608
> >> This worked and I tried moving tempdb to the different volumes that are
> >> available on the box. When I try to start SQL Server I receive the same
> >> errors about model and tempdb and this instance fails to start.
> >>
> >>
> >> I appreciate any assistance you can provide!
> >>
> >
> > Hi
> >
> > Check your logs(ldf) file size
> >
> > regards
> > SW

Could not create tempdb - SQL Server 2005 with SP1

Could not create an user to SQL Server 2005

Hi,

I am trying to add "Remote Desktop Users" as a login group to SQL Server 2005 (i.e. so they can log into management studio). I get a "Not Found Error" (see below). But it is of course found, because I selected it :-) What is going on here? I see the "Administrators" group and various SQL Server groupls added automatically there, so there must be a way, right?

I know I can add each user in the group individually, but that seems overkill when I can just use the group in which they are contained.

Here is the error I get:

TITLE: Microsoft SQL Server Management Studio

Create failed for Login 'TESTSERVER\Remote Desktop Users'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Windows NT user or group 'TESTSERVER\Remote Desktop Users' not found. Check the name again. (Microsoft SQL Server, Error: 15401)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476

BUTTONS:

This appears to be a defect within Management Studio: it qualifies the group using the machine name instead of "Builtin". I suggest that you open a bug at http://lab.msdn.microsoft.com/productfeedback/Default.aspx and put in it the information from this thread. Let me know if you need any help with filing the bug or if you wish that I would file it instead.

In the meantime, you can create such login by executing:

create login [Builtin\Remote Desktop Users] from windows;

Thanks
Laurentiu

|||Thank you Laurentiu. The script worked. I have indeed submitted a bug.|||Please note that I am the furthest thing from an expert that one can imagine, but...

I had a similar problem, but found an easy way to solve it.

Expand Security, right click Logins and select New Login
Click Search to the right of the Login Name box
Click the button Object Types
Select the box next to Groups|||

Hi ,

I am trying to create a new user in SQL Server 2005 with windows authentication.

This is the query i am trying to run.

create login [Builtin\User1] from windows

But i am getting error like "Windows NT user or group 'Builtin\waveset1' not found. Check the name again."

And the sql server is running on SQL and windows authuntication mode.

So anybody can help me what is the wrong.

I appreciate your response.

Thanks!

Tuesday, March 20, 2012

Could not start SQL Server

Could not start SQL Server

Could not set working set size to 1168512 KB

Monday, March 19, 2012

Could not locate file 'data01_log' in sysfiles

Thursday, March 8, 2012

Could not find stored procedure.....SQL 2000

Could not find stored procedure.....SQL 2000

Could not find stored procedure.....SQL 2000

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

Saturday, February 25, 2012

Could not create tempdb - SQL Server 2005 with SP1

Could not create tempdb - SQL Server 2005 with SP1

Could not create tempdb - SQL Server 2005 with SP1

Could not create an user to SQL Server 2005

Counter settings

Blog Archive

About Me