SQL 2008 R2 Install problems

Good day all.
About a month ago I cloned a virtual server "2008 R2 Ent" as our new SQL server. Upon installation of the "Microsoft SQL 2008 Ent
R2" using "run as administrator. I receive the following install error:
The following error has occurred:
Updating permission setting for folder 'E:\Program Files\Microsoft SQL Server\100\DTS\' failed. The folder permission setting were supposed to be set to 'D:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;0x1200a9;;;BU)'.
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=0x88792597%25400xD69AB41D
I have performed the following troubleshooting steps:
-Researched all forums with related issues. Attempted all findings.
-Attempted limited install.
-Attempted install to new directory.
-Downloaded another copy of SQL image.
-Tried install from CMD line.
-Cloned another server and attempted a fresh install.
Any thoughts would be greatly appreciated.
Tony Schnellbach

Chunsong, Below is the content from th summary.txt file. Thanks
Overall summary:
  Final result: Pending
  Exit code (Decimal): 0
  Exit message: Pending
  Start time: 2011-03-22 10:06:12
  End time: 2011-03-22 10:11:04
  Requested action: Install
Machine Properties:
  Machine name: ITS-COLO-SQL2
  Machine processor count: 1
  OS version: Windows Server 2008 R2
  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: 0
  Installation location: E:\Installs\SQLFULL_ENU-- first\x64\setup\
  Installation edition: ENTERPRISE
User Input Settings:
  ACTION: Install
  ADDCURRENTUSERASSQLADMIN: True
  AGTSVCACCOUNT: SrvAcctSQL
  AGTSVCPASSWORD: *****
  AGTSVCSTARTUPTYPE: Manual
  ASBACKUPDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
  ASCOLLATION: Latin1_General_CI_AS
  ASCONFIGDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
  ASDATADIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
  ASDOMAINGROUP: <empty>
  ASLOGDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP: 1
  ASSVCACCOUNT: SrvAcctSQL
  ASSVCPASSWORD: *****
  ASSVCSTARTUPTYPE: Automatic
  ASSYSADMINACCOUNTS: INFINITYBUSINES\SchnellbachAJ,INFINITYBUSINES\MerrittJM
  ASTEMPDIR: E:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE: Disabled
  CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110322_100253\ConfigurationFile.ini
  CUSOURCE:
  ENABLERANU: False
  ENU: True
  ERRORREPORTING: True
  FARMACCOUNT: <empty>
  FARMADMINPORT: 0
  FARMPASSWORD: *****
  FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
  FILESTREAMLEVEL: 0
  FILESTREAMSHARENAME: <empty>
  FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
  FTSVCPASSWORD: *****
  HELP: False
  IACCEPTSQLSERVERLICENSETERMS: False
  INDICATEPROGRESS: False
  INSTALLSHAREDDIR: E:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR: E:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR: <empty>
  INSTANCEDIR: E:\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: DefaultNativeMode
  RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
  RSSVCPASSWORD: *****
  RSSVCSTARTUPTYPE: Automatic
  SAPWD: *****
  SECURITYMODE: SQL
  SQLBACKUPDIR: <empty>
  SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
  SQLSVCPASSWORD: *****
  SQLSVCSTARTUPTYPE: Automatic
  SQLSYSADMINACCOUNTS: INFINITYBUSINES\SchnellbachAJ,INFINITYBUSINES\MerrittJM
  SQLTEMPDBDIR: <empty>
  SQLTEMPDBLOGDIR: <empty>
  SQLUSERDBDIR: <empty>
  SQLUSERDBLOGDIR: <empty>
  SQMREPORTING: True
  TCPENABLED: 1
  UIMODE: Normal
  X86: False
  Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110322_100253\ConfigurationFile.ini
Detailed results:
  Feature: Database Engine Services
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: SQL Client Connectivity SDK
  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: Analysis Services
  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: Integration Services
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Client Tools Connectivity
  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: Client Tools SDK
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Client Tools Backwards Compatibility
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: Business Intelligence Development Studio
  Status: Failed: see logs for details
  MSI status: Passed
  Configuration status: Passed
  Feature: SQL Server Books Online
  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\20110322_100253\SystemConfigurationCheck_Report.htm
Tony Schnellbach

Similar Messages

Can't get SQL 2008 Express installed

Hope some one can help me. I am trying to install 2008 Express version and I constantly get the following error. I have tried pretty much all flavors of express and get the same thing. I uninstalled several time and reinstall but keep getting the same exception error. Can someone help me out. Here is the error:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Documents and Settings\Jocelyn\Local Settings\Application Data\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
   at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
   at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
   at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
   at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
   --- End of inner exception stack trace ---
   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
   at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
   at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
   at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
   at System.Configuration.ConfigurationManager.GetSection(String sectionName)
   at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
   at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
   at System.Configuration.SettingsBase.get_Item(String propertyName)
   at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
   at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
   at Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings.get_WindowPlacement()
   at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
LandingPage
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.2531.0 ((Katmai_PCU_Main).090329-1015 )
    CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/100/Setup%20Bootstrap/Release/x86/LandingPage.exe
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.SqlServer.Configuration.Sco
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.2531.0 ((Katmai_PCU_Main).090329-1015 )
    CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/100/Setup%20Bootstrap/Release/x86/Microsoft.SqlServer.Configuration.Sco.DLL
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Microsoft.SqlServer.Management.Controls
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.2531.0 ((Katmai_PCU_Main).090329-1015 )
    CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/100/Setup%20Bootstrap/Release/x86/Microsoft.SqlServer.Management.Controls.DLL
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Thanks,
Jocs

Dear Charles!
Am trying to install SQL Server 2008 on Windows server 2008 R2 for the last five days but getting errors continuously like:
1. SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created..
2.
MicroSoft Net framework: unhandled exception occurred in your application.
An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or
assembly ‘System, Version=4.0.0.0, ............
As you suggested
I tried to install
Microsoft .Net Framework 3.5 SP1 but it doesnt run on it, then I installed
Microsoft .Net Framework 4.0.30319.1 it is installed on it.
Then I installed
Windows Installer 4.5 too
But my problem is not solved, kindly help me asap.
Ques: I am a user as “administrator” in the system, is it enough or have I to log in as a main administrator of the system.

SQL 2008 R2 install failing on windows 2008 exit code 2068054013

My install of sql server 2008 r2 is failing with exit code 2068054013. i have checked internet and found few articles to check if OS is debug mode. This is not issue with my server. Here is the summary.txt from bootstrap folder
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): -2068054013
Exit facility code: 1212
Exit error code: 3
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-14 18:24:11
End time: 2014-03-14 18:39:18
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_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.4266.0
Machine Properties:
Machine name: BEL-BHP-DB01
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SoftBank\SlipStream\SQL2008R2\x64\setup\
Installation edition: STANDARD
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\20140314_182326\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,BIDS,CONN,IS,BC,SDK,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\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: SQL
SQLBACKUPDIR: F:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: LocalAccuount
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlWriter_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SSCESqlWbTools_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SSCRuntime_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SQLSysClrTypes_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SSCESqlWbTools_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SSCRuntime_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\BestPracticesPolicies_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x3
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SqlSupport_KatmaiRTM_Cpu64_1.log
MSI error description:
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182326\SystemConfigurationCheck_Report.htm

Hi,
Thanks for the update. Glad to know your issue is resolved.
If you look at the log file SqlSupport_KatmaiRTM_Cpu64_1.log.txt, you will find this error
MSI (s) (64:94) [18:39:14:853]: Note: 1: 2203 2: D:\SoftBank\SlipStream\SQL2008R2\1033_ENU_LP\x64\setup\sql2008support\SqlSupport.msi 3: -2147287037
The exact error no. i.e. -2147287037.
Convert this error no. using a tool (Err.exe)
D:\Err>Err.EXE -2147287037
# for decimal -2147287037 / hex 0x80030003 :
STG_E_PATHNOTFOUND
oledberr.h
STG_E_PATHNOTFOUND
winerror.h
# The path %1 could not be found.
-2147287037 = The path %1 could not be found. Which means the msi file path D:\SoftBank\SlipStream\SQL2008R2\1033_ENU_LP\x64\setup\sql2008support\SqlSupport.msi doesn't exist.
This posting is provided “AS IS” with no warranties, and confers no rights.
If this reply answers your question, please mark it as Answered for others to find it easily.
If this reply help you resolving the problem, please vote the post as Helpful.

SCCM 2012 and SQL 2008 R2 Sync problems

Hi
I installed 2 servers for SCCM 2012:
-1 with SCCM 2012, FEP, WSUS console admin
-1 with SQL Server 2008 R2 complete install, WSUS complete install
When I made or the system mades the synchronization, it shows this error in SMS_WSUS_SYNC_MANAGER:
Error 6703:
WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
And in the wsyncmgr.log appears:
sync: SMS synchronizing updates, processed 3336 out of 3368 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:14:11.663+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3360 out of 3392 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:15:11.669+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3383 out of 3415 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:16:13.206+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3412 out of 3444 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:14.152+300><thread=4640 (0x1220)>
Synchronized update 3a572bd0-5976-4abc-b2d8-955008c5466f - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.131.558.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:18.227+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3446 out of 3463 items (99%), ETA in 00:00:04 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:14.400+300><thread=4640 (0x1220)>
Synchronized update 3eeb75c2-81aa-4cc0-9b7a-237a6a0bf737 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:47.964+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3482 out of 3484 items (99%), ETA in 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:19:15.587+300><thread=4640 (0x1220)>
Synchronized update 74e86346-9384-4304-9625-2c865738c552 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.659+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3508 out of 3508 items (100%) $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.662+300><thread=4640 (0x1220)>
Sync failures summary: $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.664+300><thread=4640 (0x1220)>
Failed to sync update 1ba2d28f-75fe-49d7-9cb4-cd39b8706f48. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.666+300><thread=4640 (0x1220)>
Failed to sync update 8a042978-e6d7-4ae6-b3ab-687d8f9bcd9c. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.669+300><thread=4640 (0x1220)>
Failed to sync update a3aff37b-ad3b-4dde-9464-767a516c76e5. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.671+300><thread=4640 (0x1220)>
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.421+300><thread=3536 (0xDD0)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=GDVSCCM1.gdar.local SITE=CRP PID=1908 TID=3536 GMTDATE=mar jul 24 14:20:06.423 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates"
ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.425+300><thread=3536 (0xDD0)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.501+300><thread=3536 (0xDD0)>
Setting sync alert to active state on site CRP $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.503+300><thread=3536 (0xDD0)>
Updated 173 items in SMS database, new update source content version is 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.526+300><thread=3536 (0xDD0)>
Set content version of update source {6A4B4446-1B80-4CF4-838D-405D3847A8E3} for site CRP to 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.572+300><thread=3536 (0xDD0)>
Sync time: 0d00h19m46s $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.575+300><thread=3536 (0xDD0)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:06.651+300><thread=3536 (0xDD0)>
Next scheduled sync is a retry sync at 24/07/2012 10:20:06 a.m. $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:11.940+300><thread=3536 (0xDD0)>
Why is this behavior?
Thanks
Doc MX

Hi
Today I think I discovered what was the problem:
I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.
I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.
Thanks to all for your comments.
Doc MX

Help - SQL 2008 - SP4 Install Fails - Server is in script upgrade mode - Server Down

Login failed for user 'CS\XXXXXXXXXXX'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
Clearing tempdb database.
Bits:
Windows 2003 Server Std SP2
SQL Server 2008 SP3
SQL Server has been running without issue. Installed on another SS2K8 SP3 and worked fine.
Any assistance would be appreciated as this issue is causing problems for my user applications.
Thank You
Mark Covian

Set Trace Flag -T902
Start the SQL Server and it shuts down
2015-01-28 09:41:00.00 Server Microsoft SQL Server 2008 (SP4) - 10.0.6000.29 (Intel X86)
Sep 2 2014 22:55:13
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 5.2 <X86> (Build : )
2015-01-28 09:41:00.00 Server (c) 2005 Microsoft Corporation.
2015-01-28 09:41:00.00 Server All rights reserved.
2015-01-28 09:41:00.00 Server Server process ID is 6564.
2015-01-28 09:41:00.00 Server Authentication mode is MIXED.
2015-01-28 09:41:00.00 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2015-01-28 09:41:00.00 Server This instance of SQL Server last reported using a process ID of 7580 at 1/28/2015 9:32:48 AM (local) 1/28/2015 4:32:48 PM (UTC). This is an informational message only; no user action is required.
2015-01-28 09:41:00.00 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
-T902
The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
Adding user 'CS\X910401' to SQLAgentUserRole msdb role...
Performing replication job security meta-data upgrades...
Attempting to load library 'xprepl.dll' into memory. This is an informational message only. No user action is required.
Using 'xprepl.dll' version '2007.100.1600' to execute extended stored procedure 'xp_repl_encrypt'. This is an informational message only; no user action is required.
Error: 515, Severity: 16, State: 2.
Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails.
Error: 912, Severity: 21, State: 2.
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 515, state 2, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Error: 3417, Severity: 21, State: 3.
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/ ] for the SQL Server service.
The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/R:1433 ] for the SQL Server service.
Mark Covian

HELP - SQL Server Express Install Problems

The SQL Server Express completed without error. However, when I tried to connect to the SQLEXPRESS instance I received one of those wonderful MS errors, "Specified file not found". WHAT FILE? (After all these years MS still can't figure out how
to give an error msg. that provides some hint of what's wrong.) Going on, I started the install console and selected the REPAIR option. (It didn't ask what the problem was, it just ran.) It did ask what instance needed repair. I told
it SQLSERVER. It proceeded to repairing it. My first hint that their repair function worked as well as their error handling was when I got the: That share name has already been used (or something like that) error (notice, MS didn't tell me what
share name, or what aspect of the db they were talking about). After pressing OK, the REPAIR function proceeded to run to completion. When I reviewed the REPAIR report I found that three db processes all had the same SHARE NAME ALREADY USED error.
Actually, I thought that it was no big deal. If this was a real REPAIR, it shouldn't matter that the name was already used because everything else should be the same. (I know I'm nigh eve about the
Intricacies of SQL server.) After repairing my installation, I brought up the SQL Server Management Console again. This time, it did not display SQLEXPRESS in the Connect field. I selected the drop down list arrow to see if it was
listed and the list was blank so I entered SQLEXPRESS in the connect field and clicked on the CONNECT button. I got a NETWORK PATH NOT FOUND error. So, before I really mess things up, I thought I should ask if anyone knows what I should do
next. (As an aside, I've pressed the MS Error Message HELP button numerous times abut various errors I've received over the years. Not only are MS error messages useless, their Help Page has never ONCE been able to provide any information
about the encountered error. MS should spend some time and develop some truly helpful error messages as "File not found" and unknown error code 837289 are absolutely useless and especially since their HELP PAGE is never able to provide any
information either. I do wonder how I can get Unknown Error codes from people who wrote the code that raises the error. Don't they document anything?)

I did read the requirements and made sure I met them all. The install package I used was: SQLEXPRADV_x64_ENU.exe. You're correct. I'm not familiar with SQL Server.
I downloaded SQL Server Express and Visual Studio Express to learn and explore because I wanted to learn about the new technology.
After leaving my message, I did some more studying and playing with the system. I managed to figure out that I had to turn on the data base service before I could connect with it. I'm sorry, I don't understand how Microsoft could install a data
base system without turning on its services. Why would I want to install something and NOT use it? The default should be ON and the setup manager should provide a choice to set it to OFF on the configuration page.
My experience is rather dated. I had to retire due to a disability in 2005. I couldn't control my arms and hands. The doctor recently tried a medication again that I had had a severe negative reaction to. He first administered steroids
and started me on a small dose and titrated it up as I was able to handle it. Now I have some days where I have pretty good control — I can print a little but can't write well and other days where I can't print, write, or feed myself.
I have performed many functions. I have been an analyst, a programmer, a data base designer, and a college professor at three different colleges. I've done extensive work in process automation and have even automated the management functions
for a data base system that was used to schedule every aspect of all the aircraft, ranges, and weapons development processes on Eglin AFB. I also wrote major pieces of the code used by the system and trouble shot and corrected functions written by other
programmers. The system supported over 300 users a day on two bases. Unfortunately it was developed in Fortran on a VAX and with VB6 and MS Access using VBA, Queries, Tables and Forms on networked PCs.
I plan to do a lot of reading. I'll also be looking at the Microsoft sites for a sample DB and lessons to go with it. I am a little frustrated with how information is organized on the web. The other night I needed to find some information
about something from Microsoft. It took me almost two hours to ask my question in such a way that MS was able to provide what I wanted. I kept asking essentially the same thing, but I had to use the exact phrase MS used on the page. I know
MS is big and they support multiple generations of each product. They have an almost impossible task. I just have to find the various product entry pages.
Thanks for offering your help.

2008-002 install problem

Hi, This seems to be a big problem today. I've been stuck in a startup loop since this morning. I can boot from the leopard DVD, but I cannot get beyond that. I have zapped the PRAM, unplugged all but the standard apple keyboard and mouse. Disk Utility will not complete the verify process (ERROR: underlying task reported failure on exit). or will not let me me mount my HD or do anything at all. It does not even show up in the install screen. It appears as if I have a ruined HD, but it was flawless until I did the security upgrade. Any help or suggestion would be appreciated.
I have nightly backups (offsite) but that is still a whole lost day.
Thanks
John Paul
Message was edited by: jpminda

The reason you have the problem is because you had an underlying problem with either your directory structure or formatting.
That is why you got the error message. There was likely more in the message window about nodes or b trees or something else that it identified as corrupt or missing.
This meant that the underlying structure is not fit to install anything onto, at this time.
The erase and install was what the doctor ordered and you should not have any further problems unless you have a failing hard drive.
In disk utility, if you click on the long name for the hard drive, the S.M.A.R.T status of the drive, which is located center bottom of the window, will tell you if the hard drives self diagnostics have detected any failure.
Self-Monitoring, Analysis, and Reporting Technology
http://en.wikipedia.org/wiki/Self-Monitoring,Analysis,_and_ReportingTechnology

Database sql server 2005 instalation problem.

Dear sir/mam,
I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).

Rajsarawat wrote:
Dear sir/mam,
I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).You have to turn on network (external to your computer) access.
Under programs->sql server look for "surface"

Macbook 13" late 2008, os instalation problem

Hi ,
I had installed a new harddisk for my macbook from the service centre and said that i would install the OS myself, but to my luck the OS disk does not install and i had not taken any back up before i changes the harddisk . can someone adivce me on wat to do Pls ?

Deepak K R wrote:
the OS disk does not install
Welcome to Apple's discussion groups.
What do you see when you try to do the installation? Have you used Disk Utility (under the "Utilities" menu early in the installation process) to partition and format the new drive? For your Mac the partition type should be "GUID Partition Table" and the format should be "Mac OS Extended (Journaled)".

ProApps 2008-03 Install Problem

If I download the package and run it locally I get "You cannot install Compressor 3.0.4 Update on this volume. This is not a supported installation method".
If I allow Software Update to do the download & install it completes normally.
It's essential that I retain control of what goes on and when, as Apple may at any time remove 3.0.4 and replace it with 3.0.5. With many editing clients to take care of it's vital everyone stays on the same revisions, and then move forward in unison once we've evaluated it (rather than a disjointed roll out on the whim of Software Update).
Is there a way I can install from a local copy without relying on Software Update to do it for me?

Resolved.
Download the installer from the FCP update site (license key required). This version installs standalone.

Where is the management Studio for SQL 2008 Express?

Can anyone point me to where I can download the management studio for SQL 2008 Express.
I've downloaded and installed SQL 2008 Express without problem but can't find the management studio.
Help.

Paradox1 said:
The 2008 version of the Management Studio is not a stand alone installation and can only be installed as part of the SQL Server 2008 Express with Tools or Advanced installation.
Like many others, I spent countless hours trying to figure out how to install the Management Studio for SQL Server 2008 Express - Advanced installation (same should apply to the w/ Tools version). What happened in my case was that I installed Visual Studio 2008 Express and during that process a stripped down "Instance" of SQL Server 2008 was installed that did not include the Management Studio. Through much pain and torture I learned that the Management Studio can only be installed during installation of the first instance. To delete that first instance, you must go to "Add or Remove Programs" and remove "Microsoft SQL Server 2008". The removal process will only remove one instance at a time and if you have installed more than one instance you need to keep going until all instances have been removed and the application completely disappears from the Add or Remove Programs" dialog. Note: You do not need to uninstall any of the other SQL Server 2008 applications that also appear in the "Add or Remove Programs" dialog. Then go back through the install process as follows: Double click on SQLEXPRADV_x86_ENU.exe to load the SQL Server Installation Center and then go to Installation > New SQL Server stand-alone installation. Then proceed through all of the installation steps until you get to “Feature Selection” and click on “Select All” to toggle on all of the Shared Features, which should include Management Tools - Basic.Continue the process from there and you should be good to go. Hopefully this will help others to avoid much of the pain that many of us have already experienced.

Problems install SCCM 2012 with remote sql 2008 r2 sp2

I am having issues installing sccm 2012 on a remote sql 2008 r2 sp2 server on a seperate instance.
I get the error "The network path was not found"
if i point it at the primary instance it will let me continue but i cannot install sccm into that instance.
I have turned off dynamic ports and set a static port but I do not see where i can enter that in the installer.
I cannot seem to verify is the ssb port is working correctly or not.
my account is local admin on both servers and a sql sysadm.
There is no firewall between servers.
Any suggestions?
Regards
Don

SPN is setup to AUTO register and is working. remote sql is not a cluster. Windows firewall on both servers is disabled. Sql browser is enabled and started. we have a group for system center that contains site servers and this group
is in the local admin of both servers and sysadm inside of sql server.
Why we are consolidating all or our lesser sql servers into a larger one.
Snipt of the log.
12/12/2012 2:57:37 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The network path was not found.
], Exception details: [System.IO.IOException: The network path was not found.
Server stack trace:
at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.GetSqlConnection(String databaseName, String serverName, Boolean encrypt)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.CheckSqlConnection(String serverName, String instanceName)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SystemCenter.ConfigMgr.Setup.CheckSqlAsync.EndInvoke(IAsyncResult result)
at Microsoft.SystemCenter.ConfigMgr.Setup.DatabasePage.ValidatePage()
at Microsoft.SystemCenter.ConfigMgr.SetupFramework.WizardForm.ActivatePage(String pageId, Boolean goingNext)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)].
12/12/2012 3:01:42 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database ADMIN\master on server YSQL030.srf.local.
12/12/2012 3:01:42 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The network path was not found.
], Exception details: [System.IO.IOException: The network path was not found.

SQL 2008 Problem Calling an SP on an Oracle 10G Linked Server

Hi everyone
I've read through a number of posts on many sites about this issue but haven't found anything that has helped me so far. The machine I'm using is running Microsoft SQL Server 2008 64bit and the linked server I've created to Oracle 10G is using OraOLEDB.Oracle. If I test the connection in SQL Management Studio it succeeds and for any queries I have using OpenQuery to select from the Oracle DB I have no problem getting results.
The Oracle 32bit client and 64bit client versions are installed on the machine.
My problem is that I need to exec an Oracle SP which in turn inserts into various Oracle tables. I previously had this all working fine on 32bit SQL Server 2000 installation connected to Oracle 10G. Using the same code in SQL Server 2008 I get the following error:
Msg 7357, Level 16, State 2, Line 1
Cannot process the object "{CALL INTF.INTF_TW_PO_REQ_INTERFACE.MAIN(NULL, 15.000000, 0.000000, 'BLPO0099998', 'BLPO0099998', '', '', 39804, 21883, 'BLPO0099998', 249, 1, 950, 'Main', 190506, 37336, '1', TO_DATE( '20090706','YYYYMMDD' ), TO_DATE( '20090706','YYYYMMDD' ), 'INCOMPLETE',37336, {RESULTSET 1, P_Success})}". The OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE" indicates that either the object has no columns or the current user does not have permissions on that object
The call is made by the following piece of code in SQL:
SET @execCmd = N'SELECT
P_Success
FROM
OPENQUERY( ORACLE, '''+ @oracleCmd + ''')';
EXECUTE (@execCmd);
Where @oracleCmd = {CALL INTF.INTF_TW_PO_REQ_INTERFACE.MAIN(NULL, 15.000000, 0.000000, ''BLPO0099998'', ''BLPO0099998'', '''', '''', 39804, 21883, ''BLPO0099998'', 249, 1, 950, ''Main'', 190506, 37336, ''1'', TO_DATE( ''20090706'',''YYYYMMDD'' ), TO_DATE( ''20090706'',''YYYYMMDD'' ), ''INCOMPLETE'',37336, {RESULTSET 1, P_Success})}
I also tried using the below snippet from another post I found and got no joy either.
declare @result varchar(255)
exec ('BEGIN
?:= your_SP_Name(''arg1'', ''arg2'', etc);
END;
',@result OUTPUT) at your_LinkedServerName;
select @result;
OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE" returned message "ORA-06550: line 3, column 7:
PLS-00222: no function with name 'INTF_TW_PO_REQ_INTERFACE' exists in this scope
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored".
I can't figure out why it doesn't work in SQL 2008 when it worked fine in SQL 2000 - PLEASE HELP!
Thank you
Alida Hope

Why development on 10g and production on 8i? Either both should be 8i or both should be 10g.
If you will keep production on 8i and development on 10g then you cannot stop such errors as there are features that are enabled by default in 10g and both the versions have very big differences.
Just go ahead and install 8i.

Dg4odbc, unixODBC, freeTDS - connection problems to MS SQL 2008

I am trying to set up a database link between my 64bit Oracle 11g running on CentOS 6.2 and my MS SQL 2008 server running on MS Windows server 2003. I have installed the following -
freeTDS - version 0.91 (64 bit)
unixODBC - version 2.3.1 (64 bit)
I have successfully configured ODBC and freeTDS so that I can connect using isql and query my MSSQL database. The problem I am having is connecting Oracle to MSSQL, I am sure it is a simple configuration error but I have been going round in circles with this and hope someone can help!
freetds.conf
[global]
timeout = 10
connect timeout = 10
text size = 64512
[CERM]
host = 192.168.xxx.xxx
port = 1101
tds version = 7.2
instance = SSLSQLDB
dump file = /tmp/dump.log
odbc.ini
[ODBC Data Sources]
CERM=TDS connection
[CERM]
Servername = CERM
Description = TDS connection
Driver = /usr/local/lib/libtdsodbc.so
UsageCount = 1
FileUsage = 1
[ODBC]
Trace=255
odbcinst.ini
[TDS]
Description = FreeTDS driver for MS SQL
Driver = /usr/local/lib/libtdsodbc.so
Setup = /usr/lib64/libtdsS.so
Trace = Yes
TraceFile = /tmp/freetd.log
FileUsage = 1
[FreeTDS]
Description = FreeTDS driver for MS SQL
Driver = /usr/local/lib/libtdsodbc.so
Setup = /usr/lib64/libtdsS.so
Trace = Yes
TraceFile = /tmp/freetd.log
FileUsage = 1
(Because I have put the actual path to the driver in the odbc.ini file I don;t believe the odbcinst.ini file is actually used)
inithscerm.ora
# This is a sample agent init file containing the HS parameters that
# are needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO=CERM
HS_FDS_TRACE_LEVEL=255
#HS_FDS_TRACE_FILE_NAME = /tmp/hsodbcsql.trc
HS_FDS_SHAREABLE_NAME=/usr/local/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
set ODBCINI=/usr/local/etc/odbc.ini
(my odbc.ini file is located in /usr/local/etc)
listener.ora
# listener.ora Network Configuration File: /usr/oracle/product/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = ssl-oracle.domain)(PORT = 1521))
ADR_BASE_LISTENER = /usr/oracle
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC=
(SID_NAME=hscerm)
(ORACLE_HOME=/usr/oracle/product)
(PROGRAM=dg4odbc)
(ENVS=LD_LIBRARY_PATH = /usr/local/lib:$ORACLE_HOME/lib)
(SID_DESC=
(SID_NAME=PROD)
(ORACLE_HOME=/usr/oracle/product)
tnsnames.ora
# tnsnames.ora Network Configuration File: /usr/oracle/product/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
PROD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ssl-oracle.domain)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = PROD.DOMAIN)
hscerm=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST=ssl-oracle.domain)(PORT=1521))
(CONNECT_DATA= (SID=hscerm))
(HS=OK)
right - I can tnsping my hscerm instance and that returns ok so I'm fairly sure the configuration is fine for both tnsnames.ora and listener.ora. I can isql connect to the ODBC defined name for the the MSSQL database. but when I create a database link in Oracle and then test it I get the following trace output :-
[ODBC][14030][1339512618.356535][SQLSetConnectAttrW.c][332]
Entry:
Connection = 0x2054640
Attribute = SQL_ATTR_AUTOCOMMIT
Value = (nil)
StrLen = -5
[ODBC][14030][1339512618.356616][SQLSetConnectAttrW.c][616]
Exit:[SQL_SUCCESS]
[ODBC][14030][1339512618.356984][SQLDriverConnectW.c][290]
Entry:
Connection = 0x2054640
Window Hdl = (nil)
Str In = [DNCR;I=APDagj20][length = 30]
Str Out = 0x2053408
Str Out Max = 1024
Str Out Ptr = 0x7fff6d305770
Completion = 0
[ODBC][14030][1339512618.357030][SQLDriverConnectW.c][500]Error: IM002
[ODBC][14030][1339512618.357115][SQLGetDiagRecW.c][508]
Entry:
Connection = 0x2054640
Rec Number = 1
SQLState = 0x7fff6d3053d0
Native = 0x7fff6d3051c4
Message Text = 0x7fff6d3051d0
Buffer Length = 510
Text Len Ptr = 0x7fff6d305420
[ODBC][14030][1339512618.357153][SQLGetDiagRecW.c][550]
Exit:[SQL_SUCCESS]
SQLState = IM002
Native = 0x7fff6d3051c4 -> 0
Message Text = [[unixODBC][Driver Manager]Data source name not found, and no default driver specified]
[ODBC][14030][1339512618.357197][SQLGetDiagRecW.c][508]
Entry:
Connection = 0x2054640
Rec Number = 2
SQLState = 0x7fff6d3053d0
Native = 0x7fff6d3051c4
Message Text = 0x7fff6d3051d0
Buffer Length = 510
Text Len Ptr = 0x7fff6d305420
[ODBC][14030][1339512618.357228][SQLGetDiagRecW.c][550]
Exit:[SQL_NO_DATA]
[ODBC][14030][1339512618.357291][SQLDisconnect.c][208]
Entry:
Connection = 0x2054640
[ODBC][14030][1339512618.357321][SQLDisconnect.c][237]Error: 08003
[ODBC][14030][1339512618.357387][SQLFreeHandle.c][284]
Entry:
Handle Type = 2
Input Handle = 0x2054640
Now I can clearly see the error "Data source name not found, and no default driver specified" which according to all the documentation means that the entry HS_FDS_CONNECT_INFO=CERM does not match the entry in my odbc.ini file ([CERM]) but for the life of me I can;t see why they don;t match ??
Any help greatly received.

Yeah I verified with isql but I have changed the odbc.ini file as you suggested -
[root@ssl-oracle ~]# more /usr/local/etc/odbc.ini
[ODBC Data Sources]
CERM=TDS connection
[CERM]
Server = 192.168.xxx.xxx
Driver = /usr/local/lib/libtdsodbc.so
Database = sqlb00
Port = 1101
TDS_Version = 8.0
QuotedId = YES
[ODBC]
Trace=255
[root@ssl-oracle admin]# more inithscerm.ora
# This is a sample agent init file containing the HS parameters that
# are needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO=CERM
HS_FDS_TRACE_LEVEL=255
#HS_FDS_TRACE_FILE_NAME = /tmp/hsodbcsql.trc
HS_FDS_SHAREABLE_NAME=/usr/local/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
HS_LANGUAGE=american_america.we8mswin1252
HS_NLS_NCHAR=UCS2
set ODBCINI=/usr/local/etc/odbc.ini
[root@ssl-oracle admin]# osql -S CERM -U sa -P supersecretpassword
checking shared odbc libraries linked to isql for default directories...
trying /tmp/sql ... no
trying /tmp/sql ... no
trying /usr/loc ... no
trying /tmp/sql.log ... no
trying /home ... no
trying /.odbc.ini ... no
trying /usr/local/etc ... OK
checking odbc.ini files
cannot read "/root/.odbc.ini"
reading /usr/local/etc/odbc.ini
[CERM] found in /usr/local/etc/odbc.ini
found this section:
[CERM]
Server = 192.168.xxx.xxx
Driver = /usr/local/lib/libtdsodbc.so
Database = sqlb00
Port = 1101
TDS_Version = 8.0
QuotedId = YES
looking for driver for DSN [CERM] in /usr/local/etc/odbc.ini
found driver line: " Driver = /usr/local/lib/libtdsodbc.so"
driver "/usr/local/lib/libtdsodbc.so" found for [CERM] in odbc.ini
found driver named "/usr/local/lib/libtdsodbc.so"
/usr/local/lib/libtdsodbc.so is an executable file
"Server" found, not using freetds.conf
Server is "192.168.xxx.xxx"
looking up hostname for ip address 192.168.xxx.xxx
Configuration looks OK. Connection details:
DSN: CERM
odbc.ini: /usr/local/etc/odbc.ini
Driver: /usr/local/lib/libtdsodbc.so
Server hostname: ssl-database.domain
Address: 192.168.xxx.xxx
Attempting connection as sa ...
+ isql CERM sa supersecretpassword -v
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
SQL>
sql.log
[ODBC][31473][1339581606.488571][SQLSetConnectAttr.c][396]
Entry:
Connection = 0x26c2a30
Attribute = SQL_ATTR_AUTOCOMMIT
Value = (nil)
StrLen = -5
[ODBC][31473][1339581606.488638][SQLSetConnectAttr.c][681]
Exit:[SQL_SUCCESS]
[ODBC][31473][1339581606.488924][SQLDriverConnect.c][726]
Entry:
Connection = 0x26c2a30
Window Hdl = (nil)
Str In = [DSN=CERM;UID=SA;PWD=**********][length = 30]
Str Out = 0x26c4b18
Str Out Max = 1024
Str Out Ptr = 0x7fff12846560
Completion = 0
UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE'
DIAG [01000] [FreeTDS][SQL Server]Unknown host machine name.
DIAG [08001] [FreeTDS][SQL Server]Unable to connect to data source
[ODBC][31473][1339581606.491276][SQLDriverConnect.c][1353]
Exit:[SQL_ERROR]
[ODBC][31473][1339581606.491358][SQLGetDiagRec.c][680]
Entry:
Connection = 0x26c2a30
Rec Number = 1
SQLState = 0x7fff128461c0
Native = 0x7fff12845fb4
Message Text = 0x7fff12845fc0
Buffer Length = 510
Text Len Ptr = 0x7fff12846210
[ODBC][31473][1339581606.491395][SQLGetDiagRec.c][717]
Exit:[SQL_SUCCESS]
SQLState = 08001
Native = 0x7fff12845fb4 -> 0
Message Text = [[unixODBC][FreeTDS][SQL Server]Unable to connect to data source]
[ODBC][31473][1339581606.491442][SQLGetDiagRec.c][680]
Entry:
Connection = 0x26c2a30
Rec Number = 2
SQLState = 0x7fff128461c0
Native = 0x7fff12845fb4
Message Text = 0x7fff12845fc0
Buffer Length = 510
Text Len Ptr = 0x7fff12846210
[ODBC][31473][1339581606.491493][SQLGetDiagRec.c][717]
Exit:[SQL_SUCCESS]
SQLState = 01000
Native = 0x7fff12845fb4 -> 20013
Message Text = [[unixODBC][FreeTDS][SQL Server]Unknown host machine name.]
[ODBC][31473][1339581606.491528][SQLGetDiagRec.c][680]
Entry:
Connection = 0x26c2a30
Rec Number = 3
SQLState = 0x7fff128461c0
Native = 0x7fff12845fb4
Message Text = 0x7fff12845fc0
Buffer Length = 510
Text Len Ptr = 0x7fff12846210
[ODBC][31473][1339581606.491558][SQLGetDiagRec.c][717]
Exit:[SQL_NO_DATA]
[ODBC][31473][1339581606.491623][SQLDisconnect.c][208]
Entry:
Connection = 0x26c2a30
[ODBC][31473][1339581606.491652][SQLDisconnect.c][237]Error: 08003
[ODBC][31473][1339581606.491719][SQLFreeHandle.c][284]
Entry:
Handle Type = 2
Input Handle = 0x26c2a30
[ODBC][31473][1339581606.491750][SQLFreeHandle.c][333]
Exit:[SQL_SUCCESS]
[ODBC][31473][1339581606.493083][SQLFreeHandle.c][219]
Entry:
Handle Type = 1
Input Handle = 0x26abfe0
I can also ping both the hostname and ip address of the MSSQL server.

Error installing SQL 2008 R2 anyversion. Error code: 1605

SQL Server Setup has encountered the following error:
MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{DF167CE3-60E7-44EA-99EC-2507C51F37AE}'. Error code: 1605..
What I've done so far:
1) Had to re-install Windows 7 because I kept getting a pop up that said my windows was unregistered, which it wasn't (known bug) so I re-installed as per MS recommendation.
2) Un-installed SQL 2008 + ran Microsoft Fix It tool.
3) Tried to re-install but I get this error.
4) After I got the error I deleted all the registry entries per instructions available where other's have posted this same problem. Started by reversing key and deleting what I found in the registry.
5) When I continued to get the error I renamed the registry directory UpgradeCodes to UpgradeCodes.old. Still fails with the same error.
6) I've rebooted after every step and I've repeated this many times...
In all cases when I try to re-install it fails with Error code: 1605. At this point when I search the registry for the reversed key it is not found. It's gone.
Not sure what to do next.
Any suggestions would be appreciated. Thx

Hi gridmaster54,
According to your description, you fail to install SQL Server 2008 R2 with the error code 1605. Please help to post SQL Server setup error log for analysis. By default, SQL Server setup summary and detail logs are located in C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log.
Based on my research, this issue could be due to the remains of a previous unfinished installation. To troubleshoot the issue, please pay attention to the points below.
1.Make sure that your account has admin rights and you right-click the setup.exe and choose “Run as administrator” to install SQL Server.
2.Make sure that your account has full control over the following key: HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\
Regards,
Michelle Li

SQL 2008 R2 Install problems

Similar Messages

Maybe you are looking for