Change sql server 2014 server name
Hi
This works on sql 2008 r2, but not on sql server 2014
sp_dropserver 'old_server'
Msg 15015, Level 16, State 1, Procedure sp_dropserver, Line 42
The server 'old_server' does not exist. Use sp_helpserver to show available servers.
sp_addserver 'new_server',local
Msg 15028, Level 16, State 1, Procedure sp_addserver, Line 74
The server 'new_server' already exists.
You mean you are changing server name(Host name) ? But this is only to change SQL instance name not server name.
Please paste output:
Select @@ServerName ServerName, Host_name() HostName
Follow steps from here:
http://mssqlfun.com/2014/06/30/rename-or-change-sql-server-standalone-default-instance/
Similar Messages
-
I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich PThank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P -
High PREEMPTIVE_SP_SERVER_DIAGNOSTICS wait time in sql server 2014 server
I am seeing high waittimes for PREEMPTIVE_SP_SERVER_DIAGNOSTICS and the server is runninf with high cpu.
What could have triggered this high waittime, how can this be fixed,
WaitType Wait_S
Resource_S Signal_S
WaitCount Percentage
AvgWait_S AvgRes_S
AvgSig_S
PREEMPTIVE_SP_SERVER_DIAGNOSTICS 1655043.72
1655043.72 0.00
4 39.75
413760.9305 413760.9305
0.0000
PREEMPTIVE_OS_PIPEOPS 935157.21
935157.21 0.00
343445 22.46
2.7229 2.7229
0.0000
CXPACKET 259912.58
250608.73 9303.85
25115286 6.24
0.0103 0.0100
0.0004
PAGEIOLATCH_SH 206350.14
205563.18 786.96
37649420 4.96
0.0055 0.0055
0.0000
SOS_SCHEDULER_YIELD 139263.91
2430.27 136833.63
293382681 3.35
0.0005 0.0000
0.0005Hello,
I remember I read a user complaining about high waits on PREEMPTIVE_SP_SERVER_DIAGNOSTICS when he installed CU5 for SQL
Server 2012 SP1, but in your scenario you have a SQL Server 2014 with CU1 (build 2342). I am treating this as a bug and that is the reason I would like you to consider applying CU5, the latest cumulative update, to see if that solves the issue.
http://support.microsoft.com/kb/3011055/en-us
This is the first time I read about this happening on SQL Server 2014 though.
I would like to suggest you to create a Connect item too, to see if the SQL Server team can suggest you another way to
treat this issue.
https://connect.microsoft.com/sqlServer/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server Express 2014 - Server Name
Hi Guys,
I just now installed the free edition of SQL Server 2014 (Management Studio only edition).
During installation I was not allowed to provide an instance name. Post installation when I am trying to connect the server using the management studio it fails consistently.
I have tried using LocalDB, (local), SQLExpress and all other combinations (machine\LocalDB) etc.
When I open the SQL Config Manager there "SQL Server Services" has no entries.
Can someone help me in getting the server name to connect to?
Regards,
HTH, KrishnanHey Dan,
I am not facing a different kind of challenge. I am trying to connect to this instance using a different product. I tried the following:
- Provided the same instance name as Mgmt Studio
- Tried using both Windows / SQL Authentication
When I did a netstat, it does not show that 1433 is listening. The SQL Configuration Manager has 2 sections:
1. SQL Native Client 11.0 Config - Here the TCP/IP is listening to 1433
2. SQL Server Network Configuration -> Protocols for SQL Express - TCP / IP -> Dynamic Ports -> 49819
Netstat is showing some data for 49819. However my other product is still not able to pick up SQL Server :(
HTH, Krishnan -
CHange Licencing Mode SQL Server 2014
Guys...
I need to know.
Is possible to change licensing mode from SQL Server 2014/Carl to Sq server 2014/ Core with out reintall.....
Thanks
RichardHi,
Its best to ask all licensing related question to Licensing expert. This is technical forum and you wont find any licensing expert here. Licensing is complex and for accurate answer you must speak to MS Licensing specialist of your region
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 Articles
@Shanky: The question is not related to licensing models but rather if it's required to re-install SQL Server when changing the licence model. Please re-read the question.
As you most probably know, during the installation process there's not a single step related to verify licencing. Also, starting with SQL Server 2005, SQL Server does not track any licence information.
Therefore, to answer the original (technical) question doesn't require to involve a Licensing expert.
LMU92 thats always my stand whether I know or not, and this is not forum for licensing question so even if I know a bit I always ask people to get double checked with MS licensing expert.
Like even if I know oracle I would always ask user to direct his questions to Oracle forum rather than giving him answer this is how forum works where I don't have authority i would refrain from answering and would direct it to correct place.
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 Articles -
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. -
Overlapped I/O error 997 installing SQL Server 2014 Express on Windows Server 2012 R2
I'm attempting to install SQL Server 2014 Express on a Windows Server 2012 R2 system. When I do the install, it fails (several times) with an "Error: 997. Overlapped I/O operation is in progress.". From searching the web, I can see many people
have had this problem with this installer and other non-SQL server installers.
I've tried every solution I can find discussed, but none help with my problems The system is fully updated, with the exception of the KB2538243 (VC 2008 SP1 redist), which is probably failing for the same reason.
I've tried removing several updates mentioned in other articles (KB2918614). I've confirmed that I'm not using a temporary profile.
Does anyone have an idea of how I can solve this issue?
Thanks,
Zack
Partial detail from install log file:
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: Microsoft Visual Studio 2010 Redistributables
Component error code: 997
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
Error description: Error 997.Overlapped I/O operation is in progress.
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=vc_red.msi%40ProcessComponents%40997
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: Microsoft Visual Studio 2010 Redistributables
Component error code: 997
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
Error description: Error 997.Overlapped I/O operation is in progress.
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=vc_red.msi%40ProcessComponents%40997
Partial detail from component log file:
MSI (s) (D8:3C) [15:18:29:173]: Resolving source.
MSI (s) (D8:3C) [15:18:29:173]: Resolving source to launched-from source.
MSI (s) (D8:3C) [15:18:29:173]: Setting launched-from source as last-used.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{1D8E6291-B0D5-35EC-8441-6616F567A0F7}'.
MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR ==> C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\
MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR product ==> {1D8E6291-B0D5-35EC-8441-6616F567A0F7}
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: A general error running CryptAcquireContext
MSI (s) (D8:3C) [15:18:29:188]: Determining source type
MSI (s) (D8:3C) [15:18:29:188]: Source type from package 'VC_RED.MSI': 2
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (D8:3C) [15:18:29:204]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: New Hash Database creation complete.
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:997
MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: Failed to CreateContentHash of the file: install.res.1040.dll: for computing its hash. Error: 997
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: SecureRepair Failed. Error code: 3e561F257D8
Action start 15:18:29: ProcessComponents.
MSI (s) (D8:3C) [15:19:28:843]:
Error 997.Overlapped I/O operation is in progress.Alberto,
Thanks for your help. Unfortunately, I've already tried that. I did try it again and I get an "This update is not applicable to your computer."
I tried to post the Windows Update log, but it was too large. I've posted some of it below.
Here is the WU log:
2015-02-06 11:24:25:793
5048 50
Misc =========== Logging initialized (build: 7.9.9600.17489, tz: -0500) ===========
2015-02-06 11:24:25:793
5048 50
Misc = Process: C:\Windows\system32\wusa.exe
2015-02-06 11:24:25:793
5048 50
Misc = Module: C:\Windows\System32\wuapi.dll
2015-02-06 11:24:25:793
5048 50
COMAPI ----------- COMAPI: IUpdateServiceManager::AddScanPackageService -----------
2015-02-06 11:24:25:793
5048 50
COMAPI - ServiceName = Windows Update Standalone Installer
2015-02-06 11:24:25:793
5048 50
COMAPI - ScanFileLocation = C:\c5f288db3c43a7e4613232ca1a3c\wsusscan.cab
2015-02-06 11:24:25:808
920 111c
Misc =========== Logging initialized (build: 7.9.9600.17489, tz: -0500) ===========
2015-02-06 11:24:25:808
920 111c
Misc = Process: C:\Windows\system32\svchost.exe
2015-02-06 11:24:25:808
920 111c
Misc = Module: c:\windows\system32\wuaueng.dll
2015-02-06 11:24:25:808
920 111c
Service *************
2015-02-06 11:24:25:808
920 111c
Service ** START ** Service: Service startup
2015-02-06 11:24:25:808
920 111c
Service *********
2015-02-06 11:24:25:824
920 111c
IdleTmr Non-AoAc machine. Aoac operations will be ignored.
2015-02-06 11:24:25:824
920 111c
Agent * WU client version 7.9.9600.17489
2015-02-06 11:24:25:824
920 111c
Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2015-02-06 11:24:25:824
920 111c
Agent * Base directory: C:\Windows\SoftwareDistribution
2015-02-06 11:24:25:824
920 111c
Agent * Access type: No proxy
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
2015-02-06 11:24:25:824
920 111c
Agent * Network state: Connected
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
2015-02-06 11:24:25:855
920 b64
Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2015-02-06 11:24:25:855
920 111c
Agent *********** Agent: Initializing global settings cache ***********
2015-02-06 11:24:25:887
920 111c
Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2015-02-06 11:24:25:887
920 111c
Agent * WSUS server: <NULL>
2015-02-06 11:24:25:887
920 111c
Agent * WSUS status server: <NULL>
2015-02-06 11:24:25:887
920 111c
Agent * Target group: (Unassigned Computers)
2015-02-06 11:24:25:887
920 111c
Agent * Windows Update access disabled: No
2015-02-06 11:24:25:902
920 b64
WuTask WuTaskManager delay initialize completed successfully..
2015-02-06 11:24:25:902
920 b64
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-02-06 19:30:54, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
AU Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-02-06 19:30:54, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2015-02-06 11:24:25:902
920 b64
Report CWERReporter::Init succeeded
2015-02-06 11:24:25:902
920 b64
Agent *********** Agent: Initializing Windows Update Agent ***********
2015-02-06 11:24:25:902
920 b64
DnldMgr Download manager restoring 0 downloads
2015-02-06 11:24:25:902
920 111c
AU ########### AU: Initializing Automatic Updates ###########
2015-02-06 11:24:25:902
920 111c
AU AIR Mode is disabled
2015-02-06 11:24:25:902
920 111c
AU # Approval type: Scheduled (User preference)
2015-02-06 11:24:25:902
920 111c
AU # Auto-install minor updates: Yes (User preference)
2015-02-06 11:24:25:902
920 111c
AU # Will interact with non-admins (Non-admins are elevated (User preference))
2015-02-06 11:24:25:902
920 111c
Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=2250
2015-02-06 11:24:25:918
920 111c
AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2015-02-06 11:24:25:918
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:918
920 111c
AU AU finished delayed initialization
2015-02-06 11:24:25:933
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:933
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:933
920 b64
Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\a487aa0f-3e53-4fee-a784-6171b00254e4\Source.cab with dwProvFlags 0x00000080:
2015-02-06 11:24:25:933
920 111c
AU Adding timer:
2015-02-06 11:24:25:933
920 111c
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
2015-02-06 11:24:25:949
920 af0
DnldMgr Asking handlers to reconcile their sandboxes
2015-02-06 11:24:25:949
920 b64
Misc Microsoft signed: Yes
2015-02-06 11:24:26:154
920 b64
DtaStor Default service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
2015-02-06 11:24:26:154
920 b64
IdleTmr Incremented idle timer priority operation counter to 1
2015-02-06 11:24:26:154
5048 50
COMAPI - Added scan package service, ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
2015-02-06 11:24:26:154
5048 50
COMAPI -------------
2015-02-06 11:24:26:154
5048 50
COMAPI -- START -- COMAPI: Init Search [ClientId = wusa]
2015-02-06 11:24:26:154
5048 50
COMAPI ---------
2015-02-06 11:24:26:154
5048 50
COMAPI -------------
2015-02-06 11:24:26:154
5048 50
COMAPI -- START -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:26:154
5048 50
COMAPI ---------
2015-02-06 11:24:26:169
920 b64
IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 17; does use network; is not at background priority
2015-02-06 11:24:26:169
920 b64
IdleTmr Incremented idle timer priority operation counter to 2
2015-02-06 11:24:26:341
920 b64
Report *********** Report: Initializing static reporting data ***********
2015-02-06 11:24:26:341
920 b64
Report * OS Version = 6.3.9600.0.0.131344
2015-02-06 11:24:26:341
920 b64
Report * OS Product Type = 0x00000021
2015-02-06 11:24:26:357
920 b64
Report * Computer Brand = PowerSpec
2015-02-06 11:24:26:357
920 b64
Report * Computer Model = S Series
2015-02-06 11:24:26:357
920 b64
Report * Platform Role = 1
2015-02-06 11:24:26:357
920 b64
Report * AlwaysOn/AlwaysConnected (AOAC) = 0
2015-02-06 11:24:26:357
920 b64
Report * Bios Revision = 1.1a
2015-02-06 11:24:26:357
920 b64
Report * Bios Name = 1.1a
2015-02-06 11:24:26:357
920 b64
Report * Bios Release Date = 2013-08-20T00:00:00
2015-02-06 11:24:26:357
920 b64
Report * Bios Sku Number = S Series
2015-02-06 11:24:26:357
920 b64
Report * Bios Vendor = American Megatrends Inc.
2015-02-06 11:24:26:357
920 b64
Report * Bios Family = Server
2015-02-06 11:24:26:357
920 b64
Report * Bios Major Release = 4
2015-02-06 11:24:26:357
920 b64
Report * Bios Minor Release = 6
2015-02-06 11:24:26:357
920 b64
Report * Locale ID = 1033
2015-02-06 11:24:26:357
920 b64
Handler Calculating current update level for this session
[ Omitted data ]
http://support.microsoft.com/?kbid=3000850, timestamp 01d039c57a22c0be
2015-02-06 11:24:28:388
920 b64
Handler Done calculating current update level for this session
2015-02-06 11:24:28:982
920 b64
Agent *** START *** Queueing Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
5048 50
COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:28:982
920 11f4
Agent *** END *** Queueing Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
920 11f4
Agent *************
2015-02-06 11:24:28:982
920 11f4
Agent ** START ** Agent: Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
920 11f4
Agent *********
2015-02-06 11:24:28:982
920 11f4
Agent * Online = Yes; Ignore download priority = No
2015-02-06 11:24:28:982
920 11f4
Agent * Criteria = "DeploymentAction='Installation'"
2015-02-06 11:24:28:982
920 11f4
Agent * ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
2015-02-06 11:24:28:982
920 11f4
Agent * Search Scope = {Machine}
2015-02-06 11:24:28:982
920 11f4
Agent * Caller SID for Applicability: S-1-5-21-3157695610-3447843402-2534478823-500
2015-02-06 11:24:28:982
920 11f4
Agent * RegisterService is set
2015-02-06 11:24:29:185
920 11f4
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2015-02-06 11:24:29:185
920 11f4
PT + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
2015-02-06 11:24:29:185
920 11f4
PT WARNING: Cached cookie has expired or new PID is available
2015-02-06 11:24:29:185
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:185
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:185
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:294
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:294
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:294
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:357
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:357
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:357
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:638
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:638
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:638
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:013
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:30:013
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:30:013
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:044
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:30:044
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:30:044
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:044
920 11f4
PT + SyncUpdates round trips: 5
2015-02-06 11:24:30:076
920 11f4
PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2015-02-06 11:24:30:076
920 11f4
PT + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
2015-02-06 11:24:30:138
920 11f4
Agent * Found 0 updates and 54 categories in search; evaluated appl. rules of 126 out of 284 deployed entities
2015-02-06 11:24:30:138
920 11f4
Agent *********
2015-02-06 11:24:30:138
920 11f4
Agent ** END ** Agent: Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:30:138
920 11f4
Agent *************
2015-02-06 11:24:30:138
920 11f4
IdleTmr WU operation (CSearchCall::Init ID 1, operation # 17) stopped; does use network; is not at background priority
2015-02-06 11:24:30:138
920 11f4
IdleTmr Decremented idle timer priority operation counter to 1
2015-02-06 11:24:30:154
5048 1428
COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:30:154
5048 1428
COMAPI - Updates found = 0
2015-02-06 11:24:30:154
5048 1428
COMAPI ---------
2015-02-06 11:24:30:154
5048 1428
COMAPI -- END -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:30:154
5048 1428
COMAPI ------------- -
Export to Excel Error in SQL Server 2014 Report Builder/Viewer
Hi,
I am using the 2014 version of ReportViewer in a WinForm to display an RDL report.
The report was originally created in Report Builder 2.0 (SQL 2008 R2), but has since been edited in Report Builder 3.0 (SQL 2014).
The report loads and displays OK, and even exports to Word and PDF. But when exporting to Excel and then opening the Excel document, the following error occurs:
"We found a problem with some content in <filename>. Do you want us to try and recover as much as we can? If you trust the source of this workbook, click Yes."
If you click Yes, then a second message appears:
"Removed Part: /xl/styles.xml part. (Styles)
Repaired Records: Cell information from /xl/worksheets/sheet1.xml part"
The Excel document then opens, and the data is there, but there is no formatting (no border columns, colours, bolds etc.)
The three interesting things are:
- When exported from SQL 2008 R2 Report Builder 3.0, which exports to .xsl instead of .xslx, it works
- A brand new report created in 2014 Report Builder 3.0 exports to .xslx great
- In Report Builder 2014, I stripped everything back and removed all rows and columns so the original table in the report only has one empty row and column it the export still errors - it is only by removing the original table and creating a brand new table
that export works OK
It appears to be a problem with the tablix, but ideally we don't want to have to recreate our reports from scratch to fix this issue.
Has anyone come across an issue like this before, and know of any potential resolutions to it?
Thank you.Hello,
Based on your description, you render a report originally created in Report Builder 2.0 (SQL 2008 R2) and export the report to excel with format of Excel 2007-2010.
Edit the report in Report Builder will not upgrader the report. In that case the report still with SSRS 2008 R2 RDL schema. Please try to upgrade the report by open the report in Report Designer in SQL Server Data Tools (SSDT) and then try again.
If you don’t want to upgrade the report, please try to export the report
with Excel 2003 rendering extension and check if the issue persists.
The SQL Server 2014 and SQL Server 2012 Reporting Services Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010 with .xlsx as file extension. Only the Excel rendering extension is available by default.
You must update the Reporting Services configuration files to make the Excel 2003 rendering extension available.
For example, changing the value of Visible to
true in the following line in the RSReportServer.config:
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"
Visible="true"/>
Reference:Upgrade Reports
Exporting to Microsoft Excel (Report Builder and SSRS)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support -
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. -
SQL Server 2014 - calling sp_setapprole failing
The corporation I work at has decided to start using the application role functionality in SQL Server. We are able to successfully implement the app roles into the application (PowerBuilder 12.1) when running against a SQL Server 2012 database,
however the same code when running against a SQL Server 2014 database fails.
Because PB execute everything from within a transaction we had to do some "interesting" code to get the approles working. Here is the SQL that is being passed into the DB:
SET QUOTED_IDENTIFIER OFF
SET IMPLICIT_TRANSACTIONS OFF
SET ANSI_PADDING ON
create table "<generated temp table name>" (id int identity( 1, 1) not null, cookie varbinary(8000) not null )
declare @cookie1 varbinary( 8000) exec sp_setapprole @rolename = '"+ <rolename>+"', @password = '"+<password>+"', @fCreateCookie = 1, @cookie = @cookie1 output insert "+<generated temp
table name>+"( cookie) values( @cookie1)
So what happens is the approle is being called and the cookie stored in a temp table on the database. This is because of the translation between SQL Server and PB with the Varbinary cookie that is created for the approle. If brought into PB it gets
messed up and the unset approle doesn't work.
As stated, the code above WORKS in SQL Server 2012, not in 2014. I run the profile trace on the server and I can see the temp table being created, the sp_setapprole proc being called and the statements inside being executed, but once hitting the function
setuser we get the error that the approle does no exist or the password is invalid. I've been able to trace through the password being sent in and it's the same as that PB is sending across so it's not a corruption issues.
Running the SQL through SS Management Studio works. The temp table created and the approle is set. Additionally we have .Net applications using the same user/password, and retrieving a cookie, and they work as well.
Does anyone know if there has been changes to the way approles are handled in 2014, or if there was a change to the setuser functionality that could be causing the approle to fail?The call "SET QUOTED_IDENTIFIER OFF" was an attempt to get the DB working the same way our SQL Server 2012 database is set-up. I've since removed it
from the code. Also each of the calls are executed separately:
ls_sql = "SET IMPLICIT_TRANSACTIONS OFF"
EXECUTE IMMEDIATE :ls_sql USING atrTrans;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
ls_sql = "SET ANSI_PADDING ON"
EXECUTE IMMEDIATE :ls_sql USING atrTrans ;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
ls_sql = "create table "+atrTrans.isTempTableName+"( id int identity( 1, 1) not null, cookie varbinary(8000) not null ) "
EXECUTE IMMEDIATE :ls_sql USING atrTrans ;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
ls_sql = "declare @cookie1 varbinary( 8000), @password1 sysname = '" + ls_appRollPass + "' exec sp_setapprole @rolename = '"+ ls_AppRoleName +"', @password = @password1, @fCreateCookie
= 1, @cookie = @cookie1 output insert "+atrTrans.isTempTableName+"( cookie) values( @cookie1) "
EXECUTE IMMEDIATE :ls_sql USING atrTrans ;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
atrTrans.AutoCommit = FALSE
ls_sql = "SET IMPLICIT_TRANSACTIONS ON"
EXECUTE IMMEDIATE :ls_sql USING atrTrans ;
ls_sql = "SET ANSI_PADDING OFF"
EXECUTE IMMEDIATE :ls_sql USING atrTrans ;
commit using atrTrans ;
EDIT: Note that the passing of the password as a variable was only for testing/validation to ensure that the password matched what was being sent from PB and NOT intended to be there in the actual implementation. -
MS SQL Server 2014: Error inserting into Temp table with index and identity field
In this thread, I mentioned a problem with SQL Server 2014:
SQL Server 2014: Bug with IDENTITY INSERT ON
The question was answered, it is a bug. To keep you informed on this issue, I open this discussion.
Problem:
The code below works perfectly fine on MS SQL Server 2008 R2 and MS SQL Server 2012, but gives an error every second time the proc is executed on MS SQL Server 2014. If I do not define any index on the temp table, the problem disappears. Defining the index
after the insert, does not help.
SET NOCOUNT ON
GO
IF EXISTS (SELECT 1 FROM sys.procedures WHERE name = 'usp_Test') DROP PROC dbo.usp_Test;
GO
CREATE PROC dbo.usp_Test AS
BEGIN
SET NOCOUNT ON
CREATE TABLE #Source(ID integer NOT NULL);
INSERT INTO #Source VALUES (1), (2), (3);
CREATE TABLE #Dest (ID integer IDENTITY(1,1) NOT NULL);
CREATE INDEX #IDX_Dest ON #Dest (ID);
PRINT 'Check if the insert might cause an identity crisis';
SELECT 'Source' AS SourceTable, * FROM #Source;
SELECT 'Destination' AS DestTable, * FROM #Dest;
SET IDENTITY_INSERT #Dest ON;
PRINT 'Do the insert';
INSERT INTO #Dest (ID) SELECT ID FROM #Source;
PRINT 'Insert ready';
SET IDENTITY_INSERT #Dest OFF;
SELECT * FROM #Dest;
DROP TABLE #Source;
DROP TABLE #Dest;
END;
GO
PRINT 'First execution of the proc, everything OK';
EXEC dbo.usp_Test;
PRINT '';
PRINT 'Second execution of the proc, the insert fails.';
PRINT 'Removing the index #IDX_Dest causes the error to disappear.';
EXEC dbo.usp_Test;
GO
DROP PROC dbo.usp_Test;
GOThere is some progress. Communication from a former Microsoft employee tells us this:
Shivendra Vishal
Engineer at Microsoft
I am no longer with MS, and I do not have code access, however from the public symbols, I could make out following:
sqlmin!SetidentI2I4+0x1f3:
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
ExceptionAddress: 000007fef4d865d3 (sqlmin!SetidentI2I4+0x00000000000001f3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
This is a read AV and from registers it is clear that we were trying to move the value of location pointed by qword of register rax which is not valid:
rax=0000000000000000 rbx=0000000000000038 rcx=0000000000001030
rdx=0000000000000006 rsi=00000001f55def98 rdi=00000000106fd070
rip=000007fef4d865d3 rsp=00000000106fcf40 rbp=00000000106fcfe9
r8=0000000000000000 r9=00000001f55def60 r10=00000001f55defa0
r11=00000000106fcd20 r12=0000000000000000 r13=0000000000000002
r14=00000001f49c3860 r15=00000001f58c0040
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
The stack is:
# Child-SP RetAddr Call Site
00 00000000`106fcf40 000007fe`f30c1437 sqlmin!SetidentI2I4+0x1f3
01 00000000`106fd050 000007fe`f474e7ce sqlTsEs!CEsExec::GeneralEval4+0xe7
02 00000000`106fd120 000007fe`f470e6ef sqlmin!CQScanUpdateNew::GetRow+0x43d
03 00000000`106fd1d0 000007fe`f08ff517 sqlmin!CQueryScan::GetRow+0x81
04 00000000`106fd200 000007fe`f091cebe sqllang!CXStmtQuery::ErsqExecuteQuery+0x36d
05 00000000`106fd390 000007fe`f091ccb9 sqllang!CXStmtDML::XretDMLExecute+0x2ee
06 00000000`106fd480 000007fe`f08fa058 sqllang!CXStmtDML::XretExecute+0xad
07 00000000`106fd4b0 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
08 00000000`106fd5f0 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
09 00000000`106fd7e0 000007fe`f152cfaa sqllang!CSQLSource::Execute+0x86c
0a 00000000`106fd9b0 000007fe`f152c9e8 sqllang!CStmtExecProc::XretLocalExec+0x25a
0b 00000000`106fda30 000007fe`f152a1d8 sqllang!CStmtExecProc::XretExecExecute+0x4e8
0c 00000000`106fe1e0 000007fe`f08fa058 sqllang!CXStmtExecProc::XretExecute+0x38
0d 00000000`106fe220 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
0e 00000000`106fe360 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
0f 00000000`106fe550 000007fe`f0902267 sqllang!CSQLSource::Execute+0x86c
10 00000000`106fe720 000007fe`f0909087 sqllang!process_request+0xa57
11 00000000`106feee0 000007fe`f2bf49d0 sqllang!process_commands+0x4a3
12 00000000`106ff200 000007fe`f2bf47b4 sqldk!SOS_Task::Param::Execute+0x21e
13 00000000`106ff800 000007fe`f2bf45b6 sqldk!SOS_Scheduler::RunTask+0xa8
14 00000000`106ff870 000007fe`f2c136ff sqldk!SOS_Scheduler::ProcessTasks+0x279
15 00000000`106ff8f0 000007fe`f2c138f0 sqldk!SchedulerManager::WorkerEntryPoint+0x24c
16 00000000`106ff990 000007fe`f2c13246 sqldk!SystemThread::RunWorker+0x8f
17 00000000`106ff9c0 000007fe`f2c13558 sqldk!SystemThreadDispatcher::ProcessWorker+0x3ab
18 00000000`106ffa70 00000000`775d59ed sqldk!SchedulerManager::ThreadEntryPoint+0x226
19 00000000`106ffb10 00000000`7780c541 kernel32!BaseThreadInitThunk+0xd
1a 00000000`106ffb40 00000000`00000000 ntdll!RtlUserThreadStart+0x21
Unassembling the function:
000007fe`f4d8658e 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d86591 4533e4 xor r12d,r12d
000007fe`f4d86594 410fb7d5 movzx edx,r13w
000007fe`f4d86598 4533c9 xor r9d,r9d
000007fe`f4d8659b 4533c0 xor r8d,r8d
000007fe`f4d8659e 488bc8 mov rcx,rax
000007fe`f4d865a1 4489642420 mov dword ptr [rsp+20h],r12d
000007fe`f4d865a6 41ff5230 call qword ptr [r10+30h]
000007fe`f4d865aa 8b5597 mov edx,dword ptr [rbp-69h]
000007fe`f4d865ad 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d865b0 4489642438 mov dword ptr [rsp+38h],r12d
000007fe`f4d865b5 4489642430 mov dword ptr [rsp+30h],r12d
000007fe`f4d865ba 458d442401 lea r8d,[r12+1]
000007fe`f4d865bf 4533c9 xor r9d,r9d
000007fe`f4d865c2 488bc8 mov rcx,rax
000007fe`f4d865c5 c644242801 mov byte ptr [rsp+28h],1
000007fe`f4d865ca 4488642420 mov byte ptr [rsp+20h],r12b
000007fe`f4d865cf 41ff5250 call qword ptr [r10+50h]
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] <=================== AV happened over here
000007fe`f4d865d6 488bc8 mov rcx,rax
000007fe`f4d865d9 4c8bf0 mov r14,rax
000007fe`f4d865dc ff5268 call qword ptr [rdx+68h]
000007fe`f4d865df 488d55e7 lea rdx,[rbp-19h]
000007fe`f4d865e3 4c8b00 mov r8,qword ptr [rax]
000007fe`f4d865e6 488bc8 mov rcx,rax
000007fe`f4d865e9 41ff5010 call qword ptr [r8+10h]
000007fe`f4d865ed f6450a04 test byte ptr [rbp+0Ah],4
I remember few issues with scan2ident function, I am not sure if they have fixed it however it appears that this is intoduced to SQL 2014 and we need help from MS to get this resolved as it needs code analysis.
It is not getting simulated for other versions of SQL apart from SQL 2014.
Also to add, interestingly, the value of rax is not visibly changed and it was successfully passed on to rcx, which has a valid value, so something should have changed the value of rax inside call to function using call qword ptr [r10+50h], and looking at this
it appears that it might be a list of functions and we are going at particular offset [50h]. So, bottom line is that the call to function qword ptr [r10+50h], should be changing something in rax, and debugging/analyzing this code might give us some more idea. -
Trouble Turneing on FileStream/Ad Hoc Query with new SQL Server 2014 64-BIt Version
SQL Server Help,
I have recently installed SQL SERVER 2014 on my Window 7 SP1 Acer laptop.
I am trying to do a simple upload of an Excel file into SQL Server using the OPENROWSET command:
Which I found requires some configuration change I attempted below.
When I execute this:
execute sp_configure 'show advanced options', 1;
RECONFIGURE;
execute sp_configure 'Ad Hoc Distributed Queries', 1;
RECONFIGURE;
GO
I get this message
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5593, Level 16, State 1, Line 2
FILESTREAM feature is not supported on WoW64. The feature is disabled.
Msg 15123, Level 16, State 1, Procedure sp_configure, Line 62
The configuration option 'Ad Hoc Distributed Queries' does not exist, or it may be an advanced option.
Msg 5593, Level 16, State 1, Line 4
FILESTREAM feature is not supported on WoW64. The feature is disabled.
When I go to the SQL Server Services and Properties on the Server and try to change the FileStream options to be on..I get the error:
"There was an unknown error applying the FILESTREAM settings. Check the parameters are valid (0x80070002)."
Perhaps my issue is with the Windows Share Name: . I have put in a local driver C:\A_Excel....also the computer name, my user ID. Is there a special format or way to define a Share Name that I am unaware of?
Is there a way to fix this? Can I not load Excel files with a 64-Bit system? Or what is the easiest way that I can do this with my configuration?
Thanks for any help.FILESTREAM feature is not supported on WoW64. The feature is disabled.
By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
Can't connect to remote SQL Server 2014 Standard with VS 2012
Hi all,
I am trying to create a development environment using SQL Server 2014 (not Express). The SQL server instance is on a Windows 8.1 Pro machine in a non-domain environment. I have Visual Studio 2012 installed on the same machine which can connect
to the SQL server instance without problems. I have another machine with VS 2012 that cannot connect. SQL server is configured for mixed authentication. The SSDT on the remote machine can see the SQL server networked instance, but will not
connect with SQL authentication.
I have rounded up all the usual suspects;
- The SQL server service is running
- Remote connections are enabled on SQL server and the relevant firewall ports are open.
- TCP/IP and named pipes are enabled
- Remote connections are enabled in Management Studio
- SQL Server Browser service in enabled and running
What am I missing? I have been out of developer mode for a few years and all of the tools have changed, but I seem to be missing something obvious.
Many thanks in advance,
Tim
Tim in DublinHello,
Have you configured the Windows Firewall on the Visual Studio computer too? Is there any other security software on those
2 computers?
Can you ping between both computers by computer name? If not, try connecting using the IP address. For example:
10.0.0.10,1433
1433 is the default SQL Server port number.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
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
ThanksHi,
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 -
Sql server 2005 reports with sql server 2014
Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
h2007You can upgrade the the RDL schema will be upgraded.
Report definition (.rdl) files are automatically upgraded in the following ways:
When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
definition is saved in a schema that is compatible with the target server.
When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
What's New (Reporting Services).
Check the below Microsoft link for more information
http://msdn.microsoft.com/en-us/library/ms143674.aspx
Mudassar
Maybe you are looking for
-
MOVED: Windows 8 secure boot on P67A-GD55
This topic has been moved to Intel Core-iX boards. https://forum-en.msi.com/index.php?topic=165611.0
-
Rman Error at the end of the backup
Hi Guru's When i am taking complete backup through Rman , At the end i am getting an error like 'there is no space in the Flash recovery area'. Error generation is like this, =========================================================== RMAN-00569: ===
-
Restrict Search results not to Show custom Pages
Hi, I have 10 Pages . The pages are like this : http://site/file/Pages/abc-thank-you.aspx http://site/file/Pages/cod-thank-you.aspx http://site/gog/Pages/ghf-thank-you.aspx http://site/file/Pagesdiv-thank-you.html I don't want these pages to appear i
-
Hi I need help with a smartform issue. I'm working on ECC 6.0 system. I have created a smartform in English but need terms and Conditions in English and French. Some of French characters coming with # Sign. followed OSS Note 776507 and the problem is
-
After updates, my zotero has gone. Urgently need it back - what do I do?
How do I restore zotero and all my information in zotero?