SQL server 2014 and VS 2013 - BuilInsert task - truncate a field data of a CSV file and insert it to SQL table.

Hello everyone,
To move data from roughly 50 CSV files in a loop to SQL tables (table per CSV file), I've used BulkInsert task in For each loop container.
Please know, for all different columns of all CSV files, the filed length was specified as varchar(255).
It worked well for the first 6 files but on 7th file, it has found the data in one of the columns of CSV file, which exceeds the limit of 255 characters. I would like to truncate the data and insert the remaining data for this column. In other words, I would
like to insert first 255 characters into table for this field and let the package execute further.
Also, if I would use SQLBulkCopy in Script task, will it be able to resolve this problem? I believe, I would face the similar problem over there too. Although, would like to get confirmation for the same from experts.
Can you please advise how to get rid of this truncation error?
Any help would be greatly appreciated.
Thanks, Ankit Shah <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Hello! I suggest you add a derived column transformation between Source and Destination, use string functions to extract first 255 characters from the incoming field and send this output to destination field, that ways you can get rid of these sort of issues.
Useful Links:
http://sqlage.blogspot.in/2013/07/ssis-how-to-use-derived-column.html
Good Luck!
Please Mark This As Answer if it solved your issue.
Please Vote This As Helpful if it helps to solve your issue

Similar Messages

SQL server 2014 in VS 2013 - Develop 3 different types of packages and maintain them efficiently

Hello Everyone,
I’ve been assigned a task to develop 3 different SSIS packages.
Package 1 – There will be roughly 50 CSV files, I need to read them one by one and create a new database and a table per CSV file in SQL 2014.
This will be a one-time job.
Which is the best option in SSIS package to create database and tables in SQL 2014? I assume I need use “Execute Script Task” here, although please advise.
Package 2 – This will run on daily basis. It will again read those 50 CSV files one by one and migrate their data to tables.
Also, out of 50, couple of files (the exceptional file names have to be configured somewhere as client might add some more files for it out of 50) needs to be treated in different way.
For them the tables have to be truncated first and then insert data into them.
Which is the optimal and fastest way to move such data from these files to SQL tables? Can I run the parallel job in for each loop container?
Where should I configure such “no ordinary” file names?
Package 3 – This job will run once a six months. It will basically perform a purge for the data.
This needs to be parameterized where client can set-up a cut-of-date for it and it will delete the data from all these 50 tables at SQL server.
How to allow a client to insert the cut-of-date?
What is the optimal option to read all tables of database (50 tables) and perform purge based on the cut-of-date?
Common question:
Where should I keep the path for the folder from where I need to pick the CSV files?
How should I deploy and schedule package 2 and 3?
Can anybody please advise what are the efficient/standard ways to maintain such packages?
Any help on this would be greatly appreciated.
Thanks, Ankit Shah <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

You can create a Table in your Database to store all folder path and/or other parameter values (i.e. Error
File Path, Export/Archive file folder path, email address for notification, SSIS catalog deployed folder/project name etc).
For Project deployment: Deploying
the Lesson 6 Package
After deploying the project, use SQL Agent to schedule Scheduling SSIS packages
with SQL Server Agent
web: www.ronnierahman.com

Exporting data to a csv file and include column names

I am creating a SSIS package which creates a .csv file. The package works fine except it is not putting the column names as the first row.
How do I get the column names to also export?
Thanks,
~John

SQL Server 2012 T-SQL has the new FORMAT command:
SELECT FORMAT(CONVERT(MONEY,123456.78),'c0','en-US'), -- $123,457
FORMAT(CONVERT(MONEY,123456.78),'c2','en-US'), -- $123,456.78
FORMAT(CONVERT(MONEY,123456.78),'c2','en-GB'), -- £123,456.78
FORMAT(CONVERT(MONEY,123456.78),'c2','de-DE') -- 123.456,78 €
Prior to SS 2012:
SELECT CONVERT(varchar(40),CONVERT(MONEY,123456.78),1) -- 123,456.78
SSIS Import/Export Wizard:
http://www.sqlusa.com/bestpractices/ssis-wizard/
Kalman Toth SQL 2008 GRAND SLAM
New Book: SQL Programming & Database Design Using Microsoft SQL Server 2012

SQL Server 2014 with AGs - Over 6 million DONE tasks in dm_os_tasks

Hello,
We've noticed that our SQL Server deployment has a very high number of tasks in the done state. On our 5 node cluster we have values in the millions on most servers (depending on last restart time), with our highest server returning over 6 million
for the following query:
select count(*)
from sys.dm_os_tasks
where task_state = 'done'
We also track the count daily, and we have never seen the number of tasks decrease. The average growth per day is 50,000. The servers are all running SQL Server 2014 Enterprise Edition CU2 (build 12.0.2370). The servers host between 4 and 8
availability groups each, with 1 to 3 databases per AG.
We're a little concerned that this behaviour is very reminiscent of that noted in the Memory Leak in 2012 KB 2877100), and wondered if anyone else is having a similar experience with 2014 AGs?
We did open a product support case for a separate issue where we mentioned this, but were told that until we could provide a memory dump of a crashing instance we wouldn't be able to investigate if this was actually a leak.
Any advice or discussion that suggests this behaviour is actually 'worked as intended' would be appreciated.
Kind Regards,
Tim

Hi Tim,
This does indeed look quite reminiscent of 2877100 and this behavior does certainly seem abnormal, particularly if you can establish memory consumption growth over time. I'd recommend providing MSFT additional statistics regarding memory usage via DMVs and
perfmon if you haven't already.
Product support is still definitely the recommended route - and you might try escalating or asking for another engineer. I understand why they are asking for this information, but perhaps ask if they can provide less invasive methods for root cause
analysis. If the answer is still "no" - hopefully you have a prod-like environment where you can reproduce this? And if so, then the memory dump is less of a risk in non-prod.
Best Regards, Joe Sack, MVP, SQL MCM | SackHQ.com

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

Error message when installing SQL Server 2014 Express

When installing SQL Server 2014 Express,
I get the error shown below.
Why do I get this and how to correct for it?
TITLE: Microsoft SQL Server 2014 Setup
The following error has occurred:
An error occurred during the installation of assembly 'Microsoft.VC80.MFC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more
information. HRESULT: 0x80070422.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xDF039760%25401201%25401
BUTTONS:
OK
Thanks

Hi,
here is the log file:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068052081
Start time: 2015-04-14 10:25:00
End time: 2015-04-14 10:38:21
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for Browser: Use the following information to resolve the error, and then try the setup process again.
Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: BRENDA-PC-HOME
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: italiano (Italia)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Brenda\Downloads\SQLEXPRWT_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\SERVIZIO DI RETE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, CONN, BC, SDK, SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Brenda-PC-Home\Brenda
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: true
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Setup Support Files
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 Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SystemConfigurationCheck_Report.htm

Installing SQL Server 2014 Express package as ClickOnce prerequisite

I'm using clickOnce and deploying an installer with it.
I have tried various settings. Using SQL Server 2008 Express and SQL Server 2012 Express as prerequisite is all ok (I've dowloaded them and set the option of clickonce "download prerequisites from the same path of app").
Now I'm trying to do the same thing with SQL Server 2014 Express.
Since the SQL Server 2014 Express package isn't alredy done line 2008 and 2012 versiones, I'm trying to create it.
I have done and it seems to work, but while installing it gives error number **-2054422506**. It is a very generic error and I don't understand it.
It appears a pop up saying the installation is stopped because it is an error installing SQL Server Express 2014 and to look the log for more infos.
The log only says:
 Installing using command
 'C:\Users\VIRTUA~1\AppData\Local\Temp\VSD24F4.tmp\SqlExpress2014\
 SQLEXPR32_x86_ITA.EXE' and parameters '/q /action=Install /features=SQL
 /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is
 /sqlsvcaccount="NT Authority\Network Service'
 Process exited with code -2054422506
 Status of package 'SQL Server 2014 Express' after install is 'InstallFailed'
So, I've tried to install SQL Server 2014 Express manually, without ClickOnce, and it works. So I think I've made some mess in the xml file of the package.
My package is so build (in C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\Bootstrapper\Packages\):
 \SqlExpress2014
 \it
 SQLEXPR32_x86_ITA.exe
 SQLEXPR_x64_ITA.exe
 eula.rtf
 package.xml
 product.xml
 SqlExpressChk.exe
This is my package.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<Package
xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"
Name="DisplayName"
Culture="Culture"
LicenseAgreement="eula.rtf">
<PackageFiles CopyAllPackageFiles="false">
<PackageFile Name="SQLEXPR32_x86_ITA.EXE"/>
<PackageFile Name="SQLEXPR_x64_ITA.EXE" />
<PackageFile Name="eula.rtf"/>
</PackageFiles>
<InstallChecks>
<ExternalCheck Property="SQLExpressChk" PackageFile="SqlExpressChk.exe" Arguments="11.0.2100 1040"/>
</InstallChecks>
<Commands Reboot="Defer">

<Command PackageFile="SQLEXPR32_x86_ITA.EXE"
Arguments='/q /action=Install /features=SQL /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /sqlsvcaccount="NT Authority\Network Service"
/IAcceptSqlServerLicenseTerms /SQLSVCPASSWORD="234692Is" /SQLSYSADMINACCOUNTS="NT Authority\Network Service" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"'
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<FailIf Property="VersionNT" Compare="ValueNotExists" String="InvalidPlatformOS"/>
<FailIf Property="VersionNT" Compare="VersionLessThan" Value="6.0.0" String="InvalidPlatformOS"/>
<FailIf Property="VersionNT" Compare="VersionLessThan" Value="6.0.2" String="InvalidPlatformOSServicePack"/>
<FailIf Property="VersionNT" Compare="VersionEqualTo" Value="6.1.0" String="InvalidPlatformOSServicePack"/>
<FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="AdminRequired"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-1" String="InvalidUpgradeNotExpress"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-2" String="InvalidUpgradeNotExpressCore"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-3" String="InvalidUpgradeLanguage"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-4" String="InvalidUpgradeWoW"/>
<FailIf Property="SQLExpressChk" Compare="ValueLessThan" Value="-4" String="GeneralFailure"/>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="Intel"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="1"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>

<Command PackageFile="SQLEXPR32_x86_ITA.EXE"
Arguments="/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck"
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="Intel"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="2"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>

<Command PackageFile="SQLEXPR_x64_ITA.EXE"
Arguments='/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck'
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="amd64"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="1"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>

<Command PackageFile="SQLEXPR_x64_ITA.EXE"
Arguments="/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck"
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="amd64"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="2"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>
</Commands>
<Strings>
<String Name="DisplayName">SQL Server 2014 Express</String>
<String Name="Culture">it</String>
<String Name="SqlExpr32Exe">http://download.microsoft.com/download/1/6/E/16E343FB-7961-457C-A9C9-E6919F2B7188/Express%2032BIT/SQLEXPR_x86_ITA.exe</String>
<String Name="SqlExpr64Exe">http://download.microsoft.com/download/1/6/E/16E343FB-7961-457C-A9C9-E6919F2B7188/Express%2064BIT/SQLEXPR_x64_ITA.exe</String>
<String Name="AdminRequired">Non si dispone delle autorizzazioni necessarie per installare SQL Server 2014 Express. Rivolgersi all'amministratore.</String>
<String Name="GeneralFailure">Errore durante il tentativo di installazione di SQL Server 2014 Express.</String>
<String Name="InvalidPlatformOS">La versione del sistema operativo corrente non supporta SQL Server 2014 Express.</String>
<String Name="InvalidPlatformOSServicePack">Il sistema operativo corrente non soddisfa i requisiti di livello di Service Pack per SQL Server 2014 Express. Installare il Service Pack più recente dall'Area download Microsoft all'indirizzo http://www.microsoft.com/downloads prima di continuare l'installazione.</String>
<String Name="InvalidPlatformOSLanguage">La versione italiana di SQL Server 2014 Express può essere installata unicamente in un sistema operativo Windows nella stessa lingua.</String>
<String Name="AnotherInstanceRunning">Un'altra istanza del programma di installazione è già in esecuzione. Per continuare, è necessario attendere il completamento di tale istanza.</String>
<String Name="BetaComponentsFailure">È stata rilevata una versione beta di .NET Framework o SQL Server nel computer. Disinstallare le versioni beta precedenti dei componenti di SQL Server 2014, dei file di supporto di SQL Server o di .NET Framework prima di continuare.</String>
<String Name="InvalidPlatformArchitecture">Questa versione di SQL Server 2014 Express non è supportata per l'architettura del processore corrente.</String>
<String Name="InvalidUpgradeNotExpress">L'istanza di SQL Server denominata 'SQLEXPRESS' non è un'istanza di SQL Server Express. Impossibile eseguirne l'aggiornamento a SQL Server 2014 Express.</String>
<String Name="InvalidUpgradeNotExpressCore">L'istanza di SQL Server Express denominata 'SQLEXPRESS' contiene componenti non inclusi in SQL Server 2014 Express. Impossibile eseguire l'aggiornamento di tale istanza in SQL Server 2014 Express. Utilizzare SQL Server 2014 Express with Advanced Services.</String>
<String Name="InvalidUpgradeLanguage">L'istanza di SQL Server Express denominata 'SQLEXPRESS' è una versione in una lingua diversa rispetto a SQL Server 2014 Express. Impossibile eseguire l'aggiornamento di tale istanza.</String>
<String Name="InvalidUpgradeWoW">Impossibile eseguire l'aggiornamento dell'istanza esistente di SQL Server Express (x64 WoW) denominata 'SQLEXPRESS' mediante SQL Server 2014 Express (x64). Disinstallare l'istanza esistente di SQL Server Express e riprovare a installare SQL Server 2014 Express (x64).</String>
</Strings>
</Package>
And this is the product.xml:
<?xml version="1.0" encoding="utf-8"?>

<Product xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" ProductCode="Microsoft.SqlServer.Express.12.0">
<RelatedProducts>
<EitherProducts>
<DependsOnProduct Code=".NETFramework,Version=v4.5" />
<DependsOnProduct Code=".NETFramework,Version=v4.0" />
</EitherProducts>

<IncludesProduct Code="Microsoft.Sql.Server.Express.1.0" />
<IncludesProduct Code="Microsoft.Sql.Server.Express.9.2" />
<IncludesProduct Code="Microsoft.Sql.Server.Express.10.0" />
<IncludesProduct Code="Microsoft.SqlServer.Express.10.5" />
<IncludesProduct Code="Microsoft.SqlServer.Express.11.0" />
</RelatedProducts>
<PackageFiles>
<PackageFile Name="SqlExpressChk.exe" />
</PackageFiles>
</Product>
I've copied the SqlExpressChk.exe file from the SQL Server 2012 Express package, hoping it is the same (2008 and 2012 versions seems the same, so I supposed it also for the 2014).
I've delete the part in package.xml about the publicKey, since I don't know it and, further, I think I don't need it.
In the same file, I've inserted custom parameters, first like in the 2008 and 2012 versions, then doing some attempts (without success).
Did anyone have this problem? How did you have manage it?
**NOTE**: I'm using my clickOnce deploy in an empty virtual machine, so there aren't any conflicts o something similar.
More attempts, more failures, always the same error! I'm deleting the optional stuff to study better the core of the xml, but still no success.. does microsoft have a package of sql server 2014 express?

refer to this link
http://bootstrapper-manifest-generator-for-vs20.software.informer.com/2.0/
remember make the reply as answer and vote the reply as helpful if it helps.
thanks! =)
SqlServer usually runs a file (SqlExpressChk.exe) to see if there is already an installation and a sql instance called sqlExpress (for the express installations). Do you know how can do this test with the bootstrapper manifest generator?
I am not able to test it currently, but I assume that will also check whether that has installed.
You have tested it, right?
remember make the reply as answer and vote the reply as helpful if it helps.

SQL Server 2014 issues

Hello:
I have bumped upon a design issue with SQL Server 2014.
I want to report this to Microsoft, where it can be addressed and corrected in the upcoming Service packs.
This is something critical.. (that's what at least....I feel).
Please let me know the link/Forum where I can post this.
Thanks

Two possibilities. On Microsoft connect
https://connect.microsoft.com/SQLServer/Feedback
or in SQL Server forums.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

SQL Server 2014 - Columnstore Incorrect Results

Hello,
we are running into a problem with SQL Server 2014 and the columnstore index. We have a partitioned table with about 300 Million records in it. With SQL Server 2012 this has been in use without problems.
Since we upgraded to SQL Server 2014, the exact same queries on exactly the same data return incorrect results. We can only bypass the problem by either dropping the CS Index or adding a maxdop = 1 query hint.
I thought this was an old bug in SQL Server 2012? We have not installed the CU Pack 4 for SQL Server 2014, yet but will it solve the problem (assuming others have faced the same problem)
We are running: Microsoft SQL Server 2014 Enterprise Edition - 12.0.2000.8 (X64) on a 2x6Core Machine
Thanks in advance!

SQL Server 2012 only featured non-clustered columnstore indexes which were separate structures. Have you changed to a clustered columnstore (cs) index in SQL Server 2014? (ie dropped your non-clustered cs, created a cs)
There are a number of fixes that reference columnstore indexes in the current CUs (
CU1,
CU2, CU3,
CU4 ), but none which sound exactly like your problem.
This sounds similar and is fixed in CU1. You should review the CU documents yourself to see if any of them mention a similar problem and then consider applying the CU. You might also try applying them to a test environment, or a temporary Azure
VM for example to see if one of them solves your problem.
If you can create a reliable "repro" of the problem, consider raising a
connect item which is a Microsoft bug report.

SCVMM support for Microsoft SQL Server 2014

Hi
Does anybody know if Microsoft SQL Server 2014 supported and/or does it work, when installing SCVMM 2012. Current documentation stills says SQL Sever 2012.
Thanks

hi,
SQL Server 2014 is not supported: https://technet.microsoft.com/en-us/library/dn281933.aspx
I did not test if SQL 2014 works.
regards,
Thomas
Thomas Hanrath [MCT | Regional Lead Germany]
Thomas Hanrath Private Cloud Blog
Microsoft Learning and Certification Blog
Follow me on Twitter

Windows 8.1 SQL Server 2014 Enterprise Error Number: 18456

I didn't have this problem with the Sql 2014 Developer but not I am having issues with the Enterprise Edition giving me the following error I am using Windows 8.1:
Server Name: GERRY
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
Program Location:
 at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
 at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
 at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
 at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
 at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
 at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
 at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
 at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
 at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
 at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
 at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
 at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
 at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
 at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
 at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
 at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
 at System.Data.SqlClient.SqlConnection.Open()
 at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
 at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

2014-04-24 17:19:15.09 Logon Error: 18456, Severity: 14, State: 5.
2014-04-24 17:19:15.09 Logon Login failed for user 'MicrosoftAccount\[email protected]'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
This is the error I get during installation:
TITLE: Microsoft SQL Server 2014 Setup
The following error has occurred:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
This is what I found under the Errorlog files:
2014-04-24 18:38:16.07 spid17s Error: 17190, Severity: 16, State: 1.
2014-04-24 18:38:16.07 spid17s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-04-24 18:38:16.07 spid17s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-04-24 18:38:16.08 spid7s Starting up database 'msdb'.
2014-04-24 18:38:16.08 spid17s Error: 17182, Severity: 16, State: 1.
2014-04-24 18:38:16.08 spid17s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-04-24 18:38:16.08 spid9s Starting up database 'mssqlsystemresource'.
2014-04-24 18:38:16.08 spid17s Error: 17182, Severity: 16, State: 1.
2014-04-24 18:38:16.08 spid17s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-04-24 18:38:16.08 spid17s Error: 17826, Severity: 18, State: 3.
2014-04-24 18:38:16.08 spid17s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-04-24 18:38:16.08 spid17s Error: 17120, Severity: 16, State: 1.
2014-04-24 18:38:16.08 spid17s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Ok, now how do you fix this?

SQL server 2014 and VS 2013 - Dataflow task, read CSV file and insert data to SQL table

Hello everyone,
I was assigned a work item wherein, I've a dataflow task on For Each Loop container at control flow of SSIS package. This For Each Loop container reads the CSV files from the specified location one by one, and populates a variable with current
file name. Note, the tables where I would like to push the data from each CSV file are also having the same names as CSV file names.
On the dataflow task, I've Flat File component as a source, this component uses the above variable to read the data of a particular file. Now, here my question comes, how can I move the data to destination, SQL table, using the same variable name?
I've tried to setup the OLE DB destination component dynamically but it executes well only for first time. It does not change the mappings as per the columns of the second CSV file. There're around 50 CSV files, each has different set off columns
in it. These files needs to be migrated to SQL tables using the optimum way.
Does anybody know which is the best way to setup the Dataflow task for this requirement?
Also, I cannot use Bulk insert task here as we would like to keep a log of corrupted rows.
Any help would be much appreciated. It's very urgent.
Thanks, Ankit Shah <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

The standard Data Flow Task supports only static metadata defined during design time. I would recommend you check the commercial COZYROC
Data Flow Task Plus. It is an extension of the standard Data Flow Task and it supports dynamic metadata at runtime. You can process all your input CSV files using a single Data Flow Task
Plus. No programming skills are required.
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Upgrade DTSX packages from VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014

Hello everyone,
I’m very new to SSIS world. I’ve been assigned a task to upgrade the existing packages running in VS 2010 with SQL Server 2008 to VS 2013 and SQL Server 2014. And then submit the migration report to my client.
On very quick search at Google, I've found the following link. It seems like I just need to open the existing SSIS project in VS 2013 and follow the wizard.
https://msdn.microsoft.com/en-us/library/cc280547.aspx
Can anybody please advise, are there any other things need to be taken care while doing this up gradation process?
Please share your experience.
Any help would be much appreciated.
Thanks, Ankit Shah <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Hello Arthur,
Thank you for the response.
I just got an access of the packages. They are of VS 2008 and not 2010.
Do you know how to upgrade VS 2008 packaged to VS 2013?
When I tried to open the solution file in VS 2013, it says "incompatible".
Any help would be much appreciated.
Thanks,
Ankit
Thanks, Ankit Shah <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Power Pivot Configuration error while refreshing connection on excel sheet for SharePoint 2013 and Sql server 2014 using BISM file connection

I am getting following error while refreshing connection on excel sheet in power pivot gallery,
my scenario,
using BISM file connection to create and refresh power pivot excel sheet in power pivot gallery
throws error and we have sql server 2014 CU6 updated installed plus sharepoint 2013. i checked following msolap110.dll is available in our environment but assembly
Microsoft.AnalysisServices.ChannelTransport is not available.
i found error in event viewer,
"Activation context generation failed for "C:\Program Files\Microsoft Analysis
Services\AS OLEDB\110\msolap110.dll". Dependent Assembly
Microsoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
not be found. Please use sxstrace.exe for detailed diagnosis.
what should i do to fix it?
Thanks for help.
Deepak Patel

Rebecca,
yes, this is issue i am getting.
Activation
context generation failed for "C:\Program
Files\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll".
Dependent AssemblyMicrosoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
not be found. Please use sxstrace.exe for detailed diagnosis.
let me know if you can find fix for it.
THanks,

SharePoint 2013 and SQL Server 2014

Does SharePoint 2013 supports SQL Server 2014 for Reporting Services, PowerPivot

Yes it does (or rather, SSRS 2014/PowerPivot 2014 support SharePoint 2013). They also support SharePoint 2010.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL server 2014 and VS 2013 - BuilInsert task - truncate a field data of a CSV file and insert it to SQL table.

Similar Messages

Maybe you are looking for