Backup Restore With SQL Server 2008 R2 although it succeeded with SQL Server 2008

Dears;
I have a Full backup of some DB of around 417 GB within SQL Server 2008 R2 , and when I tried to restore it , i get  stuck several times with the error below :
Restore failed for Server   (Microsoft.SqlServer.SmoExtended)
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider
running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical 
Although I have restored
 successfully other several Full+ Deferential backups for the same DB while it was in SQL Server 2008 not 2008 R2.
And so I have rounded all different possible assumptions for such common know error by Microsoft for SQL Server 2000, 2005, 2008 but 
no way as next:
1-     
I have attempted to restore it within 2 environments clustered and non-clustered of SQL Server 2008 R2.
2-     
I have attempted to restore verify it and it was so fine .
3-     
I have attempted to restore it using Continue_after_error ,no_checksum but no way.
4-     
I have attempted to move Backup file to another Storage but no way.
5-     
I have scheduled jobs to DBCC
 Checkdb the live DB and it wasn’t any errors since long time right now
6-     
I have also DBCC check all master +msdb+model+Tempdb ,and they are so fine
7-     
I have also checked all I/O subsystem of SAN and Network controllers , but they are fine evidenced much more by my trial on 2 different environments.
8-     
I have also checked Memory and it is so fine all the time since I have 128 GB memory and I control it also so well.
For DB Design +Structure :
It has 20 Files containing tables partitioned horizontal +Vertically
 (Schema Partitioning +File Stream partitioning ) through these 20 files.
I have Data compression of the required tables only.
I have one table of more than 300 GB alone which is partitioned as mentioned above.
I have implemented Read Committed Snapshot isolation level using row versioning integrated so well with File stream technology since it is a new feature of SQL 2008 R2.
DB is in simple recovery model for garbage collection of all file stream data as a result of much Delete /update in images themselves.
 So any one has any idea about such case..How to solve it…?

Hi Ashwin,
When i searched with no answers these are listed out. So i thought this is still existing. Now on wards let me check the data and time of latest reply. Thanks for guidance.
It was happening by oversight. Thanks for guidance.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/

Similar Messages

  • Why can't I migrate from an iPhone 3GS to a 4GS using iCloud Backup/Restore?? (Says incompatible.)

    Why can't I -simply- migrate from an iPhone 3GS to a 4GS using iCloud Backup/Restore??
    (The 4GS says it's incompatible with 3GS iCloud Backups and so it cannot restore them.)
    I've had to use a computer with iTunes, but surely iCloud can be used fior this?

    You need to update your 4 to newer software to restore from icloud back up, until then you will get incompatible message. So steps are - set up your iphone 4 as new. Update. Erase. Restore from cloud backup. If you update does not take long you should be all set within an hour.

  • SAP SQL System Copy backup restore method with ADS(Adobe document services)

    Hello all,
    i´m preparing a system copy with ERP 6.0 in windows and SQL server with ADS.
    I have a doubt, can i do the System Copy backup/restore method with ADS??
    or the only method that works is with system export/import in all instances??
    Thank you

    Hi Oscar,
    Is your ADS system separate from your ERP system, or are they on the same server?
    In any case, you can use backup/restore to copy a Java system, but you must also make a system export/import for the Java server components.  The two work in conjunction, so that the export tool doesn't export your whole database, only the components maintained in the filesystem.  If you select the database detach/attach or backup/restore method in the tool when going against the Java system, it will prompt you at the right point in the process to make your Java export as well.
    The caveat is that the Java export requires downtime, so it isn't possible to copy a Java system without impacting system availability, as it is with a pure ABAP system.
    Best regards,
    Matt

  • Lync Backup/Restore with SQL backup

    Is it possible to backup and restore the XDS database (Lync topology and configuration information) using SQL database tools?  Technet is very confusing, it describes in great detail how to use cmdletts to export the configuration then back it up with
    te regular backups.  But then at link for Backup - restore best practices  it states "The simplest and most commonly used backup type and rotation schedule is a full, nightly backup of the entire SQL Server database. Then, if restoration is necessary,
    the restoration process requires only one backup and no more than a day’s data should be lost."
    http://technet.microsoft.com/en-us/library/hh202184.aspx
    Best Practices for Backup and Restoration
    To facilitate your back up and restoration process, apply the following best practices when you back up or restore your data:
    Perform regular backups at appropriate intervals. The simplest and most commonly used backup type and rotation schedule is a full, nightly backup of the entire SQL Server database. Then, if restoration is necessary, the restoration process requires only
    one backup and no more than a day’s data should be lost.
    If you use cmdlets or the Lync Server Control Panel to make configuration changes, use the
    Export-CsConfiguration cmdlet to take a snapshot backup of the topology configuration file (Xds.mdf) after you make the changes so that you won't lose the changes if you need to restore your databases.
    Ensure that the shared folder you plan to use for backing up Lync Server 2010 has sufficient disk space to hold all the backed up data.
    Schedule backups when Lync Server usage typically is low to improve server performance and the user experience.
    Ensure that the location where you back up data is secure.
    Keep the backup files where they are available in case you need to restore the data.
    Plan for and schedule periodic testing of the restoration processes supported by your organization.
    Validate your backup and restoration processes in advance to ensure that they work as expected.
    Thanks for your help,
    Paul MacLean

    Take a look if this helps you out:
    http://designinglync.blogspot.com/2011/04/lync-backup-and-recovery.html
    and in detail:
    http://blogs.technet.com/b/uc_mess/archive/2011/03/17/lync_2d00_server_2d00_2010_2d00_backup_2d00_instructions.aspx
    +Say thanks and observe basic forum courtesy:
    +If this post answered your question, Mark As Answer
    +If this post was helpful, Vote as Helpful
    windowspbx blog: my thots/howtos
    see/submit Lync suggestions here: simple and public

  • Backup / Restore Test on SQL server. Am I right?

    Hello Colleagues,
    We want to execute the following plan in order to test our backup&restore infrastucture. Please couls you point me if I´m leaving something back?
    SQL Server 2005 SAP nw2004s based system (I think that the below procedure is valid no matter the system is Abap standalone, JAVA standalone or ABAP+JAVA standalone)
    We want to Stop SAP production System HRP in production host.
    Detach HRP SQL server in production Host.
    Restore from the last full backup on production Host changing the database name to HRPNEW (logical name and filenames)
    Attach the new restored files to the SQL Server 2005 (I think that this point is not needed because the restore will leave the database operational if I mark the corresponding option)
    Start Sap System and check that everything is OK inside.
    Stop SAP system again
    detach HRPNEW database
    attach HRP original database
    Start SAP system and check
    FInally delete db files and log files from HRPNEW database.
    What do you think?
    Thank you very much in advance!
    Regards

    Thank you for your response.
    But, is it needed if I´m restoring in the production server (same host name) the database with another name?
    Or you meant to change the database name in anywhere?
    Thanks
    Regards!

  • How to backup/restore credentials in sql server 2012

    Hi, Can any one direct how to restore credentials using T-sql or GUI on SQL Server 2012.
    As per BOL, we know how to create credentials. 
    http://msdn.microsoft.com/en-us/library/ms189522.
    But looking for taking backup/restore credentials sql serve 2012.
    Thanks

    Hi,
    I highly recommend to go from step 1 to the end in this tutorial, but if you realy want to just only to restore than you can start in Lesson 4: Perform a Restore From a Full Database Backup
    http://msdn.microsoft.com/en-us/library/jj852091(v=sql.110).aspx
      Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]

  • Update SQL Server 2008 R2 CLUSTER To SP1 With TFS 2010

    Hi,
    I have Cluster SQL Server 2008 R2 configured to store  Team Foundation Server 2010 DBs
    I want to Update this Cluster to SP1 to support Sharepoint DBs 
    So i want to see if this update can impact my TFS DBs 
    Thnx
    vote if you think useful

    Hello,
    I which way is this "Database Design" related, the Topic of this forum?
    You can install the SP 1 without any harm to your TFS 2010 database; we host them on SQL Server 2012 and also this work.
    But instead of the old SP1 you should go with the last SP 3 for SQL Server 2008 R2.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]
    thank you for your reply
    I want to test it in a lab environment
    vote if you think useful

  • SQL Server Reporting Service 2008 R2 - The request failed with HTTP status 401: Unauthorized.

    I got the error "The request failed with HTTP status 401: Unauthorized." when I call the Reporting Service Web Service.
    The code is very simple:
    // Initialise the reporting service Web Service
    this.RSWebService = new ReportingService2010();
    // Pass windos authentication credentials to Web Service
    this.RSWebService.Credentials = System.Net.CredentialCache.DefaultCredentials;
    // List children
    List<CatalogItem> reports = this.RSWebService.ListChildren(folder, false).ToList();
    The SQL Server is installed on a different machine (say server A) from the Web server (say server B). We are using Windows Server 2003.
    The code work fine for all the scenario below:
    i) Run locally (XP) to call the web service on the sql server
    ii) Provide the Network Credentials with the username, password, and domain when calling the web service
    iii) If the web server and sql server is using same server (i.e. not distributed)
    I'm using windows authentication and impersonation. Any idea?

    Hi Raymond,
    If I understand correctly, the issue only happens in the environment that the web server is different with the SQL Server Reporting Services server. This means the web server is a remote server of the Report Server. Windows Integrated authentication is used
    in this case. When running the web page, the 401 error occurs.
    If so, it is actually a double hop issue. The double-hop problem will usually only be an issue to those of you who write some sort of web-based code (a web application or web service) that uses impersonation.
    To fix the issue, we can configure kerberos authentication for the web application and the SQL Server Reporting Services.
    Below is a great article that has delivered many solutions to fix the issue you met:
    http://odetocode.com/articles/216.aspx
    Additionally, you can read the following article to know more about double-hop:
    http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx
    http://blogs.msdn.com/b/knowledgecast/archive/2007/01/31/the-double-hop-problem.aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Jin Chen
    Jin Chen - MSFT
    Thanks Jin. I believe this is the cause of the problem as well.
    I tried to register the SPN but unfortunately it still doesn't work. I'm not sure whether I'm using the correct SPN name.
    I have 3 reporting server instance on the SQL box. So the Web Service URL is like
    http://Server:80/VirtualDirectoryDev,
    http://Server:80/VirtualDirectoryTest  and
    http://Server:80/VirtualDirectoryStaging .
    What's the SPN I need to register?
    I tried
    Setspn -a http/Server:80/VirtualDirectoryDev domain\account
    and
    Setspn -a http/aerver:80 domain\account.
    But both of them are not working :(

  • Installed SQL Server 2008 R2 Express ADV SP1 (with advanced services), but installed 2005 Express

    My English - bad =)
    Download SQL Server 2008 R2 Express ADV SP1 from
    http://www.microsoft.com/en-us/download/details.aspx?id=26729
    this
    SQLEXPRADV_x64_ENU.exe
    Installed, opened Management Studio,
    made the request
    print @@version
    result:
    Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) 
    Feb  9 2007 22:47:07 
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 6.1 (Build 7600: )
    How to install the 2008 R2 Express ADV?? =)
    I can't open the database version 661, because SQL Server 2005 - 612

    Hi,
    You just installed SQl server management studio I guess and when you connected the system already had SQL Server 2005 and it connected to it.
    If you are sure you installed express with advanced services (2008 r2) you need to go to Start..all program..can you see SQL server 2008 r2 listed ?
    Now open SSMS for 2008 r2 and instead of connecting with default instance look for other instances in drop down in server name you would fine that for SQL Server 2008 r2 connect to that
    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 Article
    MVP

  • Backup & Restore SQL Server 2005

    Dear Experts,
    One of our SAP system got crash due to some hardware problem . we have rectified the problem and installed the OS again.
    Now could you please tell me how to restore taken SQL to bring the system up to date. Now I have Backup datas in my External HDD. I don't have Tape Drive media for that system.
    I would appreciate the procedure and steps to be followed backup restore on the SQL 2005 & windows 2003 server system
    Please Let me know.
    Thanks in advance
    Regards
    Thomas.T

    hi,
    you have to install SAP on that machine then
    1.  Detach the database from newly installed sap.
    if you had offline backup
    2. copy the database from the external HDD to  newly installed location for e.g if on installation you had
         database location on E:\ then copy to E:\
    3. attach the database.
    if online backup
    3. you have to use Restore method in SQL server.
         start SQL 2005 server, right click on database option-->select Restore database, select from device -->specify backup
         Backup media> file, click on Add> select file (external HDD location), in To database -->specify name of database (like PRD,DEV your SAP database name), in option, give the proper path for the restore.
    4. run STM tool.
    Thanks
    Ganesh

  • Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?

    Hi All,
    Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?
    aa

    I think you are confused with the way cluster is installed. Installing SQL on cluster is a two step process. On first node you create a new SQL cluster and on second node you need "AddNode" action.
    Same edition media has to be used in above two operation.
    you can install two separate instances with one enterprise and one standard.
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • How to detect whether a database was created by Restoring (from SQL Server Enterprise Manager) or by Attaching (from SQL Server Enterprise Manager)

    Ours is a SQL Server Express Edition 2008-R2 - Windows Forms based application. We have a backup/restore utility provided with our software which performs some logical checks before restoring a backup to ensure that the backup is functionally valid.
    However, our clients often use the SQL Server Enterprise Manager utility to 1) Restore backups or 2) Attach data files (kept aside before formatting) directly. This type of action bypasses all our functional checks and allows the user to restore an invalid
    backup.
    We want to detect that a database was restored/attached and may be we will stop the software from loading if such a thing happened. We think that this information (attach/restore) should be available within some table of SQL Server itself but don't know the
    right location/query.
    If any change is required in our software to achieve the above, we are ready to do the same too, e.g. may be we need to store some data at some point of time to make the detection happen, please advise.
    So, how can we detect that
    A database backup was restored using SQL Server Management Utility
    (Note: MSDB.Restorehistory may not be a good option as we have often found this table blank for unknown reasons even after backup was restored and just in case user restores the MSDB from MSDB backup or MSDB template due to a data corruption, may be due to
    abnormal shutdown of system, then the RestoreHistory table data is gone)
    A database was created by attaching a data/log file using SQL Server Management Utility
    Any help in this regard is highly appreciated.
    Rajarshi
    ProjectServer 2007 Beginner

    Hi,
    For Enterprise edition, we can enable Auditing to audit BACKUP_RESTORE_GROUP in a server audit specification. However, SQL Server audit (fine-grained auditing) feature is not available for the SQL Server Express.
    Features Supported by the Editions of SQL Server 2008 R2
    http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx
    When a database is attached, SQL Server ERRORLOG will record “Starting up database 'DBNAME'.”
    Using ALTER DATABASE OFFLINE and ONLINE will re-open the database files under the SQL Server, the SQL Server error log also contains the following informational message: “Setting database option ONLINE to ON for database 'DBNAME'.”
    Additional information:
    SQL Server Audit (Database Engine)
    http://msdn.microsoft.com/en-us/library/cc280386.aspx
    Tracy Cai
    TechNet Community Support

  • Moving from SQL server 2005 to SQL server 2008 ... for a MS/SQL newbie.

    Hello,
    I am in charge of moving an existing SAP NW BI (SPS20) from a MS SQL Server 2005 database on Windows Server 2003 (x864/64 bit) Platform to a MS SQL Server 2008 database/Windows Server 2008 Platform (x64/64 bit).
    The SID of the SAP system will remain the same.
    The thing is  that I have always worrked so far on Oracle/Unix environements, windows/MSSQL is an entire new world for me,
    so I am quite worried.
    I  have read many sap notes/installation guides/forum posts regarding this operation, I will describe here my understanding
    of the techinical operations that I will need to perfrom.
    Could you correct me if I am wrong, as well as give me your comments ?
    1/ I will need to perform an SQL server database copy within a homogeneous system copy.
    2/First ,I'll have to install on the target environnement the SQL server 2008 database. I'll have to install the SQL Server Database Software with SQL4SAP (no need to install the database server software manually, right ?). Afterwards, I'll install on the target environnent, SAP Netweaver 7.0 SR3 with a modified Instalaltion Master DVD.
    3/ On the source environement, I'll perfrom a database backup of the SQL Server 2005 system and restore the database on the target environement. since I choose to perfrom a restore of the database , there is no need to follow all the steps described in sap note 151603 :determine the file structure of the source database, create the directory structure for the target database, etc ...
    4/ Once the restoration is finished, I use SAPINST and finish the homogeneous copy :  >additional sofware->system copy>target system->central system --> Based on AS Abap --central installation
    Your comments are welcome.
    Thank you for your attention
    Best Regards.
    Raoul

    Hi Raoul,
    you also need a modified Kernel DVD for the installation on SQL 2008 (see SAP Note 1152240).
    And don't forget to install and patch the Visual Studio c++ Runtime (also described in that note).
    I also would recommend to restore the backup and then install SAP NW 7.0 SR3 and use the restored SQL 2008 database.
    So the basic steps are:
    1. Perform backup and restore to SQL 2008
    1.1 Install SQL 2008 with SQL4SAP
    1.2 Backup old database
    1.3. Restore backup on SQL 2008
    2. Install VC runtime on Win 2008
    3. Create modified Kernel DVD
    4. Create modified Master DVD
    5. Perform system copy target installaton with - additional sofware->system copy>target system--->central system --> Based on AS Abap --central installation and use the SQL 2008 database
    You could also use SQL Server 2008 R2 which was release last month.
    Please also check Note 1476928
    Best,
    Sebastian Dusch

  • SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

    Hi All,
    I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
    When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains  invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
    Below is the screenshot for the same.
    So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    Again i still see the same above errors and with that a new error related to a MOF File.
    Below are the contents of the error logs. Can some one assist on this issue.
    ======================================================
    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):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      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:                    2015-01-15 13:53:03
      End time:                      2015-01-15 14:04:29
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      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:         D:\SQLServer2008R2_SP1\x64\setup\
      Installation edition:          ENTERPRISE
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 E2KLAB\SCOMAC
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      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:         Automatic
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     D:\SQLServer2008R2_SP1\SP
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  E2KLAB\SCOMAC
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 E2KLAB\SCOMAC
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
      MSI error description:         The folder path 'Program Files' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
    Gautam.75801

    Hi Alberto,
    Still the same issue.
    I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and  repaired the .NET using the .NET Repair tool
    Also changed the installation directory to D:\ Drive this time. Still same issue.
    log file:
    ===============
    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):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      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:                    2015-01-15 22:55:37
      End time:                      2015-01-15 23:07:32
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_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:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      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:                       1
      Installation location:         D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      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:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
    Any other suggestion i can try ?
    Gautam.75801

  • Why SCCM 20012 Install fails with remote 64 bit SQL Server but proceeds for remote 32 bit SQL Server

    I have the following setup:
    AD User accounts
    - SQLAdmin (used to run SQL Services i.e. Database Engine)
    - SCCMADmin (used to install SCCM 2012)
    SPN registered for user account SQLAdmin
    setspn -S MSSQLSvc/SQL.Domain_Name:1432 Domain_Naem\SQLAdmin
    setspn -S MSSQLSvc/SQL:1432 Domain_Name\SQLAdmin
    setspn -S MSSQLSvc/SQL.Domain_Name:1433 Domain_Naem\SQLAdmin
    setspn -S MSSQLSvc/SQL:1433 Domain_Name\SQLAdmin
    and checked with setspn -L TESTING\SQLAdmin
    1 SERVER called SQL
    32bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
    2 SQL instances - Default (MSSQLSERVER) and
    SCCM2012
    MSSQLSERVER instance uses TCP port 1433
    SCCM2012 Instance users TCP port 1432 (no dynamic ports)
    User accounts that have been given public and sysadmin SQL server roles
    on both instances are: SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
    Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
    Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
    Firewall turned on with access allowed on Ports 1432, 1433, 4022,445, and WMI - WMI-in, DCOM-in and ASync-iN builtin rules allowed\enabled.
    1 SERVER called SQL3
    64bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
    2 SQL instances - Default (MSSQLSERVER) and
    SCCM2012
    MSSQLSERVER instance uses TCP port 1433
    SCCM2012 Instance users TCP port 1432 (no dymanic ports)
    User accounts that have been given public and sysafmin SQL server roles on both instances are:
    SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
    Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
    Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
    Firewall turned off
    1 SERVER called SCCM
    64bit Server that is to be the Primary Site Server\MP for SCCM 2012
    ODBC link to SQL\SCCM2012,1432
    ODBC link to SQL3\SCCM2012,1432
    ODBC uses SQL Native Client 10.0 (64 bit)
    Both ODBC connections when TESTed pass and suggest connectivity to SQL Servers
    Install process doe SCCM2012
    Tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account
    SCCMAdmin,  and when utilising the SCCM2012 SQL instance on
    32 bit server of SQL install proceeds barring warning about 8GB rec, for SQL Server. Then fails on PKI certificate issue. Installation (chose HTTP for MP). I beleive the PKI failure as install starts is
    due to the fact that SCCM 2012 needs its database server to b 64 bit ?
    Thus i then tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account SCCMAdmin,  and
    when using the SCCM2012 SQL instance on
    64 bit server of SQL install proceeds but fails at checking stage and says:
    SQL Server sysadmin rights FAILED SQL3.Domain_Name
    Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup
    cannot continue.
    and
    Site System to SQL Server communication  WARNING SCCM.Domain_Name
    A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL
    Server instance hosting the site database. Setup cannot continue.
    Why does the install of SCCM 2012 with 32 bit SQL proceed further than the install with 64 bit SQL, with the latter process failing as above error meesages show and yet both servers are set identically (apart from temporary turning off Firewall on the 64 
    bit server) and during the install the Databse Server specified is accepted ?

    Thanks for the reply.
    I can connect via ODBC to the the 32 bit SQL Server and the 64 bit SQL Server from the SCCM Server
    The SQL Server Unit called SQL3 unit is a 64 bit SQL.
    The SQL Server Unit called SQL is only 32 bit, but at least gets past the final checking stage and the error messages about sysadmin rights and Site System to SQL Server communication problem, and then fails with PKI certificate error message. 
    When trying to install SCCM specifying the 64 bit SQL Server as the Database Server it gives the 2 error messages at the final checking stage of the installation as listed.
    So as I said what is confusing is the fact that if the SCCM install uses the remote 32 bit SQL Server it passes the final checking (although fails with PKI certificate message) but the 64 bit SQL Server set up exactly the same apart from the Firewall being
    left off for the time being, fails at the final check stage with the 2 listed errors.
    If I use a local 64 bit SQL Server the installation is fine.
    Still would like to find out what cause the 2 issues for the remote 64 bit SQL Server, when ODBC seems fine, sysadmin rights have been given for the installer account and the SCCM computer account and SPNs have been set for the user account running the SQL
    Services.

Maybe you are looking for

  • Basic questions about Bigdata, NOSQL and Hadoop

    Hi, I've basic questions related to Bigdata. (I've googled it but still wants to confirm with experts) Please correct me if I am wrong on below. 1) As far as I know big data is collection of unstructured data. Even we can store relational data as wel

  • Failure to launch Camera Raw 5.2 correctly on a Mac with Elements 6?

    I downloaded and installed the Adobe Camera Raw application, and I read the readme and followed the instructions (although I'm not positive that I did it correctly). When I open Elements and then Camera Raw, the loading window for Camera Raw pops up

  • Photos are not showing up in the edit menu

    When I hit the edit button the photos all show up on the top of the screen but in the box they are not there to edit each individual photo.  Please help, I need to edit my photos!

  • IMPORT FROM MEMORY ERROR

    When ever i run a driver program of Sap-Scrip i get an abend msg statin IMPORT FROM MEMORY ERROR: Program canceled. what should i do to get over this error...???

  • Best practice for Yes / No column

    Hello, When the column stores only Yes / No Values. What is the right definition for that column. Is the following right pertaining IS_PAID column : CREATE TABLE ABSENCE     ID         NUMBER (3) NOT NULL ,     USER_ID    NUMBER (3) NOT NULL ,     IS