New Files in SQL Server Log Directory

Does anyone know which process generates files to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log.
I started seeing new files are added from yestoday. The file name pattern is like "ServerName_MSSQLSERVER_SQLDIAG_0_130632533281120000.xel".
Thanks,

Can you right click and script the system_health session monitor? Check the corresponding path and name of the file.
Its enabled by default. The system_health session collects system data that can be used to help troubleshoot performance issues.
I think someone has created the file.
--Prashanth

Similar Messages

Error in sql_engine_core_inst_Cpu64_1.log file for SQL Server 2012

I was running SQL Server 2012 in Win 7 64 bit OS. Some how I found SQLSERVER server is not running and I was not able to run the service. Then I tried to unisntall and install again. And I found that some of the SQL Server
features got failed, like: Reporting Services - Native, Database Engine Services, Data Quality Services, Full-Text and Semantic Extractions for Search and SQL Server Replication. I checked the Summary.txt
file from location C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log. It thsi logs referes to another log file location like:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140127_151409\sql_engine_core_inst_Cpu64_1.log
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639
I did unisntall/install multipel times. But fhw to fix the issue that saying in sql_engine_core_inst_Cpu64_1.log file.:
=== Verbose logging started: 1/27/2014 15:45:04 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\ScenarioEngine.exe ===
MSI (c) (C4:BC) [15:45:04:321]: Resetting cached policy values
MSI (c) (C4:BC) [15:45:04:321]: Machine policy value 'Debug' is 0
MSI (c) (C4:BC) [15:45:04:321]: ******* RunEngine:
******* Product: E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
******* Action:
******* CommandLine: **********
MSI (c) (C4:BC) [15:45:04:322]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (C4:BC) [15:45:04:322]: Grabbed execution mutex.
MSI (c) (C4:BC) [15:45:04:323]: Cloaking enabled.
MSI (c) (C4:BC) [15:45:04:323]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (C4:BC) [15:45:04:323]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:8C) [15:45:04:327]: Running installation inside multi-package transaction E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
MSI (s) (38:8C) [15:45:04:327]: Grabbed execution mutex.
MSI (s) (38:A0) [15:45:04:327]: Resetting cached policy values
MSI (s) (38:A0) [15:45:04:327]: Machine policy value 'Debug' is 0
MSI (s) (38:A0) [15:45:04:327]: ******* RunEngine:
******* Product: E:\Software\SQL Full Installation\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi
******* Action:
******* CommandLine: **********
MSI (s) (38:A0) [15:45:04:452]: Machine policy value 'TransformsSecure' is 0
MSI (s) (38:A0) [15:45:04:452]: User policy value 'TransformsAtSource' is 0
MSI (s) (38:A0) [15:45:04:475]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (38:A0) [15:45:04:475]: Specified instance {18B2A97C-92C3-4AC7-BE72-F823E0BC895B} via transform :InstID01.mst;:InstName02.mst is already installed. MSINEWINSTANCE requires a new instance that is not installed.
MSI (s) (38:A0) [15:45:04:475]: MainEngineThread is returning 1639
MSI (s) (38:8C) [15:45:04:477]: User policy value 'DisableRollback' is 0
MSI (s) (38:8C) [15:45:04:477]: Machine policy value 'DisableRollback' is 0
MSI (s) (38:8C) [15:45:04:477]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:8C) [15:45:04:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:8C) [15:45:04:478]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:8C) [15:45:04:478]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (38:8C) [15:45:04:478]: Restoring environment variables
MSI (c) (C4:BC) [15:45:04:481]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C4:BC) [15:45:04:481]: MainEngineThread is returning 1639
=== Verbose logging stopped: 1/27/2014 15:45:04 ===
Please advice. I searched many places and did not get actual solution that will resolve my case.
Nusrat Akhter

Hi Nusrat Akhter,
According to your description, when installing the first install failed, and it looks like the instance did not uninstall completely. To solve the issue I recommend you changed the instance name in re-installing SQL Server, and check if it can work fine.
There is a similar issue that the SQL engine will not start, and there is no method of uninstalling either it, or any of the components etc. You can review the following post.
https://connect.microsoft.com/SQLServer/feedback/details/710892/sql-server-2012-rc0-install-fails-citing-invalid-drivers
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server log file

We are facing one issue can anyone please help me out.
Logs are getting full in below path . Can we remove the logs ? is it archive logs ?
Path : H:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA

If T-Log backups are configured then the log automatically get truncated once backup is compelted. If you dont have backups configured and you dont want to save the transactions you can manually truncate it
Hi,
From SQL Server 2008 onwards truncate_only is removed, it is replaced by
backup log db_name to disk='Null'
Also if your log is growing AND YOU DONT NEED POINT IN TIME RECOVERY switch recovery model to simple it will force checkpoint and logs will get truncated( If transaction does not requires the log) . Avoid using backup log to null or truncate only.
Swapna,
>>Also if you dont want the transactions to be saved then you can set the recovery model and Simple
This is incorrect language used saving/committing transaction does not depends on recovery model. Recovery model only controls logging and recovery. if transaction is committed it will be present in database no matter what recovery model you use.
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

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.

I see most recent file is called sql server log shipping work file

What is "SQL server log shipping work file"?

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/62a6556e-6655-4d19-9112-1788cf7bbcfc/wrk-file-in-logshipping-2005
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

How to Open Or read SQL Server log file .ldf

Hi all,
How to Open Or read SQL Server log file .ldf
When ever we create database from sql server, it's create two file. (1) .mdf (2) .ldf.
I want to see what's available inside the .ldf file.
Thanks,
Ashok

I am not too sure but may be the below two undocumented commands might yield the desired result.
DBCC Log
Fn_dblog function
Refer these links for more info,
http://www.mssqlcity.com/Articles/Undoc/SQL2000UndocDBCC.htm
http://blogs.sqlserver.org.au/blogs/greg_linwood/archive/2004/11/27/37.aspx
http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1173464,00.html
Some 3rd party tools like Log Explorer can do the job for you.
http://www.lumigent.com/products/le_sql.html
- Deepak

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

Crystal Report 2008 results "Password did not match error" in SQL Server Log

Hi,
I am trying to develop some crystal reports using Crystal Report 2008 SP4 to connect to SQL server 2008 through RDO (ODBC). My problem is that anytime Crystal Report is trying to establish a connection with SQL Server, first it tries to connect with the wrong password and results the following error message in SQL Server log:
Login failed for user 'peyman'. Reason: Password did not match that for the login provided. [CLIENT: 192.168.2.198]
The login name 'peyman' is the right one as I have quoted the same in setting up ODBC System DSN using "SQL Server Native Client 10". But somehow Crystal Report is taking its chance and trying to connect before prompting me for the password. After this error logged to SQL server side, I can see Crystal Report pops up the prompt to enter DSN password. After supplying password to this prompt, Crystal Report works fine and pulls the data and renders the report without having any more incorrect password error logged to SQL Server.
The attached file shows the step I am taking to regenerate the issue. I need this to be fixed as anytime uses any of these reports and tries to render it with crystal runtime engine the same error message raises in SQL Server side and logged in the log file.
Thanks,

Hi Peyman,
This is the way it should work, In CR designer when you open the report it does nothing. As soon as you hit the Refresh button then CR tries to use the connection saved with the report. It assumes what is saved with the report is a valid server and connection info. CR simply tries to verify the server is still active.
If you don't want it to fail in CRD then before opening any report Click the File, Log on Database option and connect. Now when refreshing reports it won't log the failed.
In the SDK it does the same thing, it assumes the Server info is the same and does try to connect to verify the Server does exist. It only takes a few milli-seconds to do this
To stop this from happening set the log on info first then it won't log the attempt to connect, it's checking to see if Trusted is allowed.
TIMESTAMP    THREAD_ID    FILENAME    LINE_NUMBER    LOGGED_DATA    LEVEL
2014-6-2 8:30:11.439    57320    .\QESession.cpp    444    Set Product View Locale: 4105    20
2014-6-2 8:30:11.439    57320    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
2014-6-2 8:30:11.439    57320    .\QESession.cpp    500    Set Process Locale: 4105    20
2014-6-2 8:30:11.440    57320    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
2014-6-2 8:30:11.967    57208    .\QESession.cpp    444    Set Product View Locale: 4105    20
2014-6-2 8:30:11.967    57208    .\QESession.cpp    478    Set Preferred View Locale: 4105    20
2014-6-2 8:30:11.967    57208    .\QESession.cpp    500    Set Process Locale: 4105    20
2014-6-2 8:30:11.968    57208    .\qecommon.cpp    117    This property is currently in a read-only state and cannot be modified. File Name: ".\QEProperty.cpp". Line: 217    1
2014-6-2 8:30:11.999    57208    .\QESession.cpp    444    Set Product View Locale: 1033    20
2014-6-2 8:30:12.4    57320    .\qecommon.cpp    117    This value is write-only. File Name: ".\QEProperty.cpp". Line: 145    1
2014-6-2 8:30:56.278    57208    .\odbcapi.cpp    301    Beginning COdbcapi::DriverConnect    20
2014-6-2 8:30:56.342    57208    .\odbcapi.cpp    335    Ending COdbcapi::DriverConnect    20
2014-6-2 8:30:56.342    57208    .\connect.cpp    2170    SQLDriverConnect succeeded: DSN = 192.168.13.172, User ID = sa, Password = ********    10
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 826    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 854    1
2014-6-2 8:30:56.348    57208    .\qecommon.cpp    117     File Name: ".\QEQueryInfo.cpp". Line: 916    1
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    1184    Beginning CQERowset::readFirstRecord    20
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2149    Beginning CQERowset::restart    20
2014-6-2 8:30:56.348    57208    .\QERowset.cpp    2370    Beginning CQERowset::execute    20
2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    514    Query Targets: sqlncli10, ODBC3SQLServer    10
2014-6-2 8:30:56.353    57208    .\DbQueryBuilder.cpp    525    Successfully built query:    SELECT "Orders"."Customer ID", "Orders"."Employee ID"   FROM   "xtreme"."dbo"."Orders" "Orders"    10
2014-6-2 8:30:56.353    57208    .\odbcapi.cpp    875    Beginning COdbcapi::ExecDirect    20
2014-6-2 8:30:56.354    57208    .\odbcapi.cpp    884    Finishing COdbcapi::ExecDirect    20
2014-6-2 8:30:56.354    57208    .\rowset.cpp    220    SQLExecDirect succeeded: SELECT "Orders"."Customer ID", "Orders"."Employee ID" FROM   "xtreme"."dbo"."Orders" "Orders"    10
2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Customer ID is using client buffer    10
2014-6-2 8:30:56.354    57208    .\QERowset.cpp    2814    bindToField succeeded: Orders.Employee ID is using client buffer    10
Notice it doesn't try to connect first if I set the log on info first using code.
So nothing we can do to stop SQL server from logging this info. Check with the DBA, possibly they can "filter" out the application attempts to connect or change your work flow in the app.
If you have a Preview Button to view the report then simply add your Database log on info prompt there if Connectioninfo.Trusted is not true:
mainSecureDB = rpt.Database.Tables[tableIndex].LogOnInfo.ConnectionInfo.IntegratedSecurity;
if mainSecureDB = false then prompt the user for log on info and set accordingly, if it is true the it should not fail when it connects.
This is simply a matter of changing your App work flow...
Thanks
Don

Moving Default Trace File in SQL Server

How can I move the default trace file in SQL server?
SQL Server 2012?
Thanks in advance
ebro

Please have a look at these links:
Change path for default SQL Server trace
Steps to change the default location of SQL Server /SQL Server Agent - Error log files
DETERMINING DEFAULT TRACE LOCATION
Collecting the Information in the Default Trace
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog

Loading a CSV file to Sql Server

Hi,
How can i load a csv file, which is in a shared location itn osql using bods.
Where can i create the data source pointing to csv file

Hi,
Use fileformat to load CSV file into SQL server, below the details
A file format defines a connection to a file. Therefore, you use a file format to connect to source or target data when the data is stored in a file rather than a database table. The object library stores file format templates that you use to define specific file formats as sources and targets in data flows.
To work with file formats, perform the following tasks:
• Create a file format template that defines the structure for a file.
• Create a specific source or target file format in a data flow. The source or target file format is based on a template and specifies connection information such as the file name.
File format objects can describe files of the following types:
• Delimited: Characters such as commas or tabs separate each field.
• Fixed width: You specify the column width.
• SAP transport: Use to define data transport objects in SAP application data flows.
• Unstructured text: Use to read one or more files of unstructured text from a directory.
• Unstructured binary: Use to read one or more binary documents from a directory.
More details, refer the designer guide
http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_designer_en.pdf

Sql server log shipping space consumption

I have implemented sql server logs shipping from hq to dr server
The secondary databases are in standby mode .
The issue is that after configuring it , my dr server is running out of space very rapidly
I have checked the log shipping folders where the trn files resides and they are of very decent size , and the retention is configured for twenty four hours
I checked the secondary databases and their size is exactly same as that of the corresponding primary databases
Could you guys please help me out in identifying the reason behind this odd space increase
I would be grateful if you could point me to some online resources that explains this matter with depth

The retention is happening . I have checked the folders they do not have records older then 24 hours .
I dont know may be its because in the secondary server (Dr) there is no full backup job working , is it because of this the ldf file is getting bigger and bigger but again I far as my understanding goes we cannot take a database full backup in the stand
by mode .
The TLog files of log shipped DBs on the secondary will be same size as that of primary. The only way to shrink the TLog files on secondary (I am not advising you to do this) is to shrink them on the primary, force-start the TLog backup job, then the copy
job, then the restore job on the secondary, which will sync the size of the TLog file on the secondary.
If you have allocated the same sized disk on both primary and secondary for TLog files, then check if the Volume Shadow Copy is consuming the space on the secondary
Satish Kartan www.sqlfood.com

How to run Exe file through Sql server agent job

Hello All
i have 2 servers
1.Application Server
2.Database server
Application server has a .exe file so i wanted to run this exe file through SQL server agent job from database server.
What is the process for run this Exe file
Can you plz suggest me step by step process
Kamal

While i'm trying to implement this below method
Step1 : Right Click SQL Server Agent. Select New -> Job. This will open a wizard to schedule a new
job.
Step2 : Select Steps from options given on the left side of wizard. This is the main place to set your
exe\program as a running step. Give some name to this step, Select Operating System (cmdexec) for the Type and give the full path of exe in Text box for Command.
ex:\\10.11.00.98(your application serverIP)\ch.exe
Thanks vanchan-Please
mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
I got this below error
Message
Executed as user:NJROSJ345\SYSTEM. The process could not be created for step1 of job
(Reason:Access is Denied)The step failed.
But i have sys admin rights on the both the servers
Kamal

Warning: Failure to calculate super-latch promotion threshold. appears in SQL Server log

We are running SQL Server 2008 R2 and have just applied Service Pack 2 to our QA environment.
Today we noticed this message in the SQL Server log:
Warning: Failure to calculate super-latch promotion threshold.
Can someone please tell us what this means and how to fix whatever it is?
There is no associated error message number.
We believe this message is new with Service Pack 2. Can someone tell us for sure?
This entry has occurred in the middle of the night when nothing was running that we could see and during the day.
Environment
SQL server 10.50.4000
Windows Server 2008 R2 Standard Service pack 1
Server has 4 processors, 8 Gig of Ram with 4 Gig set for SQL Server. Usage is generally light as it is a test environment.
KD

Its just a warning message about super latch .
Since SQL 2005 SuperLatches have been introducted which can enable increased performance for accessing the shared pages in the database for a multiple concurrency workload which intrun requires worker threads require SH (shared) latches. No need to set or
enable any configuration this is performed automatically/dynamically based on the mutli-CPU configuration to promote a latch on a page to be a super-latch. Then this SuperLatch partitions the single latch into array of sublatch structure per CPU core.
Super latches are way of promoting a latch for entire NUMA Node to reduce contention.
you can also read following detailed article
http://blogs.msdn.com/b/psssql/archive/2010/03/24/how-it-works-bob-dorr-s-sql-server-i-o-presentation.aspx
Soldier..Sir we are surrounded from all sides by enemy.. Major: Good, we can attack in any direction Thats attitude..

How to link Excel 2010 .XLSX file to SQL server 2008R2 - a method that actually works?

I have been trying unsuccessfully to link my excel file to SQL server like I used to with SQL 2005.
In SQL 2008R2 I have installed the 64-bit data access components from Office 2010 to get the provider 'Microsoft.ACE.OLEDB.12.0' avilable.
When I try this command:
SELECT
FROM
OPENDATASOURCE(
'Microsoft.ACE.OLEDB.12.0',
'Data Source="E:\ADUpdates\Employee List1.xlsx"; Extended properties=Excel 12.0')...[Sheet1$]
I get this error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)" reported an error. Access denied.
Msg 7301, Level 16, State 2, Line 1
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)".
The Access Denied error seems to be form the worksheet and not the file itself. Evidence is that if I enter a bogus sheet name it tells me the sheet doesn't exist and after this error the file is locked open and can't be saved again from Excel until the
query windows is closed. The sheet is not protected in Excel so I don't know how access to it can be denied.
Does anyone actually have this working in SQL 2008R2?

Some minor progress on this issue by running SQL Server service under a domain account with Administrator priv on the SQL server.
This query now works in a query window:
SELECT * FROM OPENDATASOURCE( 'Microsoft.ACE.OLEDB.12.0', 'Data Source="E:\ADUpdates\Employee List.xlsx"; Extended properties=Excel 12.0')...[EmployeeData];
However, creating a Linked server object for the same spreadsheet still does not work:
EXEC master.dbo.sp_addlinkedserver @server = N'TEST', @srvproduct=N'Excel 12.0', @provider=N'Microsoft.ACE.OLEDB.12.0', @datasrc=N'E:\ADUpdates\Employee List.xlsx'
The test connection to the linked server failed.
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "TEST".
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "TEST" returned message "Unrecognized database format 'E:\ADUpdates\Employee List.xlsx'.". (Microsoft SQL Server, Error: 7303)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=7303&LinkId=20476
Naturally, the help link provided only confirms the contempt microsoft holds for their customers by not providing any information at all.
(appologies for the weird colour and fonts, this is a microsoft product, just have to live with obvious defects).

Problem attaching mdf file in sql server 2008

hi...!
I have an mdf file of sql server 2005 database now i want it to attach in sql server 2008 R2 but when i try to attach it, it gave me error saying.
Fail to retrieve data for this request.
An exception occur while executing a Transact-SQL statement or batch.(Microsoft.sqlServer.connectionInfo)
C:\program files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\file6.mdf is not a primary database file. (Microsoft SQL Server, Error:5171)
Thanks in advance

hi...!
I have an mdf file of sql server 2005 database now i want it to attach in sql server 2008 R2 but when i try to attach it, it gave me error saying.
Fail to retrieve data for this request.
An exception occur while executing a Transact-SQL statement or batch.(Microsoft.sqlServer.connectionInfo)
C:\program files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\file6.mdf is not a primary database file. (Microsoft SQL Server, Error:5171)
Thanks in advance
Hello,
As the message says the file is not primary data file ,i guess it must be ndf(secondary data file) or some other file you might have selected by mistake.PLease select primary data file and try attching you will succed
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

New Files in SQL Server Log Directory

Similar Messages

Maybe you are looking for