SQL Server 2014 PowerPivot installation on SharePoint 2013
Hello:
I saw many references on the topic but one thing is still not clear.
Is
spPowerPivot.msi installer for SharePoint 2013 is another package that has to run after the
“SQL Server PowerPivot for SharePoint” installation on SharePoint server via SQL Server setup?
Or spPowerPivot.msi is the same thing as “SQL Server PowerPivot
for SharePoint” from SQL Server setup?
I run
spPowerPivot.msi on my SharePoint server, but don't see the SQL Server PowerPivot Configuration manager created.
Please advise
-Jeff
SQL Server PowerPivot for SharePoint is the SQL Server Analysis Services Tabular Mode instance with the instance name POWERPIVOT. The spPowerPivot.msi installs the proxy that connects to the SQL Server Analysis Services Tabular Mode instance. You run the
SQL Server PowerPivot for SharePoint installation on the server that you want to run the SQL Server Analysis Services Tabular Mode instance whereas you run the spPowerPivot.msi installation on all of the servers in your SharePoint farm (except the database
server.) For SQL Server 2014, this is
a separate download and is not included in the SQL Server 2014 installation media.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course
Similar Messages
-
SQL Server 2014 Express Installation Error
I get the error shown below when installing SQL Server 2014 Express. 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 'policy.8.0.Microsoft.VC80.MFCLOC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32-policy"'. Please refer to Help
and Support for more information. HRESULT: 0x80073712.
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
ThanksI have Visual Studio 2013 Professional Update 2 and Visual Studio 2012 Professional Update 4 installed. Here is a section of the log file where the error occurred. Thanks for your help.
(01) 2014-07-07 10:34:28 Slp: Running Action: Install_VSSMO_Cpu32_Action
(01) 2014-07-07 10:34:28 Slp: SetFeaturePropsModifyInstallAction for VSSMO_Cpu32
(01) 2014-07-07 10:34:28 Slp: Sco: File 'C:\Users\xxxxx\Desktop\SQL Server 2014\SQLEXPRADV_x64_ENU\1033_ENU_LP\redist\VisualStudioShell\SMO\x86\SharedManagementObjects.msi' does not exist
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to open registry subkey
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\10.0
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to get registry value InstallDir
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\11.0
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to get registry value InstallDir
(01) 2014-07-07 10:34:28 Slp: Sco: File 'C:\Users\xxxxx\Desktop\SQL Server 2014\SQLEXPRADV_x64_ENU\1033_ENU_LP\redist\VisualStudioShell\SMO\x86\SharedManagementObjects.msi' does not exist
(01) 2014-07-07 10:34:28 Slp: Sco: File 'C:\Users\xxxxx\Desktop\SQL Server 2014\SQLEXPRADV_x64_ENU\1033_ENU_LP\redist\VisualStudioShell\SMO\x86\SharedManagementObjects.msi' does not exist
(01) 2014-07-07 10:34:28 Slp: Checkpoint: PREINSTALL_VSSMO_CPU32_ACTION
(01) 2014-07-07 10:34:28 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to open SC Manager
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to open service handle for service msiserver
(01) 2014-07-07 10:34:28 Slp: Invoking QueryServiceStatus Win32 API
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to close service handle for service msiserver
(01) 2014-07-07 10:34:28 Slp: Sco: Attempting to close SC Manager
(01) 2014-07-07 10:34:28 Slp: Target package: "C:\Users\xxxxx\Desktop\SQL Server 2014\SQLEXPRADV_x64_ENU\1033_ENU_LP\redist\VisualStudioShell\SMO\SharedManagementObjects.msi"
(01) 2014-07-07 10:34:35 Slp: MSI Error: 1935 An error occurred during the installation of assembly 'policy.8.0.Microsoft.VC80.MFCLOC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32-policy"'. Please refer to
Help and Support for more information. HRESULT: 0x80073712.
(01) 2014-07-07 10:34:38 Slp: Attempting to get HResult for what appears to be an Assembly install error
(01) 2014-07-07 10:34:53 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.
(01) 2014-07-07 10:34:53 Slp: Using MSI error code to detect the retry option: 1935
(01) 2014-07-07 10:34:53 Slp: Retry-able MSI return code detected: 1935
(01) 2014-07-07 10:34:53 Slp: Prompting user if they want to retry this action due to the following failure: -
SQL Server 2014 Express Installation Failure
Hi,
Now trying to install SQL Server 2014 Express on my work machine. Here is the error log. Any ideas? The error help link is useless.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-06-19 16:24:17
End time: 2014-06-19 16:38:03
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: PC12345
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Scott\Software\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
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
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, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: C:\SQL Server Data
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
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: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: INTERNAL\sbass
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140619_162416\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: Reporting Services - Native
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140619_162416\SystemConfigurationCheck_Report.htmThanks Shanky, that fixed my issue. I reinstalled, specifying NT AUTHORITY\LOCALSYSTEM for the SQL Server Database Engine account. After the successful installation, I used Sql Server Configuration Manager to change the account to LocalService
(NT AUTHORITY\LocalService). The Database Engine is restarting OK.
So, my accounts are:
SQL Server (MSSQLSERVER): NT AUTHORITY\LocalService
SQL Full-text Fiter Daemon Launcher (MSSQLSERVER): NT Service\MSSQLFDLauncher
SQL Server Reporting Services (MSSQLSERVER): NT Service\ReportServer
SQL Server Browser: NT AUTHORITY\LOCALSERVICE
SQL Server Agent (MSSQLSERVER): NT AUTHORITY\NETWORKSERVICE
I check out the link http://msdn.microsoft.com/en-us/library/ms143504.aspx#Serv_Perm. I'm a bit confused how the NT Service\* accounts are created, such as NT Service\MSSQLSERVER. However, I did see this http://msdn.microsoft.com/en-us/library/ms191153.aspx#manual;
perhaps I need to read it further.
Regardless, this is my desktop machine, the installation is for development only, it's inside our network, and no external users will be accessing this SQL Server instance. So, while I haven't fully read the details on running under LocalService, I
believe this will meet my needs.
Thanks again for your help. -
I'm trying to install SQL Server 2014 Developer. In "global rules" requieres to restart computer. It would not be a big issue, if the next button was not disabled. I can't continue the installation and the only way is to cancel the installation.
I'm trying to install it on Windows 8.Hello,
Please restart the computer if after the restart SQL Server continues to failed at the Restart Required rule, the run SQL
Server setup with the following switch.
Setup.exe /SkipRules=RebootRequiredCheck
For more information, please read the following article for detailed steps.
https://support.microsoft.com/en-us/kb/2008982
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Unable to open power pivot dashboard excel files SQL server 2014 powerpivot for sharepoint
The Execute method of job definition Microsoft.AnalysisServices.SPAddin.UsageProcessingTimerJob (ID 726034a7-b9a9-45a6-b720-640b3f785e49) threw an exception. More information is included below. Call to Excel Services returned an
error.
System.InvalidOperationException: Call to Excel Services returned an error. ---> Microsoft.AnalysisServices.SPClient.Interfaces.ExcelServicesException: We're sorry. We ran into a problem completing your request
RaviHI, I got the solution SharePoint Web Services Root application pool was stopped
Faraz Javaid -
WCF-Custom Biztalk 2013 - Access to SQL Server 2014 Database
Hi,
i don't see nowhere of capability from the Biztalk adapter to access differente version of Sql server.
I want to send ou receive information with a WCF-Custom from SQL Server 2014, i'm in Biztalk 2013 (not R2 ) it's possible ?
Do you have a link or a list of version autorized to accessed by the wcf-custom Sql binging ?
Thanks a lotHi, I can suppose that the main problem for Joao is not if it works in general or not.
The real problem is that he is not sure if this configuration is officially supported by Microsoft.
If you are developing an integration project for a client you need to have this guarantee. If not, you can have an unsupported scenario, and if something fails you could have a big problem with your client.
If I were you, I would talk with the client account manager about this.
Regards. -
Hello,
Can anyone help me that i installed sql server 2014 after installation when i open it it is asking for server name ,how to solve this problem?Hello,
Can anyone help me that i installed sql server 2014 after installation when i open it it is asking for server name ,how to solve this problem?
First please tell did you installed named instance or default instance. Did you installed licensed version/evaluation edition or express edition.
You always connect to SQL Server using SSMS like
Hostname\instancename. You can go to Run type cmd and in command prompt type hostname the name returned is your hostname. Instance name is name of SQL Server instance which you created with installation ( if you created one or else it will be default instance)
If it is default instance and not a SQL Express you can just type dot. Dot like
. and can connect. If it is SQL express you can connect like Hostame\SQLEXPRESS.
If it is named instance connect like Hostname\instancename.
PS: Use account which you have added as administrator while installing SQL server as shown by Javier. if you selected mixed mode authentication you can connect by SA.
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 -
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...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
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 PatelRebecca,
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, -
Which version of sql server 2012 or 2014 is best for sharepoint 2013.. Any excellent comparision available please let me know..i mean enterprise version BI version or standard version.. i just need a detailed comparison if available please thank you
As of right this very second, SQL Server 2014 is not supported. SharePoint 2013 supports:
One of the following:
The 64-bit edition of Microsoft SQL Server 2012.
The 64-bit edition of SQL Server 2008 R2 Service Pack 1
Hardware and software requirements for SharePoint 2013
Edit: I may be mistaken. It looks like the April 2014 CU adds support for SQL Server 2014. If this is the case generally going with the latest SQL Edition provides you with the latest SQL functionality. I'm not aware of any SharePoint features that would
make use of functionality that is new to SQL Server 2014 but this could change with a future service pack.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights -
Sharepoint Foundation 2010 compatibility with SQL Server 2014
Due to a requirement to use Sharepoint without Active Directory access. I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014. I have seen that Sharepoint Server 2010 and 2013 are compatible
with SQL Server 2014 as of CU 1 (released in April). But there is no mention of Sharepoint Foundation.
This chart is great except it doesn't mention whether the Foundation versions are supported.
http://msdn.microsoft.com/en-us/library/gg492257.aspx
Thanks.Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
supported at all with SQL 2014 as a Database Engine.
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
How to install a Business Contact Manager 2013 database on SQL Server 2014
When I use the BCM Database Tool 2013 to create a database on a server, it doesn't pick up on any of my SQL Server 2014 instances. So far I can only get it to pick up SQL Server 2008 R2 instances in order to install the BCM database.
Someone mentioned that it works with SQL Server 2012, so is there any way to get it work on the 2014 version? I don't want to have to install 2008 or 2012 just for the sake of BCM.event if 3355 means 3 things:
The SQL Server might be offline.
The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
A firewall that runs on either the local server or on SQL Server might be blocking network communications.
Big question, how you trying to connect SQL windows or sql authentication? is it throwing error on Config wizard or somewhere else?
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog -
SSDT-BI for SQL Server 2014, Command line(silent unattendant automatic) installation script/steps
Hi,
I have downloaded SSDT-BI software and looking for commandline steps,config file for this.
http://www.microsoft.com/en-us/download/details.aspx?id=42313
Any one have Command line installations steps for SSDT-BI automatic(command line) installation for SQL Server 2014 with giving the files location,where to install.....etc, i mean config.xml.
I found below but not sure it will work or not. If any one have working correct command line script, please reply on this forum.
Looking for config.xml file, i searched online and did not find any where with clear config.xml file details.
--Found below from link and not sure it will work or not
http://blogs.technet.com/b/ilikesql_by_dandyman/archive/2013/03/10/how-to-automate-the-installation-of-sql-server-ssdt-office-2013-and-visual-studio-2012.aspx
setup.exe /ACTION=INSTALL /FEATURES=SSDTBI_VS2012 /Q /IACCEPTSQLSERVERLICENSETERMS /norestart
thanks in advance.Hi SQLDBA321,
The SSDT-BI is automatically installed under xxx:\Program Files\Microsoft SQL Server\. Now matter in GUI or command line, we can't change the path. Because SSDT is a feature of SQL Server, not a feature of Visual Studio. It just use the Visual
Studio Shell. So SSDT will only be installed with SQL Server.
Reference:
Install SQL Server Data Tools - Business Intelligence for Visual Studio 2013
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support -
Fatal error while executing the DQS installer on SQL Server 2014
Hi all.
I am receiving the following error when attempting to install DQS on the following platform:
Windows Server 2012
Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
(no entries in event viewer)
Error is:
[4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
to an instance of an object.
at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
--- End of inner exception stack trace ---
at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
Thanks for any advice you can give.
Full log below:
Microsoft (R) DQS Installer Command Line Tool
Copyright (c) 2014 Microsoft. All rights reserved.
[4/15/2015 7:58:20 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
[4/15/2015 7:58:20 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
[4/15/2015 7:58:20 AM] Using instance: DW01, catalog: DQS.
[4/15/2015 7:58:20 AM] Executing action: Validate collation argument.
[4/15/2015 7:58:20 AM] Action 'Validate collation argument' finished successfully.
[4/15/2015 7:58:20 AM] Executing action: Check whether system reboot is pending.
[4/15/2015 7:58:20 AM] Action 'Check whether system reboot is pending' finished successfully.
[4/15/2015 7:58:20 AM] Executing action: Create data quality event source.
[4/15/2015 7:58:20 AM] Action 'Create data quality event source' finished successfully.
[4/15/2015 7:58:20 AM] Executing action: Request Database Master Key password from user..
Microsoft (R) DQS Installer Command Line Tool
Copyright (c) 2014 Microsoft. All rights reserved.
[4/15/2015 8:39:59 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
[4/15/2015 8:39:59 AM] Parsing DqsInstaller command line arguments.
[4/15/2015 8:39:59 AM] Setting the catalog to default value: DQS
[4/15/2015 8:39:59 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
[4/15/2015 8:39:59 AM] Using instance: DEV01, catalog: DQS.
[4/15/2015 8:39:59 AM] Executing action: Validate collation argument.
[4/15/2015 8:39:59 AM] Action 'Validate collation argument' finished successfully.
[4/15/2015 8:39:59 AM] Executing action: Check whether system reboot is pending.
[4/15/2015 8:39:59 AM] Action 'Check whether system reboot is pending' finished successfully.
[4/15/2015 8:39:59 AM] Executing action: Create data quality event source.
[4/15/2015 8:39:59 AM] Action 'Create data quality event source' finished successfully.
[4/15/2015 8:39:59 AM] Executing action: Request Database Master Key password from user..
[4/15/2015 8:41:05 AM] Action 'Request Database Master Key password from user.' finished successfully.
[4/15/2015 8:41:05 AM] Executing action: Approve removal of data quality services previous schema.
[4/15/2015 8:41:05 AM] Action 'Approve removal of data quality services previous schema' finished successfully.
[4/15/2015 8:41:05 AM] Executing action: Load Installation Scripts.
[4/15/2015 8:41:05 AM] Extracting script to: C:\Users\SqlServiceAcct\AppData\Local\Temp\3mo2vwbu.xch
[4/15/2015 8:41:06 AM] Extracting script: db\create_core_db_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\create_logic_db_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\create_transient_db_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\static_data.sql
[4/15/2015 8:41:06 AM] Extracting script: db\drop_dq_databases.sql
[4/15/2015 8:41:06 AM] Extracting script: db\db_version.sql
[4/15/2015 8:41:06 AM] Extracting script: helper\DeleteSchemaDs.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_assemblies.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\create_databases.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_databases.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_tables.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_database_properties.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\master_create.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\master_recreate.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies_tsql.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\register_dq_assemblies.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\create_service_broker_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: sql\drop_service_broker_objects.sql
[4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_single_user.sql
[4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_multi_user.sql
[4/15/2015 8:41:06 AM] Extracting script: db\upgrade_all_versions.sql
[4/15/2015 8:41:06 AM] Extracting script: recreate_schema.bat
[4/15/2015 8:41:06 AM] Extracting script: upgrade_schema.bat
[4/15/2015 8:41:06 AM] Extracting script: upgrade_version_tables.bat
[4/15/2015 8:41:06 AM] Extracting script: drop_databases.cmd
[4/15/2015 8:41:06 AM] Extracting script: register_dlls.cmd
[4/15/2015 8:41:06 AM] Extracting script: unregister_dlls.cmd
[4/15/2015 8:41:06 AM] Extracting script: assembly_paths_retail.txt
[4/15/2015 8:41:06 AM] Extracting script: DQS_Data.dqs
[4/15/2015 8:41:06 AM] Extracting script: DefaultKbs.xml
[4/15/2015 8:41:06 AM] Total scripts extracted: 31
[4/15/2015 8:41:06 AM] Action 'Load Installation Scripts' finished successfully.
[4/15/2015 8:41:06 AM] Executing action: Create data quality schema.
[4/15/2015 8:41:06 AM] Script: 'recreate_schema.bat CMTSQLSVR04\DEV01 DQS SQL_Latin1_General_CP1_CI_AS'
[4/15/2015 8:41:06 AM] . Trying to connect using Windows Authentication and db name...
[4/15/2015 8:41:06 AM] Run create_databases.sql to create Data Quality Service databases if they do not exist.
[4/15/2015 8:41:07 AM]
[4/15/2015 8:41:07 AM] --> Running File: create_databases.sql
[4/15/2015 8:41:07 AM] ---[ Creating databases ]---
[4/15/2015 8:41:07 AM] Changed database context to 'master'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_dq_database.sql
[4/15/2015 8:41:10 AM] ---[ Dropping Data Quality Databases ]---
[4/15/2015 8:41:10 AM] Creating DQS databases (DQS_MAIN, DQS_PROJECTS, DQS_STAGING_DATA)...
[4/15/2015 8:41:10 AM] Configuring DQS databases
[4/15/2015 8:41:10 AM] Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 0 to 1. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Creating Master Key for database DQS_MAIN...
[4/15/2015 8:41:10 AM] Creating Module Signing Certificate for database DQS_MAIN...
[4/15/2015 8:41:10 AM] Exporting Certificate from DQS_MAIN
[4/15/2015 8:41:10 AM] Importing Certificate into DQS_PROJECTS
[4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 1 to 0. Run the RECONFIGURE statement to install.
[4/15/2015 8:41:10 AM] Creating DQS roles
[4/15/2015 8:41:10 AM] Run master_recreate.sql to recreate Data Quality Service Main and Projects Databases and drop all tables including known temporary tables.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running master_recreate.sql
[4/15/2015 8:41:10 AM] ---[ Recreate DQS Main and Projects Databases ]---
[4/15/2015 8:41:10 AM] Changed database context to 'DQS_STAGING_DATA'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_database_properties.sql
[4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
[4/15/2015 8:41:10 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_all_tables.sql
[4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all Symmetric Keys ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all Certificates ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all FK constraints ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all views ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all tables and synonyms ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all database triggers ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all stored procedures in Knowledge Base schemas ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all types in Knowledge Base schemas ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --[ Drop all Knowledge Base schemas ]
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_database_properties.sql
[4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
[4/15/2015 8:41:10 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:10 AM]
[4/15/2015 8:41:10 AM] --> Running File: drop_all_tables.sql
[4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all Symmetric Keys ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all Certificates ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all FK constraints ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all views ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all tables and synonyms ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all database triggers ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all stored procedures in Knowledge Base schemas ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all types in Knowledge Base schemas ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --[ Drop all Knowledge Base schemas ]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: drop_database_properties.sql
[4/15/2015 8:41:11 AM] ---[ Dropping Database Properties]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running master_create.sql
[4/15/2015 8:41:11 AM] ---[ Creating and Populating Main DQS DB ]---
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_STAGING_DATA'.
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: create_core_db_objects.sql
[4/15/2015 8:41:11 AM] ---[ Creating Certificates ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] ---[ Creating Symmetric Keys ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] ---[ Creating Tables ]---
[4/15/2015 8:41:11 AM] Creating Table: A_TEST
[4/15/2015 8:41:11 AM] Creating Table: A_TEST2
[4/15/2015 8:41:11 AM] Creating Table: A_FLOW
[4/15/2015 8:41:11 AM] Creating Table: A_FLOW_ANSWER
[4/15/2015 8:41:11 AM] Creating Table: A_EXECUTION_UNIT
[4/15/2015 8:41:11 AM] Creating Table: A_CODE_GROUP
[4/15/2015 8:41:11 AM] Creating Table: A_CODE_MEMBER
[4/15/2015 8:41:11 AM] Creating Table: A_CONFIGURATION
[4/15/2015 8:41:11 AM] Creating Table: A_PROCESS
[4/15/2015 8:41:11 AM] Creating Table: A_SERVICE_BROKER_TASK
[4/15/2015 8:41:11 AM] Creating Table: A_KNOWLEDGEBASE
[4/15/2015 8:41:11 AM] Creating Table: A_KNOWLEDGEBASE_AUDIT
[4/15/2015 8:41:11 AM] Creating Table: A_KNOWLEDGEBASE_ACTIVITY
[4/15/2015 8:41:11 AM] Creating Table: A_PROFILING_ACTIVITY_ARCHIVE
[4/15/2015 8:41:11 AM] Creating Table: A_CLIENT_SESSION
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_PROVIDER
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_PROVIDER_SCHEMA
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_CACHE
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_CACHE_SUGGESTION
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_CACHE_SUGGESTION_PARSED
[4/15/2015 8:41:11 AM] Creating Table: A_REFERENCE_DATA_AUDIT
[4/15/2015 8:41:11 AM] Creating Table: A_IMPORTED_PROJECT
[4/15/2015 8:41:11 AM] Creating Table: A_SPELLER_DICTIONARY_VALUE
[4/15/2015 8:41:11 AM] Creating Table: A_SPECIAL_CHARACTER_RULE
[4/15/2015 8:41:11 AM] Creating Table: A_PERSISTENT_CACHE
[4/15/2015 8:41:11 AM] Creating Table: A_TEMPLATE_OBJECTS
[4/15/2015 8:41:11 AM] Creating Table: A_TEMPLATE_FOREIGN_KEYS
[4/15/2015 8:41:11 AM] Creating Table: A_TEMPLATE_COLUMNS
[4/15/2015 8:41:11 AM] ---[ Creating Views ]---
[4/15/2015 8:41:11 AM] Creating View: V_A_FLOW
[4/15/2015 8:41:11 AM] Creating View: V_A_KNOWLEDGEBASE
[4/15/2015 8:41:11 AM] Creating View: V_A_KNOWLEDGEBASE_AUDIT
[4/15/2015 8:41:11 AM] Creating View: V_A_REFERENCE_DATA_PROVIDER
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: static_data.sql
[4/15/2015 8:41:11 AM] ---[ Inserting Data ]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Cleansing configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Association configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert DataValueService configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Association rules configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert IndexService configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Knowledgebase configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Notification configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert Interactive Cleansing configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Reference Data configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert client paging configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Insert client process sampling configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Matching configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Profiling configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Process configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[FileStorageManager configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[ImportExportManager configuration section]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Reference Data Add provider]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Reference Data Add provider schema]---
[4/15/2015 8:41:11 AM] ---[Add Special characters for term normalization]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] --> Running File: db_version.sql
[4/15/2015 8:41:11 AM] ---[ Running version related work ]---
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION_INFO
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION_UPGRADE_SCRIPTS
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION_UPGADE_SCRIPT_PATH
[4/15/2015 8:41:11 AM] Creating view: V_DB_VERSION
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version information]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (0 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] (1 rows affected)
[4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
[4/15/2015 8:41:11 AM] Creating Table: A_DB_VERSION in PROJECTS database
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM]
[4/15/2015 8:41:11 AM] Action 'Create data quality schema' finished successfully.
[4/15/2015 8:41:11 AM] Executing action: Register data quality assemblies and stored procedures.
[4/15/2015 8:41:11 AM] Script: 'register_dlls.cmd CMTSQLSVR04\DEV01 DQS'
[4/15/2015 8:41:12 AM] . Trying to connect using Windows Authentication and db name...
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Running File: drop_all_assemblies.sql
[4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Executable Objects ]---
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all SSDQS Types
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all SSDQS Assemblies
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all SSDQS Schemas
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop all CLR Assemblies
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Drop DQ startup stored procedure DQInitDQS_MAIN
[4/15/2015 8:41:12 AM] Changed database context to 'master'.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Running File: drop_service_broker_objects.sql
[4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Service Broker Objects ]---
[4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:12 AM] Dropping Service Broker Services.
[4/15/2015 8:41:12 AM] Dropping Service Broker Queues.
[4/15/2015 8:41:12 AM] Dropping Service Broker Contracts.
[4/15/2015 8:41:12 AM] Dropping Service Broker Messages.
[4/15/2015 8:41:12 AM] Completed - Service Broker objects dropped.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Running register_assemblies.sql
[4/15/2015 8:41:12 AM] ---[ Registering Assemblies ]---
[4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] --> Registering Assemblies
[4/15/2015 8:41:12 AM] The following Warnings are benign to DQSInstaller and may be ignored.
[4/15/2015 8:41:12 AM]
[4/15/2015 8:41:12 AM] * Register .NET dependency assemblies
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.management, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.configuration.install, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'smdiagnostics, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.windows.forms, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'accessibility, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization.formatters.soap, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the
SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.jscript, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:26 AM] Warning: The Microsoft .NET Framework assembly 'system.management.instrumentation, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.messaging, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.enterpriseservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.remoting, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.framework, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.xaml, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.caching, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.utilities.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices.protocols, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web.regularexpressions, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.tasks.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.serviceprocess, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:44 AM] * Register Microsoft.Practices assemblies
[4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.csharp, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'system.dynamic, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
[4/15/2015 8:41:47 AM]
[4/15/2015 8:41:47 AM] The preceding Warnings are benign to DQSInstaller and may be ignored.
[4/15/2015 8:41:48 AM]
[4/15/2015 8:41:48 AM] --> Running register_dq_assemblies.sql
[4/15/2015 8:41:48 AM] ---[ Registering Data Quality assemblies ]---
[4/15/2015 8:41:49 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.infra, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:50 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.core, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.dataservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.referencedata, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.index, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.associationrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:53 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.datavalueservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.domainrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.cleansing, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.association, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.flow, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:56 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.matching, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:57 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
[4/15/2015 8:41:57 AM] Resource file was not copied
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] --> Running register_assemblies_tsql.sql
[4/15/2015 8:41:57 AM] ---[ Registering Assemblies for TSQL]---
[4/15/2015 8:41:57 AM] Changed database context to 'master'.
[4/15/2015 8:41:57 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Clear the Code Member Table A_CODE_MEMBER.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] (0 rows affected)
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Clear the Code Group Table A_CODE_GROUP.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] (0 rows affected)
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Register assemblies T-SQL executable objects
[4/15/2015 8:41:57 AM] - Creating assemblies T-SQL registeration stored procedure.
[4/15/2015 8:41:57 AM]
[4/15/2015 8:41:57 AM] * Creating the internal_core schema
[4/15/2015 8:41:57 AM] - Registering Microsoft.Ssdqs.Infra T-SQL executable objects.
[4/15/2015 8:42:05 AM] - Registering Microsoft.Ssdqs.Core T-SQL executable objects.
[4/15/2015 8:42:11 AM] - Registering Microsoft.Ssdqs.DataService T-SQL executable objects.
[4/15/2015 8:42:16 AM] - Registering Microsoft.Ssdqs.ReferenceData T-SQL executable objects.
[4/15/2015 8:42:21 AM] - Registering Microsoft.Ssdqs.Index T-SQL executable objects.
[4/15/2015 8:42:26 AM] - Registering Microsoft.Ssdqs.Cleansing T-SQL executable objects.
[4/15/2015 8:42:32 AM] - Registering Microsoft.Ssdqs.Association T-SQL executable objects.
[4/15/2015 8:42:37 AM] - Registering Microsoft.Ssdqs.Flow T-SQL executable objects.
[4/15/2015 8:42:42 AM] - Registering Microsoft.Ssdqs T-SQL executable objects.
[4/15/2015 8:42:51 AM] - Registering Microsoft.Ssdqs.DataValueService T-SQL executable objects.
[4/15/2015 8:42:56 AM] - Registering Microsoft.Ssdqs.DomainRules T-SQL executable objects.
[4/15/2015 8:43:01 AM] - Registering Microsoft.Ssdqs.AssociationRules T-SQL executable objects.
[4/15/2015 8:43:06 AM] - Registering Microsoft.Ssdqs.Matching T-SQL executable objects.
[4/15/2015 8:43:12 AM] - Creating refresh assemblies stored procedure.
[4/15/2015 8:43:12 AM] Changed database context to 'master'.
[4/15/2015 8:43:12 AM] - Creating refresh assemblies helper linked server.
[4/15/2015 8:43:12 AM] - Creating and registering [dbo].[DQInitDQS_MAIN] (calls internal_core.InitServer) as startup stored procedure.
[4/15/2015 8:43:12 AM]
[4/15/2015 8:43:12 AM] --> Running File: create_service_broker_objects.sql
[4/15/2015 8:43:12 AM] ---[ Registering Service Broker Objects ]---
[4/15/2015 8:43:12 AM] Changed database context to 'DQS_MAIN'.
[4/15/2015 8:43:12 AM] - Creating SB dispatcher stored procedure, messages and contract
[4/15/2015 8:43:13 AM] - Creating parallel execution SB queues and services
[4/15/2015 8:43:13 AM] - Creating calibration SB queues and services
[4/15/2015 8:43:13 AM] - Creating parallel calibration SB queues and services
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM] Successfully registered all assemblies.
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM]
[4/15/2015 8:43:13 AM] Action 'Register data quality assemblies and stored procedures' finished successfully.
[4/15/2015 8:43:13 AM] Executing action: Set product version property.
[4/15/2015 8:43:13 AM] Action 'Set product version property' finished successfully.
[4/15/2015 8:43:13 AM] Executing action: Create MDS user (if MDS login exists).
[4/15/2015 8:43:13 AM] Action 'Create MDS user (if MDS login exists)' finished successfully.
[4/15/2015 8:43:13 AM] Executing action: Load out of the box data.
[4/15/2015 8:43:22 AM] Started loading knowledgebase 'DQS Data'
[4/15/2015 8:45:04 AM] Starting installation rollback...
[4/15/2015 8:45:04 AM] Installation rollback completed successfully.
[4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
to an instance of an object.
at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
--- End of inner exception stack trace ---
at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
Microsoft (R) DQS Installer Command Line Tool
Copyright (c) 2014 Microsoft. All rights reserved.Thank you for the quick response.
Unfortunately running cmd as admin had no effect on the result. Same exact error.
After the rollback indicated in the log above, only the DQS_STAGING_DATA database remains in the sql server instance. -
Installation of SCCM 2012 R2 and SQL Server 2014 error
Hello All,
I am attempting to setup SQL Server 2014 and SCCM 2012 R2 but I keep running into an error stating that "Configuration Manager requires Microsoft SQL Server
2008 SP2 w/ CU9........ all the way up to Microsoft SQL Server 2012 with CU2 or higher." I am using all evaluation versions for this configuration as we are looking to test and evaluate the products. I was trying it with SQL 2014 because I was running
into the same error with SQL 2012 and according to "http://blogs.technet.com/b/configmgrteam/archive/2015/03/30/updated-sc2012-configmgr-sp1-and-sc2012r2-configmgr-support-sql-server-2014.aspx" SQL
2014 is supported with SCCM 2012 R2. SQL is installed locally on the same box.
Any suggestions would be appreciated.
Thanks,
Tucker
Update: When running the Pre-Req check these are some of the failed returns.....
SQL Server Edition: Failed: Configuration Manager primary site and central administration site don't support SQL Server Express Edition
Not sure why it is recognizing SQL Express as this is a new machine.
SQL Server service running account: Failed: The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure
the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
For the SQL Service I am using a domain account created specifically for this.This has nothing to do with moving or restoring. The kb article says "This hotfix provides updated versions of the setup files and enables new installations
of the System Center 2012 R2 Configuration Manager site database role and the System Center 2012 Configuration Manager SP1 site database role in Microsoft SQL Server 2014"
Torsten Meringer | http://www.mssccmfaq.de
Maybe you are looking for
-
In print or print preview I only see the 1st page and can only print the 1st page
to my printer or to and Adobe file, but with IE I see all the pages which are formed and can print them. How do I correct this in Firefox
-
How do you hide the Page Options button on dashboards in 11g?
Hello, I would like to hide the "Page Options" button on a dashboard in 11g. I found some examples on how to do it in 10g, and they all talk about editing a file called dashboardtemplates.xml. I can't find this file on my 11g BI server, so I'm assumi
-
NOT able to connect my Black Berry Curve 3g to black berry desktop manager
Hi , i purchased a new blackberry curve 3g yesterday ....i have to import all my contacts in bb so i downloaded the blackbery dektop manager and tried to connect my mobile with it ....when i pluged the cable inside my lappy due to my antivirus a star
-
BPA Suite 11g Installation halts at Step 10
Hello, I have downloaded BPA Suite 11G from OTN. The installation of BPA suite halts at step 10. No error occures. I was waiting for 10-15 minutes to finish the installation. I am using 11G data base installed along with R12.1 on the virtual machine.
-
Mail downloading phantom messages
Hi everybody. Something strange is happening from about 2/3/ days ago. When I open Mail, on the Mail activity box there are 6 messages downloading but then no new message show up in any of the mailboxes. This is happening every 10-15 minutes. I have