Here is the command I'm running from SSMS:įROM OPENROWSET('.12.0',
OLE DB provider ".12.0" for linked server "(null)" returned message "Unspecified error".Ĭannot initialize the data source object of OLE DB provider ".12.0" for linked server "(null)". But when I attempt the OPENROWSET below, I am now seeing this error: I'm on Win10 64 and I beleive I've followed all the steps, I now see both the OLEDB.12.0 and OLEDB.16.0 and have run the AllowProcess for both. I'm attempting this on a test db on my local machine before trying it on the server. Hi Diana, thank you very much for these tips. It doesn't work from the web server calling the procedure OR from SSMS when I uncheck InProcess.Īny suggestion on getting past this? Tried several security options (folder permissions for the OS User running SQL) found on other posts but that hasn't helped. It works when I check "InProcess" within SSMS, but we are trying to run this from the web server, executing the SPs that read the XLSX file into a temp table. Upon splitting SQL to a 2nd machine, we can't get past the ".12.0" for linked server "(null)" reported an error. We have been using this method for years on our web server that also hosted the SQL Server. I do this on a regular basis for multiple clients. I would suggest instead checking out Doug Finke's import-excel for powershell, which, in combination with Write-SQLTableData makes it fairly easy to import excel data right into SQL Server. If you use the ACE provider on the server, especially in automated processes or processes running in parallel, you may see unexpected results. The ACE provider (formerly the Jet provider) that connects to Excel data sources is intended for interactive client-side use. In addition, I came across the following i Microsoft Documentation: I went down this path once - however all the changes drove me bonkers. Foreach ($provider in ::GetRootEnumerator())Īdam, thanks for the blog link, I'm also using Powershell to import Excel files on a scheduled basis.
0 kommentar(er)
