Backp is failed in SQL 2014 (RTM)
I tried to take Database full backup in SQL 2014 RTM (12.0.2000) but backup is failed with below
error
i am facing this issue for all databases in server and tried to take backup to all drives but getting same issue. Any suggestions would be appreciate.
I am getting same backup issue again and again...
once i restart the SQL service then backup is running fine, after 2 or 3 days i am getting same error message. i created backup in Maintenance plans and i tried with sql script also getting same issue. i am using SQL 2014 (RTM). Complete error message given
below.
============================================================================
spid69 * wship6 000007FEFCEA0000 000007FEFCEA6FFF 00007000
2015-04-20 04:51:34.91 spid69 * wshtcpip 000007FEFC8B0000 000007FEFC8B6FFF 00007000
2015-04-20 04:51:34.91 spid69 * ntdsapi 000007FEFAC90000 000007FEFACB6FFF 00027000
2015-04-20 04:51:34.91 spid69 * IPHLPAPI 000007FEFB730000 000007FEFB756FFF 00027000
2015-04-20 04:51:34.91 spid69 * WINNSI 000007FEFB710000 000007FEFB71AFFF 0000b000
2015-04-20 04:51:34.91 spid69 * rasadhlp 000007FEFADF0000 000007FEFADF7FFF 00008000
2015-04-20 04:51:34.91 spid69 * fwpuclnt 000007FEFB440000 000007FEFB492FFF 00053000
2015-04-20 04:51:34.91 spid69 * BROWCLI 000007FEE9930000 000007FEE9941FFF 00012000
2015-04-20 04:51:34.91 spid69 * rasman 000007FEFB4A0000 000007FEFB4BBFFF 0001c000
2015-04-20 04:51:34.91 spid69 * xpsqlbot 000007FEF3280000 000007FEF3287FFF 00008000
2015-04-20 04:51:34.91 spid69 * xpstar 000007FEF30C0000 000007FEF3128FFF 00069000
2015-04-20 04:51:34.91 spid69 * ODBC32 000007FEE61A0000 000007FEE6250FFF 000b1000
2015-04-20 04:51:34.92 spid69 * SQLSCM 000007FEF34E0000 000007FEF34EEFFF 0000f000
2015-04-20 04:51:34.92 spid69 * odbcint 00000000A52C0000 00000000A52F7FFF 00038000
2015-04-20 04:51:34.92 spid69 * xpstar 000007FEF3270000 000007FEF327CFFF 0000d000
2015-04-20 04:51:34.92 spid69 * msxml3 000007FEEE630000 000007FEEE803FFF 001d4000
2015-04-20 04:51:34.92 spid69 * xplog70 000007FEEA710000 000007FEEA720FFF 00011000
2015-04-20 04:51:34.92 spid69 * xplog70 000007FEE9880000 000007FEE9883FFF 00004000
2015-04-20 04:51:34.92 spid69 * System.ni 000007FEF7650000 000007FEF830AFFF 00cbb000
2015-04-20 04:51:34.92 spid69 * System.Data 000007FEEC090000 000007FEEC3ADFFF 0031e000
2015-04-20 04:51:34.92 spid69 * System.Transactions 000007FEF1EC0000 000007FEF1F08FFF 00049000
2015-04-20 04:51:34.92 spid69 * System.Security.ni 000007FEF2A20000 000007FEF2B0CFFF 000ed000
2015-04-20 04:51:34.92 spid69 * System.Xml.ni 000007FEF1F10000 000007FEF28D1FFF 009c2000
2015-04-20 04:51:34.92 spid69 * System.Configuration.ni 000007FEEF5C0000 000007FEEF6F8FFF 00139000
2015-04-20 04:51:34.92 spid69 * perfproc 000007FEFADD0000 000007FEFADDDFFF 0000e000
2015-04-20 04:51:34.92 spid69 * apphelp 000007FEFD510000 000007FEFD566FFF 00057000
2015-04-20 04:51:34.92 spid69 * dbghelp 000000007CAD0000 000000007CC65FFF 00196000
2015-04-20 04:51:34.92 spid69 *
2015-04-20 04:51:34.92 spid69 * P1Home: 00000000D86EE220: 00000000C0000005 0000000000000000 000007FEDB552D45 0000000000000002 0000000000000000 000007FEDEC6B160
2015-04-20 04:51:34.92 spid69 * P2Home: 00000000D86EDD30: 00000000D86EE220 00000000D86EDD30 0000007400000000 000007FE00000000 0000000078D9CB40 000007FE00000001
2015-04-20 04:51:34.92 spid69 * P3Home: 0000007400000000:
2015-04-20 04:51:34.92 spid69 * P4Home: 000007FE00000000:
2015-04-20 04:51:34.92 spid69 * P5Home: 0000000078D9CB40: 0000000000000000 0000000000000000 0000000003423D20 0000000078D9CBE0 00000074C2000000 0000000000000000
2015-04-20 04:51:34.92 spid69 * P6Home: 000007FE00000001:
2015-04-20 04:51:34.92 spid69 * ContextFlags: 000000000010001F: 0000010000001400 0000340000000200 000001000000D400 0000000000000000 0000000000000000 0000020000000000
2015-04-20 04:51:34.92 spid69 * MxCsr: 0000000000001FA0:
2015-04-20 04:51:34.92 spid69 * SegCs: 0000000000000033:
2015-04-20 04:51:34.92 spid69 * SegDs: 000000000000002B:
2015-04-20 04:51:34.92 spid69 * SegEs: 000000000000002B:
2015-04-20 04:51:34.92 spid69 * SegFs: 0000000000000053:
2015-04-20 04:51:34.92 spid69 * SegGs: 000000000000002B:
2015-04-20 04:51:34.92 spid69 * SegSs: 000000000000002B:
2015-04-20 04:51:34.92 spid69 * EFlags: 0000000000010212: 000000000000FFFF 0000000000000000 0FA0000000000000 0000000000000000 0080000000000000 0001000000010000
2015-04-20 04:51:34.92 spid69 * Rax: 0000000000000000:
2015-04-20 04:51:34.92 spid69 * Rcx: 00000000005A5C40: 4D545FA89792E114 1ED9A321EA2BCD19 A88130C3DF31A1FC A081041F1D550306 81A09A81309D8130 746848869481A097
2015-04-20 04:51:34.92 spid69 * Rdx: 0000000078D11AA0: FFFFFFFFFFFFFFFF 0053004C00510053 0065007600720065 00610042003A0072 00700075006B0063 0076006500440020
2015-04-20 04:51:34.92 spid69 * Rbx: 0000007510614160: 0000000000000000 0000000000000000 000000752FEB2170 0000007537E08298 000007FE00000001 0000007537E08298
2015-04-20 04:51:34.92 spid69 * Rsp: 00000000D86EE2E8: 000007FEDD808E85 0000000000000000 00000000D86EE399 0000000000000000 0000000000000958 00000074C2026640
2015-04-20 04:51:34.92 spid69 * Rbp: 00000000D86EE399: 0000000000000000 0000000000000000 FE00000000000000 FAFFFFFFFFFFFFFF 1500000000000000 4000000000000000
2015-04-20 04:51:34.92 spid69 * Rsi: 0000000000000000:
2015-04-20 04:51:34.92 spid69 * Rdi: 0000000000000015:
2015-04-20 04:51:34.92 spid69 * R8: 00000000D86EE370: 0000000078D2E90B 0000000078D298F8 00000074C203A040 000007FE004002B6 0000000000000000 0000000000000000
2015-04-20 04:51:34.92 spid69 * R9: 000007FEDE6C5520: 0000000078D10000 0000000000000958 006C004700000001 006C00610062006F 004C00510053005C 003000310031005F
2015-04-20 04:51:34.92 spid69 * R10: 0000000000000019:
2015-04-20 04:51:34.92 spid69 * R11: 000007FEDE6FD490: 000007FEDE6E4C90 000000752E560040 0000000000000000 0000000000000000 0000000000000000 0000000000000000
2015-04-20 04:51:34.92 spid69 * R12: 0000000000000019:
2015-04-20 04:51:34.92 spid69 * R13: 0000000078D2E90B: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000
2015-04-20 04:51:34.92 spid69 * R14: 00000074C2026650: 0044005C003A0044 0042005F0079006C 0075006B00630061 0052005C00730070 0072006F00700065 0072006500530074
2015-04-20 04:51:34.92 spid69 * R15: FFFFFFFFFFFFFFFF:
2015-04-20 04:51:34.92 spid69 * Rip: 000007FEDB552D45: 104089490904034A C033C300000001B8 000001B810408949 909090C3C033C300 9090909090909090 27A9058B4C909090
2015-04-20 04:51:34.92 spid69 * *******************************************************************************
2015-04-20 04:51:34.92 spid69 * -------------------------------------------------------------------------------
2015-04-20 04:51:34.92 spid69 * Short Stack Dump
2015-04-20 04:51:34.93 spid69 000007FEDB552D45 Module(sqlmin+00000000009D2D45)
2015-04-20 04:51:34.93 spid69 000007FEDD808E85 Module(sqlmin+0000000002C88E85)
2015-04-20 04:51:34.93 spid69 000007FEDDB1BF6F Module(sqlmin+0000000002F9BF6F)
2015-04-20 04:51:34.93 spid69 000007FEDDB1C29C Module(sqlmin+0000000002F9C29C)
2015-04-20 04:51:34.93 spid69 000007FEDDAF8614 Module(sqlmin+0000000002F78614)
2015-04-20 04:51:34.93 spid69 000007FEDDAFAE67 Module(sqlmin+0000000002F7AE67)
2015-04-20 04:51:34.94 spid69 000007FEDDB20377 Module(sqlmin+0000000002FA0377)
2015-04-20 04:51:34.94 spid69 000007FEDDB21310 Module(sqlmin+0000000002FA1310)
2015-04-20 04:51:34.94 spid69 000007FEDDB2D491 Module(sqlmin+0000000002FAD491)
2015-04-20 04:51:34.95 spid69 000007FEDAC7BC3F Module(sqlmin+00000000000FBC3F)
2015-04-20 04:51:34.95 spid69 000007FEF61C49D0 Module(sqldk+00000000000049D0)
2015-04-20 04:51:34.95 spid69 000007FEF61C47B4 Module(sqldk+00000000000047B4)
2015-04-20 04:51:34.95 spid69 000007FEF61C45B6 Module(sqldk+00000000000045B6)
2015-04-20 04:51:34.95 spid69 000007FEF61E36FF Module(sqldk+00000000000236FF)
2015-04-20 04:51:34.95 spid69 000007FEF61E38F0 Module(sqldk+00000000000238F0)
2015-04-20 04:51:34.95 spid69 000007FEF61E3246 Module(sqldk+0000000000023246)
2015-04-20 04:51:34.96 spid69 000007FEF61E3558 Module(sqldk+0000000000023558)
2015-04-20 04:51:34.97 spid69 00000000777F59ED Module(kernel32+00000000000159ED)
2015-04-20 04:51:34.97 spid69 000000007792C541 Module(ntdll+000000000002C541)
2015-04-20 04:51:34.97 spid69 Stack Signature for the dump is 0x000000003A4041F2
2015-04-20 04:51:35.19 spid69 [INFO] Identity Begin End | State Result Error Speculate Prepared LazyCommit ReadOnly | Transaction Database ThreadId | ReadSet WriteSet ScanSet Savepoint LogSizeRq | CommitDep TotalComm Dependent 0 Dependent 1 Dependent 2 Dependent
3 Dependent 4 Dependent 5 Dependent 6 Dependent 7 | Area Location |
2015-04-20 04:51:36.81 spid69 External dump process return code 0x20000001.
External dump process returned no errors.
2015-04-20 04:51:36.82 Backup Error: 3041, Severity: 16, State: 1.
2015-04-20 04:51:36.82 Backup BACKUP failed to complete the command BACKUP DATABASE ReportServerTempDB. Check the backup application log for detailed messages.
2015-04-20 04:51:36.85 spid69 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\LOG\SQLDump1162.txt
2015-04-20 04:51:36.85 spid69 SqlDumpExceptionHandler: Process 12408 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2015-04-20 04:51:36.85 spid69 * *******************************************************************************
2015-04-20 04:51:36.85 spid69 *
2015-04-20 04:51:36.85 spid69 * BEGIN STACK DUMP:
2015-04-20 04:51:36.85 spid69 * 04/20/15 04:51:36 spid 12408
2015-04-20 04:51:36.85 spid69 * Private server build.
2015-04-20 04:51:36.85 spid69 *
2015-04-20 04:51:36.85 spid69 *
2015-04-20 04:51:36.85 spid69 * Exception Address = 000007FEDB552D45 Module(sqlmin+00000000009D2D45)
2015-04-20 04:51:36.85 spid69 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2015-04-20 04:51:36.85 spid69 * Access Violation occurred reading address 000007FEDEC6B160
2015-04-20 04:51:36.85 spid69 * Input Buffer 448 bytes -
2015-04-20 04:51:36.85 spid69 * BACKUP DATABASE [Support] TO DISK = N'D:\Dly_Backups\Support
2015-04-20 04:51:36.85 spid69 * _backup_2015_04_20_045121_7184311.bak' WITH NOFORMAT, NOINIT, NAME = N'
2015-04-20 04:51:36.85 spid69 * Support_backup_2015_04_20_045121_7184311', SKIP, REWIND, NOUNLOAD, STAT
2015-04-20 04:51:36.85 spid69 * S = 10
2015-04-20 04:51:36.85 spid69 *
2015-04-20 04:51:36.85 spid69 *
2015-04-20 04:51:36.85 spid69 * MODULE BASE END SIZE
2015-04-20 04:51:36.85 spid69 * sqlservr 00000000FFD70000 00000000FFDCEFFF 0005f000
2015-04-20 04:51:36.85 spid69 * ntdll 0000000077900000 0000000077AA8FFF 001a9000
2015-04-20 04:51:36.85 spid69 * kernel32 00000000777E0000 00000000778FEFFF 0011f000
2015-04-20 04:51:36.85 spid69 * KERNELBASE 000007FEFDA60000 000007FEFDACBFFF 0006c000
2015-04-20 04:51:36.85 spid69 * NETAPI32 000007FEFB190000 000007FEFB1A5FFF 00016000
2015-04-20 04:51:36.85 spid69 * netutils 000007FEFCB40000 000007FEFCB4BFFF 0000c000
2015-04-20 04:51:36.85 spid69 * msvcrt 000007FEFDEE0000 000007FEFDF7EFFF 0009f000
2015-04-20 04:51:36.85 spid69 * srvcli 000007FEFD280000 000007FEFD2A2FFF 00023000
2015-04-20 04:51:36.85 spid69 * RPCRT4 000007FEFE270000 000007FEFE39CFFF 0012d000
2015-04-20 04:51:36.85 spid69 * wkscli 000007FEFB170000 000007FEFB184FFF 00015000
2015-04-20 04:51:36.85 spid69 * pdh 000007FEF7160000 000007FEF71ADFFF 0004e000
2015-04-20 04:51:36.85 spid69 * ADVAPI32 000007FEFFB30000 000007FEFFC0AFFF 000db000
2015-04-20 04:51:36.85 spid69 * sechost 000007FEFF740000 000007FEFF75EFFF 0001f000
2015-04-20 04:51:36.85 spid69 * opends60 000007FEFADA0000 000007FEFADA8FFF 00009000
2015-04-20 04:51:36.85 spid69 * MSVCR100 0000000074570000 0000000074641FFF 000d2000
2015-04-20 04:51:36.85 spid69 * MSVCP100 00000000744A0000 0000000074537FFF 00098000
2015-04-20 04:51:36.85 spid69 * SQLOS 000007FEFAD90000 000007FEFAD96FFF 00007000
2015-04-20 04:51:36.85 spid69 * sqlmin 000007FEDAB80000 000007FEDEA1CFFF 03e9d000
2015-04-20 04:51:36.85 spid69 * CRYPT32 000007FEFD740000 000007FEFD8ABFFF 0016c000
2015-04-20 04:51:36.85 spid69 * MSASN1 000007FEFD720000 000007FEFD72EFFF 0000f000
2015-04-20 04:51:36.85 spid69 * Secur32 000007FEFD4A0000 000007FEFD4AAFFF 0000b000
2015-04-20 04:51:36.85 spid69 * SSPICLI 000007FEFD4E0000 000007FEFD504FFF 00025000
2015-04-20 04:51:36.85 spid69 * PSAPI 0000000077AD0000 0000000077AD6FFF 00007000
2015-04-20 04:51:36.85 spid69 * WS2_32 000007FEFF4E0000 000007FEFF52CFFF 0004d000
2015-04-20 04:51:36.85 spid69 * NSI 000007FEFE070000 000007FEFE077FFF 00008000
2015-04-20 04:51:36.85 spid69 * WINHTTP 000007FEF31F0000 000007FEF3260FFF 00071000
2015-04-20 04:51:36.85 spid69 * webio 000007FEF3180000 000007FEF31E3FFF 00064000
2015-04-20 04:51:36.85 spid69 * USER32 00000000776E0000 00000000777D9FFF 000fa000
2015-04-20 04:51:36.85 spid69 * GDI32 000007FEFE200000 000007FEFE266FFF 00067000
2015-04-20 04:51:36.85 spid69 * LPK 000007FEFE420000 000007FEFE42DFFF 0000e000
2015-04-20 04:51:36.85 spid69 * USP10 000007FEFDF80000 000007FEFE048FFF 000c9000
2015-04-20 04:51:36.85 spid69 * ole32 000007FEFF530000 000007FEFF732FFF 00203000
2015-04-20 04:51:36.85 spid69 * OLEAUT32 000007FEFE120000 000007FEFE1F6FFF 000d7000
2015-04-20 04:51:36.85 spid69 * sqlTsEs 000007FEF6690000 000007FEF6F22FFF 00893000
2015-04-20 04:51:36.85 spid69 * sqldk 000007FEF61C0000 000007FEF6688FFF 004c9000
2015-04-20 04:51:36.85 spid69 * WINMM 000007FEF1A00000 000007FEF1A3AFFF 0003b000
2015-04-20 04:51:36.85 spid69 * qds 000007FEF6130000 000007FEF61BDFFF 0008e000
2015-04-20 04:51:36.85 spid69 * sqllang 000007FEF3EC0000 000007FEF6126FFF 02267000
2015-04-20 04:51:36.85 spid69 * USERENV 000007FEFD970000 000007FEFD98DFFF 0001e000
2015-04-20 04:51:36.85 spid69 * profapi 000007FEFD710000 000007FEFD71EFFF 0000f000
2015-04-20 04:51:36.85 spid69 * LOGONCLI 000007FEFCD00000 000007FEFCD2FFFF 00030000
2015-04-20 04:51:36.85 spid69 * SAMCLI 000007FEFA980000 000007FEFA993FFF 00014000
2015-04-20 04:51:36.85 spid69 * AUTHZ 000007FEFD0E0000 000007FEFD10EFFF 0002f000
2015-04-20 04:51:36.85 spid69 * WINTRUST 000007FEFD990000 000007FEFD9C9FFF 0003a000
2015-04-20 04:51:36.85 spid69 * IMM32 000007FEFE540000 000007FEFE56DFFF 0002e000
2015-04-20 04:51:36.85 spid69 * MSCTF 000007FEFE430000 000007FEFE538FFF 00109000
2015-04-20 04:51:36.85 spid69 * CRYPTBASE 000007FEFD570000 000007FEFD57EFFF 0000f000
2015-04-20 04:51:36.85 spid69 * instapi120 000007FEF71B0000 000007FEF71BEFFF 0000f000
2015-04-20 04:51:36.85 spid69 * cscapi 000007FEEF460000 000007FEEF46EFFF 0000f000
2015-04-20 04:51:36.85 spid69 * sqlevn70 000007FEF3C10000 000007FEF3EBCFFF 002ad000
2015-04-20 04:51:36.85 spid69 * CRYPTSP 000007FEFCF10000 000007FEFCF26FFF 00017000
2015-04-20 04:51:36.85 spid69 * rsaenh 000007FEFCC10000 000007FEFCC56FFF 00047000
2015-04-20 04:51:36.85 spid69 * imagehlp 000007FEFE050000 000007FEFE068FFF 00019000
2015-04-20 04:51:36.85 spid69 * ncrypt 000007FEFD090000 000007FEFD0DCFFF 0004d000
2015-04-20 04:51:36.85 spid69 * bcrypt 000007FEFD060000 000007FEFD081FFF 00022000
2015-04-20 04:51:36.85 spid69 * bcryptprimitives 000007FEFCB50000 000007FEFCB9BFFF 0004c000
2015-04-20 04:51:36.85 spid69 * GPAPI 000007FEFC9B0000 000007FEFC9CAFFF 0001b000
2015-04-20 04:51:36.85 spid69 * cryptnet 000007FEFA7A0000 000007FEFA7C6FFF 00027000
2015-04-20 04:51:36.85 spid69 * WLDAP32 000007FEFDAD0000 000007FEFDB21FFF 00052000
2015-04-20 04:51:36.85 spid69 * SHLWAPI 000007FEFFAB0000 000007FEFFB20FFF 00071000
2015-04-20 04:51:36.85 spid69 * ntmarta 000007FEFC7B0000 000007FEFC7DCFFF 0002d000
2015-04-20 04:51:36.85 spid69 * CLUSAPI 000007FEEDBE0000 000007FEEDC2FFFF 00050000
2015-04-20 04:51:36.85 spid69 * cryptdll 000007FEFD190000 000007FEFD1A3FFF 00014000
2015-04-20 04:51:36.85 spid69 * RESUTILS 000007FEEDBC0000 000007FEEDBD8FFF 00019000
2015-04-20 04:51:36.85 spid69 * VERSION 000007FEFC7E0000 000007FEFC7EBFFF 0000c000
2015-04-20 04:51:36.85 spid69 * hkruntime 000007FEF3950000 000007FEF3C06FFF 002b7000
2015-04-20 04:51:36.85 spid69 * hkcompile 000007FEF3890000 000007FEF394DFFF 000be000
2015-04-20 04:51:36.85 spid69 * XmlLite 000007FEFB910000 000007FEFB944FFF 00035000
2015-04-20 04:51:36.85 spid69 * hkengine 000007FEF36E0000 000007FEF388EFFF 001af000
2015-04-20 04:51:36.85 spid69 * dbghelp 000000007A770000 000000007A905FFF 00196000
2015-04-20 04:51:36.85 spid69 * pcwum 000007FEFC970000 000007FEFC97CFFF 0000d000
2015-04-20 04:51:36.85 spid69 * credssp 000007FEFCB00000 000007FEFCB09FFF 0000a000
2015-04-20 04:51:36.85 spid69 * msv1_0 000007FEFCE40000 000007FEFCE91FFF 00052000
2015-04-20 04:51:36.85 spid69 * kerberos 000007FEFCF30000 000007FEFCFE7FFF 000b8000
2015-04-20 04:51:36.85 spid69 * schannel 000007FEFCCA0000 000007FEFCCF6FFF 00057000
2015-04-20 04:51:36.85 spid69 * MSCOREE 000007FEFA400000 000007FEFA46EFFF 0006f000
2015-04-20 04:51:36.85 spid69 * mscoreei 000007FEFA360000 000007FEFA3F6FFF 00097000
2015-04-20 04:51:36.85 spid69 * security 0000000079DD0000 0000000079DD2FFF 00003000
2015-04-20 04:51:36.85 spid69 * CLBCatQ 000007FEFE080000 000007FEFE118FFF 00099000
2015-04-20 04:51:36.85 spid69 * sqlncli11 00000000C17F0000 00000000C1B42FFF 00353000
2015-04-20 04:51:36.85 spid69 * COMCTL32 000007FEFA4A0000 000007FEFA53FFFF 000a0000
2015-04-20 04:51:36.85 spid69 * COMDLG32 000007FEFF760000 000007FEFF7F6FFF 00097000
2015-04-20 04:51:36.85 spid69 * SHELL32 000007FEFE570000 000007FEFF2F7FFF 00d88000
2015-04-20 04:51:36.85 spid69 * SQLNCLIR11 000000007A110000 000000007A147FFF 00038000
2015-04-20 04:51:36.85 spid69 * clr 000007FEF99F0000 000007FEFA35AFFF 0096b000
2015-04-20 04:51:36.85 spid69 * MSVCR110_CLR0400 000007FEF9910000 000007FEF99E1FFF 000d2000
2015-04-20 04:51:36.85 spid69 * mscorlib.ni 000007FEF8310000 000007FEF9909FFF 015fa000
2015-04-20 04:51:36.85 spid69 * SqlAccess 000000007D9A0000 000000007DA11FFF 00072000
2015-04-20 04:51:36.85 spid69 * clrjit 000007FEEEAD0000 000007FEEEC00FFF 00131000
2015-04-20 04:51:36.85 spid69 * BatchParser 000007FEF3680000 000007FEF36A7FFF 00028000
2015-04-20 04:51:36.85 spid69 * nlssorting 000007FEF7540000 000007FEF7555FFF 00016000
2015-04-20 04:51:36.85 spid69 * ftimport 000000007B560000 000000007B584FFF 00025000
2015-04-20 04:51:36.85 spid69 * MSFTE 00000000CA7D0000 00000000CAB7DFFF 003ae000
2015-04-20 04:51:36.85 spid69 * perfcounter 000007FEF3640000 000007FEF367BFFF 0003c000
2015-04-20 04:51:36.86 spid69 * aspnet_counters 000007FEFADC0000 000007FEFADC7FFF 00008000
2015-04-20 04:51:36.86 spid69 * aspnet_perf 000007FEFAD80000 000007FEFAD8CFFF 0000d000
2015-04-20 04:51:36.86 spid69 * MSVCR120_CLR0400 000007FEF33B0000 000007FEF3485FFF 000d6000
2015-04-20 04:51:36.86 spid69 * aspnet_perf 000007FEFAD70000 000007FEFAD7CFFF 0000d000
2015-04-20 04:51:36.86 spid69 * MSVCR80 00000000A4010000 00000000A40D8FFF 000c9000
2015-04-20 04:51:36.86 spid69 * DNSAPI 000007FEFCD30000 000007FEFCD8AFFF 0005b000
2015-04-20 04:51:36.86 spid69 * CFGMGR32 000007FEFD9E0000 000007FEFDA15FFF 00036000
2015-04-20 04:51:36.86 spid69 * mswsock 000007FEFCEB0000 000007FEFCF04FFF 00055000
2015-04-20 04:51:36.86 spid69 * wship6 000007FEFCEA0000 000007FEFCEA6FFF 00007000
2015-04-20 04:51:36.86 spid69 * wshtcpip 000007FEFC8B0000 000007FEFC8B6FFF 00007000
2015-04-20 04:51:36.86 spid69 * ntdsapi 000007FEFAC90000 000007FEFACB6FFF 00027000
2015-04-20 04:51:36.86 spid69 * IPHLPAPI 000007FEFB730000 000007FEFB756FFF 00027000
2015-04-20 04:51:36.86 spid69 * WINNSI 000007FEFB710000 000007FEFB71AFFF 0000b000
2015-04-20 04:51:36.86 spid69 * rasadhlp 000007FEFADF0000 000007FEFADF7FFF 00008000
2015-04-20 04:51:36.86 spid69 * fwpuclnt 000007FEFB440000 000007FEFB492FFF 00053000
2015-04-20 04:51:36.86 spid69 * BROWCLI 000007FEE9930000 000007FEE9941FFF 00012000
2015-04-20 04:51:36.86 spid69 * rasman 000007FEFB4A0000 000007FEFB4BBFFF 0001c000
2015-04-20 04:51:36.86 spid69 * xpsqlbot 000007FEF3280000 000007FEF3287FFF 00008000
2015-04-20 04:51:36.86 spid69 * xpstar 000007FEF30C0000 000007FEF3128FFF 00069000
2015-04-20 04:51:36.86 spid69 * ODBC32 000007FEE61A0000 000007FEE6250FFF 000b1000
2015-04-20 04:51:36.86 spid69 * SQLSCM 000007FEF34E0000 000007FEF34EEFFF 0000f000
2015-04-20 04:51:36.86 spid69 * odbcint 00000000A52C0000 00000000A52F7FFF 00038000
2015-04-20 04:51:36.86 spid69 * xpstar 000007FEF3270000 000007FEF327CFFF 0000d000
2015-04-20 04:51:36.86 spid69 * msxml3 000007FEEE630000 000007FEEE803FFF 001d4000
2015-04-20 04:51:36.86 spid69 * xplog70 000007FEEA710000 000007FEEA720FFF 00011000
2015-04-20 04:51:36.86 spid69 * xplog70 000007FEE9880000 000007FEE9883FFF 00004000
2015-04-20 04:51:36.86 spid69 * System.ni 000007FEF7650000 000007FEF830AFFF 00cbb000
2015-04-20 04:51:36.86 spid69 * System.Data 000007FEEC090000 000007FEEC3ADFFF 0031e000
2015-04-20 04:51:36.86 spid69 * System.Transactions 000007FEF1EC0000 000007FEF1F08FFF 00049000
2015-04-20 04:51:36.86 spid69 * System.Security.ni 000007FEF2A20000 000007FEF2B0CFFF 000ed000
2015-04-20 04:51:36.86 spid69 * System.Xml.ni 000007FEF1F10000 000007FEF28D1FFF 009c2000
2015-04-20 04:51:36.86 spid69 * System.Configuration.ni 000007FEEF5C0000 000007FEEF6F8FFF 00139000
2015-04-20 04:51:36.86 spid69 * perfproc 000007FEFADD0000 000007FEFADDDFFF 0000e000
2015-04-20 04:51:36.86 spid69 * apphelp 000007FEFD510000 000007FEFD566FFF 00057000
2015-04-20 04:51:36.86 spid69 * dbghelp 000000007CAD0000 000000007CC65FFF 00196000
2015-04-20 04:51:36.86 spid69 *
2015-04-20 04:51:36.86 spid69 * P1Home: 00000000D86EE220: 00000000C0000005 0000000000000000 000007FEDB552D45 0000000000000002 0000000000000000 000007FEDEC6B160
2015-04-20 04:51:36.86 spid69 * P2Home: 00000000D86EDD30: 00000000D86EE220 00000000D86EDD30 0000007400000000 000007FE00000000 0000000078D9CB40 000007FE00000001
2015-04-20 04:51:36.86 spid69 * P3Home: 0000007400000000:
2015-04-20 04:51:36.86 spid69 * P4Home: 000007FE00000000:
2015-04-20 04:51:36.86 spid69 * P5Home: 0000000078D9CB40: 0000000000000000 0000000000000000 0000000003423D20 0000000078D9CBE0 00000074C2000000 0000000000000000
2015-04-20 04:51:36.86 spid69 * P6Home: 000007FE00000001:
2015-04-20 04:51:36.86 spid69 * ContextFlags: 000000000010001F: 0000010000001400 0000340000000200 000001000000D400 0000000000000000 0000000000000000 0000020000000000
2015-04-20 04:51:36.86 spid69 * MxCsr: 0000000000001FA0:
2015-04-20 04:51:36.86 spid69 * SegCs: 0000000000000033:
2015-04-20 04:51:36.86 spid69 * SegDs: 000000000000002B:
2015-04-20 04:51:36.86 spid69 * SegEs: 000000000000002B:
2015-04-20 04:51:36.86 spid69 * SegFs: 0000000000000053:
2015-04-20 04:51:36.86 spid69 * SegGs: 000000000000002B:
2015-04-20 04:51:36.86 spid69 * SegSs: 000000000000002B:
2015-04-20 04:51:36.86 spid69 * EFlags: 0000000000010212: 000000000000FFFF 0000000000000000 0FA0000000000000 0000000000000000 0080000000000000 0001000000010000
2015-04-20 04:51:36.86 spid69 * Rax: 0000000000000000:
2015-04-20 04:51:36.86 spid69 * Rcx: 00000000005A5C40: 4D545FA89792E114 1ED9A321EA2BCD19 A88130C3DF31A1FC A081041F1D550306 81A09A81309D8130 746848869481A097
2015-04-20 04:51:36.86 spid69 * Rdx: 0000000078D11AA0: FFFFFFFFFFFFFFFF 0053004C00510053 0065007600720065 00610042003A0072 00700075006B0063 0076006500440020
2015-04-20 04:51:36.86 spid69 * Rbx: 0000007510614160: 0000000000000000 0000000000000000 000000752FEB2170 0000007537E08298 000007FE00000001 0000007537E08298
2015-04-20 04:51:36.86 spid69 * Rsp: 00000000D86EE2E8: 000007FEDD808E85 0000000000000000 00000000D86EE399 0000000000000000 0000000000000958 00000074C187DF10
2015-04-20 04:51:36.86 spid69 * Rbp: 00000000D86EE399: 0000000000000000 0000000000000000 FE00000000000000 FAFFFFFFFFFFFFFF 1500000000000000 4000000000000000
2015-04-20 04:51:36.86 spid69 * Rsi: 0000000000000000:
2015-04-20 04:51:36.86 spid69 * Rdi: 0000000000000015:
2015-04-20 04:51:36.86 spid69 * R8: 00000000D86EE370: 0000000078D2E90B 0000000078D298F8 00000074C2026040 000007FE004002B6 0000000000000000 0000000000000000
2015-04-20 04:51:36.86 spid69 * R9: 000007FEDE6C5520: 0000000078D10000 0000000000000958 006C004700000001 006C00610062006F 004C00510053005C 003000310031005F
2015-04-20 04:51:36.86 spid69 * R10: 0000000000000019:
2015-04-20 04:51:36.86 spid69 * R11: 000007FEDE6FD490: 000007FEDE6E4C90 000000752E560040 0000000000000000 0000000000000000 0000000000000000 0000000000000000
2015-04-20 04:51:36.86 spid69 * R12: 0000000000000019:
2015-04-20 04:51:36.86 spid69 * R13: 0000000078D2E90B: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000
2015-04-20 04:51:36.86 spid69 * R14: 00000074C187DF20: 0044005C003A0044 0042005F0079006C 0075006B00630061 0053005C00730070 006F007000700075 0062005F00740072
2015-04-20 04:51:36.86 spid69 * R15: FFFFFFFFFFFFFFFF:
2015-04-20 04:51:36.86 spid69 * Rip: 000007FEDB552D45: 104089490904034A C033C300000001B8 000001B810408949 909090C3C033C300 9090909090909090 27A9058B4C909090
2015-04-20 04:51:36.86 spid69 * *******************************************************************************
2015-04-20 04:51:36.86 spid69 * -------------------------------------------------------------------------------
2015-04-20 04:51:36.86 spid69 * Short Stack Dump
2015-04-20 04:51:36.87 spid69 000007FEDB552D45 Module(sqlmin+00000000009D2D45)
2015-04-20 04:51:36.87 spid69 000007FEDD808E85 Module(sqlmin+0000000002C88E85)
2015-04-20 04:51:36.87 spid69 000007FEDDB1BF6F Module(sqlmin+0000000002F9BF6F)
2015-04-20 04:51:36.88 spid69 000007FEDDB1C29C Module(sqlmin+0000000002F9C29C)
2015-04-20 04:51:36.88 spid69 000007FEDDAF8614 Module(sqlmin+0000000002F78614)
2015-04-20 04:51:36.88 spid69 000007FEDDAFAE67 Module(sqlmin+0000000002F7AE67)
2015-04-20 04:51:36.88 spid69 000007FEDDB20377 Module(sqlmin+0000000002FA0377)
2015-04-20 04:51:36.88 spid69 000007FEDDB21310 Module(sqlmin+0000000002FA1310)
2015-04-20 04:51:36.88 spid69 000007FEDDB2D491 Module(sqlmin+0000000002FAD491)
2015-04-20 04:51:36.89 spid69 000007FEDAC7BC3F Module(sqlmin+00000000000FBC3F)
2015-04-20 04:51:36.89 spid69 000007FEF61C49D0 Module(sqldk+00000000000049D0)
2015-04-20 04:51:36.89 spid69 000007FEF61C47B4 Module(sqldk+00000000000047B4)
2015-04-20 04:51:36.89 spid69 000007FEF61C45B6 Module(sqldk+00000000000045B6)
2015-04-20 04:51:36.89 spid69 000007FEF61E36FF Module(sqldk+00000000000236FF)
2015-04-20 04:51:36.89 spid69 000007FEF61E38F0 Module(sqldk+00000000000238F0)
2015-04-20 04:51:36.89 spid69 000007FEF61E3246 Module(sqldk+0000000000023246)
2015-04-20 04:51:36.90 spid69 000007FEF61E3558 Module(sqldk+0000000000023558)
2015-04-20 04:51:36.91 spid69 00000000777F59ED Module(kernel32+00000000000159ED)
2015-04-20 04:51:36.91 spid69 000000007792C541 Module(ntdll+000000000002C541)
2015-04-20 04:51:36.92 spid69 Stack Signature for the dump is 0x000000003A4041F2
2015-04-20 04:51:37.13 spid69 [INFO] Identity Begin End | State Result Error Speculate Prepared LazyCommit ReadOnly | Transaction Database ThreadId | ReadSet WriteSet ScanSet Savepoint LogSizeRq | CommitDep TotalComm Dependent 0 Dependent 1 Dependent 2 Dependent
3 Dependent 4 Dependent 5 Dependent 6 Dependent 7 | Area Location |
=============================================================================
Please check if this helps:
SQL Server Backup Failing with EXCEPTION_ACCESS_VIOLATION
http://sqlserver-help.com/2015/03/25/
Similar Messages
-
Is backing up and Restoring SharePoint 2013 SP1 Farm with SQL 2014 RTM "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find information anywhere.
Regards,
IgorThis is a DPM supportability issue, I believe. Last I heard, no it was not supported. SharePoint 2013 does not support SQL 2014 until the April 2014 CU. The CU should be out soon, although it appears to have been delayed (usually comes out on Patch Tuesday,
which was this past Tuesday).
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
SQL 2014 RTM and Sql 2008r2 standard side by side installation ..
We are planning on reconfiguring our database server and then installing SQL 2008 R2 Standard edition in a side by side installation with SQL 2014 RTM. I have researched a little, and have not seen any major issues when planning this type of configuration.
Are there any issues that may occur with this?
2008 R2 will be in the default instance, and 2014 will be using a named instance. We do foresee uninstalling 2008 R2 after a period of time, and moving all of our databases to 2014 after testing has been performed. Once we uninstall 2008 R2, will we be able
to install a default instance of 2014? Are there any special steps that need to be taken to do that?Hello,
If possible install the SQL Server 2008 R2 instance first, then install SQL Server 2014. Through the years, the formula
of installing the older versions of SQL Server first has proved to be a winner for me.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server 2014 RTM In-Memory OLTP sample
Hi I am trying to get the sample
https://msftdbprodsamples.codeplex.com/releases/view/114491
but it does not appear to be there, has it been moved?If you want download In-Memory sample, please download it from this link:
SQL Server 2014 RTM In-Memory OLTP Sample.zip
If you want Adventure Works 2014, you can download it from the following link:
Adventure Works 2014 Full Database Backup.zip
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog -
SQL Server Setup Failure 0x84B10001 (SQL 2012 SP2 and SQL 2014 Standard)
I'm having a problem with SQL Server Setup. I had SQL Server 2012 R2 SP1 installed, and the SP2 installer would fail.
I decided to just get SQL Server 2014. The setup (and system configuration checker) for that fails with the same error.
SQL Server Setup failure
SQL Server Setup has encountered the following error:
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
Error code 0x84B10001
I found this and other posts about similar problems that point at MSDE being the cause.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc9f4949-1b45-427c-aa2b-d2222488a13e/problems-installing-sql-server-2012error-code-0x84b10001?forum=sqlexpress
I definitely had MSDE installed, but I went through the steps to manually remove it and rebooted with no luck.
/* Don Reynolds */(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xsd' loaded
into datastore path '/Datastore/ProductSettings/SqlBrowserStopService/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd' loaded into datastore path
'/Datastore/ProductSettings/Repl/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd' loaded into datastore
path '/Datastore/ProductSettings/SqlRSSHP/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd' loaded into
datastore path '/Datastore/ProductSettings/SqlRSSHP/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd' loaded into datastore path
'/Datastore/ProductSettings/SqlRS/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd' loaded into datastore path
'/Datastore/ProductSettings/SqlRS/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd' loaded into datastore
path '/Datastore/ProductSettings/SqlRS/DBPrivate'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd' loaded
into datastore path '/Datastore/ProductSettings/DReplayController/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd' loaded into
datastore path '/Datastore/ProductSettings/DReplayClient/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailOverClusterName/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailoverClusterName/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/SQLServerSCP/Private'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml' loaded into datastore path '/Datastore/ProductSettings/ClusterNodesStatus/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml' validated with schema 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/ASSIP/Public'
(01) 2014-07-02 10:52:57 Slp: Completed Action: LoadPackageDatastoreObjects, returned True
(01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:57 Slp: Running Action: InitializeInputSettingStore
(01) 2014-07-02 10:52:57 Slp: Completed Action: InitializeInputSettingStore, returned True
(01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:57 Slp: Running Action: InitializeRoleService
(01) 2014-07-02 10:52:57 Slp: Loading role: SPI_AS_NewFarm
(01) 2014-07-02 10:52:58 Slp: Loading role: SPI_AS_ExistingFarm
(01) 2014-07-02 10:52:58 Slp: Loading role: AllFeatures_WithDefaults
(01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRoleService, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerCommandLineArguments
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: WORKFLOW
(01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: TIMESTAMP
(01) 2014-07-02 10:52:58 Slp: Value specified: 20140702_105236
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: LOGMARKER
(01) 2014-07-02 10:52:58 Slp: Value specified:
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: MEDIASOURCE
(01) 2014-07-02 10:52:58 Slp: Value specified: R:\
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: INSTALLMEDIAPATH
(01) 2014-07-02 10:52:58 Slp: Value specified: R:\x64\setup\
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: ENU
(01) 2014-07-02 10:52:58 Slp: Value specified: True
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: MEDIALAYOUT
(01) 2014-07-02 10:52:58 Slp: Value specified: Full
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: ACTION
(01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: RULES
(01) 2014-07-02 10:52:58 Slp: Value specified: SCCCheckRules
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessMediaChainerConfigFileArguments
(01) 2014-07-02 10:52:58 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: PID
(01) 2014-07-02 10:52:58 Slp: New setting source: ConfigFile; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerConfigFileArguments
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessSlipstreamParameters
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessSlipstreamParameters, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
(01) 2014-07-02 10:52:58 Slp: Action is being skipped due to the following restrictions:
(01) 2014-07-02 10:52:58 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: InitializeRetryHandler
(01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRetryHandler, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ExecuteBootstrapProcessInputSettings
(01) 2014-07-02 10:52:58 Slp: Workflow to execute: 'BOOTSTRAPPROCESSINPUTSETTINGS'
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: StartSqmSession
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2014-07-02 10:52:58 Slp: SQM Service: Sqm does not have active session.
(01) 2014-07-02 10:52:58 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
(01) 2014-07-02 10:52:58 Slp: Completed Action: StartSqmSession, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ValidateChainerSetting
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Compute new PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Read lcid 1033 from CultureInfo
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateChainerSetting, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureCommandLineArguments
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
(01) 2014-07-02 10:52:59 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureConfigFileArguments
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ValidateSettingsAgainstScenario
(01) 2014-07-02 10:52:59 Slp: Scenario: RunRules
(01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: FinalCalculateSettings
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: Completed Action: FinalCalculateSettings, returned True
(01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapProcessInputSettings, returned True
(01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: RunRemoteDiscoveryAction
(01) 2014-07-02 10:52:59 Slp: Running discovery on local machine
(01) 2014-07-02 10:53:03 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction" threw an exception during execution.
(01) 2014-07-02 10:53:03 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException:
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributes()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElement()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElementContent()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlDocument.Load(XmlReader reader)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: --- End of inner exception stack trace ---
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp: --- End of inner exception stack trace ---
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2014-07-02 10:53:03 Slp: Received request to add the following file to Watson reporting: c:\temp\tmpFEEB.tmp
(01) 2014-07-02 10:53:03 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2014-07-02 10:53:03 Slp: Inner exceptions are being indented
(01) 2014-07-02 10:53:03 Slp:
(01) 2014-07-02 10:53:03 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
(01) 2014-07-02 10:53:03 Slp: Message:
(01) 2014-07-02 10:53:03 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp: HResult : 0x84b10001
(01) 2014-07-02 10:53:03 Slp: FacilityCode : 1201 (4b1)
(01) 2014-07-02 10:53:03 Slp: ErrorCode : 1 (0001)
(01) 2014-07-02 10:53:03 Slp: Stack:
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp: Inner exception type: System.Xml.XmlException
(01) 2014-07-02 10:53:03 Slp: Message:
(01) 2014-07-02 10:53:03 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp: HResult : 0x80131940
(01) 2014-07-02 10:53:03 Slp: Stack:
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32&
charCount, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseAttributes()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElement()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlTextReaderImpl.ParseElementContent()
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
(01) 2014-07-02 10:53:03 Slp: at System.Xml.XmlDocument.Load(XmlReader reader)
(01) 2014-07-02 10:53:03 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix,
String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:08 Slp: Watson Bucket 2
Original Parameter Values
(01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
2014@RTM@
(01) 2014-07-02 10:53:08 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : System.Xml.XmlTextReaderImpl.Throw
(01) 2014-07-02 10:53:08 Slp: Parameter 3 :
Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1
(01) 2014-07-02 10:53:08 Slp: Parameter 4 :
System.Xml.XmlException@-2146232000
(01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-07-02 10:53:08 Slp:
Final Parameter Values
(01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
2014@RTM@
(01) 2014-07-02 10:53:08 Slp: Parameter 1 : 0xDBE3EAAC
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : 0x066FCAFD
(01) 2014-07-02 10:53:08 Slp: Parameter 3 :
0xDF039760@1201@1
(01) 2014-07-02 10:53:08 Slp: Parameter 4 : 0x5539C151
(01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:10 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:10 Slp: Watson bucket for exception based failure has been created
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2014-07-02 10:53:10 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\120\EnableErrorReporting=.
(01) 2014-07-02 10:53:10 Slp: WER: Application level consent value '' was mapped to consent status 'WerConsentNotAsked'
(01) 2014-07-02 10:53:12 Slp: WER: Result of the submission:: 'WerReportCancelled'
(01) 2014-07-02 10:53:12 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: Error result: -2068774911
(01) 2014-07-02 10:53:12 Slp: Result facility code: 1201
(01) 2014-07-02 10:53:12 Slp: Result error code: 1
(01) 2014-07-02 10:53:12 Slp: SQM Service: Sqm does not have active session.
/* Don Reynolds */ -
The dreaded: The network address is invalid error - SQL 2014 Cluster on Server 2012 R2
Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-AndrewHi Alberto and Lydia,
The cluster was verified, there are only warnings related to a lack of redundant network paths as the cluster verification doesn't recognize a team of 4 nics are redundant. I updated AD to include the permissions detailed in the link Lydia provided,
still no go.
I'm not sure how to attach the installation logs to this message forum other than as text in the message, so here you go:
Summary:
Overall summary:
Final result: User cancelled
Exit code (Decimal): -2068380094
Exit facility code: 1207
Exit error code: 1602
Exit message: User has cancelled.
Start time: 2015-03-24 09:55:25
End time: 2015-03-24 10:01:04
Requested action: CompleteFailoverCluster
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Cluster properties:
Machine name: SUN-PIE-CS-01
Product Instance Instance ID
Feature Language
Edition Version Clustered Configured
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Database Engine Services
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER SQL Server Replication
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Data Quality Services
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSRS12.MSSQLSERVER Reporting Services - Native
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014
Management Tools - Basic 1033 Standard Edition
12.0.2000.8 No Yes
SQL Server 2014
Management Tools - Complete 1033 Standard Edition 12.0.2000.8
No Yes
SQL Server 2014
Client Tools Connectivity 1033 Standard Edition
12.0.2000.8 No Yes
SQL Server 2014
Client Tools Backwards Compatibility 1033 Standard Edition 12.0.2000.8 No
Yes
SQL Server 2014
Integration Services 1033 Standard Edition
12.0.2000.8 No Yes
Machine name: SUN-PIE-CS-02
Product Instance Instance ID
Feature Language
Edition Version Clustered Configured
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Database Engine Services
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER SQL Server Replication
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Full-Text and Semantic Extractions for Search
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Data Quality Services
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSRS12.MSSQLSERVER Reporting Services - Native
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014
Management Tools - Basic 1033 Standard Edition
12.0.2000.8 No Yes
SQL Server 2014
Management Tools - Complete 1033 Standard Edition 12.0.2000.8
No Yes
SQL Server 2014
Client Tools Connectivity 1033 Standard Edition
12.0.2000.8 No Yes
SQL Server 2014
Client Tools Backwards Compatibility 1033 Standard Edition 12.0.2000.8 No
Yes
SQL Server 2014
Data Quality Client 1033 Standard
Edition 12.0.2000.8 No Yes
SQL Server 2014
Integration Services 1033 Standard Edition
12.0.2000.8 No Yes
Machine Properties:
Machine name: SUN-PIE-CS-01
Machine processor count: 16
OS version: Windows Server 2012
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: Yes
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered Configured
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Database Engine Services
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER SQL Server Replication
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSSQL12.MSSQLSERVER Data Quality Services
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014 MSSQLSERVER MSRS12.MSSQLSERVER Reporting Services - Native
1033 Standard Edition 12.0.2000.8 No Yes
SQL Server 2014
Management Tools - Basic 1033 Standard Edition
12.0.2000.8 No Yes
SQL Server 2014
Management Tools - Complete 1033 Standard Edition 12.0.2000.8
No Yes
SQL Server 2014
Client Tools Connectivity 1033 Standard Edition
12.0.2000.8 No Yes
SQL Server 2014
Client Tools Backwards Compatibility 1033 Standard Edition 12.0.2000.8 No
Yes
SQL Server 2014
Integration Services 1033 Standard Edition
12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: \\sun-server2\data\Software\Microsoft\SQL 2014\x64\setup\
Installation edition: Standard
User Input Settings:
ACTION: CompleteFailoverCluster
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASSERVERMODE: MULTIDIMENSIONAL
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
CONFIGURATIONFILE:
CONFIRMIPDEPENDENCYCHANGE: false
ENU: true
FAILOVERCLUSTERDISKS: <empty>
FAILOVERCLUSTERGROUP: SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES: <empty>
FAILOVERCLUSTERNETWORKNAME: sun-pie-mt-01
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSQLDATADIR: <empty>
INSTANCENAME: MSSQLSERVER
QUIET: false
QUIETSIMPLE: false
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Setup Support Files
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Writer
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Documentation Components
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
Message:
User has cancelled.
HResult : 0x84b70642
FacilityCode : 1207 (4b7)
ErrorCode : 1602 (0642)
Stack:
at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate) -
(BUG??) Team Foundation Server 2013 Update 4 Support for SQL 2014
Scenario: On Windows 2012 R2 x64 I have installed SQL, Reporting Services & AS 2014 (applied all updates through Windows Update), SharePoint 2013 Foundation, and installed Team Foundation Server 2013 RTM (did not configure).
Before configuring TFS, I applied Update 4 to the server (not update 1,2 or 3 directly). When trying to configure I get the following error:
==========================
TF255146: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance you supplied is version 12.0.2254.0.
TF400403: The Report Server instance specified is version 12.0.2254.0, the minimum supported version is 11.0.3000.
TF400070: A required version of a component is not installed on the application tier. You must exit the Team Foundation Administration Console and install a supported version of either SQL Server Analysis Services of the SQL Server Client Tools on the application
tier to ensure that the Analysis Services object model is present for warehouse processing.
====================================
My understanding is that as of Update 2 (or was it 3) that SQL 2014 was supported. However it appears if that particular update is not installed directly it bypasses the check. Can someone verify I am seeing the intended result or is this a bug?Hi Jazzy,
Thanks for your post.
And thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
We have a fresh install of SQL 2014 running on Windows 2012 R2 running in Production.
We tested this extensively first and most of our code ran as fast as SQL 2012 or slightly better.
Pure engine processes such as Backup jobs run about 30% faster.
However, now that we’re in Production for the first day we’re seeing some very sporadic performance.
For example, 90% of our jobs are running just fine. 10% of the jobs are running significantly longer.
Jobs that used to take 7-8 minutes are now running in 40 minutes plus.
Not only is this slowing down our server in general but it’s causing a lot of blocking issues.
We’re convinced this is a SQL 2014 issue and not hardware.
Using iometer we can tell that this server outperforms our old server.
SQL doesn’t always substantiate the numbers we’re seeing from iometer as far as performance compared to our old server.
We’re running on RTM, not Cumulative Update 1.
Our hardware is a beast of a server; DL580 G8, 384 GB ram, only 2 physical hard drives (running the OS/SQL) and the rest are Fusion iO cards.
We have 9 total Fusion cards for the database, log and tempdb.
Our old server is also a very robust server: DL380 G8, 384 GB ram, 48 physical drives and 2 Fusion iO cards for tempdb.
Has anyone else deployed SQL 2014? Has anyone else encountered these sporadic performance issues?
If so, did cumulative update 1 fix the issues?
Separate question: If I put my database in 2012 compatibility mode and do a backup, can SQL 2012 read the SQL 2014 backup?
Thanks in advance,
André
AndréWe applied CU2 last night. Things seem to be better this morning but we're still seeing some differences between SQL 2012. Here are 2 of the biggest issues we're seeing.
1 - views are slow. We have queries that use views that are taking forever. In some cases the view might be a simple "select 10 fields from table" type of views. If we change our query to use the base table instead of the view, the query
finishes very quickly. As an example, a query using the view takes 3 minutes. If we change the query to use the base table instead of the view it finishes in 5 seconds.
2 - inner joins are slow compared to "not exists" or "exists". Back when we migrated from SQL 2000 to 2008 we were told that joins were faster, so we migrated our code to use joins and our code flew. Now we're seeing performance issues on some,
but not all, queries that use joins.
3 - inner joins are not able to see the outside table. For example, this query worked just fine in SQL 2012, and it throws an error in 2014
select
top100
fromcustomers c(nolock)
inner
join(selectcorpnumber,fdate,code
fromdbo.FN_Customers_ParseCodes(c.rcode,c.corpnumber,c.fdate))r
onr.corpnumber=c.corpnumber
where
c.importtimestamp='2014-06-30
15:37:17.347'
and
c.customerid='123'
The error it throws is:
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.codes" could
notbe bound.
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.corpnumber" could
notbe bound.
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.fdate" could
notbe bound.
André -
Best practice configuration for SQL 2014 to achieve HA when hosted on Hyper-V 2012R2 cluster
Hi,
I've had a hunt around but so far I've not found a conclusive answer to my question. I am currently moving from a SQL 2008R2 (physical tin) failover cluster to a virtual environment build on Hyper-V 2012R2. I am building everything with SQL 2014
SP1.
I want to achieve the same level of high availability that I currently have and at the same time make sure that I can replicate (DR) data offsite (Azure) in the future. I have two options with SQL which are clustered instance (basically the same as
I have now) or AlwaysOn Availability Groups for database level HA.
I am unsure which is the best method to use when the SQL nodes are highly available guests on Hyper-V, trying to imagine how the guests will all move around in the case of a host server failure is a bit mind boggling to say the least.
I am leaning towards a instance failover but I would appreciate any input/advice etc.
Thanks
RobHi Rob,
To start with I will not be installing SQL Server 2014 with SP1, as SP1 has bugs and Microsoft has disabled its download. See reference: http://www.eweek.com/database/microsoft-halts-sql-server-2014-sp1-downloads.html
With regards, I would go for AlwaysOn Availability Groups configuration, because it has several benefits:
You will get same amount of high availability you normally get with native cluster configuration, if you use AlwaysOn configuration. However, AlwaysOn configuration provides more granular high availability, and fail-over are invisible to the application,
if you using Availability Group listener to connect to server.
You can offload read-only workloads to secondary replica.
You can perform transaction log backups on secondary replica.
Reduce production downtime during patching or other planned work on the server.
So in short, you should use AlwaysOn configuration.
Regards,
Basit A. Farooq (MSC Computing, MCITP SQL Server 2005 & 2008, MCDBA SQL Server 2000)
http://basitaalishan.com
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Can't update SQL 2014 DB during web publish from Visual Studio 2013
According to Visual Studio 2013 I have "SQL Server Data Tool 12.0.40706.0" installed, which should allow me to update a SQL 2014 database but when I try to publish my web application I get the error: "Web deployment task failed. (Could not
generatedeployment script. Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database
platform service. Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service isloaded, or you must provide the full type name of a valid database platform
service. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.)" I can update the database fine if I go into the package managment console and run -UPDATE-DATABASE but I don't want to have to go into myweb.config, update it to point to the production
database, run the update command, and then change my web.config back everytime I try to update my database. What do I have to do to getthis working? I had no problems when I was on an Azure DB.Actually problem seems to be related when web publish to remote server. I tried local web publish to sql2014 db and it works.
For remote server web publish works to sql 2012 express db but when try with sql 2014 express db on same server get bellow error.
Error message "The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider
is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service."
Any ideea what may be causing it? I have installed the sql server 2014 express with advanced services x86, exact same version as on my local machine, and also restarted server after install. Need install/configure anything else on server like SSDT 2014 to
make this work?
Cheers! -
Read Only SQL 2012 Replica DB on a SQL 2014 box
I have set up a data availability group between two SQl 2012 boxes on my windows cluster. they are failing over fine and synchronized as expected.
I want to add an additional read only replica on my SQL 2014 box which is also included in my windows cluster (so i can use this replica for reporting with 2014 In Memory features) the fail-over is still between the two 2012 boxes.
Problem is even tho i have set this replica to read only - yes, the database is always in - Synchronized / In recovery - so i can never connect to it.
Is this scenario possible?Thanks David
Yes the whole point of this was to get access to real time data from within 2014, but the more i think about it the linked server still would not give me what i want as I belive the in memory is defined at table creation level.
With the tables being created in 2012 that would be a problem.
Thanks for the info mate. -
SQL 2014 cluster installation on mounting point disks error: Updating permission setting for file
Dear all,
I am attempting to install SQL 2014 fail over cluster under a physical windows 2012 R2 server which have mounting point disks.
At the finish of setup I get the following error message.
Could you please help me on this?
Thanks
The following error has occurred:
Updating permission setting for file 'E:\Sysdata!System Volume Information\.....................................' failed. The file permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: go.microsoft.com/fwlink
I am using an administrator account which have all security rights (cheched on secpol.msc mmc) needed for installation.Hi Marco_Ben_IT,
Do not install SQL Server to the root directory of a mount point, setup fails when the root of a mounted volume is chosen for the data file directory, we must always specify
a subdirectory for all files. This has to do with how permissions are granted. If you must put files in the root of the mount point you must manually manage the ACLs/permissions. We need to create a subfolder under the root of the mount point, and install
there.
More related information:
Using Mount Points with SQL Server
http://blogs.msdn.com/b/cindygross/archive/2011/07/05/using-mount-points-with-sql-server.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
The following MSDN reference
http://msdn.microsoft.com/en-us/library/ms143393%28v=sql.120%29.aspx says
SQL Server 2014 supports upgrade from the following versions of SQL Server:
SQL Server 2008 SP3 or later
SQL Server 2008 R2 SP2 or later
SQL Server 2012 SP1 or later
However, in our testing, it is possible to upgrade from SQL 2005 SP4 to SQL 2014. There are no messages or detection errors when doing so. Will the final release of SQL 2014 support upgrading from SQL 2005 directly or will there be detection
added to the installation to prevent it?Hello,
SQL Server 2005 won’t be supported as a valid upgrade path when SQL Server 2014 RTM is released as the article you posted states. The behavior you are seeing with the CTP version of SQL Server 2014 maybe is part due to some binaries of the SQL Server 2012
version still in use on the CTP version.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL 2014 - Group Membership for sysadmin permissions not working
I am using SQL 2014 on Windows Server 2012 R2 and am running into a permission issue. During the install I specified the local server's Administrators group as well as my specific domain account to have sysadmin privileges.
The issue is that accounts that are a member of the local server's administrators group can't even login to SQL Server Management Studio unless they are specifically granted permissions for their account (my domain account works fine as it has a specific
credential in SQL).
The log just gives the following error:
Login failed for user 'domainname\username'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
Error: 18456, Severity: 14, State: 11.
I haven't had this issue in previous versions. Is there something that must be done differently in 2014 to grant permissions to groups?Hi, something like
this?
Bye
Questo post è fornito "così com'è". Non conferisce garanzie o diritti di alcun tipo. Ricorda di usare la funzione "segna come risposta" per i post che ti hanno aiutato a risolvere il problema e "deseleziona come risposta"
quando le risposte segnate non sono effettivamente utili. Questo è particolarmente utile per altri utenti che leggono il thread, alla ricerca di soluzioni a problemi similari. ENG: This posting is provided "AS IS" with no warranties, and confers
no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location
Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
LpdOK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd
Maybe you are looking for
-
Printer only prints half the words, HP6200
Printer only prints half the text. In other words, the text is shown only half the size.
-
Automator Folder Actions - Use filename as subject in email
I regularly email .pdf atttachments to my head office. These are hand-written sales orders which are scanned in. The scanner software gives each file a sequential filename (eg. OrderNo_110612). I have set up a Folder Action in Automator to create a n
-
How can I measure my daily usage of my macbook
Hey, I would like to know how many hours I use my macbook on a daily basis. Is there any application which just starts a timer as soon as the mac boots and then provides an overview of the total time, average usage time per day etc.? Thanks for your
-
Often I get messages that say 'turn off Mozilla Firefox' in order for software to update. ie. Adobe Flash Player. But I don't know how to turn Mozilla Firefox.. off so I can update. Heeeellllp please?
-
Hi, How can I convert float to Float? thanks andrew