"Disable Check for SQL Express" against SQL Server Agent

Good afternoon,
Seeing as it has been a know issue for many years now[1],
is there a reason why Microsoft has yet to include a “Disable Check for SQL Express” override (similar to the
Automatic Configuration (& other) monitors) for each of the following objects included in the
Microsoft SQL Server Management Pack?
SQL Server Agent Windows Service (Monitor)
Discover SQL Server Agent for a DB Engine (Discovery)
This would prevent me from have to continually create overrides
disabling the monitor|discovery each time a new instance of SQL Express is installed in our Management Group.
Thanks,
Larry
[1]
http://jmkehayias.blogspot.ca/2009/01/sql-server-2008-express-sql-agent-won.html
http://sqlblogcasts.com/blogs/sqldbatips/archive/2008/06/28/sql-server-2008-express-installs-sql-agent-but-don-t-bother-trying-to-start-it.aspx

Hello,
This is much easier
http://blogs.technet.com/b/emreguclu/archive/2013/01/21/undiscovering-stop-monitoring-sql-2008-express-editions.aspx
just exclude sqlexpress
Regards
Mohammad, IT NOC Team

Similar Messages

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?
only below details found in error log
07:26:44.170 spid60
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:26:45.720 spid51
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
07:26:45.730 spid51
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:28:57.840 spid64
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
07:28:57.840 spid64
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
and below error on agent log
2014-01-01 07:26:28 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2014-01-01 07:26:43 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
2014-01-01 07:26:44 - + [098] SQLServerAgent terminated (forcefully)
Rahul

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?
only below details found in error log
07:26:44.170 spid60
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:26:45.720 spid51
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
07:26:45.730 spid51
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:28:57.840 spid64
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
07:28:57.840 spid64
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
and below error on agent log
2014-01-01 07:26:28 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2014-01-01 07:26:43 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
2014-01-01 07:26:44 - + [098] SQLServerAgent terminated (forcefully)
Rahul
Can you post the output of below query
select @@version.
If you are using SQl server express edition ,SQL server agent feature is not available.It seems from errorlog that you can start it but actually you cannot.But first confirm what is version and edition of your SQL server
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?
This has been a very common question I have seen relatedt to Database mail and I thought will post here so if you run into this issue, it could be due to one of the following and also have mentioned below how to get around them. Bottom line is datbase mail works fine with SQL Agent jobs and maintenace plans in SP1 on all platforms.
1. If you see this on 64 bit platform and on RTM build, this is a bug that is addressed in SP1.
2. If you see the below error message, it is known issue and this is because of design that requires SQL Agent to restart, if SQL Agent was started before enabling databasemail and setting a new profile. We are evaluating to change this design of not requiring to restart agent for our future release.
Re: 264] An attempt was made to send an email when no email session has been established
This problem will go away after restarting SQL Server Agent in this case. Thanks,
Gops Dwarak, MSFT

This may be related to the fact that DBMail, by default, shuts itself down after 10 minutes of inactivty. If the mail service isn't running, you won't be able to queue up any mail messages.
There may be a built-in mechanism for addressing this problem, but I found that I can detect this situation and start the mail listener before sending db mail. I use the following in stored procs that need to send email.
You could increase the inactivity period for db mail shutdown from 600 seconds to some larger value.  It might not make sense to do so, since shutting it down releases its resources back to teh system; if your SQL server only sneds mail infrequently, it might be better to start the mail listener on demand. Someone with more experience than I might want to add their two cents' worth. :-)
/* Check the mail engine. Start the service if is is stopped         */
/* -- the DB Mail engine shuts down after 10 minutes (of inactivity) */
/* -- this setting can be changed, but we probably don't need to.    */
DECLARE @rc INT
IF NOT EXISTS (SELECT * FROM msdb.sys.service_queues
               WHERE name = N'ExternalMailQueue' AND is_receive_enabled = 1)
    EXEC @rc = msdb.dbo.sysmail_start_sp
    -- TODO: add handling and logging for any engine start issues

Logs for sql server agent restart

Hi,
Can I get log on the sql server agent restart history of week. I mean the sql server agent has been restarted several times in last week I want to know the date and time when the sql server agent restarted in that week. Is it possible to get
the info?
Thanks in advance,
Pavan
Pavan

In addition to Uri's post, here is some more information that might help you:
SQLAGENT.OUT, the log file for SQL Agent. SQL Server Agent can maintain up to 10 Error Logs files. The currently used SQL Server Agent Error Log will be named SQLAGENT.OUT
where is the SQLAGENT.OUT file?
C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\Log\
What will be when a new file create?
The old file should get a name like SQLAGENT.X and the new file get the name SQLAGENT.OUT (X is numbers 1-9)
This can help you to get more information on sql agent properties (like the location of the log file, the user that start the service and more):
EXEC msdb..sp_get_sqlagent_properties
[Personal Site] [Blog] [Facebook]

Service Account for SQL Server Agent on SQL Server 2008 R2

This SQL Server instance is SQL Server 2008 R2 (10.50.4000). We had Active Domain Service accounts created to run the service accounts for SQL Server and SQL Server Agent.
It has become company policy to alter the service accounts that run SQL Server and SQL Server Agent. Currently, both were running under the Local System Accounts. We have altered the SQL Server but we are having issues with the SQL Server Agent.
I am told by another DBA that
"The agent is requiring elevated rights. It will startup if it has local admin rights, but not with domain accounts without admin rights."
So I was wondering if anyone has come across this issue and how did they resolve it.
lcerni

"The agent is requiring elevated rights. It will startup if it has local admin rights, but not with domain accounts without admin rights."
This is completely not true. It is indeed possible to run agent as a domain account without giving it local admin. Chances are you'll need to update the local acls by adding the account to the local security groups. Please see this article for more information:
http://technet.microsoft.com/en-us/library/ms143504(v=sql.105).aspx
Edit: In addition, it'll need rights to SQL server for that account to connect and do its work. It will need to be given sysadmin:
http://technet.microsoft.com/en-us/library/ms191543.aspx
Sean Gallardy | Blog |
Twitter

Using the SQL Server Agent for the first time

I have set up several jobs to run automatically throughout the day. Each job just does one thing: executes an SSIS package.
The packages themselves run perfect when I test them in Visual Studio 2005, but when the SQL Server Agent tries to run the job I am getting failed jobs.
Is there any tutorials or walkthroughs that can teach my about using the SQL Server Agent? If I wanted extensive help troubleshooting my SQL Server Agent problems which part of the message boards would I post that too?
Thanks for the info!

Anyone?
I really need some resources for SQL Server Agent 2005.
Refer these links,
http://technet.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
http://stackoverflow.com/questions/10489392/permissions-issue-running-ssis-package-from-sql-job
Regards, RSingh

Permissions needed for sql server job to execute stored procedure on linked server?

Hi all
I have a job step which attempts to call a stored procedure on a linked server.
This step is failing with a permission denied error. How can I debug or resolve this?
The job owner is sysadmin on both servers so should have execute permission to the database/proc I'm calling, right?
The error is:
The EXECUTE permission was denied on the object 'myProc', database 'myDatabase', schema 'dbo'. [SQLSTATE 42000] (Error 229). The step failed.
My code is:
EXEC [LinkedServer].myDatabase.dbo.myProc
Also tried:
SELECT * FROM OPENQUERY([LinkedServer], 'SET FMTONLY OFF EXEC myDatabase.dbo.myProc')
With the same result.
Any help appreciated.

The job owner may be sysadmin on the remote server. The service account for SQL Server Agent may not. And it is the latter that counts, since the it the service accounts that logs in and impersonates the job owner. But the impersonation inside SQL Server
does not count much in Windows, and it is through Windows connection is made to the other site.
One way to resolve this is to set up a login mapping for the job owner. The login mapping must be for an SQL login on the remote server.
You can verify the theory, but running this query from the job:
SELECT * FROM OPENQUERY([LinkedServer], 'SELECT SYSTEM_USER')
By the way, putting SET FMTONLY OFF in OPENQUERY is a terrible idea. This has the effect that the procedure is executed twice. (Unless both servers are SQL 2012 or higher in which case FMTONLY has no effect at all.)
Erland Sommarskog, SQL Server MVP, [email protected]

Replication stopp after change changing SQL Server Agent User

Hi,
I tryed to change the user for SQL Server Agent on my Distributor. We use pushed transaction replications. But after i changed the user, all replications stopped:
ERROR: (from SQL Monitor)
The job failed. The Job was invoked by Start Sequence 0. The last step to run was step 3 (Detect nonlogged agent shutdown.).
The new user is a domainusert too, and had administrative rights on the server. I changed the user to start SQL Server Agent on other servers without error.
Can anybody tell me, how to change the user on a distributor, without stopping all replications?
Thanks
Kind regards,
Andreas

Hi Andreas,
You are likely running into a permissions issue.
Verify the Log Reader Agent process account is db_owner in the distribution database and that the account used to connect to the Publisher is db_owner in the publication database.
Verify the Distribution Agent process account is db_owner in the distribution and subscription databases, is a member of the PAL, and has read permissions on the snapshot share.
This is covered in
Replication Agent Security Model.
Brandon Williams (blog |
linkedin)

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

I am geeting problem whem i run bulk insert query i got error Location:_ bcpimp.cpp:1797 Expression:_ cbOutTemp cbOutputStr SPID:__ 52 Process ID:_ 2364 Msg 3624, Level 20, State 1, Line 3 A system assertion check has failed. Check the SQL Server error

Location: bcpimp.cpp:1797
Expression: cbOutTemp < cbOutputStr
SPID: 52
Process ID: 2364
Msg 3624, Level 20, State 1, Line 3
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

If you check your sql server error log folder you will see dump files created. You need to send those dump files to Microsoft for inspection because outside of microsoft product support the symbols for reading the dumps are not available without which it
wont be easy to find the issue.
http://support.microsoft.com/kb/2028589
In the meantime check if you are on the latest version of Service Pack and if not apply the latest service pack. Majority of these kind of assertions are bugs which are solved in Service Packs/Cumulative Updates.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Tutorials for SQL Server Express?

Hello!
Where can I find good (if possible video) tutorials for SQL Server Express 2012?
I saw several commercial tutorial DVDs, but those are not for the Express edition. :(
Thank you!

Hello!
Where can I find good (if possible video) tutorials for SQL Server Express 2012?
I saw several commercial tutorial DVDs, but those are not for the Express edition. :(
Thank you!
Hello,
As Olaf said SQL server basic functioning remains same for all its features point here is express edition does not support all features.If you create 2 basic queries express and enterprise theay both will return same result.So I would suggest keep reading
tutorials you find out
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Analysis Server for sql server 2008 r2 express?

Not sure if this is a forum where I could ask about how I could obtain analysis server for sql server 2008 R2 express - only for academic purposes (not doing any production stuff - just getting up to speed on OLAP, creating fact tables, star schema,
snowflake schema, ...). Suggestions appreciated how I may obtain a version of analysis server for sql server 2008 R2 Express -- or if this is not a good forum to ask that question then I would be grateful for being pointed to the proper forum.
Thanks
Rich P

SQL Express Edition Doesn't support analysis services.
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx#SSAS
As Li said, you need to go with the developer edition.
-Prashanth

Problem to create "New Database Diagram" in Microsoft SQL Server Management Studio for SQL Server 2012 SQL Express

Hi,
I have installed SQL Server 2012 Express edition (name of installation media: en_sql_server_2012_express_edition_with_advanced_services_x64.exe) from MSDN and I have installed the application on my pc with Windows 7 Exterprise.
Everything is working fine except when I am trying to create "New Database Diagram", where I recieve following error message:
TITLE: Microsoft SQL Server Management Studio
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft.VisualStudio.OLE.Interop)
BUTTONS:
OK
I have tried two times to reinstall SQL Server 2012 Express and I have installed Cumulative Update #3 for SQL Server 2012 and restarted the machine, but I have still the same problem with the same error message.
Installed the following fixes:
1) 2012_RTM_DAC_CU3_2723749_11_0_2332_x64
2) SQLServer2012_RTM_CU3_2723749_11_0_2332_x64
These files was installed successful.
How can I solve the problem?
BR
Jan Nilsson

Hi Jan,
Have you installed Visual Studio in your machine?
The problem seems to be related to installing and uninstalling the VS 2011 RC0 program.
The workaround involves copying the files from another PC with SQL 2008 or 2012 from one machine to another. Just replace this folder:
C:\Program Files (x86)\Common Files\microsoft shared\MSDesigners8
See also the following for further details:
http://social.msdn.microsoft.com/Forums/en-GB/vstsdb/thread/d65c71f5-3887-4f2a-bbd3-e799a4ac6fdc
Best Regards,
Iric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Security Update for SQL Server 2005 SP3 (KB2494113) failed

Here is the Error, Can't get the update install, please help.
KB Number: KB2494113
Machine: MJA01
OS Version: Server 4.0 Service Pack 1 (Build 7601)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4060
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (BKUPEXEC) ENU SP3 2005.090.4035.00 x86 EXPRESS
SQL Server Tools and Workstation Components 2005 ENU SP2 9.2.3042 x86 EXPRESS
Products Disqualified & Reason
Product Reason
SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 4035 installed. Update 4060 is dependent on prerequisite update 4035. Exit setup and refer to the Knowledge Base article to find the prerequisite
patch. Install the prerequisite and rerun the installation.
Processes Locking Files
Process Name Feature Type User Name PID
Product Installation Status
Product : SQL Server Database Services 2005 (BKUPEXEC)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Product : SQL Server Tools and Workstation Components 2005
Product Version (Previous): 3042
Product Version (Final) :
Status : NA
Log File :
SQL Express Features :
Error Description : The product instance SQL Tools does not have prerequisite update 4035 installed. Update 4060 is dependent on prerequisite update 4035. Exit setup and refer to the Knowledge Base article to find the prerequisite
patch. Install the prerequisite and rerun the installation.
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29528

Hi Bhanu,
I have uninstall the SQL Server Tools and Workstation Components 2005.
But still unable to upg the SQL Server with the KB249411. Any more ideas?
This is the Summary log.
Time: 09/10/2014 11:09:48.218
KB Number: KB2494113
Machine: MJA01
OS Version: Server 4.0 Service Pack 1 (Build 7601)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4060
Command-line parameters specified:
Cluster Installation: No
Prerequisites Check & Status
SQLSupport: Passed
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (BKUPEXEC) ENU SP3 2005.090.4035.00 x86 EXPRESS
Products Disqualified & Reason
Product Reason
Processes Locking Files
Process Name Feature Type User Name PID
Product Installation Status
Product : SQL Server Database Services 2005 (BKUPEXEC)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29528
Here is what is log in the SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files (x86)\Common Files\
MSI (s) (B8:F0) [11:09:39:826]: Product: Microsoft SQL Server 2005 Express Edition - Update 'GDR 4060 for SQL Server Database Services 2005 ENU (KB2494113)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program
Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log.
MSI (s) (B8:F0) [11:09:39:827]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.3.4035.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: GDR 4060 for SQL Server Database
Services 2005 ENU (KB2494113). Installation success or error status: 1603.
MSI (s) (B8:F0) [11:09:39:828]: Note: 1: 1729
MSI (s) (B8:F0) [11:09:39:828]: Product: Microsoft SQL Server 2005 Express Edition -- Configuration failed.
MSI (s) (B8:F0) [11:09:39:829]: Windows Installer reconfigured the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.3.4035.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error
status: 1603.
MSI (s) (B8:F0) [11:09:39:829]: Attempting to delete file C:\Windows\Installer\63906e.msp
MSI (s) (B8:F0) [11:09:39:829]: Unable to delete the file. LastError = 32
MSI (s) (B8:F0) [11:09:40:092]: Deferring clean up of packages/files, if any exist
MSI (s) (B8:F0) [11:09:40:092]: Attempting to delete file C:\Windows\Installer\63906e.msp
MSI (s) (B8:F0) [11:09:40:094]: MainEngineThread is returning 1603
MSI (s) (B8:6C) [11:09:40:097]: RESTART MANAGER: Session closed.
MSI (s) (B8:6C) [11:09:40:097]: No System Restore sequence number for this installation.
=== Logging stopped: 9/10/2014 11:09:39 ===
MSI (s) (B8:6C) [11:09:40:098]: User policy value 'DisableRollback' is 0
MSI (s) (B8:6C) [11:09:40:098]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:6C) [11:09:40:098]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B8:6C) [11:09:40:098]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (B8:6C) [11:09:40:099]: Restoring environment variables
MSI (s) (B8:6C) [11:09:40:099]: Destroying RemoteAPI object.
MSI (s) (B8:30) [11:09:40:099]: Custom Action Manager thread ending.
MSI (c) (FC:60) [11:09:40:100]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (FC:60) [11:09:40:101]: MainEngineThread is returning 1603
Thanks,
Alice

HotFix4 for SQL Server 2005 doesn't work

I am having problems getting a machine running SQL Server 2008 R2 (Express) to connect to a SQL Server 2005 (Full Standard Edition) DB on another machine via the LAN. It times out when connecting from a C# application. SSMS on the SQL 2008 machine
connects fine, but SSMS on the 2005 machine (connecting to a copy of the same DB on the 2008 machine) says it isn't supported and I need a hotfix.
I downloaded the hotfix link from Microsoft, but when I paste it into the Browser I get a DNS name failure for the Hotfix4 server. I don't want to paste the full link here because it is not made public by MS and you need to request it. However, the
first part of the URL is: http://hotfix4.microsoft.com/SQL%20Server%202005...etc.
I have checked out all of the obvious things in both instances (2005 AND 2008)... Both instances are configured to accept remote connections, both have TCP/IP and named pipes protocols enabled, both are running fine for local connections, both have the SQL
Browser enabled and the Computer Browser Service running on the network.
As the hot fix doesn't install, I am kind of out of ideas.
Any suggestions?
Thanks,
Pete
I used to write COBOL... now I can do anything.

SQL 2005 is out of
mainstream support:
SQL Server
2005
SP4
04/12/2011
04/12/2016
Technical support continues till 04/12/2016, yet mainstream (hotfix) support ends as of 04/12/2011; options
for hotfix support after 04/12/2011:
ð  Continue
with self-help
ð  Upgrade
to the latest supported service pack for SQL Server 2005 or SQL Server 2008 or SQL Server 2008 R2
ð  Extended
hotfix support agreement
SP4 and CU3 are still available for download, if this helps...
http://support.microsoft.com/kb/2507769
http://www.microsoft.com/en-US/download/details.aspx?id=7218
But you should update your SQL-Server..... SQL 2014 is the latest version

"Disable Check for SQL Express" against SQL Server Agent

Similar Messages

Maybe you are looking for