SQL 2014 Exp Wont Install Win 8.1
Hello All,
Im really struggling to install SQL 2014 express on my windows 8.1 SL pc. x64
i installed SQL 2008 first but when i tried to install the studio management, it refused to work.
so i redownloaded the latest setups. ive tried both 32bit and 64bit
SQLEXPR_x86_ENU.exe 172mb
SQLManagementStudio_x86_ENU.exe 689mb
It just stays on the one screen after the landing page. ive left my pc for 6 to 8 hours...
ive tried this more than once... and no luck...
Note i have cleaned the registry and directorys each time.
Logs------------
http://1drv.ms/1pJFzTq
http://1drv.ms/1pJFAXC
I am little confused are you trying to install SQL server 2008 express or SQL server 2014 express.
You should first refer to
Hardware and Software requirements for installing SQL server 2014
You should also read Installing SQL server On windows 8
Finally when you are ready download
SQL server 2014 express
Edit: reg logs you posted it seems your machine where you are installing SQL server does not have internet connection. Internet connection is required for installation of SQL server 2014 express read Hardware and software requirements.
06) 2014-05-30 03:21:36 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: SQL Server Setup was not able to scan for product updates within 5 minutes. This can happen when there are Internet or network issues. ---> Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSelectServerTimeoutException: SQL Server Setup was not able to scan for product updates within 5 minutes. This can happen when there are Internet or network issues.
Please revert if any Issue.
Hope this helps
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
Similar Messages
-
I am unable to see following SQL Server Analysis Services in central admin services after the SQL 2014 power pivot installations
RaviHi Ravi,
Per my knowledge, there is no Analysis Service in SharePoint.
After running the SQL 2014 setup to install PowerPivot for SharePoint, you need to open the PowerPivot for SharePoint 2013 Configuration tool in Central Admin Server and configure PowerPivot for SharePoint.
After that, you will see new Service Application called "Default PowerPivot Service Application" in Central Administration.
If you have other WFE servers, then you need to install the PowerPivot Add-In on all the other servers in the SharePoint farm.
More references:
http://sridharbabuk.blogspot.jp/2013/02/installing-configuring-analysis-service.html
http://msdn.microsoft.com/en-us/library/jj219067.aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support -
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) -
Trying to install a new version of SQL 2014 Std 64 or x86. Installing on Windows 8.1Pro 64bit machine.
I get:
"TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging.
Error code 0x858C0017."
I looked at the summary log and that is the only error.
I made sure there were no other instances of SQL on this machine. Uninstalled all VS2013 and sql instances just in case. IF there is somewhere to check if a previous version or license is causing the issue, i would be glad to check.
Any help would be appreciated.Hi,
Please read this thread with similar issue
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bdd94577-515c-49fa-be44-008eacece057/installing-sql-server-2012-on-a-new-vm-error-code-0x858c0017?forum=sqlsetupandupgrade
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
Hi,
how to find using SCCM SQL query, application deployed on win 7 machines with SCCM 2012 server or user/technician installed manually. Please let me know.Thanks, is it not possible via any script also?
Like Torsten said, how can you tell the difference between CM12 installed applications and locally installed? Once you can answer that, then you can write report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ -
SSDT does not load after a fresh install of SQL 2014
Greetings!
I just installed SQL Server 2014. Interestingly, there is no Feature check for SQL Server Data Tools. After installation (installed SQL 2014 on Windows Server 2012 R2) I try to launch DEVENV.exe and get the error, "Invalid license data. Reinstall is
required."
How do I properly install and configure SSDT with the BI templates?
Thank you.
---------------- GeorgeS, aka "SQLPadawan"Hi George and Kevin,
There is a similar tread on
Connect which refers to the download location of
Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013. Unfortunately the download is not yet available.
Best regards,
Arjen Krap -
How to install sql server 2012 using the license of sql 2014
Hello,
We want to install sql server 2012 on a server because of an application that can not work with sql server 2014.
We have a license for sql server 2014. The license is not visible for sql 2014 in our licenses because it is now included in the installation package. We also can not get a license key for SQL 2012 server now.
How can we get a valid sql server 2012 license key?
Thanks,
Gr. Peter.Hello Peter,
This is a community forum for technical questions & issues.
For question regarding pricing / licensing please contact a Microsoft sales partner or licensing expert.
Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist.
Regards.
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog -
Hi guys.
I downloaded the latest iTunes and it wont install.
Im running Win 7 Ultimate 64bit. When i downloaded the 64bit version i got a msg saying that its not a valid win32 app????
I then downloaded it again with the same issue.
When i installed a earlier version that i used on my 32bit system it worked but i cant rip my cd's.
Ayn ideas??Hello;
I also had trouble installing iTunes on Windows 7, but 32 bit.
It looks like maybe you are trying to install iTunes 64 bit on 32 bit machine or version of Windows, as it is looking for a valid Win32 app?
You might want to verify the version of Windows you are running, and whether your machine is correctly configured for 64 bit.
Here is an account of my trouble, and my suggestions for installing iTunes on any Windows 7 machine:
First, I found that the setup would freeze when it was almost done. The last screen, the progress bar would freeze about 3/4 of the way through.
I found that, after stopping the process in Task Manager, that iTunes was installed, and ran properly. So, it was only the install program that had frozen, after it had completely installed iTunes.
I did run the setup in compatibility mode for Vista SP2, and ticked the run as admin box.
I think that there are issues with iTunes (32 and 64 bit) on Windows 7 (32 and 64 bit) but Apple doesn't seem to want to address this. I have yet to see an acknowledgment from Apple on this problem.
What I recommend, is this:
Before attempting to install iTunes, create a system image (not just a restore point) so that you can restore your system if and when iTunes messes up your system.
Make sure you are logged into your computer as admin or a user that has admin privs.
Run the iTunes setup program with the "run this program as administrator" box ticked.
Try running with compatibility for Vista SP2. -
K8n neo2 plat wont let me install win 2000 pro
Help! HAve neo2 mb-2 10k rpm 36 gig harddrives. I am trying to set it up as raid 0. I hit f6 to install raid drivers and it tries to install win 2000 but gives me a message of "the file nvraid.sys could not be found." then it says hit control alt del to restart.
install vista from within XP but i'm not sure whether you will succeed since you will have to set your sata2 drive in the bios as the primary drive that contains the OS. beleive me the only way you will get to install the raid drivers for nvraid controller is if you start the setup from within xp
-
Install win 8.1 error looking for disk
I have a new Mac Mini w/ Mavericks OS. I have been trying to install Win 8.1 for days. I had a keyboard on order, finally came today to allow me to Recover the Mac from a failed Win 8.1 install. I have read hundreds of conversations on this topic. And to air one question constantly asked, 'Why! Why is it that there are dozens of different ways people are having to use to install one program? Why?!?'
I am able to get to the page in Windows setup where I am to select the drive called BOOTCAMP.
I select the drive
I then FORMAT the drive
Then I am told that drive - or any installation for Windows drive - is NOT found or available.
I've gotten to this screen a dozen times now.
I have arrived there by two methods 1) following the 'book' on Win 8.1 installation via BOOTCAMP and 2) Once here I shut the machine down and reboot with CTRL-key at restart -> select the WINDOWS drive from those available -> then follow the Windows install panels. Which, every time leads me right back to this page.
A note about this page. Every online tutorial, including the one on the Windows site and here on Apple forums, shows a DIFFERENT layout of the page. The tutorials show a page with a link to click for Advanced settings. My window just shows those Advanced settings. I don't see how this makes the process work or not, but that's a peculiarity of my setup woes compared to the instructions that exist.
NOW .. HOW in the name of all that is sensible!! -- do I get from the page where I select the partition I need to install Win 8.1 on..?
Again ..PLEASE!!! DO NOT retroute me through all the old settings everyone has been hashing about since September 2013. I need to know What Works NOW - January 2014- to get Windows 8.1, installed and working on my Mac Mini running latest version of Mavericks.
Thank you ... I HOPE!Windows 8.1 is not yet officially supported in Bootcamp. There is no way to know when it will be supported.
Having said that some systems will install it and it runs fine, though these systems appear to be few and far between.
The only advice I can give is to try some of the workarounds available on various sites or wait until it is supported by Bootcamp. -
Error trying to install Win 8.1 x64 Enterprise
Brand new iMac 27", fully loaded, 1 TB SSD, 32 GB RAM, running Mavericks 10.9.3. Trying to install Win 8.1 x64 Enterprise (from MSDN).
Downloaded the ISO file and license and used Boot Camp to install the files and Apple Support files to a 16 GB USB 3.0 thumbdrive.
Used Boot Camp to repartition the 1 TB SSD to set a Windows partion of 256 GB, then the computer rebooted into Windows Setup.
Came to the drives listing, selected the BOOTCAMP parition (Drive 0, Partition 4, 239 GB) and formated it, then clicked on NEXT.
Thought for a while, then it came up with this error message: "We couldn't install Windows in the location you chose. Please check your media drive. Here's more info about what happened: 0x80300002"
Got some hits on Google about issues with VISTA, or with Intel processors, but, nothing specific.
Checked USB thumb drive with Norton, no issues, CHKDSK, no issues.
Have repeated the entire process twice, including restoring the patition and recreating it, and rebuilding the USB Thumbdrive.
Any ideas on what to do?
Thanks!More sadness. I finally started getting the BSOD as soon as Windows booted, and, I could not restart or shutdown the computer...had to power off. That, after a few times, corrupted my BootCamp partition. I messed around with trying to fix, but, no joy.
Redid the partition, checked all drives for errors (fixed permissions on the Mac HD...LOT of errors), and created a new partition.
Used USB 2.0 (VERY SLOW) thumbdrive and had all external drives removed, and installed Win 8.1 Pro, not Enterprise this time.
Got it back up, patched it, configured it, put Norton 360 on it (have on all my computers and iOS devices) shut down, and hooked up the external drives. Booted up and...got the BSOD.
This time I had Windows Debugger loaded, and after the BSOD could reboot, go back intoWindows, and Debug.
Culprit seems to be Norton--in particular a Norton Storage driver. Will be contacting vendor to fix.
Here's dump:
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
System Uptime: 0 days 0:03:09.864
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
TRAP_FRAME: ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
r8=0000000000005aa0 r9=00000000000007ff r10=ffffd00066cc8000
r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x682b:
fffff802`0f9e8cdb cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: ffffd0002852d338 -- (.exr 0xffffd0002852d338)
ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff8020f9ddae9 to fffff8020f9d1fa0
STACK_TEXT:
ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS64+71be6
fffff800`1d7a0be6 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: SYMDS64+71be6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS64
IMAGE_NAME: SYMDS64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 51f84c44
FAILURE_BUCKET_ID: 0x139_3_SYMDS64+71be6
BUCKET_ID: 0x139_3_SYMDS64+71be6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_symds64+71be6
FAILURE_ID_HASH: {bf9be68b-5f04-08d4-3152-3d420dc362f6}
Followup: MachineOwner -
(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é -
Visual Studio prevents SQL 2008 Express installation on win 8.1
I wanted to install SQL Express 2008 on my Win 8.1 desktop. It gives an error indicating that I should install Visual Studio 2008 SP1 first. I tried, but SP1 installation fails. I also tried to remove VS2008 completely but I still get the same fail when
installing SQL 2008 Express.
Now I cannot even install SQL Manager 2008, to manage database on SQL server.Hello,
You should install SQL Server 2008 Express with SP3 included to make it compatible with Windows 8.1. Please try the following download:
http://www.microsoft.com/en-us/download/details.aspx?id=27597
For more information, please read the following article:
http://support.microsoft.com/kb/2681562
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
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.
Maybe you are looking for
-
Why is my page set up drop down different from your illustration in help for printing background
''duplicate - https://support.mozilla.com/en-US/questions/830795'' The page set up drop down menu looks nothing like the illustration in help. It does not include a box to check for "print background. How do I print background
-
Pre10 wont start disc/folder burn. Tried everything!
Hi there, I recently bought a new computer and I can not get Pre7 or Pre10 to burn a folder or a disc. I have browsed these forums for hours and hours looking for a solution but no success. I initially loaded Pre7 when i got the computer but when it
-
HT1711 Downloaded an album today, it will not play.what can I do?
Help with an album that will not play please
-
Help! All of my photos are "missing".
I currently have Lightroom 3. I was working on my blog earlier, and all of my photos were there. Once I finished w/ my blog, I got back into lightroom. One by one, the little question mark appeared in each photo of my film strip. I checked each of th
-
Hi, I have Oracle8i and tried to work on Export/import/Load. But it asks for Management Servers. Can anybody tell what is Oracle Management Server and how create and use it ? Thanks in advance. Rajesh null