Alerts Not Working

I defined an Alert in Enterprise Manager for Severity 19 - Fatal Error In Resource. The alert is enabled, the type is "sql server event alert" and the alert is defined against a specific database. SQLSERVERAGENT and SQL Mail session are both started. I test the alert using the following statement in the specified database.

raiserror (50001,19,1) with log

A message is placed in the SQL Server log, however no alert is fired. The alert history indicates the alert has never occurred. What am I missing?

Thanks, DaveHere's an update.

I refreshed EM earlier in the day and still saw no history. This time I disconnected and reconnected the instance. For some reason I have to do this in certain situations. After reconnecting I noticed a history existed under a demo for Severity 19. I didn't realize the demos were enabled. I just disabled the demo alert and all appears to be working.

Thanks, Dave|||all the demos are enabled for each of the severity levels if you are defining errors soley based on severity they will as you found out hit first
also ...
[BOL] Says

Error messages with a severity level of 19 or higher stop the current batch. Errors messages with a severity level of 20 or higher are considered fatal errors and terminate the client connection. Errors messages in this range may affect all of the processes in the database, and may indicate that a database or object is damaged. Error messages with a severity level from 19 through 25 are written to the error log.

you might want to consider refining your alert to fire on the event id's that are acutally being thrown..
just a suggest

by the way good debugging on your part.|||The error message I'm seeing is being generated by a vendor's software package.

Error: 1204, Severity: 19, State: 1
The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration..

There are multiple performance problems associated with this application. I suspect the error above is connected to many of the problems. I don't believe the database is damaged. I'm guessing it's just a matter of poorly written code. Now I have to figure out how to setup Profiler to look for this error.

Thanks, Dave|||http://www.sql-server-performance.com/deadlocks.asp to prevent deadlocks and error defined.

Ensure to run the statement in batches if it is affecting large number of rows. Another option is to specify a hint like table or page lock so that the number of locks can be reduced.

What are lock settings defined at SQL server?|||The lock setting is still at the default of 0. I'm not sure what code is causing this problem to occur. I need to setup Profiler to trap the logic. I just setup Profiler to look for Severity 19, but the filter does not appear to be working. I'm still seeing all server activity. Am I missing something?

- Filters
- Severity
- Equals 19

Dave|||Oh, then follow this link http://www.sql-server-performance.com/blocking.asp to monitor the blocking and capture the trace.|||Not missing much about profiler. Any null value is returned as a valid hit. You may want to just run profiler to a table with the SQL statement complete, RPC complete, and some of the error events getting logged. Once you have a pile of data in a table, you can run queries off of that for severity 19, then try to work back via the identity column to figure out what statement did it.|||Can you tell Profiler to ignore NULL?

I'll give your suggestion a try.

Thankssql

After upgrade MSDE Sp4 Can't connect it through Enterprise Manager

Hi,
I have upgrade MSDE to SP4, but can't connect it throught enterprise manager
after upgrade.
How can I fix it?
Thanks,
Tiger
hi Tiger (Oracle user? :D ),
Tiger wrote:
> Hi,
> I have upgrade MSDE to SP4, but can't connect it throught enterprise
> manager after upgrade.
actually you shoud have no technical problem (but legal)...
what kind of exception are you reported with when trying connection to MSDE
instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||No, I'm not use Oracle
I just use SQL Server Enterprise Manager to connect client PC MSDE, but
after upgrade MSDE to SP4, then fail to connect.
Tiger
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ngm9cF1ecmrU1@.individual.net...
> hi Tiger (Oracle user? :D ),
> Tiger wrote:
> actually you shoud have no technical problem (but legal)...
> what kind of exception are you reported with when trying connection to
> MSDE instance?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Tiger,
Tiger wrote:
> No, I'm not use Oracle
>
that was a joke, as Scott / Tiger are the "default" sample credentials for
accessing Oracle

> I just use SQL Server Enterprise Manager to connect client PC MSDE,
> but after upgrade MSDE to SP4, then fail to connect.
what kind of exception are you reported with when trying connection to MSDE
instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On Mon, 29 Aug 2005 17:01:01 +0200, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

> hi Tiger (Oracle user? :D ),
> Tiger wrote:
> actually you shoud have no technical problem (but legal)...
Legal problem?
I thought a SQL Server Developer Edition license ($39 or free with MSDN)
allows you to use Enterprise Manager to configure your development copies
of MSDE.
Managing production copies is another matter, but Tiger never mentioned
that.
|||hi,
Lucvdv wrote:
> Legal problem?
> I thought a SQL Server Developer Edition license ($39 or free with
> MSDN) allows you to use Enterprise Manager to configure your
> development copies of MSDE.
> Managing production copies is another matter, but Tiger never
> mentioned that.
if you install SQL Server Dev Edition (for dev and test) you already have a
full SQL Server instance and should not require MSDE at all, but I must
confess as well I've both installed on the same dev pc for my own tests/dev
tasks...
as regard the "legal" problem, I always refer to http://tinyurl.com/ac3v2 ,
where Steve presents a good metaphor about using SQL Server Client Tools
against MSDE in production...
then it's all up to you...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi!
I had the same problem - it seems that SP4 changes the server port ... check
this in server network utility.
greeting
Lukas
"Tiger" <tigerwong666@.hotmail.com> schrieb im Newsbeitrag
news:OBwjydHrFHA.3216@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have upgrade MSDE to SP4, but can't connect it throught enterprise
> manager after upgrade.
> How can I fix it?
> Thanks,
> Tiger
>

After installing SP2 SSRS will not start

Installed SP2 and now SSRS will not start.

Errors:

At Report Manager URL: The report server is not responding. Verify that the report server is running and can be accessed from this computer. At Report Server URL: The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError) Access to the path '<DRIIVE>\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\RSReportServer.config' is denied. In SSS Log Files: ReportingServicesService!library!8!6/20/2007-16:04:04:: i INFO: Current DB Version C.0.8.40, Instance Version C.0.8.54.
ReportingServicesService!library!8!6/20/2007-16:04:04:: i INFO: Starting upgrade DB version from C.0.8.40 to C.0.8.54.
ReportingServicesService!library!8!6/20/2007-16:04:04:: e ERROR: Exception caught while starting service. Error: System.Data.SqlClient.SqlException: Could not locate entry in sysdatabases for database 'PD'. No entry found with that name. Make sure that the name is entered correctly.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script)
at Microsoft.ReportingServices.Library.ConnectionManager.EnsureCorrectDBVersion()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread()
ReportingServicesService!library!8!6/20/2007-16:04:04:: e ERROR: Attempting to start service again...

When I go to the RS Configurator the Database is reported as .40 and the Upgrade Button results in an upgrade success but the Database stays the same version.

Joy....

Much help needed and appreciated....

-p

Since the upgrade went so horribly I created a NEW SSRS database using the SSRS Configuation Tool. I also had to change the permission the '<DRIIVE>\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\RSReportServer.config' file. I have NO idea why the services could r/w from the file before the upgrade and not afterwards that actually scares me the most about this because the SQL team can't fix my box with a QFE. The database upgrader is clearly buggy and that scares me as well, but I bet the SQL team could fix that and repair turfed databases via script.

The impact of doing this meant I had to re-do the following things:

Re-set all Permissions and Site Settings (I had customized the My Reports role) Recreate all Folders and Permissions. (I have top level folders and grant rights there not at the HOME folder). Re-publish all reports (for me and all my "My Users") Re-set passwords on Data Sources which needed them. Inform users all subscriptions were lost