SQL 2012 Installation Error

Good Day
I am trying to install SQL 2012.
during the installation process it halts and I receive the following message:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
Setup encountered a failure while running job UpdateResult.
Error code 0x876E0003.
I have spent hours looking through help blogs and other resources trying to find answers and help but have not been able to find a solution..!
Any advise or how to work around this would be greatly appreciated!
Thank you.

Hi BrendanDev,
According to the error message, the issue may occur due to the permission issue with Windows update.
In this case, If you have the DefaultSetup.ini file in the \x86 or \x64 folders at the root level of the SQL Server source media, please open the DefaultSetup.ini file, and then add the UpdateEnabled or UpdateSource parameters to the file. If the DefaultSetup.ini
file does not exist, we can create it and copy it to the \x86 and \x64 folders at the root level of the SQL Server source media. And then we need to modify the "DefaultSetup.ini" file and set the switch "UpdateEnabled=False" which skips the product updates
in the installation.
For the detailed information, please refer to the link below:
http://blogs.msdn.com/b/petersad/archive/2011/07/13/product-update-in-sql-server-code-named-denali.aspx
If you need more assistance, please feel free to let me know. 
Regards,
Heidi Duan

Similar Messages

  • SQL 2012 installation Error-The MOF compiler could not connect with the WMI server

    Hi all,
      I am getting below error while installing SQL 2012 Dev edition in Win 8.1 Pro.
    I am facing lot of issues while installing SQL 2012 in Win 8.1 Pro.Any other steps we need to take to install SQL 2012 in Win 8.1.
    Thanks in advance. 

    Installation:
    Installation for SQL Server 2012
    Hardware and Software Requirements for Installing SQL Server 2012
    Installing the .NET Framework 3.5 on Windows 8 or 8.1
    About "The MOF compiler could not connected with the WMI server" error message:
      Please, verify the Windows Management Instrumentation has status "started" and is set with Startup Type "Automatic". (Alberto Morillo, SQLCoffee.com).
    José Diz     Belo Horizonte, MG - Brasil

  • SharePoint 2010 with SQL Reporting Services 2012 "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"

    i have a small sharepoint farm "2 servers" (WFE) and SQL Server 2012 ,
    i installed rsSharePoint for reporting services , as a read the Reporting services is Application Service  with SQL 2012 not as SQL 2008 R2 with SharePoint integrated mode, so after installation when am trying to configure the  SQL Server
    Reporting Services Application services i got the below error :
    "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"
    any kind of help would be much appreciated .

    I'm having the same issue, but to me it seems like the instructions I've seen are all over the place.  I already have SP 2013 and SQL 2012 SP 1 installed.  I already added the features for Reporting Services - Sharepoint and Reporting Services
    Add-in for SharePoint Products.  I didn't see the Reporting Service service in CA, so I ran the powershell scripts to add SPRSService and SPRSServiceProxy. 
    My initial quest, was to get the BI features enabled, which took me on the journey of adding the Report Services, then I got the error.
    Then when I read this about installing the BI features
    http://blogs.msdn.com/b/querysimon/archive/2012/11/26/installing-the-bi-features-of-sharepoint-2013.aspx, which I already had SQL and SP installed.  Do I have to rerun and selct the SQL Server PowerPoint for SharePoint option?  I have the PowerPoint
    Configuration Tool on my SQL server, I run it and I get PowerPivot for SP 2013 Configuranoi is missing prerequisits:  SP 2013 EE is required.  Which I have EE.
    Is Reporting Services different or in addition to the BI Feature (PowerPivot)? 
    Have I missed a step?
    Thanks for you help.
    Kim
    Kim.Williams

  • Sql server 2012 installation error

    can someone please tell me why i am getting an error when i am trying to install sql 2012 SP1. it when i get to the installation  it says "sql server Setup has encountered the following error. hexadecimal value 0x00, is an invalid character.Line
    1, position 51471. error code 0x84B10001.

    Hi vijatkumar.ptl,
    According to your description and your error message, when you install SQL Server 2012, check if splinters of an MSDE instance (Microsoft Desktop Engine) was left over from other program. If this hidden instance exists, and the installer perform the RunDiscoveryAction
    process, the issue will occur. So I recommend you manually remove a Microsoft SQL Server
     Desktop Engine instance (MSDE) by using Add/Remove Programs in Control Panel, and so on, then reinstall again.
    There is a similar issue about SQL Server 2012 setup issue, you can refer to the following posts.
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/72fbd726-730b-4aef-9db1-aeb8bfb5d334/sql-2012-setup-issues-hexadecimal-value-0x00-is-an-invalid-character
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f37e18eb-f1ab-4106-83f6-8bbf04d6a41a/setup-failed-0x84b10001-sql-2012-hexadecimal-value-0x00-is-an-invalid-character-line-1-position?forum=sqlsetupandupgrade
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Object reference not set to an instance of an object. Unable to finish the SQL 2012 installation on a VM Machine

    Hi, My name is Leonard and I am studying SQL. I have downloaded the newest MS SQL 2012 and also MS 2012 Hyper-V. I have set a MS 2012 Hyper-V on a laptop with AMD Turion 64 X2 and 3G of RAM (Planing
    to add more to max at 8G).
    Following the instructions in the free online
    Administering Microsoft SQL Server 2012 Databases” Training Kit, I have set 6 virtual machines as instructed in the Training Kit. While the installation of the MS Server Core 2008 R2 SP1 completed with no
    problem, the same cannot be said for the SQL Server 2012 installation. I have encountered an error that I have not seen anyone address in any of the SQL web forums.
    After running the unattended setup instruction (Setup.exe /qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER
    /SQLSVCACCOUNT="Njowa\Pa$$worD>" /SQLSVCPASSWORD=" Pa$$worD” /SQLSYSADMINACCOUNTS="Njowa\lenny#4!@" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"
     /IACCEPTSQLSERVERLICENSETERMS) this is what I get after a series SQL setup
     initiation windows popups then disappears.
    The following error occurred:
    Object reference not set to an instance of an object.
    Error result: -2147467261
    Result facility Code: 0
    Result error Code: 16387
    Please review the summary.txt log for further details
    My question is: What instance of an object is not properly initialize in the Setup instructions

    Hello,
    Please note that SQL Server requires at least 1 GB of RAM. The operating system (Windows Server) requires 2 GB of RAM (recommended) or 512 MB (minimum). This means any virtual machine that will receive the installation of a SQL Server instance requires 1.5
    or 2 GB at least.
    The behavior of SQL Server setup tells me that the virtual machine does not have enough memory assigned or .NET Framework 3.5 was not enable on Control Panel->Program
    and Features before trying to install SQL Server.
    The following thread is about another possible cause of this error:
    http://social.msdn.microsoft.com/Forums/mr-IN/sqlsetupandupgrade/thread/575d3025-69f5-4152-a473-44496b008811
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

    Hi All
    Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server).  Im trying to install to the SQL Default server instance, note that the server also has a named instance
    which hosts the SCOM databases.  SQL Reporting Services is up and running fine (can access the web urls etc).  Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install.  Ive checked that the Firewall
    is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
    The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
    Configurations document for further information.
    Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error.  The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
    this would be the case (same account that I used for SQL install etc).  Any help much appreciated! : )
    Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:51:46]: Debug: :CheckPrerequisites:  IsComputerNameValidTitle: Passed
    [11:51:46]: Debug: :
    [11:51:46]: Debug: :**************************************************
    [11:51:46]: Debug: :**************************************************
    [11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
    [11:51:46]: Debug: :
    [11:51:46]: Debug: :CheckPrerequisites:  AVIcodeAgentCheck: Passed
    [11:51:46]: Debug: :
    [11:51:46]: Debug: :**************************************************
    [11:51:46]: Always: :CheckPrerequisites: Return Value 0
    [11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
    [11:51:48]: Always: :Entering Page: ShortEulaPage
    [11:51:48]: Always: :Displaying localized EULA for localization: en
    [11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
    [11:51:49]: Info: :Info:User has agreed to EULA.
    [11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
    [11:52:08]: Info: :Info:Management Server matches the current version of setup.
    [11:52:08]: Always: :Entering Page: SelectReportingInstance
    [11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
    [11:52:08]: Info: :Attempting to get the SSRS version from:
    \\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
    [11:52:08]: Debug: :Path is
    \\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
    [11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
    [11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
    [11:52:08]: Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
    [11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
    [11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
       at System.Version.Parse(String input)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
    [11:52:11]: Info: :Attempting to check SRS version
    [11:52:11]: Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
    [11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
    [11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
       at System.Version.Parse(String input)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
    [11:52:28]: Info: :The user canceled setup
    [11:52:28]: Always: :Begin: Property bag dump.
    [11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
    [11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
    [11:52:28]: Always: : [0] = ActionAccountPassword
    [11:52:28]: Always: : [1] = DASAccountPassword
    [11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
    [11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
    [11:52:28]: Always: :path = F:\Setup\AMD64\
    [11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
    [11:52:28]: Always: :ArchitectureIs64Check = True
    [11:52:28]: Always: :OperationManagerAgentInstalled = 1
    [11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
    [11:52:28]: Always: : [0] = OMCONSOLE
    [11:52:28]: Always: : [1] = OMSERVER
    [11:52:28]: Always: : [2] = OMWEBCONSOLE
    [11:52:28]: Always: : [3] = OMREPORTING
    [11:52:28]: Always: :install = 1
    [11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
    [11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
    [11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
    [11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
    [11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
    [11:52:28]: Always: :ScreensLoaded = 1
    [11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
    [11:52:28]: Always: : [0] = OMREPORTING
    [11:52:28]: Always: :OMREPORTING = 1
    [11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
    [11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
    [11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
    [11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
    [11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
    [11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
    [11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
    [11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
    [11:52:28]: Always: :PrerequisiteState = Passed
    [11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
    [11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
    name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
    [11:52:28]: Always: :End XML property
    [11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
    [11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
    [11:52:28]: Always: :UserCanceledInstall = 1
    [11:52:28]: Always: :InstallSuccess = 1
    [11:52:28]: Always: :End: Property bag dump.
    [11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
    [11:52:28]: Always: :Application Ended: Successful
    [11:52:28]: Always: :
    [2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

    Hi,
    According to the error message:
    [11:52:11]: Error: :getSQLInstanceVersion:  Unable to find the SRS Instance Key: MSSQLSERVER
    [11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
    [11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
    The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
    http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
    In addition, here is thread for your reference also:
    http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
    Regards,
    Yan Li
    Regards, Yan Li

  • 2008 R2 upgrade to SQL 2012 validation error - No Features Selected

    I need a work-around for a known bug.  Some features of Server 2008 R2 Enterprise install an instance of SQL Server.  I'm attempting to upgrade the in-place instance to SQL 2012 Express.  After selecting 'Upgrade', it returns this error:
    Upgrade to SQL Server 2012
    There are validation errors on this page.  Click OK to close this dialog box.  Review errors at the bottom of the setup page, then provide valid parameters or click Help for more information.
    There are no features selected for upgrade.
    In researching, I find this is a known problem in which the hotfix is available in a cumulative update.  The 2419 build updates the released 2100 build.  My problem now is that applying the cumulative update requires that SQL 2012 already be installed.
    What is the correct procedure for upgrading the in-place SQL instance to 2012 SQL Express?
    Beware of unmoderated moderators in the Expression Web forums.

    One of us is confused.... likely me.  The SQL currently installed is the built-in SQL of Windows Server 2008 R2 Enterprise.  It is not SQL Enterprise.  I understand it to be a limited variation called SSEE, SQL Server Embedded Edition. 
    I believe the installation of this variation can be triggered by installing IIS or WSUS.  The instance name is Microsoft##SSEE.
    Nevertheless, there must be a proper way to install SQL 2012 Express, migrate, and uninstall the Windows Internal Database SQL 2005.  Where can I find the correct procedure for upgrading the in-place SQL instance to 2012 SQL Express?
    Hi backup,
    According to your description, I recommend you install SQL Server 2012 Express directly. Before installing, you should note the
    hardware and software requirements, for example, you need to download and install Microsoft .Net Framework 3.5 SP1 and Windows Installer 4.5.
    There is a process of installing SQL Server 2012 Express, you can review it.
    http://www.jsinh.in/2012/09/install-sql-server-2012-express-step-by-step/
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SQL 2012 installation for Failover Cluster failed

    While installation of SQL 2012 on FOC validation fails on "Database Engine configuration" page with following error:
    The volume that contains SQL Server data directory g:\MSSQL11.MSSQLSERVER\MSSQL\DATA does not belong to the cluster group.
    Want to know how does SQL installation wizard queries volumes configured with Failover Cluster. does it:
    - Enumerate "Physical Disk" resources in FOC
    - does it enumerate all Storage Class resources in FOC for getting the volume list
    - or it depends on WMI (Win32_Volume) to get volumes ?
    The wizard correctly discovers volume g:\ in its FOC group on "Cluster Resource Group" and "Cluster Disk Selection" page. but gives the error on Database configuration page.
    Any help in this would be appreciated.
    Thanks in advance
    Rakesh
    Rakesh Agrawal

    Can you please check if there is any disk in the cluster which is not in online state? Please run below script following the steps.
    1. Save a script as "Disk.vbs" and use
    use CSCRIPT to run it.
    2. Syntax: CSCRIPT <Disk.vbs> <Windows Cluster Name>
    < Script>
    Option Explicit
    Public objArgs, objCluster
    Public Function Connect()
    ' Opens a global cluster object. Using Windows Script Host syntax,
    ' the cluster name or "" must be passed as the first argument.
    Set objArgs = WScript.Arguments
    if objArgs.Count=0  then
     wscript.Echo "Usage Cscript  <script file name>  <Windows Cluster Name> "
     WScript.Quit
    end IF
    Set objCluster = CreateObject("MSCluster.Cluster")
    objCluster.Open objArgs(0)
    End Function
    Public Function Disconnect()
    ' Dereferences global objects.  Used with Connect.
     Set objCluster = Nothing
     Set objArgs = Nothing
    End Function
    Connect
    Dim objEnum
    For Each objEnum in objCluster.Resources
     If objEnum.ClassInfo = 1 Then
      WScript.Echo ObjEnum.Name
      Dim objDisk
      Dim objPartition
      On Error Resume Next
       Set objDisk = objEnum.Disk
       If Err.Number <> 0 Then
        WScript.Echo "Unable to retrieve the disk: " & Err
       Else
        For Each objPartition in objDisk.Partitions
         WScript.Echo objPartition.DeviceName
        Next
       End If
     End If
    Next
    Disconnect
    </Script>

  • SQL 2012 standart. error when installing

    hello there I'm having trouble installing SQL server 2012. it says unauthorized action during process.
    trying to do repair and no good
    the error log is here :
    https://onedrive.live.com/redir?resid=1457F260708DF6F6!84695&authkey=!AEpBM0tn2dv_HHw&ithint=file%2ctxt
    any idea how to resolve this. thanks in advance

    Hi,
    If you check option suggested by SQL Server intallation it says repair
    Overall summary:
    Final result: Failed: see details below
    Exit code (Decimal): -2068119551
    Start time: 2015-03-14 07:00:06
    End time: 2015-03-14 07:59:04
    Requested action: Repair
    And I agree you should repair because of following in summary logs
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2012 <Unconfigured> MSSQL11.MSSQLSERVER Database Engine Services 1033 11.2.5058.0 No No
    SQL Server 2012 <Unconfigured> MSSQL11.MSSQLSERVER SQL Server Replication 1033 11.2.5058.0 No No
    SQL Server 2012 <Unconfigured> MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033 11.2.5058.0 No No
    The instance name is coming Unconfigured, I dont know what that exactly means but gives m hunch that SQL Server is configured incorrectly so you must repair it.  You already have instance of SQL Server 2012 standard installed if you see "Product
    Features discovered " section in errorlog.
    To repair SQL Server installation See
    Rapair SQL Server 2012 Installation
    The error "Attempt to perform unauthorized operation' is wide and can have many reasons
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • SQL 2012 - SSIS Error -The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.

    Hi guys 
     Trying to run this package on SQL 2012 agent  and getting below error . No more details I could find so far.
    The step did not generate any output.  The return value was unknown.  The process exit code was -1073741819.  The step failed.
    About Package - Its connecting to different version (2000,2005,2008,2008R2,2012) servers and putting Jobs information into one Database table.  
    Any workaround or fix ?
    Thanks
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

    New package or one that used to work? Connecting how? How does it poll?
    On the surface it is an error from a memory space of the binary/non-managed code, so nothing can be really concluded based on what you decided to share with us.
    Arthur My Blog
    So Same package is working fine from my local machine which has SQL 2008 R2 and SQL 2012 installed. I am trying to push the package on server which has sql server 2012 Installed . 
    I don't see any error .
    I ran package manually from server using SQL Data tools and ran successfully...
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

  • SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    Hi,
    I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
    setup rolls the SCOM install back.
    Has anyone seen this issue before or know how to help resolve it?
    Appreciate your help, below is the SCOM installation log:
    Thanks
    Marc
    [13:27:27]: Always: :Creating Database: OperationsManagerDW
    [13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    : Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
    [14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
    [14:55:33]: Error: :InnerException.StackTrace:
    [14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
    [14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:55:33]: Error: :Exception running sql string
    DECLARE @sql NVARCHAR(MAX);
    SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
        ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
        LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
    EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    [14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
    [14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
    [14:55:33]: Error: :InnerException.StackTrace:
    [14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired.  The timeout period elapsed prior to completion
    of the operation or the server is not responding.
    [14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
    String logPath)
    [14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
    [14:55:33]: Always: :InnerException.StackTrace:
    [14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired.  The timeout period elapsed prior to completion of the operation or
    the server is not responding.
    [14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
    String logPath)
       at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
    [14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
    [14:55:33]: Error: :InnerException.StackTrace:
    [14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
    [14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
    [14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
    [14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
    [14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item.  Setting rollback.
    marc nalder

    Hi,
    Based on the log, I recommend you use the following way to test SQL connectivity.
    You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
    if it fails to connect.
    For more information, please review the link below:
    The easy way to test SQL connectivity
    http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SQL 2012 Installation

    Hello,
    I'm reading the Hardware and Software requirements to install  SQL Server 2012 and I´ve read the this point:
    -The installation of SQL Server 2012 fails if you launch the setup through Terminal Services Client. Launching SQL Server Setup through Terminal Services Client is not supported.
    Anybody has found with this scenario?

    Hi Ruben,
    People have faced issues while running setup of MSSQL 2012 using Terminal services Hardware and Software Requirements for Installing SQL Server 2012.
    Similar issue is discussed and resolved here
    SQL Server 2012 setup fails immediately (Error result: -2067529723)
    Best option to take remote desktop of the server and then perform installation using Administrator login.
    Hope this helps.
    Regards,
    Deepak Kori

  • SQL 2012 Installation - ProductVersion?

    I've been trying to install SQL Server 2012 on a brand new server for days. At first I was getting an error regarding not being able to find certain files - this problem exactly: http://stackoverflow.com/questions/11724160/installing-sql-server-2012-error-the-system-cannot-open-the-device-or-file-spec,
    but after trying multiple times, I finally remoted into the server and ran the installation from the CD. From one error to this new one.
    SQL Server Setup has encountered the following error:
    1: 2228 2: D:\1033_ENU_LP\x64\setup\x64\sqlls.msi 3: Property 4: SELECT `Value` FROM `Property` WHERE `Property` = 'ProductVersion' .
    We have a site license for SQL so the CD and key were provided to me. I saw one solution online regarding finding the product code and then looking in the registry. I've seen a bunch of upgrade codes in DLL files (on the CD), but not a product code, and
    if I'm supposed to use one of those to lookup in the registry, I don't know which. Also, the product codes from the example solutions look nothing like my product key, so I'm assuming they're the same thing.
    Any help would be GREATLY appreciated. The sooner I can install this, the sooner our pharmacy can have a working server.

    Hi Courtney Kinder,
    I’m writing to follow up with you on this post. Was the problem resolved?
     If not, I recommend you uninstall SQL Server 2012 completely and reinstall again. According to your description, when you install SQL Server 2012 from the CD, the error will occur. As other post, you should help us to collect the detailed error
    message, it is very useful for our research.
    In an clean server, you install SQL Server 2012, we need to verify if it meet the hardware and software requirements in the server. You can review the following
     article about step by step installation guide for SQL Server 2012.
    http://sivasqlbi.blogspot.com/2012/03/sql-server-step-by-step-installation.html
    In addition, about finding the product key from an installed instance, you can use T-SQL script or a power shell script. For more information, you can review the following post.
    http://social.msdn.microsoft.com/Forums/en-US/0cb2286a-7d0c-49ad-8248-aa4a0e381e52/finding-sql-server-2008-product-key-from-an-installed-instance?forum=sqlgetstarted
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Using MSXML2.ServerXMLHttp in MS SQL 2012 - receiving error "The Parameter is incorrect".

    I have a procedure used to make http post requests to a REST web service external to my SQL server, using MSXML2.ServerXMLHttp via POST request. This procedure works without issue in SQL 2008 r2, but upon upgrade to 2012, begins to fail with the message
    : "The Parameter is incorrect."
    It is failing when I attempt to exec the 'send' method on line 137. I cannot find any documentation about how the MSXML2.ServerXMLHttp object needs to be treated differently in 2012. I found a similar question here: http://social.technet.microsoft.com/Forums/sqlserver/en-US/a6de1eea-5fe9-4087-809b-524c98f20a4d/msxml6dll-methodsend-dont-work-in-windows-server-2012-and-sql-2008r2?forum=sqlxml 
    But it isn't resovled - just indications to file a bug report - and one solution that says to just copy the DLL from 2008 over to 2012 to fix the issue. Is that really the right solution here or does someone have information on how to do this properly with
    2012?
    Here is my procedure:
    CREATE procedure [dbo].[HTTP_REQUEST](@response varchar(4000) out, 
    @method varchar(64),
    @p1name varchar(256) = null,
    @p1value varchar(max) = null,
    @p2name varchar(256) = null,
    @p2value varchar(max) = null,
    @p3name varchar(256) = null,
    @p3value varchar(max) = null,
    @p4name varchar(256) = null,
    @p4value varchar(max) = null,
    @p5name varchar(256) = null,
    @p5value varchar(max) = null,
    @p6name varchar(256) = null,
    @p6value varchar(max) = null,
    @parent_table varchar(30) = null
    As
    Declare
    @obj int
    ,@hr int
    ,@status int
    ,@msg varchar(255)
    ,@apiKey varchar (64)
    ,@params varchar (max)
    SET @apiKey = (Select a.default_value from T_DEFAULTS a WHERE a.parent_table = @parent_table AND a.field_name = 'm2apiKey')
    SET @params = ''
    If @apiKey is null
      Begin
    select @msg = 'Invalid mail2 APIKey'
    RAISERROR(@msg, 11, 2) WITH SETERROR
    return -101
      End
    If @method is null
      Begin
    select @msg = 'No valid mail2 API method provided'
    RAISERROR(@msg, 11, 2) WITH SETERROR
    return -101
      End
    exec @hr = sp_OACreate 'MSXML2.ServerXMLHttp', @obj OUT
    if @hr <> 0 begin Raiserror('sp_OACreate MSXML2.ServerXMLHttp.3.0
    failed', 16,1) return end
    exec @hr = sp_OAMethod @obj, 'open', NULL, 'POST', 'http://api.someapiurl.net/REST/', true
    if @hr <>0 begin set @msg = 'sp_OAMethod Open failed' goto eh end
    exec @hr = sp_OAMethod @obj, 'setRequestHeader', NULL, 'Content-Type',
    'application/x-www-form-urlencoded'
    if @hr <>0 begin set @msg = 'sp_OAMethod setRequestHeader failed' goto
    eh end
    --Set Timeouts
    exec @hr = sp_OAMethod @obj, 'setTimeouts',NULL,5000,5000,10000,10000
    if @hr <>0 begin set @msg = 'sp_OAMethod setTimeouts failed' goto
    eh end
    --Add Method
    SET @params = '&method='+@method
    --Add API key
    SET @params = @params + '&key='+@apiKey
    --Add p1 if present
    IF @p1name IS NOT NULL
    BEGIN
    SET @params = @params + '&' + @p1name + '=' + @p1value
    END
    --Add p2
    IF @p2name IS NOT NULL
    BEGIN
    SET @params = @params + '&' + @p2name + '=' + @p2value
    END
    --Add p3
    IF @p3name IS NOT NULL
    BEGIN
    SET @params = @params + '&' + @p3name + '=' + @p3value
    END
    --Add p4
    IF @p4name IS NOT NULL
    BEGIN
    SET @params = @params + '&' + @p4name + '=' + @p4value
    END
    --Add p5
    IF @p5name IS NOT NULL
    BEGIN
    SET @params = @params + '&' + @p5name + '=' + @p5value
    END
    --Add p6
    IF @p6name IS NOT NULL
    BEGIN
    SET @params = @params + '&' + @p6name + '=' + @p6value
    END
    --SELECT @params
    --Send the request
    exec @hr = sp_OAMethod @obj, send, NULL, @params
    if @hr <>0 begin set @msg = 'sp_OAMethod Send failed' goto eh end
    --Get the status
    exec @hr = sp_OAGetProperty @obj, 'status', @status OUT
    if @hr <>0 begin set @msg = 'sp_OAGetProperty read status failed on get status' goto
    eh
    end
    if @status <> 200 begin set @msg = 'sp_OAMethod http status ' +
    str(@status) goto eh end
    if @status = 200 begin print 'sp_OAMethod http status is 200:Successful ' +
    str(@status) + @params end
    exec @hr = sp_OAGetProperty @obj, 'responseText', @response OUT
    if @hr <>0 begin set @msg = 'sp_OAGetProperty read response failed on get response text error code' + convert(varchar,@hr) goto
    eh end
    exec @hr = sp_OADestroy @obj
    return
    eh:
    exec @hr = sp_OADestroy @obj
    Raiserror(@msg, 16, 1)
    return
    Many thanks for the input - 
    Chris

    How can I fix the problem? changing the OS? I just bought the new server. I do?
    thanks
    Miky
    Rambaldi

  • SQL DEVELOPER INSTALLATION ERROR

    Hi Guru's,
    My OS : Linux
    DB : Oracle 10g
    When i am trying to install Oracle Sql Developer, I am getting the below error:
    Type the full pathname of a J2SE installation (or Ctrl-C to quit), the path will be stored in ~/.sqldeveloper/jdk
    I install jdk-7u9-linux-i586.rpm but i am still getting this error, wheather i need to set some path
    KIndly advice over the same.

    This is not really an error it's just SQLDeveloper requesting a JDK to run.
    You should supply a valid JDK 1.6.X path, where X should be the latests release of JDK6.
    on average linux systems a valid path should look like this
    /usr/java/jdk1.6.0_37JDK 7 is not officially supported yet, and there are known issues on it, so i'd advise you to install the latest JDK6 and use that.

Maybe you are looking for