SQL Server Delete statements failing

Hello,
I am using SQL 2012 SE and I have been using a purge job that deletes data older than 5 days from 4 table in a database. The job had been running fine and deleting older data for the past 5 years and it failed for the first time today with the following
error:
Time-out occurred while waiting for buffer latch type 2 for page (1:15945892), database ID 6
I am not seeing any deadlocks at the time the job failed. What caused this job to fail?
How can this be prevented? Experts need your valuable inputs.
Thanks

That's not really a normal error, and it's not trivial to diagnose. Hasrh Kumar was kind to point you to a fix for one situation where this error can occur. Unfortunately, that fix is for SQL 2008 and you are on SQL 2012, so that is not of any help for you.
My advice would be to restart SQL Server, and if the problem does not reoccur, forget it. If it comes back, my suggestion would be to open a case with Microsoft to have this resolved. I found a blog post where someone had run into this error:
http://sqlblog.com/blogs/michael_zilberstein/archive/2013/03/22/48339.aspx
but the steps the author applies are not exactly trivial.
It is a important to understand that this message is an indication that things are not what they are supposed to be, but what is the exact root cause is not apparent.
Erland Sommarskog, SQL Server MVP, [email protected]
The thing is the job is a weekly once job. It failed for the first time on saturday night and then I reran it last night and it failed again.

Similar Messages

Problem : SQL Server Delete Statement vs Oracle Delete Statement

Hi,
I am currently involved in a SQL Server - Oracle Migration effort and I have hit a roadblock on one of the queries.
I have created two tables named DUMMY and DUMMY1 in MSDE with the same structure :-
CREATE TABLE DUMMY
     CLIENT_ID                                             INT,
     NME                                                   VARCHAR(80),
     BATCH_ID                                              INT,
     CATALOG_NAME                                          VARCHAR(50),
     DATA_SOURCE                                           VARCHAR(50)
GOI have a DELETE statement that deletes from the two tables, by selecting common data using Joins:-
DELETE DUMMY
FROM      DUMMY src
        JOIN
     DUMMY1 dst
          ON
              src.batch_id = dst.batch_id
          AND src.catalog_name = dst.catalog_name
          AND src.data_source = dst.data_source
     WHERE
               src.batch_id     = 1
          AND      src.catalog_name = '1'
              AND      src.data_source = '1'Now, I have created the same Tables ( DUMMY and DUMMY1 ) in Oracle :-
CREATE TABLE DUMMY
     CLIENT_ID                                             NUMBER(5),
     NME                                                      VARCHAR2(80),
     BATCH_ID                                             NUMBER(10),
     CATALOG_NAME                                  VARCHAR2(50),
     DATA_SOURCE                                     VARCHAR2(50)
)I have written a Delete statement to mimic the fucntionality in this manner :-
DELETE FROM
          DUMMY
WHERE
               client_id,
               nme,
               batch_id,
               catalog_name,
               data_source
          IN
               SELECT *
               FROM
                    DUMMY src
                                       JOIN
                    DUMMY1 dst
                         ON
                              src.batch_id = dst.batch_id
                         AND      src.catalog_name = dst.catalog_name
                         AND      src.data_source = dst.data_source
                    WHERE
                              src.batch_id = 1
                         AND      src.catalog_name= '1'
                         AND      src.data_source = '1'
          )However, I keep getting this error whe I try to test it :-
ORA-06550: line 1, column 89:
PL/SQL: ORA-00913: too many values
Can you please help me modify the query to simulate the same functionality as the orignial SQL Server Query ?
Thanks,
Sandeep

There is probably a mismatch between the number of columns.
Try this * Not Tested *
DELETE FROM
          DUMMY
WHERE
               client_id,
               nme,
               batch_id,
               catalog_name,
               data_source
          IN
               SELECT      src.client_id,
               src.nme,
               src.batch_id,
               src.catalog_name,
               src.data_source
               FROM
                    DUMMY src
                                       JOIN
                    DUMMY1 dst
                         ON
                              src.batch_id = dst.batch_id
                         AND      src.catalog_name = dst.catalog_name
                         AND      src.data_source = dst.data_source
                    WHERE
                              src.batch_id = 1
                         AND      src.catalog_name= '1'
                         AND      src.data_source = '1'
          );

Official documents on escaping characters in SQL Server query statements

Hi,
Are there any official documents on how to escaping special characters in SQL Server query statements? I find a lot of online resources discussing about this, but there are no definitive conclusions on:
Which characters should be escaped? (Some only said single-quote needs to be escaped, double-quote does not need. While others said both need to be escaped)
How to escape characters? (Some said using two single-quote to escape a single-quote. Others said using a backslash, etc.)
So I just wonder if there is an official document from Microsoft regarding this?
Thanks
Alan

Depends on where you're using them
If its string values then single quotes(') should be escaped by putting one more single quote before it.
If its LIKE operator you can use ESCAPE keyword or use [] to escapre special characters
see
http://visakhm.blogspot.in/2013/01/wildcard-character-based-pattern-search.html
If inside SSIS expression you can escape characters like \ " etc by adding an extra \ before the characters
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL Server Agent job fails with error : The package execution returned DTSER_FAILURE (1).

Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
at Teradata.Client.Provider.WpMessageManager.CheckForError()
at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
at Teradata.Client.Provider.WpLogonManager.Action()
at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
at Teradata.Client.Provider.TdConnection.Open()
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
Elapsed: 6.692 seconds. The package execution failed. The step failed.
SQL Server agent job fails with above error, Please let me know process tohandle it.
Thanks,
Vishal.

The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL Server 2008 KB2977321 Failed with Error code 1642

As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?

I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No

Setting up Multi server environment in Sql Server 2012 - Enlist Failed Error

I am trying to Configure the Master target server / Multi server environment in Sql Server 2012.
I changed :
- `MSXENCryptChannnelOptions`-->Changed from 2 to 0
- `AllowDownloadedJobsToMatchProxyName` - changed from 0 to 1 on the target
When I run the wizard I am getting below error
>MSX Enlist failed for Job Server 'MasterServerName'
>The enlist operation Failed(Reason:SQL Server Agent Error: Unable to connect to MSX 'MasterServerName'(Microsoft Sql Server, Error : 22026)
They both servers SQL Agents are running on the same windows service account.
Any Suggestions on how to fix this?
**Adding the Log:**
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'Test3' is running (Success)
The service 'SQLSERVERAGENT' is running.
- Ensure the agent startup account for 'Test4' has rights to login as a target server (Success)
Checking to see if the startup account for 'Test4' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.
- Enlist 'Test4' into 'Test3' (Error)
Enlisting target server 'Test4' with master server 'Test3'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'Test4'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'TEST3'.) (Microsoft SQL Server, Error: 22026)

hi SmilingLily,
you can try to run the SQL Agent under a domain account.

Upgrade to SQL Server 2008 R2 fails

I'm trying to upgrade from SQL Server 2008 Express to SQL Server 2008 R2 Enterprise. The installation is failing. I get two log files. The first appears to be a summary. The second is an MSI install log file. The MSI log is too large to paste in here and
I cannot attach files, so I included the section where it appears to fail. Based on the log contents below, how can I fix this?
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068024447
Exit facility code:            1212
Exit error code:               29569
Exit message:                  Failed: see details below
Start time:                    2015-04-06 21:07:14
End time:                      2015-04-06 21:13:54
Requested action:              Upgrade
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\sql_engine_core_inst_ctp6_Cpu64_1.log
Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  DAD-PC
Machine processor count:       12
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
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services
1033                 Express Edition      10.3.5500.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.3.5500.0     No
Sql Server 2008
Management Tools - Basic                 1033                 Express Edition
10.0.1600.22    No
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         H:\x64\setup\
Installation edition:          ENTERPRISE
User Input Settings:
ACTION:                        Upgrade
AGTDOMAINGROUP:                <empty>
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                True
FAILOVERCLUSTERROLLOWNERSHIP: 2
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
FTUPGRADEOPTION:               Import
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTANCEID:                    SQLEXPRESS
INSTANCENAME:                  SQLEXPRESS
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSCATALOGSERVERINSTANCENAME:   Unknown
RSUPGRADEDATABASEACCOUNT:
RSUPGRADEPASSWORD:             *****
SQLDOMAINGROUP:                <empty>
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Writer
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Browser
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Compact Edition Tools
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150406_210629\SystemConfigurationCheck_Report.htm
PARTIAL MSI LOG BELOW
Action start 21:13:47: AppSearch.
MSI (s) (40:00) [21:13:47:914]: Note: 1: 1325 2: v2.0.50727
MSI (s) (40:00) [21:13:47:914]: Note: 1: 1325 2: EventLogMessages.dll
MSI (s) (40:00) [21:13:47:914]: PROPERTY CHANGE: Adding ASPNET_EVENTLOGDLL property. Its value is 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\EventLogMessages.dll'.
MSI (s) (40:00) [21:13:47:915]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\\Setup 3: 2
MSI (s) (40:00) [21:13:47:915]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FBD367D1-642F-47CF-B79B-9BE48FB34007} 3: 2
MSI (s) (40:00) [21:13:47:915]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_32 property. Its value is 'C:\Program Files (x86)\Microsoft SQL Server\'.
MSI (s) (40:00) [21:13:47:916]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_64 property. Its value is 'C:\Program Files\Microsoft SQL Server\'.
MSI (s) (40:00) [21:13:47:916]: PROPERTY CHANGE: Adding DEVENV_IDE8 property. Its value is 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\'.
MSI (s) (40:00) [21:13:47:917]: PROPERTY CHANGE: Adding SQLSETUPARPWRAPPER property. Its value is 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release\x64\SetupARP.exe'.
MSI (s) (40:00) [21:13:47:917]: Doing action: RestoreSetupParams_64
Action ended 21:13:47: AppSearch. Return value 1.
MSI (s) (40:00) [21:13:47:920]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'RestoreSetupParams_64'
MSI (s) (40:C0) [21:13:47:921]: Invoking remote custom action. DLL: C:\Windows\Installer\MSICCED.tmp, Entrypoint: RestoreSetupParams
Action start 21:13:47: RestoreSetupParams_64.
<Func Name='LaunchFunction'>
Function=RestoreSetupParams
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: RestoreSetupParams
PerfTime Start: RestoreSetupParams : Mon Apr 06 21:13:47 2015
<Func Name='RestoreSetupParams'>
        Error Code: 0x80077381 (29569)
Windows Error Text:   Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Thu Jul 3 22:23:09 2008
     Function Name: RestoreSetupParams
Source Line Number: 190
Error Code: 29569
MSI (s) (40!D0) [21:13:51:016]: Product: Microsoft SQL Server 2008 Database Engine Services -- Error 29569. SQL Server Setup failed to restore the instance id.
Error 29569. SQL Server Setup failed to restore the instance id.
<Failure Type='Fatal' Error='29569'>
<EndFunc Name='LaunchFunction' Return='29569' GetLastError='203'>
CustomAction RestoreSetupParams_64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Hello,
You shared with us the following lines part of one of the logs created during the upgrade process:
Error Code: 29569
MSI (s) (40!D0) [21:13:51:016]: Product: Microsoft SQL Server 2008 Database Engine Services -- Error
29569. SQL
Server Setup failed to restore the instance id.
These lines are associated with Registry corruption. If this instance is a production instance, please call Microsoft Support for help.
For more information, please read the answer provided by Cathy Miller (MSFT) on the following thread.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/15a67403-3e67-47cd-8595-4330945bd6cc/sql-server-2008-sp2-update-fails-error-29569-sql-server-setup-failed-to-restore-the-instance-id?forum=sqlsetupandupgrade
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Sql Server 2012 Login Failed for user "NT Authority\System"

I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
Here is some information on the instance:
1) Default instance
2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
3) Sql Server Browser is disabled.
4) SQL Server VSS Writer is running / log on as Local Service.
5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
I ran a trace on login failed and I get:
ApplicationName: Microsoft Windows Script Host
and it runs every 15 minutes.
Help please?

Hi,
The error was thrown when the SCOM components connected to the backend SCOM databases.
You can specify a domain account, grant it the sysadmin role and the error should be gone.
Also, see the replies in your previous thread:
http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
Thanks.
Tracy Cai
TechNet Community Support

Sql server agent job failing

Hi, I created a ssis package, that simply transfer an excel sheet into ole db, it works on its own, but when I try to use the sql server agent service, the first step is successful,but the second step of execution is not, but I don't have enough details
to check the problem.
when I check the database , a table is created, with only the column headers, but no rows.
please can some one guide me. cheers.
this was in the error log, i checked, and imake sure the file dtx, or the excel was not opened, but what i dont know is about the file permission
,ssa3,Error,1,USER-PC,ssa3,ssas3,,Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:38:23
Error: 2014-10-23 11:38:23.34
Code: 0xC0202009 Source: Package Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "The Microsoft Jet database engine cannot open the file 'C:\Users\User\Desktop\dup.xls'. It is already opened exclusively by another user<c/>
or you need permission to view its data.".
Code: 0xC020801C Source: Data Flow Task Excel Source [2] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection
Manager" failed with error code 0xC0202009.

You can also create a proxy account in sql agent with required permissions to folder etc and configure it to run the job so that it always works
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS running through SQL Server agent Job Fails --SQL Server 2012

Hi All,
I am getting the below error.
Executed as user: sak\thiru. ...ion 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:31:17 PM Error: 2014-03-07 15:32:22.46 Code: 0xC0202009 Source: CommonDataSource
Connection manager "TESTDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0"
Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "A network-related or instance-specific
error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". End Error Error:
2014-03-07 15:32:43.58
The package execution fa... The step failed.
I checked namedpipes, ports,services, SqlBrowser all are running fine.
share your views.
Thanks
Thiru
Thiru

Hi Thiru,
The error messages are rather general and the issue may occur due to various causes. You can check the “Connect Time” setting of the Connection Manager "TESTDB", and increase its timeout value.
If the issue persists, maybe it occurs because the Windows Firewall or certain anti-virus software blocks the RPC dynamic range of TCP Ports between SQL Server and Domain Controllers. In this case, temporarily disable third party anti-virus software, or
configure RPC dynamic port allocation to work with firewalls referring to the following KB article
http://support.microsoft.com/kb/154596.
In addition, the issue may be related to the SQL Server that the OLE DB Source adapter connects to. You can check the SQL Server log to see if any error occurs at that time.
Hope this helps.
Regards,
Mike Yin
TechNet Community Support

SQL Server 2005 SP2 Failed to install the update

I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for me. Is
there a simple way to fix this problem?

I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for
me. Is there a simple way to fix this problem?
I am curious which Windows update installs SQL server 2005. Were you installing any program which installed SQL 2005 as part of it ?
Anyways you can share log file as asked by Alberto. Please also give more details whether SQL server was installed by you or machine or whether it was SQL 2005 update.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL Server Agent Job Failing on Job Step

Hi,
Firstly, apologies if this post has been made in the wrong group. Running SQL Server 2012. I'm attempting to add a SQL Server Agent Job which calls a stored procedure that sends a Database Mail message. The SQL Server and SQL Server Agent
both run under the NT AUTHORITY\NETWORK SERVICE account. The Database Mail service has been enabled, and a public profile created. When running the stored procedure manually, I receive no errors - everything runs as expected and I do receive an
email containing the expected information.
I've created the job, job step, job schedule, attached the schedule to the job, and assigned the job to server, all using T-SQL without error. I've also enabled the mail profile on the SQL Server Agent, and I know that part is working because when
the job fails, I get an email notification of the failure.
I've checked the command text in the job step and parsed it within the SQL Job Step Edit window to confirm, it shows as parsing correctly. However, when I manually run the job itself, I get the following:
Execution of job failed. See the history log for details.
I check the history log and it shows:
[474] Unable to refresh Database Mail profile Database Mail Profile. (reason: ) (Not a typo, the history log shows no reason)
[260] Unable to start mail session.
[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
The command text on the failing job step is as follows:
DECLARE @date [varchar](10)
SET @date = CAST(GETDATE() AS [varchar](10))
EXEC [dbo].[GetExceptions]
@company = 'MyCompany',
@checkDate = @date
With regard to the date value being passed as varchar: This stored procedure is used to check for exceptions against multiple databases on this server (hence the company parameter) via dynamic SQL. I'd much prefer to use proper data typing but this
is the only way I could get it to work.
Does anyone have any suggestions on anything else I could check, or insights into why this is failing? Any help is greatly appreciated!
Best Regards
Brad

I am not sure if this really helps but I would do follow the below steps:
1. make sure sql server agent has database mail enabled(rigt click on server agent--properties--alert system--enable database mail and choose right profile.) and RESTART THE SQL SERVER AGENT.(i know you said it i working, but sometimes, restart the
sql server agent might fix)
2. check agent error log and check if any error messages.
3. run the command text you mentioned in sql server and see if it is working.(i know you said it is working but just to make sure).
4. make sure sql server agent service user has permissions to run database mail in msdb. check this https://msdn.microsoft.com/en-us/library/ms186358.aspx
5. Check the output from select * from msdb.dbo.sysmail_log and if it says anything
6.it does not look like the job log is getting truncated but to make sure, get the job step output to a text file.to do this, edit the job step and on the job step properties click on advanced, enter path to the output file. this will give the complete
output for the step.
Hope it Helps!!

SQL Server Reporting services. failed to establish connection with project server. verify the url is correct.

Dear All,
I'm working on reporting of Project Server 2010, while configuring SQL SERVER REPORTING SERVICES faced issue after two complete days of troubleshooting along with this gone through plenty of forums, unable to figure out any solution. So finally posting on
technet in order to find solution.
ISSUE/PROBLEM:
At initial configured the SQL REPORTING CONFIGURATION to sharepoint integrated database (SQL SERVER is installed on seperate machine), change the service to Domain Account and also installed sharepoint add in on server story was fine at this point. Furthur
moving to SHAREPOINT ADMIN console and while configuring the Sharepoint Integrated Reporting continuously facing this error:
Failed to establish connection with report server. . . . (Snapshot is attached for your further reference).
My point of concern is that whenerver i try to open the REPORT SERVER URL on project server machine it prompts me to enter username and password but whenever i insert the domain credentails it didnt accept though it can be accesible by using the credentials
of Local Admin of sql server machine. So i wana come to know whether its permission issue if yes then where i should mention the domain credentials.?
REGARDS DANISH DANIE

Dear Paul,
I am able to open the URL (http://psdb/ReportServer )using
domian credential and page open with these contents
Reporting Services Error
The configuration parameter SharePointIntegrated is set to True but Share Point Object Model cannot be loaded
Second,
Configured the SPN on domain controller , performed the steps required to change the AUTHENTICATION in rsreportserver.config
file also done the registry settings to disable the loop back settings.
Same error still ! .... what should i do now ???
REGARDS DANISH DANIE

Sql Server Configuration Manager fails to start

Hi,
My Os is Windows 7 Enterprise.
I have Sql Server 2008 Developer Edt. with sp1
and Sql Server 2005 express (which comes with Visual Studio)
When I try to open Configuration Manager it fails:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later server with SQL Server Configuration Manager.
Invalid class [0x80041010]
I've tried everything I could find on the net. But none of them worked for me.
Later, I realised that the file called "sqlwep-uni.mof" under "c:\Program Files\Microsoft SQL Server\MSSQL10.INSTANCENAME\MSSQL\Binn" has failed with mofcomp command.
Microsoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: sqlwep-uni.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while processing item 4 defined on lines 88 - 88 in file sqlwep-uni.mof:
Error Number: 0x8004100e, Facility: WMI
Description: Invalid namespace
Compiler returned error 0x8004100e
Any suggestions?

I think this can be fixed by parsing / registering the sqlmgmproviderxpsp2up mof file.
Have a look here - http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx
Thanks, Leks
That was the first thing I tried :)
I've also tried this: http://social.msdn.microsoft.com/Forums/en/sqltools/thread/468b8484-2729-4a06-bfc3-efe54507dcb6
and this: http://msmvps.com/blogs/martinpoon/archive/2009/11/27/sql-server-configuration-manager-cannot-connect-to-wmi-provider-invalid-class-0x80041010.aspx
and that: http://www.nucleustechnologies.com/Repair-WMI-Services.php
and some other stuff I could find.
At least I've tried to repair Sql 2008 installation. But it also did not work.
Lastly I've uninstalled all the instances and components related with sql. And I renamed the folders (C:\Program Files\Microsoft SQL Server and the hidden folder C:\ProgramData\Microsoft\Microsoft SQL Server) and made a clean install. Voila, it worked!
But the "Sql Server Configuration Manager"s icon has gone somewhere :) Anyway it works fine now.
I had to do that because I have a project to finish.
Poor Microsoft!

SQL Server agent job failing to back up database

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks
NO answer can be provided unless you show us the error message. There can be numerous reasons for backup job to fail. See job history for details please post complete information present in job history.
Check errorlog and note what error message is there at time when the backup job failed. You could find something useful. Please learn how to post question in forum just saying I have a problem will not help both of us.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL Server Delete statements failing

Similar Messages

Maybe you are looking for