SQL Server 2008 won't recognize copied database

I copied my mdf and ldf file to the cloud server, and the data path is correct. But the database does not show up in management studio. I have done this before between in house servers running SQL2008.  Could it be ownership, permissions, or that
the server has another name, or something else.?  It is a big file (130GB) that takes 4 days to upload via RDP so I dont want to create a new database on the cloud and then import my data, I would rather use the existing database file taken from my server

There might be something missing in your requests, please check below options.
1. If you are trying to attach databases and you don't see files while attaching in SSMS then Olaf point it correct and please follow that.
2. If you have just copied the db files on cloud db server and you want to see them in SSMS under Server->User Database Folder, then you need to attach them to see them on SSSMS
3. You can try backup with zip option if ssms supports or third party zip options, then copy to cloud server and then restore them by giving proper data\log file paths
4. Also please make sure that you have given you and SQL Server Services full access on SQL Server data\log\binaries folders to see them via SSMS.
Santosh Singh

Similar Messages

  • SQL Query Works in MS SQL Server 2008 but not when using Database Toolkit

    I have this SQL query:
    DECLARE @DataTypeTable TABLE (
    Name varchar(128),
    TypeID INT)
    --Add comma delimeted data type names to temp table
    INSERT INTO @DataTypeTable (Name)
    SELECT * FROM WhatWeShouldDoRead.func_Split(@DataTypeTrimmed,',')
    SELECT Name FROM @DataTypeTable
    Which takes a comma delimited string and returns the string as a table.  It works correctly in Microsoft SQL Server Management Studio.  When I run this as a stored procedure  I get back nothing.  There are no errors, SQL or otherwise.  I've verified that I am connected to the correct database and that the stored procedure is loaded by changing the no error string that is reported from this stored procedure (that code is not shown in the above example).  Has anyone seen this problem before, or have any experiance with SQL/Labview interfaces to tell me what I'm doing wrong?
    Thanks in advance. 
    Solved!
    Go to Solution.

    After doing some more research it appears that the database toolkit cannot interface with any table results from any type of temp table.  It may have to do with the fact that MS SQL 2008 stores temp tables in a seperate database (tempdb) and not the database you are currently connected to.  See this link for a good artical on temp tables:
    http://databases.aspfaq.com/database/should-i-use-a-temp-table-or-a-table-variable.html
    If possible,  I'd like a someone to prove me wrong, but for now will have to settle for exporting the contents of a temp table through a string.

  • SQL Server Service won't start on SQL Server 2008

    Hi everyone,
    I'm having trouble starting SQL Server service after stopping and starting the service. Before this happened, I created a Stored Procedure for marking all tables at once along with a maintenance plan for differential backup on all my databases based on the
    recommendation from this link, http://msdn.microsoft.com/en-us/library/ms253070.aspx.
    When I realized that the differential backup failed with some databases displaying (Restoring...) post-fix to the database name, I decided to stop SQL Server service and start it up. That is when I won't be able to start the service again.
    Is there a fix for starting the SQL Server service? Any help is very much appreciated.
    Additional information:
    - With administrator permission granted.
    - Service Pack 1 for SQL Server 2008 installed.
    - Using default database instance.
    - Tried C:\Program Files\Microsoft SQL Server\MSSQL.....\Binn>net start MSSQLSERVER /T3608 ( return msg: System error 5 has occurred. Access is denied.
    - When I start SQL Server service, I keep getting this dialog msg:
    "Windowns could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1814."
    The event log does not explain or provide any hint on how to fix the problem.
    - Log msg:
    2010-07-22 10:30:25.09 Server      (c) 2005 Microsoft Corporation.
    2010-07-22 10:30:25.09 Server      All rights reserved.
    2010-07-22 10:30:25.09 Server      Server process ID is 6076.
    2010-07-22 10:30:25.10 Server      Authentication mode is MIXED.
    2010-07-22 10:30:25.10 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2010-07-22 10:30:25.11 Server      This instance of SQL Server last reported using a process ID of 5708 at 7/21/2010 3:27:01 PM (local) 7/21/2010 10:27:01 PM (UTC). This is an informational message only; no user action is required.
    2010-07-22 10:30:25.11 Server      Registry startup parameters:
         -d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
         -e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
         -l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2010-07-22 10:30:25.14 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2010-07-22 10:30:25.14 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2010-07-22 10:30:25.23 Server      Using locked pages for buffer pool.
    2010-07-22 10:30:25.43 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2010-07-22 10:30:25.73 Server      Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational
    message only. No user action is required.
    2010-07-22 10:30:25.81 spid7s      Starting up database 'master'.
    2010-07-22 10:30:26.14 spid7s      CHECKDB for database 'master' finished without errors on 2010-07-19 21:15:02.823 (local time). This is an informational message only; no user action is required.
    2010-07-22 10:30:26.18 spid7s      Resource governor reconfiguration succeeded.
    2010-07-22 10:30:26.18 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2010-07-22 10:30:26.18 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2010-07-22 10:30:26.19 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2010-07-22 10:30:26.28 spid7s      SQL Trace ID 1 was started by login "sa".
    2010-07-22 10:30:26.29 spid7s      Starting up database 'mssqlsystemresource'.
    2010-07-22 10:30:26.31 spid7s      The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
    2010-07-22 10:30:26.43 spid10s     Starting up database 'model'.
    2010-07-22 10:30:26.43 spid7s      Server name is 'XXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
    2010-07-22 10:30:26.47 spid10s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
    2010-07-22 10:30:26.47 spid10s     Error: 927, Severity: 14, State: 2.
    2010-07-22 10:30:26.47 spid10s     Database 'model' cannot be opened. It is in the middle of a restore.
    2010-07-22 10:30:26.59 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
    the event log that may indicate why the tempdb files could not be initialized.
    2010-07-22 10:30:26.59 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    Hello,
    Could you please copy the model.mdf and modellog.ldf from
    C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\Templates
    To
    C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
    Rebuilding the system databases you will lose lose logins, jobs, SSIS packages. You may have to restore or attach user databases.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Syncronize between multiple SQL server 2008 Databases

    II am developing an application for a waterborne shipping company. The main office is running SQL server 2008 and holds an employee database. They would like each ship to have access to the Db. Each ship is also running SQL 2008. In addition each ship will
    have multiple user needing update access to the Db.
    I'm not sure it is smart (or even Possible) to sync between multiple copies of a SQL Server 2008 DB. I started (and am not opposed to using .net Sync Services, creating compact edition (.sdf) files on the servers and 'sharing' it with the users. The
    problem with this is the sdf file would have to be replicated on each user machine. This would make data integrity a challenge.
    I should note that the ships are only occasionally connected to the internet, so working directly with the office db is not possible.
    Does anyone have any ideas, or shoud I resolve myself to using a shared copy of a compact edition of the DB?
    Thanks

    Merge replication han handle occasionally connected "devices". But you need to figure out whether update conflicts are acceptable and/or whether you can write your software so they don't happen in the first place.
    Tibor Karaszi, SQL Server MVP |
    web | blog
    Thanks. That gives me a starting point. I'm sure I'll have many questions.
    Thans again.

  • How to attached a sql server 2008 database on sql server 2005

    Hi,
    I have a backup of database designed over sql server 2008. I need to attacched this on a machine where sql server 2005 is installed and I am getting the message while attaching the database.
    "The database can not be opened because it is version 661.
    the server supports version 611 and earlier"

    You need to install/have another instance of SQL Server 2008, restore over there the database and perhaps create a SSIS package to move objects and data into SQL Server 2005
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • How to install SQL SERVER 2008 r2 in window 7 home premimum 64bit

    how to install SQL SERVER 2008 r2 in home premimum 64bit os. can any say that weather it will support or not in window 7 home premimum os.
    my server log file:
    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):           -2068052700
      Exit facility code:            1212
      Exit error code:               1316
      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:                    2014-03-27 00:52:25
      End time:                      2014-03-27
    00:56:09
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL
    Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_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:                  SEVALAL-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance          
      Instance ID                    Feature                                  Language          
      Edition              Version         Clustered 
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER  
          Database Engine Services                 1033                 Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER  
          SQL Server Replication                   1033                 Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER  
          Full-Text Search                         1033                 Standard Edition     10.50.1600.1    No    
      Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER  
           Analysis Services                        1033                 Standard Edition     10.50.1600.1    No  
      Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER  
           Reporting Services                       1033                 Standard Edition     10.50.1600.1    No    
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL
                   Database Engine Services                 1033                 Express Edition      10.3.5500.0    
    No        
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL
                   SQL Server Replication                   1033                 Express Edition      10.3.5500.0  
      No        
      Sql Server 2008 R2                        
                                  Client Tools Connectivity                1033                    
                     10.50.1600.1    No        
      Sql Server 2008 R2                        
                                  Client Tools Backwards Compatibility     1033                            
             10.50.1600.1    No        
      Sql Server 2008 R2                        
                                  Client Tools SDK                         1033              
                           10.50.1600.1    No        
    Package properties:
      Description:                   SQL Server Database Services
    2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
      Installation edition:          STANDARD
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      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:             C:\Program Files\Microsoft SQL Server\100\Setup
    Bootstrap\Log\20140327_005035\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      IS,SSMS,ADV_SSMS,OCS
      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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  True
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup
    Bootstrap\Log\20140327_005035\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration
    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:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync
    Framework
      Status:                        Failed:
    see logs for details
      MSI status:                    Passed
      Configuration status:          Passed

    my summary log file information:
    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):           -2068052700
      Exit facility code:            1212
      Exit error code:               1316
      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:                    2014-03-27 00:52:25
      End time:                      2014-03-27 00:56:09
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_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:                  SEVALAL-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033            
        Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                   1033            
        Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text Search                         1033      
              Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                        1033      
              Standard Edition     10.50.1600.1    No        
      Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services                       1033      
              Standard Edition     10.50.1600.1    No        
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL                Database Engine Services                 1033  
                  Express Edition      10.3.5500.0     No        
      Sql Server 2008      SEVALAL              MSSQL10.SEVALAL                SQL Server Replication                   1033
                    Express Edition      10.3.5500.0     No        
      Sql Server 2008 R2                                                       Client Tools Connectivity      
             1033                                      10.50.1600.1    No        
      Sql Server 2008 R2                                                       Client Tools Backwards Compatibility  
      1033                                      10.50.1600.1    No        
      Sql Server 2008 R2                                                       Client Tools SDK        
                    1033                                      10.50.1600.1    No        
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
      Installation edition:          STANDARD
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      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:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      IS,SSMS,ADV_SSMS,OCS
      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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  True
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration 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:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync Framework
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SystemConfigurationCheck_Report.htm

  • Service-specific error code -2146885628- MS SQL Server 2008 r2 Express

    I have had no end of problems starting my MS SQL Server 2008 r2 Express.
    My database program (Sage ACT! Pro 2011) starts fine. However when it attempts to start my default database, I get the following error message:
    When I start my database within my application software (ACT Pro 2011) , I get the following error:
    I am not abler to open any database with in ACT 2011. This error tells me that I must manually start SQL Server. I am running Windows 7 Pro, SP1. So I go to Services, and right click on SQL Server (ACT7) and click start and get the following error:
    I have contacted Swiftpage and spent 2 hours on the phone with their technical support. They manually (via remote desktop connection) deleted ACT Pro 2011 and manually deleted SQL Server 2008 r2 Express (in registry and all files and folders).
    I decided to upgrade, so ACT Pro v16 was installed. SQL Server still would not start automatically or manually. The ACT technical support person, after two very long hours said: that it is not an ACT problem, that I would need to turn to Microsoft for
    a resolution as to why SQL Server will not start, and how to remedy this issue.
    I hope someone can offer help or point me in the direction to get this very bad problem resolved. I cannot work without my CRM! can someone help?
    Thanks!

    This is the sum total of an error log in: C:\Program Files\Microsoft SQL Server\MSSQL10_50.act7\MSSQL\Log. There are no error logs for June 23 to July 14. This is the closest
    date to the first time I experienced this SQL Server problem.
    2014-07-15 09:32:43.31 Server      Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) 
    Jun 28 2012 08:36:30 
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    2014-07-15 09:32:44.12 Server      (c) Microsoft Corporation.
    2014-07-15 09:32:44.12 Server      All rights reserved.
    2014-07-15 09:32:44.12 Server      Server process ID is 2276.
    2014-07-15 09:32:44.15 Server      System Manufacturer: 'TOSHIBA', System Model: 'Satellite L775D'.
    2014-07-15 09:32:44.27 Server      Authentication mode is MIXED.
    2014-07-15 09:32:44.27 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG'.
    2014-07-15 09:32:44.63 Server      This instance of SQL Server last reported using a process ID of 6980 at 7/15/2014 9:13:22 AM (local) 7/15/2014 1:13:22 PM (UTC). This is an informational message only; no user action is required.
    2014-07-15 09:32:44.63 Server      Registry startup parameters: 
    -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\master.mdf
    -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG
    -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\mastlog.ldf
    2014-07-15 09:32:46.39 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-07-15 09:32:46.40 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-07-15 09:33:00.47 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-07-15 09:33:33.57 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-07-15 09:33:37.59 spid7s      Starting up database 'master'.
    2014-07-15 09:33:40.89 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'ACT7'.
    2014-07-15 09:33:42.39 spid7s      SQL Trace ID 1 was started by login "sa".
    2014-07-15 09:33:42.56 spid7s      Starting up database 'mssqlsystemresource'.
    2014-07-15 09:33:42.86 spid7s      The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
    2014-07-15 09:33:46.59 spid10s     Starting up database 'model'.
    2014-07-15 09:33:46.58 spid7s      Server name is 'Harold_Schultz\ACT7'. This is an informational message only. No user action is required.
    2014-07-15 09:33:46.59 spid10s     Error: 17204, Severity: 16, State: 1.
    2014-07-15 09:33:46.59 spid10s     FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).
    2014-07-15 09:33:46.85 spid7s      Informational: No full-text supported languages found.
    2014-07-15 09:33:46.85 spid10s     Error: 5120, Severity: 16, State: 101.
    2014-07-15 09:33:46.85 spid10s     Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
    2014-07-15 09:33:46.85 spid7s      Starting up database 'msdb'.
    2014-07-15 09:33:46.85 spid7s      Error: 17204, Severity: 16, State: 1.
    2014-07-15 09:33:46.85 spid7s      FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).
    2014-07-15 09:33:46.85 spid7s      Error: 5120, Severity: 16, State: 101.
    2014-07-15 09:33:46.85 spid7s      Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
    2014-07-15 09:33:47.04 Server      Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different network protocol and disable VIA.
    2014-07-15 09:33:47.33 Server      Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
    2014-07-15 09:33:48.03 spid7s      Error: 17207, Severity: 16, State: 1.
    2014-07-15 09:33:48.03 spid7s      FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
    Diagnose and correct the operating system error, and retry the operation.
    2014-07-15 09:33:48.04 spid10s     Error: 17207, Severity: 16, State: 1.
    2014-07-15 09:33:48.04 spid10s     FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose
    and correct the operating system error, and retry the operation.
    2014-07-15 09:33:48.08 spid7s      File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
    2014-07-15 09:33:48.08 spid10s     File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
    2014-07-15 09:33:48.15 spid10s     Error: 945, Severity: 14, State: 2.
    2014-07-15 09:33:48.15 spid10s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
    2014-07-15 09:33:48.38 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event
    log that may indicate why the tempdb files could not be initialized.
    2014-07-15 09:33:48.39 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2014-07-15 09:33:48.38 Server      Error: 17190, Severity: 16, State: 1.
    2014-07-15 09:33:48.38 Server      Initializing the FallBack certificate failed with error code: 1, state: 1, error number: -2146893802.
    2014-07-15 09:33:48.42 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-07-15 09:33:48.44 Server      Error: 17182, Severity: 16, State: 1.
    2014-07-15 09:33:48.44 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-07-15 09:33:48.44 Server      Error: 17182, Severity: 16, State: 1.
    2014-07-15 09:33:48.44 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-07-15 09:33:48.44 Server      Error: 17826, Severity: 18, State: 3.
    2014-07-15 09:33:48.44 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-07-15 09:33:48.44 Server      Error: 17120, Severity: 16, State: 1.
    2014-07-15 09:33:48.44 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

  • Oracle 9i to Sql server 2008 R2 migration

    Hi,
    We are having oracle 9i as database and migrating to sql server 2008.
    Our oracle 9i database connects to another oracle databases and these databases are having different oracle version(9.2.0.8.0, 9.2.0.7.0,10.2.0.5.0,11.2.0.2.0,9.2.0.6.0,10.2.0.4.0,8.1.7.4.0 )
    I do have two queries :
    1) how to connect from Sql server 2008 R2 to different Oracle databases
    2) How will other oracle databases connect to Sql server 2008 R2 database

    Hi,
    1) how to connect from Sql server 2008 R2 to different Oracle databasesYou can create "Linked Servers".
    <<http://www.c-sharpcorner.com/uploadfile/suthish_nair/linked-servers-in-sql-server-2008/>>
    2) How will other oracle databases connect to Sql server 2008 R2 databaseYou can create "Database link"
    <<http://www.databasejournal.com/features/oracle/article.php/10893_3442661_2/Making-a-Connection-from-Oracle-to-SQL-Server.htm>>
    But I do not know that old db (like 8i) can connect to 2008R2..
    Regards,

  • SQL Server 2008 Developer install failed - Attempted to perform an unauthorized operation

    I'm trying to install SQL Server 2008 Developer edition on my laptop running Windows XP Professional SP2.  I ran the installer as a domain user with admin rights to the local box.  The installation advisor program certified that my system was ready for the install, but nevertheless I had to uninstall SQL Server 2005 Express edition and install .NET framework 3.5 SP1 first.  Once that was done, the installer finished, having successfully installed all the components of SQL Server 2008 except for the core database engine.  It failed with this error message: Attempted to perform an unauthorized operation.
    I uninstalled SQL Server 2008 and reinstalled with the same results.
    Below is a snippet from my C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081014_203925\Detail.txt which seems like it may be relevant.
    Can anyone offer any assistance?  Would be greatly appreciated.
    2008-10-14 20:50:15 SQLEngine: --EtwSetup: Updating WMI Security
    2008-10-14 20:50:15 SQLEngine: --EtwSetup: WMI sddlA;;0x120fff;;;SY)(A;;0x120fff;;;BA)
    2008-10-14 20:50:15 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2008-10-14 20:50:15 Slp: Sco: Attempting to open registry subkey SYSTEM\CurrentControlSet\Control\WMI\Security
    2008-10-14 20:50:15 Slp: Prompting user if they want to retry this action due to the following failure:
    2008-10-14 20:50:15 Slp: ----------------------------------------
    2008-10-14 20:50:15 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2008-10-14 20:50:15 Slp: Inner exceptions are being indented
    2008-10-14 20:50:15 Slp:
    2008-10-14 20:50:15 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2008-10-14 20:50:15 Slp:     Message:
    2008-10-14 20:50:15 Slp:         Attempted to perform an unauthorized operation.
    2008-10-14 20:50:15 Slp:     Data:
    2008-10-14 20:50:15 Slp:       WatsonData = HKEY_LOCAL_MACHINE@SYSTEM\CurrentControlSet\Control\WMI\Security
    2008-10-14 20:50:15 Slp:       DisableRetry = true
    2008-10-14 20:50:15 Slp:     Inner exception type: System.UnauthorizedAccessException
    2008-10-14 20:50:15 Slp:         Message:
    2008-10-14 20:50:15 Slp:                 Attempted to perform an unauthorized operation.
    2008-10-14 20:50:15 Slp:         Stack:
    2008-10-14 20:50:15 Slp:                 at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess)
    2008-10-14 20:50:15 Slp: ----------------------------------------
    2008-10-14 20:50:31 Slp: User has chosen to cancel this action

    Hi,
    I have recently donwloaded the evaluation version of SQL SERVER 2010. I have a similar problem to this user as shown below. I have tried changing the registry permissions for Microsoft SQL Server but this made no difference. Since the registry entries are created by the installation process it seems odd that it cannnot subsequently update the entry.
    Any ideas?
    Dominic
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0xD3BEBD98@1211@1
      Configuration error description: Attempted to perform an unauthorized operation.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100408_135119\Detail.txt
    2010-04-08 14:01:43 Slp: ----------------------------------------
    2010-04-08 14:01:43 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2010-04-08 14:01:43 Slp: Inner exceptions are being indented
    2010-04-08 14:01:43 Slp:
    2010-04-08 14:01:43 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2010-04-08 14:01:43 Slp:     Message:
    2010-04-08 14:01:43 Slp:         Attempted to perform an unauthorized operation.
    2010-04-08 14:01:43 Slp:     Data:
    2010-04-08 14:01:43 Slp:       WatsonData = Microsoft SQL Server
    2010-04-08 14:01:43 Slp:       DisableRetry = true
    2010-04-08 14:01:43 Slp:     Inner exception type: System.UnauthorizedAccessException
    2010-04-08 14:01:43 Slp:         Message:
    2010-04-08 14:01:43 Slp:                 Attempted to perform an unauthorized operation.
    2010-04-08 14:01:43 Slp:         Stack:
    2010-04-08 14:01:43 Slp:                 at System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2010-04-08 14:01:43 Slp:                 at System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2010-04-08 14:01:43 Slp:                 at Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2010-04-08 14:01:43 Slp:                 at Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2010-04-08 14:01:43 Slp:                 at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2010-04-08 14:01:43 Slp: ----------------------------------------

  • Sql server 2008 access denied

    hello everyone
    I have installed Sql server 2008 then
    when i cretae database getting following error
    Msg 262, Level 14, State 1, Line 1
    CREATE DATABASE permission denied in database 'master'.

    You should be either member of the "sysadmin" or "dbcreator" server role to create databases, check the permissions
    http://technet.microsoft.com/en-us/library/ms178569.aspx
    http://msdn.microsoft.com/en-us/library/ms188659.aspx
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • DM 3.1.1 with SQL Server 2008 . Extended Properties not imported .

    Hi
    I am using Data Modeler 3.1.1 with SQL Server 2008.
    I have a database where I have Extended Properties (MS_Description) for the tables and columns.
    I use the Import Data Dictionary option (database type SQL 2005) , and the extended properties are not being imported to the model.
    Is there anything else that I should do to have the descriptions imported?
    Regards,
    Jorge

    Hi Fernando
    That is what I need to do.
    Create a Model from an existing SQL Server database with the Import data Dictionary option , be able to modify tables structures, extended properties in the model, and then sync those changes with the database.
    So far I can't import the extended properties with DM 3.1.1. If you find a way , please let me know.
    Thanks,
    Jorge

  • Unable to install Microsoft SQL Server 2008 R2

    It is showing error: Attempted to perform unauthorized operation. So was unable to install
    Database Engine
    Replication
    TITLE: Microsoft SQL Server 2008 R2 Setup
    The following error has occurred:
    Attempted to perform an unauthorized operation.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click:
    http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x6121810A%25400x92D13C14
    BUTTONS:
    &Retry
    Cancel
    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):           -2068119551
      Exit facility code:            1211
      Exit error code:               1
      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-01-25 10:59:08
      End time:                      2013-01-25 11:13:30
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\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.1600.1%26EvtType%3d0x6121810A%400x92D13C14
    Machine Properties:
      Machine name:                  VARUNGUPTA-PC
      Machine processor count:       2
      OS version:                    Windows Vista
      OS service pack:               Service Pack 2
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1033                 Express Edition      10.3.5500.0     No       
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1033                 Express Edition      10.3.5500.0     No       
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         d:\a716bfc2c0347dcd1c0fc7fcedc92a06\x86\setup\
      Installation edition:          EXPRESS_ADVANCED
    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
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:            
      CUSOURCE:                     
      ENABLERANU:                    True
      ENU:                           True
      ERRORREPORTING:                True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,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\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:                    
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AI
      SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           VarunGupta-PC\Varun Gupta
      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\20130125_105747\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\SystemConfigurationCheck_Report.htm

    I was finally able to get out of this issue... but later got stuck here with following error
    TITLE: SQL Server 2008 R2 Setup
    The following error has occurred:
    Attempted to perform an unauthorized operation.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click:
    http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0&EvtType=0x6121810A%25400x92D13C14
    BUTTONS:
    &Retry
    Cancel
    Also tried by running as administrator.
    It failed to install
    Data Engine Services
    SQL Server Replication
    Full - Text Search
    Reporting Services
    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):           -2068119551
      Exit facility code:            1211
      Exit error code:               1
      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-01-27 01:11:08
      End time:                      2013-01-27 01:23:26
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130127_010951\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%3d0x6121810A%400x92D13C14
    Machine Properties:
      Machine name:                  VARUNGUPTA-PC
      Machine processor count:       2
      OS version:                    Windows Vista
      OS service pack:               Service Pack 2
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008 R2   SQLEXPRESS           MSSQL10_50.SQLEXPRESS          Database Engine Services                
    1033                 Express Edition      10.51.2500.0    No       
      Sql Server 2008 R2   SQLEXPRESS           MSSQL10_50.SQLEXPRESS          SQL Server Replication                  
    1033                 Express Edition      10.51.2500.0    No       
      Sql Server 2008 R2   SQLEXPRESS           MSSQL10_50.SQLEXPRESS          Full-Text Search                        
    1033                 Express Edition      10.51.2500.0    No       
      Sql Server 2008 R2   SQLEXPRESS           MSRS10_50.SQLEXPRESS           Reporting Services                      
    1033                                      10.51.2500.0   
    No       
      Sql Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Express Edition     
    10.51.2500.0    No       
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         c:\c49037ca8dfa571dfe4480d170\x86\setup\
      Installation edition:          EXPRESS_ADVANCED
      Slipstream:                    True
      SP Level                       1
    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
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:            
      CUSOURCE:                     
      ENABLERANU:                    True
      ENU:                           True
      ERRORREPORTING:                True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,RS
      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\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   c:\Program Files\Microsoft SQL Server
      INSTANCEID:                    VARUNGUPTA
      INSTANCENAME:                  VARUNGUPTA
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     c:\c49037ca8dfa571dfe4480d170\PCUSOURCE
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AI
      SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           VarunGupta-PC\Varun Gupta
      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\20130127_010951\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      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
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130127_010951\SystemConfigurationCheck_Report.htm
    Here is Detail.txt file
    http://sdrv.ms/W759Wo

  • Changing CMS and Audit Repository databases from Oracle to SQl server 2008

    Hi guys,
      We have a Business Objects Dev environment which was installed with Oracle 10g database for CMS and Audit Repository.
    Our database team now decided to change the CMS and Audit databases of Dev BOE from Oracle to  SQL server 2008.
    What is the ideal way to achieve this? I'm concerned because the old DB is Oracle and the new one would be SQL server.
    Earlier, I have changed CMS database from one to another by stopping SIA , taking the backup of old DB into new and changing it in the Update Databse option. But in that case both old and new CMS databses were on SQL server 2005.
    Thanks,
    Ganga

    Denise,
      Thanks for the solution.
    We have done Windows AD and SAP integration on the Dev BOE. Will there be any issue with those after the DB change. I am guessing there won't be, but just want to confirm. Please reply.
      Also, we need to stop the old SIA and start using the new SIA after the step two is done right?

  • Problem with full backup with copy only in maintenance plan sql server 2008

    Hello
    I am starter DBA for sql server in general
    I have problem related to backup with maintenance plan in sql server 2008 and 2008 r2
    I created maintenance plan to take full back up  with copy only option checked, but when I check the back up in backupset table is_copy_only column it shows 0 for databases that I run job for.
    I did the same steps on sql server 2012 and I checked backupset table is_copy_only column it shows 1 for databases that I run job for .so it works as it should be
    Note: all the servers I mention here are production servers 

    Copy-only Backup  by using GUI ( SSMS) in SQL Server 2008 but it was not available in  Maintenance Plan "Back
    Up Database Task". Now in SQL Server 2012 It is included in "Back Up Database
    Task". 
    http://sqlage.blogspot.in/2013/06/dba-maintenance-plan-back-up-database.html

  • Does SQL Server 2008 R2 recognize only system-generated session identifiers,

    As part of the locking down of our system we are doing the Security Technical Implementation Guide (STIG) and one of the questions it asks is "The DBMS must recognize only system-generated session identifiers."
    I have looked at the STIG version for SQL Server 2012 and this is not a finding on it, since it supports the requirement and cannot be configured out of compliance.
    If anyone can help confirm that this is also the case with SQL Server 2008 R2 that would be very helpful.
    Thank you, Darren
    The discussion of it is:
    This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other
    party and in the validity of the information being transmitted.
    Unique session IDs are the opposite of sequentially generated session IDs which can be easily guessed by an attacker. Unique session identifiers help to reduce predictability of said identifiers. 
    Unique session IDs address man-in-the-middle attacks including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have
    more difficulty in hijacking the session or otherwise manipulating valid sessions.
    The DBMS must only recognize only system generated session identifiers. If an attacker was able to generate a session with a non-system generated session identifier and have it be recognized by the system, the attacker could potentially gain access to the
    system without passing through access controls designed to limit database sessions to authorized users.

    Hi Darren,
    From your description, do you mean the session_id from DMV sys.dm_exec_sessions? If so, the session_id(s) are all created and handled by SQL Server. When session_id <= 50 , it belongs to a system session, and when session_id > 50, it belongs to a user
    session.
    Below query could help you generate system sessions in SQL Server 2008 R2. Refer to :
    Explore the secrets of session- sys.dm_exec_sessions.
    SELECT
    S.SESSION_ID,
    S.STATUS,
    S.HOST_NAME,
    C.CLIENT_NET_ADDRESS,
    CASE WHEN S.LOGIN_NAME = S.ORIGINAL_LOGIN_NAME THEN S.LOGIN_NAME ELSE S.LOGIN_NAME + ' (' +S.ORIGINAL_LOGIN_NAME + ')' END AS LOGIN_NAME,
    S.PROGRAM_NAME,
    C.CONNECT_TIME, -- DIFFRENT BETWEEN CONNECT & LOGIN TIME IS TIME TAKEN BY PRELOGON ACTIVITIES
    S.LOGIN_TIME,
    CASE S.TRANSACTION_ISOLATION_LEVEL
    WHEN 0 THEN 'UNSPECIFIED'
    WHEN 1 THEN 'READUNCOMITTED'
    WHEN 2 THEN 'READCOMMITTED'
    WHEN 3 THEN 'REPEATABLE'
    WHEN 4 THEN 'SERIALIZABLE'
    WHEN 5 THEN 'SNAPSHOT'
    ELSE CAST(S.TRANSACTION_ISOLATION_LEVEL AS VARCHAR(32))
    END AS TRANSACTION_ISOLATION_LEVEL_NAME,S.LAST_SUCCESSFUL_LOGON, -- REQUIRES 'COMMON CRITERIA COMPLIANCE ENABLED' OPTION VIA SP_CONFIGURE.
    S.LAST_UNSUCCESSFUL_LOGON, -- REQUIRES 'COMMON CRITERIA COMPLIANCE ENABLED' OPTION VIA SP_CONFIGURE.
    S.UNSUCCESSFUL_LOGONS, --REQUIRES 'COMMON CRITERIA COMPLIANCE ENABLED' OPTION VIA SP_CONFIGURE.
    S.CPU_TIME AS CPU_TIME_MS,
    S.MEMORY_USAGE AS MEMORY_USAGE_PAGES,
    S.ROW_COUNT,
    S.PREV_ERROR,
    S.LAST_REQUEST_START_TIME,
    S.LAST_REQUEST_END_TIME,
    C.NET_TRANSPORT,
    C.PROTOCOL_TYPE,
    S.LANGUAGE,
    S.DATE_FORMAT,
    ST.TEXT AS QUERY_TEXT
    FROM
    SYS.DM_EXEC_SESSIONS S
    FULL OUTER JOIN SYS.DM_EXEC_CONNECTIONS C ON C.SESSION_ID = S.SESSION_ID
    CROSS APPLY SYS.DM_EXEC_SQL_TEXT(C.MOST_RECENT_SQL_HANDLE) ST
    WHERE
    S.SESSION_ID IS NULL
    OR S.SESSION_ID < = 50
    ORDER BY
    S.SESSION_ID
    Thanks,
    Lydia Zhang

Maybe you are looking for