Quantcast
Channel: SQL Server Setup & Upgrade Forum
Viewing all 7701 articles
Browse latest View live

SQL Server 2008 R2 Edition upgrade

$
0
0

We have puchased SQL Server 2008 R2 Enterprise and installed few months ago, but now it stop working and expaired. I have download from volume license site and the media included product key, now the question why it is expaied since it was purchased volume licensed and second I have downloaded again and install service pack 1 before run edition upgrade and after sucessfully complete upgrade still getting message expaired.

Can someone help what happend?

Thanks

 

how to install SQL server on Windows server 2008 (domain controller problem)

$
0
0
I need to install SQL server on my Windows Server 2008 virtual machine. The problem is that a warning is appearing that I shouldn't install SQL server on my domain controller. OK. So I am trying to create another domain/server. In fact I am trying to create a virtual machine inside the Windows Server so I can install SQL server on it. But I am having trouble to do so. I have tried to install Hyper-V but it did not install successfully and I think because my processor does not support for hardware assisted virtualization.

So my question is, How can I create another server to install SQL server for my Windows Server 2008 virtual machine?

sql server 2008 r2 with databases in compatibilty 2000(80), can I use partitions?

$
0
0

Hello

I have old apllication  that need compatibilty 2000(80). and I need  to use partionbing on the sams DB's.

Is it a problem?

Using symbolic links for SQL File locations‏

$
0
0

I believe I heard someone in a presentation mention this as a possibility, but I can't find any articles on the subject and want to make sure it isn't unsafe (Am thinking of using it for all of our servers, as well as for some form of article too :)

We have servers with lots of different configurations (not to mention our development boxes/websites), and if we could always put log files in c:\mssql\logs and that would actually be on either the well built log drive on h, i, k, or whatever the server has been configured for, or locally on the C or D drive, it would be excellent and make moving databases around very easy.

Anyone have any advice?

  

Louis

Without good requirements, my advice is only guesses. Please don't hold it against me if my answer answers my interpretation of your questions.

Warning message during cluster setup - The current node is at patch level [11.1.3000.0], which is lower than that of active node : patch level [11.1.3128.0]

$
0
0

Hello,

I have installed a two node failover cluster and I got this message when adding the second node

The current node SERVER01 is at patch level [11.1.3000.0], which is lower than that of active node SERVER02: patch level [11.1.3128.0]. After completing setup, you must download and apply the latest SQL Server 2012 service pack and/or patch and bring all nodes to the same version and patch level.

Do you know where to download patch 11.1.3128 ? I see this is not a normal CU

Regards


Javier Villegas | @javier_villhttp://sql-javier-villegas.blogspot.com/

Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

SQL LocalDb 2012 installation

$
0
0
 Hi,

Is it possible to install SQL LocalDb 2012 on drive other than C:\ during installation? The GUI does not provide the option but are there any command line options available to install on other drive?

Follow up: If not possible during installation, is it possible to move system Databases like master, model to a different location?

For my needs, due to regulations, C:\ drive is protected and cannot write data to C.

Thanks

Pare

SQL Server 2012 - Database Engine Services Failed

$
0
0

Hi all,

I can't install the SQL Server 2012 Express version with tools downloaded from http://www.microsoft.com/en-us/sqlserver/editions/2012-editions/express.aspx

I'm getting the following error: 

Error installing SQL Server Database Engine Services Instance Features
Could not find the Database Engine startup handle.
Error code: 0x851A0019

I'm trying to install a new stand-alone version with a default instance but always getting this error. From the features I'm installing the database engine services (not the replication), all the tools, only the basic management toolds and the SQL Client connectivity SDK.

Further in the installation I'm choosing the Windows authentication and in the list of SQL administrators I've already tried to install as current user but also as System. Both with the same error result.

The Summary File can be found here: http://d.pr/f/didH

Note: Visual studio is not installed.

Thanks in advance

Repair SQL Server 2008 R2 SP2

$
0
0

Hi everyone,

  Following an upgrade to SQL Server 2012 which didn't succeed, someone recommended that I repair my actual SQL Server 2008 R2 SP2 setup.  The actual setup I have, which btw is running without any problem, is the following:

  • SQL Server 2008 R2 SP2 CU1 Express Edition with advanced services  (Reporting Services is installed and active)
  • Visual Studio 2010 SP1 Professionnal Edition
  • Visual Studio 2008 SP1 Express Edition
  • Windows VISTA SP2 Ultimate Edition

  My request is very simple.  Before repairing a SQL setup:

  • Do I need to stop any services?
  • Any other thing I should stop, uninstall or else?
  • Do I launch the repair from the "Control Panel - Install/uninstall program" menu or can I just run the "SQL Server 2008 R2 SP2" setup file I just downloaded from the .NET.  I prefer asking because I thought that running this setup file under administrative rights could help avoiding privilege problems or else?

  Hope to hear from someone,

Stéphane




SQL Server 2012 Update installation fails

$
0
0

Windows 7 64 bit - I had SQL Server 2008 and SQL Server 2008 R2.  I uninstalled SS 2008 and tried to uninstall SS 2008 R2.  The SS2008 uninstalled fine.  The R2 said it uninstalled, but was still there.  I loaded a new version of SQL Server 2012.  Then I manually uninstalled each piece of the SS 2008 R2 except R2 Setup and one other piece because it said that 2012 used pieces of it.  Now I have a Microsoft update to SS 2012 and the update fails bc of something to do with the 2008 R2. Security Update for SQL Server 2012 RTM (KB2716442).  Installation status: Failed  Error details: Code 84B20001
I tried the Fix Windows Update, which said it worked, but the update still fails.  What should I do?  Thank you for your help.  Nancy

SQL Server 2012 setup hangs during wizard

$
0
0

I'm trying to re-install SQL Server 2012 Enterprise on a laptop that had an expired Trial edition.  Every step of this process is painfully slow, taking 5-10 minutes or more to launch and move between most steps in the Setup wizard.  In my Task Manager I can see ScenarioEngine.exe thrashing 100% of 1 core during that time.

OK its not a powerful laptop but it is running Windows 7, Office 2013, SQL 2008 R2 OK. All the SQL 2008 R2 services are stopped BTW.

I'm puzzled what that process could be working on e.g. while moving from the Feature Selection step to the Installation Rules step?

And when it hangs it really hangs - I cant even move the window around it is so stuck.

I'm starting Setup.exe as Administrator, from a C: drive folder.

Does anyone know how to avoid this issue?

sql server install by command line

$
0
0

I am using following command line to install sql server 2008 r2 but its not installing.Also i am not getting any error or log in summary.txt

"D:\SQLEXPR32_x86_ENU (1).exe" /q /ACTION= Install /FEATURES=SQL /INSTANCENAME=nvt /SECURITYMODE=SQL /sapwd=abc /IACCEPTSQLSERVERLICENSETERMS

SQL server memory issue

$
0
0

Hi, I need help regarding SQL server memory we faced SQL server memory issue:

In Our Production server side we had SQL Server 2005 & it used 30 GB Memory after upgrade SQL Server 2008 R2 4-5 days total memory used by SQL 8-10 GB but after that again used 30 GB. Please let me know what I should do.

SQL Instance install

$
0
0

I ran an install of a new instance for SQL 2008 R2, using media that was located on our server.  Turns out this must have been the original ISO ver 10.50.1600.1 and the SQL Cluster was at SP1 level.   This of course made the 2nd server in the cluster come to a screeching halt and rightly so.  Had to failover to the other server in the cluster and everything works. (Go figure) In reviewing the config.ini I confirmed my fear that in fact a slipstreamed version of an install was used for another instance install.  I was not aware that the slipstreamed version existed and assumed the local install met those requirements.  (Insert vivid language here.)

Question is now, is it possible to run another instance install with the same params. and have it update the needed file thereby correcting the issue on the second server or will correcting this be more difficult?

Unable to install Management Tools, SQL Server has stopped working

$
0
0

I'm having problems installing SQL Server 2008 Management Studio R2 on my Windows 7 x64 machine. The install gives me this summary:

Overall summary:
 Final result:         SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
 Exit code (Decimal):      -2068052413
 Exit facility code:      1212
 Exit error code:        1603
 Exit message:         SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
 Start time:          2011-08-17 13:28:52
 End time:           2011-08-17 13:35:27
 Requested action:       Install
 Log with failure:       C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_132659\trin_aide_Cpu32_1.log
 Exception help link:      http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1

Machine Properties:
 Machine name:         CHAZ-PC
 Machine processor count:    2
 OS version:          Windows 7
 OS service pack:        Service Pack 1
 OS region:           United States
 OS language:          English (United States)
 OS architecture:        x64
 Process architecture:     64 Bit
 OS clustered:         No

Product features discovered:
 Product       Instance       Instance ID          Feature                 Language       Edition       Version     Clustered 

Package properties:
 Description:          SQL Server Database Services 2008 R2
 ProductName:          SQL Server 2008 R2
 Type:             RTM
 Version:            10
 SPLevel:            0
 Installation location:     c:\499fe55bf116f41419ca\x64\setup\
 Installation edition:     EXPRESS_ADVANCED

User Input Settings:
 ACTION:            Install
 ADDCURRENTUSERASSQLADMIN:   True
 AGTSVCACCOUNT:         <empty>
 AGTSVCPASSWORD:        *****
 AGTSVCSTARTUPTYPE:       Manual
 ASBACKUPDIR:          Backup
 ASCOLLATION:          Latin1_General_CI_AS
 ASCONFIGDIR:          Config
 ASDATADIR:           Data
 ASDOMAINGROUP:         <empty>
 ASLOGDIR:           Log
 ASPROVIDERMSOLAP:       1
 ASSVCACCOUNT:         <empty>
 ASSVCPASSWORD:         *****
 ASSVCSTARTUPTYPE:       Automatic
 ASSYSADMINACCOUNTS:      <empty>
 ASTEMPDIR:           Temp
 BROWSERSVCSTARTUPTYPE:     Disabled
 CONFIGURATIONFILE:       
 CUSOURCE:           
 ENABLERANU:          False
 ENU:              True
 ERRORREPORTING:        True
 FARMACCOUNT:          <empty>
 FARMADMINPORT:         0
 FARMPASSWORD:         *****
 FEATURES:           SSMS
 FILESTREAMLEVEL:        0
 FILESTREAMSHARENAME:      <empty>
 FTSVCACCOUNT:         <empty>
 FTSVCPASSWORD:         *****
 HELP:             False
 IACCEPTSQLSERVERLICENSETERMS: False
 INDICATEPROGRESS:       False
 INSTALLSHAREDDIR:       C:\Program Files\Microsoft SQL Server\
 INSTALLSHAREDWOWDIR:      C:\Program Files (x86)\Microsoft SQL Server\
 INSTALLSQLDATADIR:       <empty>
 INSTANCEDIR:          C:\Program Files\Microsoft SQL Server\
 INSTANCEID:          <empty>
 INSTANCENAME:         <empty>
 ISSVCACCOUNT:         NT AUTHORITY\NetworkService
 ISSVCPASSWORD:         *****
 ISSVCSTARTUPTYPE:       Automatic
 NPENABLED:           0
 PASSPHRASE:          *****
 PCUSOURCE:           
 PID:              *****
 QUIET:             False
 QUIETSIMPLE:          False
 ROLE:             AllFeatures_WithDefaults
 RSINSTALLMODE:         FilesOnlyMode
 RSSVCACCOUNT:         NT AUTHORITY\NETWORK SERVICE
 RSSVCPASSWORD:         *****
 RSSVCSTARTUPTYPE:       Automatic
 SAPWD:             *****
 SECURITYMODE:         <empty>
 SQLBACKUPDIR:         <empty>
 SQLCOLLATION:         SQL_Latin1_General_CP1_CI_AS
 SQLSVCACCOUNT:         NT AUTHORITY\NETWORK SERVICE
 SQLSVCPASSWORD:        *****
 SQLSVCSTARTUPTYPE:       Automatic
 SQLSYSADMINACCOUNTS:      <empty>
 SQLTEMPDBDIR:         <empty>
 SQLTEMPDBLOGDIR:        <empty>
 SQLUSERDBDIR:         <empty>
 SQLUSERDBLOGDIR:        <empty>
 SQMREPORTING:         True
 TCPENABLED:          0
 UIMODE:            AutoAdvance
 X86:              False

 Configuration file:      C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_132659\ConfigurationFile.ini

Detailed results:
 Feature:            Management Tools - Basic
 Status:            Failed: see logs for details
 MSI status:          Failed: see details below
 MSI error code:        0x1603
 MSI log file location:     C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_132659\trin_aide_Cpu32_1.log
 MSI error description:     
 Configuration status:     Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:        C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110817_132659\SystemConfigurationCheck_Report.htm

It says I already have a native client installed but I practically uninstalled everything that had to do with sql. Is there something I think to change to force the install to continue?

Unable to Install SQL2008R2 Developer on Windows 7 Professional SP1 - Just purchased

$
0
0

Hello,

  After hours or installing, uninstalling, readnig and following endless MS posts in support websites and knowledgebase articles, uninstalling other componenets ercommended by those processes, reinstalling updates, and then still failing to install SQL Server Developer 2008 R2 - I'm desparate for help.

  I have a corporate image WIndows 7 Professional Machine that is about 45 days new.  I have tried on several occassions to install the following (uninstall and reinstalls inbetween).

    SQL Server 2005 Express

    SQL Server 2008 Express

    SQL Server 2012 Express

     SQL Developer 2008

     SQL Developer 2008 R2.

  I have been unssucessful with all but the SQL2012 Express - always with the same symptom the Setup produces the "SQL Server 2008 R2 Setup has stopped working" - and then the main setup layout reports that all the "tools" I tried to install "Failed", but connectivity always seems to succeed.  The only time this was EVER successful was installing the SQL2012 Express with SP1 - which does not provide the tools I need (BIDS etc to connect to our SQL2008 servers).

    Integration Services - Failed

    Client Tools Connectivity - Success

    Management Tools - Complete - Failed

   Client Tools SDK - Success

   Client Tools Backward Compatibility - Success

   Business Intelligence Development Studio - Failed

   Management Tools - Basic - Failed

   Microsoft Sync Framework - Success.

  After much searching I landed at this article: <link removed - due to account verification requirement>

 which seemed to indicate there was some type of incompatibility between SQL2008/SQL2008R2 and Windows 7 that could be addressed by "slipstreaming" the SP1 (I picked SP2 since I assume its newer and comprehensive).  After hours of copying the files off the media - downloading and extracting all the SP files, copying the content over as recommended and running the command recommended to "slipstream" - end result was the same.

  I'm at my wits end - a $50 software package shouldn't require hours of problems to install on a reasonably current operating system - nor should it require a PAID SUPPORT CHARGE to contact Microsoft to work out the issues in the product installation (thats purely a customer PoV ofc).

   Any guidance that doesn't involve "please uninstall using the recommended procedure" and "reinstall using the same process you used 10 times previous" would be very much appreciated.

  I'm hoping (after trying to follow this article that describes analyzing the logs: <link removed - due to account verification requirement>  ) that this is something the logs will really help rootcause.

  First (I believe) the setup.exe (or some .msi) is CRASHING - since it is creating Dr Watson logs.

  <PC NAME>_20130201_100448_Watson.txt contains:

Watson bucket data:
  Bucket param 1: 10.50.4000.0
  Bucket param 2: 9.0.35191
  Bucket param 3: trin_aide.msi
  Bucket param 4: 0x162A16FE
  Bucket param 5: 0x1603
  Bucket param 6: Install_trin_aide
  Bucket param 7:
  Bucket param 8:
  Bucket param 9:
  Bucket param 10:

The MS article recommends workign thru the Summary, Detail and eventually the msi-specific logs.

Summary:  Summary_<PC NAME>_20130201_100448   contains:

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Exit code (Decimal):           -2068052413
  Exit facility code:            1212
  Exit error code:               1603
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2013-02-01 10:05:58
  End time:                      2013-02-01 10:15:16
  Requested action:              Install
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130201_100448\trin_aide_Cpu32_1.log
  Exception help link:    <link removed - due to account verification requirement>

If I read correctly, I run off to check into the trin_aide_Cpu32_1.log  (17 MB) - feels like needle_in_haystack mode atm:

(searching for "error", "exception" (wasnt useful - tons of matches) and "Watson"):

MSI (s) (44:10) [10:11:51:256]: Note: 1: 1708
MSI (s) (44:10) [10:11:51:256]: Product: Microsoft Visual Studio Tools for Applications 2.0 - ENU -- Installation failed.

MSI (s) (44:10) [10:11:51:256]: Windows Installer installed the product. Product Name: Microsoft Visual Studio Tools for Applications 2.0 - ENU. Product Version: 9.0.35191. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

to be honest I'm not sure what to provide from the 17MB logfile.

Point is I'm jsut trying to install the tools - not even the SQL Engines.  Help !!

 


I'm unable to login windows authentication in sql2K5

$
0
0

I installed sql 2k5 with windows mode only.When i'm installing i selected windows mode rather than mixed mode.

After i finished every thing, i tried to login but i'm unable to do it.It showing error.

Is it not acceptable to install sql2k5 with this mode.If i did it with mixed then we can go through by 'sa'

but what to do in this case!

Microsoft Visual Studio Tools for Applications 2.0 - ENU -- Installation failed.

$
0
0

Trying to install Microsoft® SQL Server® 2008 R2 Service Pack 1

The management studio part fails

I downloaded the installation from http://www.microsoft.com/en-us/download/details.aspx?id=26727, 

I also tried the web installation.

The Management studio fails with a crash. See crash is shown in this screenshot below http://i.imgur.com/bpN1n8d.png

The installation log is shown below.

The trin_aide_Cpu32_1.log can be downloaded here. https://www.box.com/s/ai04l78t3huccfse50km

Any help is appreciated

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Exit code (Decimal):           -2068052413
  Exit facility code:            1212
  Exit error code:               1603
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2013-03-28 08:28:36
  End time:                      2013-03-28 08:31:03
  Requested action:              Install
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130328_082814\trin_aide_Cpu32_1.log
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0

Machine Properties:
  Machine name:                  VOOM64
  Machine processor count:       1
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered 

Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL Server 2008 R2
  Type:                          RTM
  Version:                       10
  Installation location:         c:\79dbf470b9cc8457bbb2\x64\setup\
  Installation edition:          EXPRESS_ADVANCED

  Slipstream:                    True
  SP Level                       1

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      True
  AGTSVCACCOUNT:                 <empty>
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASDOMAINGROUP:                 <empty>
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:             
  CUSOURCE:                      
  ENABLERANU:                    False
  ENU:                           True
  ERRORREPORTING:                False
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  FEATURES:                      SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 *****
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTALLSHAREDDIR:              c:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           c:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  NPENABLED:                     0
  PASSPHRASE:                    *****
  PCUSOURCE:                     c:\79dbf470b9cc8457bbb2\PCUSOURCE
  PID:                           *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 FilesOnlyMode
  RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           <empty>
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  False
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  X86:                           False

  Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130328_082814\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  MSI status:                    Failed: see details below
  MSI error code:                0x1603
  MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130328_082814\trin_aide_Cpu32_1.log
  MSI error description:         
  Configuration status:          Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130328_082814\SystemConfigurationCheck_Report.htm

rename drive and move mdf ldf files

$
0
0

hi ,I am having a development server:

C: drive , installation files and System databases mdf and ldf sits here

F drive : 300 GB free space( backups are stored here : i know its a bad idea )

G drive :286 GB free Space ( all user databases MDF and LDF sits here)

we have a plan to move all files from F drive to G drive and Rename the G drive to F drive

My plans were

Plan A .i would have to shut down sql server, rename the Drive to F  and  then attach the database mdf and ldf files with new F: drive names

Plan B .backup all the databases to some other location (N/W share ) and restore  with changing the mdf ldf locations.

which is the better one and also is there any other way to do it ?

and do i have to check for orphan users ?and how about execute permissions ?

Please give me some suggestions

Thanks

Set Up Failed There was a failure to calculate the default value of setting INSTANCEID

$
0
0

I've tried to install and uninstall SQL Server 2012, both express and eval, but keep getting same error. I have tried this from burned dvd and from an expanded folder on my pc; it just seems that with every attempt I have made I get so far and then I get the same error repeatedly.  I've also re-downloaded the media, tried the RTM and SP1 versions, no change.  I tried not installing setup updates, as well as installing them - each time uninstalling sql setup inbetween.  I have updated my .NET framework to the new 4.5 version, I have Powershell 2.0 installed.  All pre-req checks succeed. 

Computer is Windows 7 Home Premium 64-bit, 4GB RAM. 

This is what the Summary.text file has:

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
    Message:
        There was a failure to calculate the default value of setting INSTANCEID.
    HResult : 0x85640001
        FacilityCode : 1380 (564)
        ErrorCode : 1 (0001)
    Data:
      SettingId = INSTANCEID
      WatsonData =
      HelpLink.EvtType = 
      DisableWatson = true

sql server 2012 express error 0x851A0019 Could not find the Database Engine startup handle.

$
0
0

I tried installing sql server express on my computer but it failed.  I have windows 7 x64 home premium installed.  Three quarters of the way through the install the error "Could not find the Database Engine startup handle" failed.  There is nothing on the internet that addresses this error for the express version.  In subsequent posts, my logs will be listed.

Summary.txt file

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893607
  Start time:                    2013-03-28 10:59:35
  End time:                      2013-03-28 11:50:47
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  MICHAEL-PC
  Machine processor count:       2
  OS version:                    Windows 7
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
  SQL Server 2012                                                          Management Tools - Basic                 1033                 Express Edition      11.0.2100.60    No        

Package properties:
  Description:                   Microsoft SQL Server 2012 Service Pack 1
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  SPLevel:                       0
  Installation location:         C:\Users\Michael\Desktop\SQLEXPRADV_x64_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  NT Service\ReportServer
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Michael-PC\Michael, BUILTIN\Administrators
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  true
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130328_104945\ConfigurationFile.ini

Detailed results:
  Feature:                       Reporting Services - Native
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130328_104945\SystemConfigurationCheck_Report.htm

Viewing all 7701 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>