Microsoft sql server extended event log file

Dears
Sorry for my below questions if it is very beginner level.
In my implementation I have cluster SQL 2012 on Windows 2012; I am using MountPoints since I have many Clustered Disks.
My MountPoint Size is only 3 GB; My Extended event log are growing fast and it is storing in the MountPoint Drive directly (Path: F:\MSSQL11.MSSQLSERVER\MSSQL\Log).
What is the best practice to work with it? (is it to keep all Extended events? or recirculate? or to shrink? or to store in DB?)
Is there any relation between SQL truncate and limiting the size of Extended event logs?
How can I recirculate this Extended Events?
How can I change the default path?
How can I stop it?
and in case I stop it, does this means to stop storing SQL event in Windows event Viewer?
Thank you

After a lot of checking, I have found below:
My Case:
I am having SQL Failover Cluster Instances "FCI" and I am using Mount-Points to store my Instances.
I am having 2 Passive Copies for each FCI.
In my configuration I choose to store the Root Instance which include the logs on Mount-Point.
My Mount Point is 2 GB Only, which became full after few days of deployment.
Light Technical Information:
The Extended Event Logs files are generated Coz I have FCI, in single SQL Installation you will not find this files.
The File Maximum size will be 100 MB.
The Files start circulating after it become 10 Full Files.
If you have the FCI installed as 1 Active 2 Passive, and you are doing failover between the nodes, then you will expect to see around 14 - 30 copy of this file.
Based on above information you will need to have around 100 MB * 10 Files Per Instance copy * 3 Since in my case I have 1 Active and 2 passive instances which will = 3000 MB
So in my case My Mount-Point was 2 GB, which become full coz of this SQLDIAG Logs.
Solution:
I extended my mount point by 3 GB coz I am storing this logs on it.
In case you will need to change SQLDIAG Extended Logs Size to 50 MB for example and place to F:\Logs, then you will need below commands:
ALTER SERVER CONFIGURATION SET DIAGNOSTICS LOG OFF;
ALTER SERVER CONFIGURATION
SET DIAGNOSTICS LOG MAX_SIZE = 50 MB;
ALTER SERVER CONFIGURATION
SET DIAGNOSTICS LOG PATH = 'F:\logs';
ALTER SERVER CONFIGURATION SET DIAGNOSTICS LOG ON;
After that you will need to restart the FCI from SQL Server Configuration Manager or Failover Cluster Manager.
I wish you will find this information helpful if it is your case.
Regards

Similar Messages

Selective XML Index feature is not supported for the current database version , SQL Server Extended Events , Optimizing Reading from XML column datatype

Team , Thanks for looking into this ..
As a last resort on optimizing my stored procedure ( Below ) i wanted to create a Selective XML index ( Normal XML indexes doesn't seem to be improving performance as needed ) but i keep getting this error within my stored proc . Selective XML
Index feature is not supported for the current database version.. How ever
EXECUTE sys.sp_db_selective_xml_index; return 1 , stating Selective XML Indexes are enabled on my current database .
Is there ANY alternative way i can optimize below stored proc ?
Thanks in advance for your response(s) !
/****** Object: StoredProcedure [dbo].[MN_Process_DDLSchema_Changes] Script Date: 3/11/2015 3:10:42 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- EXEC [dbo].[MN_Process_DDLSchema_Changes]
ALTER PROCEDURE [dbo].[MN_Process_DDLSchema_Changes]
AS
BEGIN
SET NOCOUNT ON --Does'nt have impact ( May be this wont on SQL Server Extended events session's being created on Server(s) , DB's )
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
select getdate() as getdate_0
DECLARE @XML XML , @Prev_Insertion_time DATETIME
-- Staging Previous Load time for filtering purpose ( Performance optimize while on insert )
SET @Prev_Insertion_time = (SELECT MAX(EE_Time_Stamp) FROM dbo.MN_DDLSchema_Changes_log ) -- Perf Optimize
-- PRINT '1'
CREATE TABLE #Temp
EventName VARCHAR(100),
Time_Stamp_EE DATETIME,
ObjectName VARCHAR(100),
ObjectType VARCHAR(100),
DbName VARCHAR(100),
ddl_Phase VARCHAR(50),
ClientAppName VARCHAR(2000),
ClientHostName VARCHAR(100),
server_instance_name VARCHAR(100),
ServerPrincipalName VARCHAR(100),
nt_username varchar(100),
SqlText NVARCHAR(MAX)
CREATE TABLE #XML_Hold
ID INT NOT NULL IDENTITY(1,1) PRIMARY KEY , -- PK necessity for Indexing on XML Col
BufferXml XML
select getdate() as getdate_01
INSERT INTO #XML_Hold (BufferXml)
SELECT
CAST(target_data AS XML) AS BufferXml -- Buffer Storage from SQL Extended Event(s) , Looks like there is a limitation with xml size ?? Need to re-search .
FROM sys.dm_xe_session_targets xet
INNER JOIN sys.dm_xe_sessions xes
ON xes.address = xet.event_session_address
WHERE xes.name = 'Capture DDL Schema Changes' --Ryelugu : 03/05/2015 Session being created withing SQL Server Extended Events
--RETURN
--SELECT * FROM #XML_Hold
select getdate() as getdate_1
-- 03/10/2015 RYelugu : Error while creating XML Index : Selective XML Index feature is not supported for the current database version
CREATE SELECTIVE XML INDEX SXI_TimeStamp ON #XML_Hold(BufferXml)
FOR
PathTimeStamp ='/RingBufferTarget/event/timestamp' AS XQUERY 'node()'
--RETURN
--CREATE PRIMARY XML INDEX [IX_XML_Hold] ON #XML_Hold(BufferXml) -- Ryelugu 03/09/2015 - Primary Index
--SELECT GETDATE() AS GETDATE_2
-- RYelugu 03/10/2015 -Creating secondary XML index doesnt make significant improvement at Query Optimizer , Instead creation takes more time , Only primary should be good here
--CREATE XML INDEX [IX_XML_Hold_values] ON #XML_Hold(BufferXml) -- Ryelugu 03/09/2015 - Primary Index , --There should exists a Primary for a secondary creation
--USING XML INDEX [IX_XML_Hold]
---- FOR VALUE
-- --FOR PROPERTY
-- FOR PATH
--SELECT GETDATE() AS GETDATE_3
--PRINT '2'
-- RETURN
SELECT GETDATE() GETDATE_3
INSERT INTO #Temp
EventName ,
Time_Stamp_EE ,
ObjectName ,
ObjectType,
DbName ,
ddl_Phase ,
ClientAppName ,
ClientHostName,
server_instance_name,
nt_username,
ServerPrincipalName ,
SqlText
SELECT
p.q.value('@name[1]','varchar(100)') AS eventname,
p.q.value('@timestamp[1]','datetime') AS timestampvalue,
p.q.value('(./data[@name="object_name"]/value)[1]','varchar(100)') AS objectname,
p.q.value('(./data[@name="object_type"]/text)[1]','varchar(100)') AS ObjectType,
p.q.value('(./action[@name="database_name"]/value)[1]','varchar(100)') AS databasename,
p.q.value('(./data[@name="ddl_phase"]/text)[1]','varchar(100)') AS ddl_phase,
p.q.value('(./action[@name="client_app_name"]/value)[1]','varchar(100)') AS clientappname,
p.q.value('(./action[@name="client_hostname"]/value)[1]','varchar(100)') AS clienthostname,
p.q.value('(./action[@name="server_instance_name"]/value)[1]','varchar(100)') AS server_instance_name,
p.q.value('(./action[@name="nt_username"]/value)[1]','varchar(100)') AS nt_username,
p.q.value('(./action[@name="server_principal_name"]/value)[1]','varchar(100)') AS serverprincipalname,
p.q.value('(./action[@name="sql_text"]/value)[1]','Nvarchar(max)') AS sqltext
FROM #XML_Hold
CROSS APPLY BufferXml.nodes('/RingBufferTarget/event')p(q)
WHERE -- Ryelugu 03/05/2015 - Perf Optimize - Filtering the Buffered XML so as not to lookup at previoulsy loaded records into stage table
p.q.value('@timestamp[1]','datetime') >= ISNULL(@Prev_Insertion_time ,p.q.value('@timestamp[1]','datetime'))
AND p.q.value('(./data[@name="ddl_phase"]/text)[1]','varchar(100)') ='Commit' --Ryelugu 03/06/2015 - Every Event records a begin version and a commit version into Buffer ( XML ) we need the committed version
AND p.q.value('(./data[@name="object_type"]/text)[1]','varchar(100)') <> 'STATISTICS' --Ryelugu 03/06/2015 - May be SQL Server Internally Creates Statistics for #Temp tables , we do not want Creation of STATISTICS Statement to be logged
AND p.q.value('(./data[@name="object_name"]/value)[1]','varchar(100)') NOT LIKE '%#%' -- Any stored proc which creates a temp table within it Extended Event does capture this creation statement SQL as well , we dont need it though
AND p.q.value('(./action[@name="client_app_name"]/value)[1]','varchar(100)') <> 'Replication Monitor' --Ryelugu : 03/09/2015 We do not want any records being caprutred by Replication Monitor ??
SELECT GETDATE() GETDATE_4
-- SELECT * FROM #TEMP
-- SELECT COUNT(*) FROM #TEMP
-- SELECT GETDATE()
-- RETURN
-- PRINT '3'
--RETURN
INSERT INTO [dbo].[MN_DDLSchema_Changes_log]
[UserName]
,[DbName]
,[ObjectName]
,[client_app_name]
,[ClientHostName]
,[ServerName]
,[SQL_TEXT]
,[EE_Time_Stamp]
,[Event_Name]
SELECT
CASE WHEN T.nt_username IS NULL OR LEN(T.nt_username) = 0 THEN t.ServerPrincipalName
ELSE T.nt_username
END
,T.DbName
,T.objectname
,T.clientappname
,t.ClientHostName
,T.server_instance_name
,T.sqltext
,T.Time_Stamp_EE
,T.eventname
FROM
#TEMP T
/** -- RYelugu 03/06/2015 - Filters are now being applied directly while retrieving records from BUFFER or on XML
-- Ryelugu 03/15/2015 - More filters are likely to be added on further testing
WHERE ddl_Phase ='Commit'
AND ObjectType <> 'STATISTICS' --Ryelugu 03/06/2015 - May be SQL Server Internally Creates Statistics for #Temp tables , we do not want Creation of STATISTICS Statement to be logged
AND ObjectName NOT LIKE '%#%' -- Any stored proc which creates a temp table within it Extended Event does capture this creation statement SQL as well , we dont need it though
AND T.Time_Stamp_EE >= @Prev_Insertion_time --Ryelugu 03/05/2015 - Performance Optimize
AND NOT EXISTS ( SELECT 1 FROM [dbo].[MN_DDLSchema_Changes_log] MN
WHERE MN.[ServerName] = T.server_instance_name -- Ryelugu Server Name needes to be added on to to xml ( Events in session )
AND MN.[DbName] = T.DbName
AND MN.[Event_Name] = T.EventName
AND MN.[ObjectName]= T.ObjectName
AND MN.[EE_Time_Stamp] = T.Time_Stamp_EE
AND MN.[SQL_TEXT] =T.SqlText -- Ryelugu 03/05/2015 This is a comparision Metric as well , But needs to decide on
-- Peformance Factor here , Will take advise from Lance if comparision on varchar(max) is a vital idea
--SELECT GETDATE()
--PRINT '4'
--RETURN
SELECT
top 100
[EE_Time_Stamp]
,[ServerName]
,[DbName]
,[Event_Name]
,[ObjectName]
,[UserName]
,[SQL_TEXT]
,[client_app_name]
,[Created_Date]
,[ClientHostName]
FROM
[dbo].[MN_DDLSchema_Changes_log]
ORDER BY [EE_Time_Stamp] desc
-- select getdate()
-- ** DELETE EVENTS after logging into Physical table
-- NEED TO Identify if this @XML can be updated into physical system table such that previously loaded events are left untoched
-- SET @XML.modify('delete /event/class/.[@timestamp="2015-03-06T13:01:19.020Z"]')
-- SELECT @XML
SELECT GETDATE() GETDATE_5
END
GO
Rajkumar Yelugu

@@Version : ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
 May 14 2014 18:34:29
 Copyright (c) Microsoft Corporation
 Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
(1 row(s) affected)
Compatibility level is set to 110 .
One of the limitation states - XML columns with a depth of more than 128 nested nodes
How do i verify this ? Thanks .
Rajkumar Yelugu

SQL Server 2012 DB log file doesn't shrink (simple recovery model)

I've found several similar questions in this forum, but none of the answers have resolved my problem: I have a SQL Server 2012 DB using simple recovery model. The MDF file is 12 GB and the LDF file is 10 GB. I'm trying to shrink the size of the
LDF file. I've read that for simple recovery model DBs there are reasons for delaying log file shrinking, but I still can't find a solution based on these reasons.
When I try to shrink it using this command:
DBCC SHRINKFILE(MyDB_log, 1000000)
I get these results, and no change of file size:
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages8 2 1241328 128 1241328 128
The same results running this:
DBCC SHRINKFILE(MyDB_log, 1000000, TRUNCATEONLY)
There doesn't appear to be any open transactions:
DBCC OPENTRAN()No active open transactions.DBCC execution completed. If DBCC printed error messages, contact your system administrator.
And this returns NOTHING:
SELECT name, database_id, log_reuse_wait_desc FROM sys.databases WHERE database_id = DB_ID()name database_id log_reuse_wait_descMyDB 8 NOTHING
I've also tried running the following, but nothing useful is returned:
SELECT * FROM sys.dm_tran_database_transactionsSELECT * FROM sys.dm_exec_requests WHERE database_id=DB_ID()SELECT * FROM sys.dm_tran_locks WHERE resource_database_id=DB_ID()
Any other suggestions of what I can do to shrink this log file? Or perhaps someone can justify its enormous size?
David Collacott

The answer is pretty simple.
The following code is the problem:
DBCC SHRINKFILE(MyDB_log, 1000000)
You are telling SQL Server that you want to "shrink" the MyDB_log file and the target size is 1TB. Well according to you the MyDB_Log file is well below the 1TB size you are targeting, in fact it's only 10GB so SQL Server is doing precisely what you
are telling it to do.
See, according to the SQL Server documentation
here, target size "Is the size for the file in megabytes, expressed as an integer."
Now if you'd like to actually shrink the log file down to, oh say 1GB, then you should try the following command:
DBCC SHRINKFILE(MyDB_log, 1000)
The theory being 1000 * 1048576 (i.e. 1MB) is equal to 1GB.

SQL Server Extended Events Capturing DDL Schema Changes gives "NO Column Name" Value on DDL events being performed .

Team ,
I've created a session to Capture object_Created , Object_altered and Object_deleted events on to Ring Buffeer target "IN Memory Storage" on a server .Whenever i create alter or drop an object , I see a Result in SSMS Column Name "No Column
Name" and value "1" .
Is there a way we can eradicate this ?
Thanks in advance for your tip !
Rajkumar Yelugu

Thoughts ? Thanks for your time !
Rajkumar Yelugu

[Error] Microsoft SQL Server 2008 Setup. Error reading from file msdbdata.mdf

Hi all
I'm trying to install SQL 2008 Express on my Computer: Hp compact DX7300 Slim tower.
and get this error:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:Error reading from file d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template\msdbdata.mdf. Verify that the file exists and that you can access it.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0&EvtType=0xF45F6601%25401201%25401
Log file
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-12-09 23:22:03
End time: 2014-12-09 23:40:28
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\sql_engine_core_inst_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0
Machine Properties:
Machine name: VISTA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: d:\8268cd7b247d294de359c9\x86\setup\
Installation edition: EXPRESS
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLExpress
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: d:\8268cd7b247d294de359c9\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: VISTA-PC\VISTA
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
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\20141209_232121\SystemConfigurationCheck_Report.htm
I will very appriciate if someone can help me solve it. I was trying to set Full control for my account in Properties/Security of root folder and try again but error is still.
Many thanks

Hi Foreverduy,
Before you run SQL Server 2008 express setup, make sure that you have installed Windows installer 4.5 and.NET Framework 3.5 SP1 manually. For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx. Moreover, please turn off all the third-party softwares which could prohibit the installation process.
According to your error message, the issue could be due to that your account has no rights to install SQL Server, or the corruption on the media.
Firstly, please ensure that your account has admin rights. Also make sure that you right-click the setup.exe and choose “Run as administrator” to complete the installation.
Secondly, please check if "msdbdata.mdf" file exists at d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template. If it exists, please make sure that your account has read permission to the extracted
folder.
However, if the file doesn't exist in the extraction, the media could be corrupt. Please download the
media
again and check if the issue still occurs.
Regards,
Michelle Li

Unable to install Microsoft SQL Server 2008 R2

It is showing error: Attempted to perform unauthorized operation. So was unable to install
Database Engine
Replication
TITLE: Microsoft SQL Server 2008 R2 Setup
The following error has occurred:
Attempted to perform an unauthorized operation.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x6121810A%25400x92D13C14
BUTTONS:
&Retry
Cancel
Log File
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time: 2013-01-25 10:59:08
End time: 2013-01-25 11:13:30
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x6121810A%400x92D13C14
Machine Properties:
Machine name: VARUNGUPTA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 2
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 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
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: d:\a716bfc2c0347dcd1c0fc7fcedc92a06\x86\setup\
Installation edition: EXPRESS_ADVANCED
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE:
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: VarunGupta-PC\Varun Gupta
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
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\20130125_105747\SystemConfigurationCheck_Report.htm

I was finally able to get out of this issue... but later got stuck here with following error
TITLE: SQL Server 2008 R2 Setup
The following error has occurred:
Attempted to perform an unauthorized operation.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0&EvtType=0x6121810A%25400x92D13C14
BUTTONS:
&Retry
Cancel
Also tried by running as administrator.
It failed to install
Data Engine Services
SQL Server Replication
Full - Text Search
Reporting Services
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time: 2013-01-27 01:11:08
End time: 2013-01-27 01:23:26
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130127_010951\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x6121810A%400x92D13C14
Machine Properties:
Machine name: VARUNGUPTA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 2
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 R2 SQLEXPRESS MSSQL10_50.SQLEXPRESS Database Engine Services
1033 Express Edition 10.51.2500.0 No
Sql Server 2008 R2 SQLEXPRESS MSSQL10_50.SQLEXPRESS SQL Server Replication
1033 Express Edition 10.51.2500.0 No
Sql Server 2008 R2 SQLEXPRESS MSSQL10_50.SQLEXPRESS Full-Text Search
1033 Express Edition 10.51.2500.0 No
Sql Server 2008 R2 SQLEXPRESS MSRS10_50.SQLEXPRESS Reporting Services
1033 10.51.2500.0
No
Sql Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.51.2500.0 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: c:\c49037ca8dfa571dfe4480d170\x86\setup\
Installation edition: EXPRESS_ADVANCED
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE:
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,RS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: c:\Program Files\Microsoft SQL Server
INSTANCEID: VARUNGUPTA
INSTANCENAME: VARUNGUPTA
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: c:\c49037ca8dfa571dfe4480d170\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: VarunGupta-PC\Varun Gupta
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130127_010951\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
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\20130127_010951\SystemConfigurationCheck_Report.htm
Here is Detail.txt file
http://sdrv.ms/W759Wo

Microsoft sql server 2005 setup problem

i am trying to install sql server 2005 on windows 8,
they is a popup
window
that
says;
the sql server servi failed to start. for more information, see the sql server book
online topics, "How to: view sql server 2005 setup log
files" and starting sql server Manually."

i am trying to install sql server 2005 on windows 8,
they is a popup window
that says;
the sql server servi failed to start. for more information, see the sql server book online topics, "How to: view sql server 2005 setup log files" and starting sql server Manually."
I merged your two threads into one, because they are the same. Thanks for asking your questions here!
sqldevelop.wordpress.com

Tempdb in a subdirectory of \Program Files\Microsoft SQL Server\

Hi,
SAP ERP 6.0 / Sol. Man. 4.0 Installation Guide say "after initial installation of the database software, the tempdb is located in a subdirectory of \Program Files\Microsoft SQL Server. However later, when SAPinst builds and loads the database, it is transferred to a new \TEMPDB directory and extended to a size of 300 MB."
I finished the installation some days ago but I still see file tempdb.mdf & templog.ldf in
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
May I delete these files because tempdb DB currently use the 2 files in \TEMPDB directory?
Regards,
Toan Do

HI,
Moving the tempdb database
As the tempdb database is constantly being used by the SQL Server, it cannot be moved using the same process described above (sp_detach_db, sp_attach_db). Instead, you must use the 'alter database modify file' command.
a) First display all tempdb database files using the following command:
select convert(char(20),name) as name, filename from tempdb..sysfiles
name filename
tempdev d:\TEMPDB\TEMPDB.MDF
templog d:\TEMPDB\TEMPLOG.LDF
(2 row(s) affected)
b) Set a new storage location for the files by executing an ALTER DATABASE for each file:
Example:
alter database tempdb
 modify file (name=tempdev,filename='E:\NEW\tempdb.mdf')
alter database tempdb
 modify file (name=templog,filename='E:\NEW\templog.ldf')
c) Restart your SQL Server. The tempdb database is created again during each restart of the SQL Server. In this case, the files are now created in the new directory.
d) Use the NT Explorer to delete the old database files for the tempdb.
e) We recommend that you make a full backup of the master database after the change.
Refrence SAP Note:
Note 363018 - File management with SQL Server.
Award points if helpful.
Thanks,
Tanuj

Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\abc.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

hi,
am running the below command for moving sql serevr mdf and ldf files from one drive to another : c drive to d drive:
but am getting the below error
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\abc.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
use master
DECLARE @DBName nvarchar(50)
SET @DBName = 'CMP_143'
DECLARE @RC int
EXEC @RC = sp_detach_db @DBName
DECLARE @NewPath nvarchar(1000)
--SET @NewPath = 'E:\Data\Microsoft SQL Server\Data\';
SET @NewPath = 'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\';
DECLARE @OldPath nvarchar(1000)
SET @OldPath = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\';
DECLARE @DBFileName nvarchar(100)
SET @DBFileName = @DBName + '.mdf';
DECLARE @LogFileName nvarchar(100)
SET @LogFileName = @DBName + '_log.ldf';
DECLARE @SRCData nvarchar(1000)
SET @SRCData = @OldPath + @DBFileName;
DECLARE @SRCLog nvarchar(1000)
SET @SRCLog = @OldPath + @LogFileName;
DECLARE @DESTData nvarchar(1000)
SET @DESTData = @NewPath + @DBFileName;
DECLARE @DESTLog nvarchar(1000)
SET @DESTLog = @NewPath + @LogFileName;
DECLARE @FILEPATH nvarchar(1000);
DECLARE @LOGPATH nvarchar(1000);
SET @FILEPATH = N'xcopy /Y "' + @SRCData + N'" "' + @NewPath + '"';
SET @LOGPATH = N'xcopy /Y "' + @SRCLog + N'" "' + @NewPath + '"';
exec xp_cmdshell @FILEPATH;
exec xp_cmdshell @LOGPATH;
EXEC @RC = sp_attach_db @DBName, @DESTData, @DESTLog
go
can anyone pls help how to set the db offline. currently i stopped the sql server services from services.msc and started the sql server agent.
should i stop both services for moving from one drive to another?
note: I tried teh below solution but this didint work:
ALTER DATABASE <DBName> SET OFFLINE WITH ROLLBACK IMMEDIATE
Update:
now am getting the message :
Msg 15010, Level 16, State 1, Procedure sp_detach_db, Line 40
The database 'CMP_143' does not exist. Supply a valid database name. To see available databases, use sys.databases.
(3 row(s) affected)
(3 row(s) affected)
Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\CMP_143.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

First you should have checked the database mdf/ldf name and location by using the command
Use CMP_143
Go
Sp_helpfile
Looks like your database CMP_143 was successfully detached but mdf/ldf location or name was different that is why it did not get copied to target location.
Database is already detached that’s why db offline failed
Msg 15010, Level 16, State 1, Procedure sp_detach_db, Line 40
The database 'CMP_143' does not exist. Supply a valid database name. To see available databases, use sys.databases.
EXEC @RC = sp_attach_db @DBName, @DESTData, @DESTLog
Attached step is failing as there is no mdf file
Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\CMP_143.mdf". Operating system error 2: "2(The system cannot find the file specified.)"
Solution:
Search for the physical files(mdf/ldf) in the OS and copy to target location and the re-run sp_attach_db with right location and name of mdf/ldf.

The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

One of my replication job failed with below error, which means job failed because of permission issue on the folder. To resolve that, I have granted the permission and it started working fine. Now the question is as my job was running fine since long time
without any issue then how suddenly the permission of the folder got omitted automatically? I am sure that no one deleted the permission from the folder and as the server is part of SQL cluster no failover occurs.
Error:-The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
Rahul

Hi Rahul,
Error code 5 indicates that the error is "access is denied." Please make sure that the COM folder is excluded from any antivirus scan that occurs on the system.
If the issue still persists, I recommend you use
Process Monitor to find out a bit more about the accounts and access requests involved. Then grant write permission to the exact COM folder for the account that is running the SQL Server Agent service. For more details, please review the following similar
thread.
http://www.sqlservercentral.com/Forums/Topic1364832-1550-1.aspx
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

A database error occurred. Source: Microsoft SQL Server Native Client 10.0 Code: 1205 occurred

Hi
i am getting these errors in sharepoint server event viewer, and when i see the sql server the log files disk is full memory only some mbs left out of 1 TB
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Server Search
Date: 7/12/2014 9:56:04 PM
Event ID: 57
Task Category: Search service
Level: Warning
Keywords:
User: XYZ\svc-mc-sps3eServsear
Computer: SPFIND01.xyz.gov.local
Description:
A database error occurred. Source: Microsoft SQL Server Native Client 10.0 Code: 1205 occurred 1 time(s) Description: Transaction (Process ID 193) was deadlocked on lock
resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Context: Application 'XYZSP_SearchApp'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
 <EventID>57</EventID>
 <Version>14</Version>
 <Level>3</Level>
 <Task>136</Task>
 <Opcode>0</Opcode>
 <Keywords>0x4000000000000000</Keywords>
 <TimeCreated SystemTime="2014-07-12T18:56:04.665684900Z" />
 <EventRecordID>225666</EventRecordID>
 <Correlation />
 <Execution ProcessID="3408" ThreadID="2932" />
 <Channel>Application</Channel>
 <Computer>SPFIND01.xyz.gov.local</Computer>
 <Security UserID="S-1-5-21-1537596049-1164153464-4201862467-47315" />
</System>
<EventData>
 <Data Name="string0">Microsoft SQL Server Native Client 10.0</Data>
 <Data Name="string1">1205</Data>
 <Data Name="string2">1</Data>
 <Data Name="string3">Transaction (Process ID 193) was deadlocked on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction.</Data>
 <Data Name="string4">
Context: Application 'XYZSP_SearchApp'</Data>
</EventData>
</Event>
A database error occurred. Source: Microsoft SQL Server Native Client 10.0 Code: 9002 occurred 1 time(s) Description: The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'.
Context: Application 'XYZSP_SearchApp'
adil

If you've run out of disk space for your SQL databases then of course you'll get errors. Fix SQL then look to see if you're still getting errors.

High number of "Network error code 0x2746" in extended events log

In the extended event log of our database server I see 880 consecutive identical errors, all occurring between
17:00:49 and 17:15:25. The message is:
Network error code 0x2746 occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 27 ms, enqueued 0 ms, network writes 0 ms, network
reads 25 ms, establishing SSL 8 ms, negotiating SSPI 0 ms, validating login 0 ms, including user-defined login processing 0 ms. [CLIENT: 10.127.214.32]
The timings in each message are a little bit different. It might be interesting to know the averages for these timings, so here is the message again, now with the timings replaced by averages (rounded to 1 digit):
Network error code 0x2746 occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 32.5 ms, enqueued 0.5 ms, network writes 0.9 ms,
network reads 29.4 ms, establishing SSL 8.3 ms, negotiating SSPI 0.0 ms, validating login 0.0 ms, including user-defined login processing 0.0 ms. [CLIENT: 10.127.214.32]
The client is a Citrix server that runs a COTS program. It serves approx. 20 users.
What can be the cause of this? Can it only be the program that automatically tries to reconnect?

Hello,
Please read about possible causes and resolutions on the following resource:
http://technet.microsoft.com/en-us/library/ms187005(v=SQL.105).aspx
Please examine any certificate used for communications. Maybe a certificate has expired.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Failed to install Hotfix 4311 for Microsoft SQL Server 2008 (KB2494094) (64-bit)

I have a cluster install at SQL version 10.0.4272. I want to upgrade this to 10.0.4311. When I go through install on passive node it fails with message of "The patch installer has failed to update the shared features. To determine
the reason for failure, review the log files". When I review detail.txt I see error lines below. The OS is Windows Server 2008 R2 Enterprise 64-bit.
2014-07-15 18:18:34 Slp: Error: Action "SqlEngineConfigAction_patch_configrc_Cpu64" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature MPT_AGENT_CORE_CNI, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\UpgradeIncompleteState
2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value MPT_AGENT_CORE_CNI
2014-07-15 18:18:34 Slp: Sco: Attempting to get feature configuration state for feature MPT_AGENT_CORE_CNI, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature MPT_AGENT_CORE_CNI, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState
2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value MPT_AGENT_CORE_CNI
2014-07-15 18:18:34 Slp: The FeatureConfigState of MSI feature MPT_AGENT_CORE_CNI has been adjusted to patch configuration.
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "AgentConfigAction_patch_RC_Cpu64" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: AgentConfigAction_patch_RC_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "AgentConfigAction_patch_RC_Cpu64" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature SQL_Replication_Core_Inst, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\UpgradeIncompleteState
2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
2014-07-15 18:18:34 Slp: Sco: Attempting to get feature configuration state for feature SQL_Replication_Core_Inst, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature SQL_Replication_Core_Inst, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState
2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
2014-07-15 18:18:34 Slp: The FeatureConfigState of MSI feature SQL_Replication_Core_Inst has been adjusted to patch configuration.
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_ConfigRC_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_ConfigRC_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature SQL_FullText_Adv, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\UpgradeIncompleteState
2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_FullText_Adv
2014-07-15 18:18:34 Slp: Sco: Attempting to get feature configuration state for feature SQL_FullText_Adv, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature SQL_FullText_Adv, instance MSSQL10.MSSQLSERVER
2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState
2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_FullText_Adv
2014-07-15 18:18:34 Slp: The FeatureConfigState of MSI feature SQL_FullText_Adv has been adjusted to patch configuration.
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_ConfigRC_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "FulltextConfigAction_patch_configrc_Cpu64" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_patch_configrc_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "FulltextConfigAction_patch_configrc_Cpu64" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "cluster_group_cluster_patch_startup_Cpu64" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: cluster_group_cluster_patch_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "cluster_group_cluster_patch_startup_Cpu64" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Startup_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "FulltextConfigAction_patch_startup_Cpu64" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_patch_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results: ValidateResult,
Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "FulltextConfigAction_patch_startup_Cpu64" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are
10 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2
dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" failed during execution.
2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_postmsi" will return false due to the following conditions:
2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_postmsi" failed during execution.
2014-07-15 18:18:39 Slp: Error result: -2068643839
2014-07-15 18:18:39 Slp: Result facility code: 1203
2014-07-15 18:18:39 Slp: Result error code: 1
2014-07-15 18:18:39 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-07-15 18:18:39 Slp: Sco: Attempting to open registry subkey
2014-07-15 18:18:39 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-07-15 18:18:39 Slp: Sco: Attempting to get registry value DW0201
2014-07-15 18:18:40 Slp: Submitted 1 of 1 failures to the Watson data repository

Hello,
Please read the following support article:
http://support.microsoft.com/kb/2216468/en-us
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

[[DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Column name or number of supplied values does not match table definition.]

Hii ..
need help on this ..
This what I am doing ..
I am using a DATAEXPORT function to export level0 data from my essbase 11.1.2.2 to Microsoft SQL 2008 tables.
So what I did first I exported the level0 data to a flat file using DATAEXPORT and the created the SQL columns by the same in that order only in my SQL table.
When I run it fails with this error:
ODBC Layer Error: [21S01] ==> [[DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Column name or number of supplied values does not match table definition.]
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1021014)
ODBC Layer Error: Native Error code [213]
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Error(1012085)
Unable to export data to SQL table [dataexp]. Check the Essbase server log and the system console to determine the cause of the problem.
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1021002)
SQL Connection is Freed
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Warning(1080014)
Transaction [ 0x1c50001( 0x51ee7d66.0x80342 ) ] aborted due to status [1012085].
[Tue Jul 23 18:26:07 2013]Local/dataexp/dataexp/admin@Native Directory/1209813312/Info(1012579)
Total Calc Elapsed Time for [test.csc] : [1.44] seconds
=============================================================
I did a simple test on my Sample.basic application then ..
loaded the calc data to it and then used the below script to export to a flat file
//ESS_LOCALE English_UnitedStates.Latin1@Binary
SET DATAEXPORTOPTIONS
                DataExportLevel "Level0";
                DataExportOverwriteFile ON;
                DataExportColFormat OFF;
                DataExportDimHeader OFF;
FIX(
            "Jan",
            "Sales",
            "Actual"
/*DATAEXPORT "File" "," "/home/hypadmin/samtest.txt";*/
DATAEXPORT "DSN" "Abhitest" "sample" "sa" "welcome1";
ENDFIX
out put as below:
"Sales"
"100-30","California"
"Jan","Actual",145
Now In sql I created only 3 columns with name Jan/Sales/Actual and when I run this script again with comments removed .. I get the same error as what I have got in my first test case with other application ..
but when I create the columns with same name as what its in export
Sales/100-30/Califirnia/Jan/Actual
It created the new rows successfully ..
So with this I think the error which I am getting with my other application might be because of the same column issue .. but then I have created all the columns by looking at the export file only as I did in sample ..
Any idea would be helpful ..
Thanks
Abhishek
I

First make sure you add
DataExportRelationalFile ON;
to your set commands it is missing
I alwats like to also add
DataExportColHeader dimensionName;
so I am sure what dimension is getting put into the columns.
Then count the number of dimensions in your outline (exclude attribute dimensions). You need at least that many columns in your table -1 + the number of members you will be returning as columns in the export
Taking your example Sample basic has 5 dimensions
Measures
Years
Scenario
Product
Market
Since you did not specify a dataexportcolheader it took the dense dimension Scenario as the columns. Your fix statement is limiting that to one member. Doing the math
5 -1 + 1 = 5 columns in your table which is what you found works. Suppose you fixed on bothe Actual and budget in scenario then you would need 6 columns 5 -1 +2

Problem of Teststand3.1 database and microsoft SQL Server 2000 personal edition

I have a problem when using teststand database function with Microsoft sql server 2000. the error(seen in attached screenshot3.jpg) is:
"An error occurred calling 'LogResults' in 'ITSDBLog' of 'DBLog 1.0 Type Library'
An error occurred executing a statement.
Schema: Generic Recordset (NI).
Statement: UUT_RESULT.
[Microsoft][ODBC SQL Server Driver][SQL Server]unable to insert NULL value to column "ID", table "test.dbo.UUT_RESULT";This column is not alowed to be blank. INSERT Failed. Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
[Microsoft][ODBC SQL Server Driver][SQL Server]terminated.
Source: TSDBLog"
Here I listed my proceess.
1, Configure in SQL Sever, please see attached screenshot0.jpg
 a, Open SQL
 b, build a new database with the name of test
 c, import the data from "C:\Program Files\National Instruments\TestStand 3.1\Components\NI\Models\TestStandModels\Database\TestStand Results.mdb"
2, Configure Microsoft SQL sever: please see attached screenshot1.jpg
 a, Open windows Control Panel and select "Data Sources (ODBC). Under system DSN tab, add a SQL server data source
3, Configure teststand database option, see attached screenshot2.jpg
 a, configure logging option, enable
 b, configure datalink
 c, select schemas of "Generic recordset (NI)
 d, No change on the tabs of "statements" and "Columns/Parameters"
4, run an seqence file with the proess model of SequentialModel.Seq.
Attachments:
Screenshot.zip ‏425 KB

Thanks Scott,
The database function is OK now after I changed imported tables in SQL Sever.
Actually, I once tried anothor method that you refered by using the scripts
located at: <TestStand>\Components\NI\Models\TestStandModels\Database\SQL Server Create Generic Recordset Result Tables.sql. Attached is the error screenshots, please help me on this.
Thanks
Jacky
Attachments:
Error.jpg ‏59 KB

Microsoft sql server extended event log file

Similar Messages

Maybe you are looking for