Install Fails With SQL Server Version - Status: Incorrect

Hi. I am working to install BPC 7 in a single server environment. During installation the setup diangostic detects a problem with [[Microsoft and 3rd Party Software]], below is what appears:
X - SQL Server Version
____    OK - Required: 10.0.1600.22 or higher
____    OK - Currently: Not Installed
____    X   - Status: Incorrect
X - SQL Reporting Services Server Version
____    OK - Required: 10.0.1600.22 or higher
____    OK - Currently: Not Installed
____    X   - Status: Incorrect
X - OLAP Server Version
____    OK - Required: 10.0.1600.22 or higher
____    OK - Currently: Not Installed
____    X   - Status: Incorrect
Under [[Computer Services Status]] SQL Server is alright:
OK - MS SQL Server Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - MS SQL Server Agent Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - SQL Integrated Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - SQL Report Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
OK - MS SQL Server OLAP Service
____    OK - Required: Running
____    OK - Currently: Running
____    OK - Status: OK
What I've Checked so far:
- Collation
- Account for installation is SQL SysAdmin and a Windows account
- Mixed mode authentication
I should mention, this is a single server install on a 64 bit version of Windows, with 64 bit version of SQL.
Any experience, ideas or suggestions are welcome.
Joe
Edited by: jwainz on Mar 29, 2010 5:55 PM

I think the clearest statement about this is on page 11 of the Master Guide (SAP BPC 7.0 M Master Guide at [http://service.sap.com/instguidesEPM-BPC]).
Look at the rows for OLAP Server and Microsoft SQL Server.  In each of those, you wil find this statement:
"Can be 64‒bit when separate from Application/web services"
On page 10 in the Installation Guide, for look at the rows for Application server Web Server.  The prerequisites are as follow:
App Server:
Windows Server 2003 or Windows Server 2003 R2 Standard or Enterprise Edition SP2 (32-bit) configured with NTFS, set to English (United States)
Web Server:
Windows Server 2003 or Windows Server 2003 R2 Standard or Enterprise Edition SP2 (32-bit) configured with NTFS
Finally, the PAM is a bit confusing.  For product SAP BPC 7.0 FOR MICROSOFT, click on the tab Operating Systems and then click on the tab BPC Server.  That is the software that you install for the Application Server and the Web Server server types.  The Operating System Version listed is WINDOWS SERVER 2003/IA32 32BIT

Similar Messages

  • Error while Installing WAS with SQL server

    Hi all,
       I am trying to install WAS with SQL server as Database. I am getting error at "Register SDM targets"  section. We have given SQL server authentication mode to install WAS.
    Following is the error Log....
    Exception: [DataDirect][SQLServer JDBC Driver][SQLServer]Cannot open database requested in login 'HCL'. Login fails.
         at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
         at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
         at com.ddtek.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
         at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
         at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
         at com.ddtek.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
         at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
         at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
         at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
         at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
         at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
         at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
         at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
         at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
         at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
         at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
         at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
         at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
         at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
         at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
         at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
         at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
         at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
         at com.sap.sdm.control.command.Command.exec(Command.java:42)
         at SDM.main(SDM.java:21)
    Thanks in Advance
    Regards
    Vasu

    Hi Vasudevan,
    Does you password contain any special characters?
    Try using a simple password.
    Regards
    Daniel

  • Installing CE with SQL Server

    Hi,
    I have SQL server Developer edition (version 8.00) , OS : Vista
    I am trying to install CE  and I am getting the follwoing error during the installation wizard
    ERROR      2009-12-19 13:08:59.602 [sixxcstepexecute.cpp:984]
    FCO-00011  The step dAskForConnection with step key |CE_DevSystem_App|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|3|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|NW_getDBInfo|ind|ind|ind|ind|3|0|NW_MSS_DBINFO|ind|ind|ind|ind|3|0|MssLoginInfo|ind|ind|ind|ind|0|0|dAskForConnection was executed with status ERROR .
    WARNING    2009-12-19 13:08:59.649 [iaxxejshlp.cpp:150]
    Could not get property IDs of the JavaScript object.
    ERROR      2009-12-19 13:08:59.649 [iaxxejsctl.cpp:492]
    FJS-00010  Could not get value for property .
    ERROR      2009-12-19 13:08:59.587
               lib=iamodmssql module=CIaNtMssDmo
    MDB-05053  Errors when executing sql command: [Microsoft][ODBC SQL Server Driver][SQL Server]Insert Error: Column name or number of supplied values does not match table definition.
    [Microsoft][ODBC Driver Manager] Function sequence error
    <p> SOLUTION: If this message is displayed as a warning, you can ignore it. If this is an error, contact SAP support.</p>
    Regards, Anil

    Hi
    Have a look on this resolved thread. [HELP |SQL2005 Upgrade Error in Post-Processing - HELP PLEASE;
    Best Regards
    Satish Kumar

  • CRM 2015 Update 0.1 Install Fails with SQL Error

    Hi, anyone managed to install CRM 2015 Update 0.1?
    The software installed fine but the DB updates fail with a SQL error. Just want to know if this is just my issue or if MS have a bug in the update. This is the SQL error:
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The current transaction cannot be committed and cannot support operations that write to the log file. Roll
    back the transaction.
    Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.
    All of the ORGs fail with this error, even when I try to apply the DB update via Deployment manager. I've had to back out the rollup.

    The issue appears when the update process creates the index cndx_BusinessDataLocalizedLabel. This is a known cause which is under investigation internally. Currently it seems to plan to release in CRM 2015 SP1

  • Instant Client with SQL Server - HELP!!

    G'day all...
    My goal is to connect to a server using Oracle Database version 8.1.7.4, from a server which does not have either Oracle Database or the full Oracle Client, preferrably using SQL Server DTS packages.
    With that said, I have installed instant client basic and instant client ODBC suppliment on our first development server using the instructions at the following link without any difficulties, although I do admit that I only have a tnsnames.ora file and not a sqlnet.ora file:
    http://www.oracle.com/technology/tech/oci/instantclient/instantclient.html
    The trouble is, when I attempt to deploy it on any of our other servers it fails. When I attempt to connect using Microsoft ODBC Driver for Oracle in a DTS package in SQL Server I get the following error message:
    HResult of 0x8004005 (-2147467259) returned Unexpected error occurred. An error result was returned without an error message.
    (Note: This is seen on all other servers I've tried this on except for the first one).
    I have also tried setting up a System ODBC connection using the Instant Client driver but it returned this error message:
    Unable to connect
    SQLState=S1000
    [Oracle][ODBC][Ora]ORA-12705: invalid or unknown NLS parameter value specified
    In desperation I have also tried installing the Oracle RDB Driver and the Oracle 8.1.7.8.1.0 ODBC driver. Both appear to install successfully yet nothing seems to work.
    As far as I can tell,l these are the differences between the first server and the other servers:
    - First server is MS SQL Server 2000 version: 8.00.760, rest are 8.00.818
    - First server is running MS SQL Server Analysis services, rest are not
    - First server is MS Windows 2000 Advanced Server, rest are MS Windows 2000 Server
    So my first question: Does anyone know if the Instant Client tool works with SQL Server version: 8.00.818?
    My second question: Can anyone else suggest something that I haven't tried yet, short of installing the Full Oracle Client on this server? Not that I'm opposed to doing that, it's just that it's a last resort idea as of now...
    Please help - need to roll this into production soon...

    Kent, I see that many others have reported that error (doing
    a google search), but I see no ready answers. I saw something that
    reminded me of a connection string value that I've seen answer some
    problems. May be worth a shot for you: try adding this string to
    the connection string (in "advanced options") for your datasource:
    AuthenticationMethod=Type2
    If it doesn't solve it, remove it. But keep it handy in case
    it ever may help with some other problem.
    Here's one other possible answer for you:
    http://www.webmasterkb.com/Uwe/Forum.aspx/coldfusion-server/3206/SQL-Server-2000-Windows-A uth
    Sorry I can't be more clear for you.

  • OBIEE 11g Prerequisites with SQL Server 2008 Express Edition

    Hi,
    I want to install OBIEE 11g with SQL Server Express Edition 2008.
    Is it possible to install OBI with SQL server express edition or not.
    Please send me prerequisites of OBIEE11g with SQL server.
    Thanks...................

    Hi,
    The link above gives a excel document with pre-requists, However if not working see below links;
    http://docs.oracle.com/cd/E23943_01/bi.1111/e10539/c3_requrmnts.htm and
    http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
    In the second link serach for System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition 11gR1 (11.1.1.3.0-11.1.1.6.0) ( xls)
    Don't forget to mark Correct.
    Thanks and Best of Luck,
    Kashi

  • Error trying to install ICM 8.0 - "FAILED TO GET SQL SERVER VERSION."

    Hello guys, i tried to install ICM 8.0 but when i click on Setup.exe appears this error:
    "FAILED TO GET SQL SERVER VERSION. MAKE SURE SQL SERVER INSTALLED PROPERLLY
    NO INSTANCE NAME FOUND.NO SCHEMA UPGRADES ATTEMPTED"
    I try to check the SQL COnfiguration, about Named Pipes, but everything is allright. Someone knows what is it?
    Thank you very much.

    You should be able to see the ICMSetup.log file somewhere - check TEMP. It seems to me that this is the first thing it does - tries to connect to the SQL database and ask for the version. Clearly it cannot. I assume you installed SQL OK, probably have the service running under a domain user created especially for the task, or the domain admin, and you are also logged in as the domain admin, and that SQL is running.
    Check that log file for clues.
    Regards,
    Geoff

  • "BCP Commit Failed" New Install On Windows 2008 R2 with SQL Server 2008 R2

    I am installing a new Netweaver install on a virtual machine loaded with Windows 2008 R2 and SQL Server 2008 R2. The install gets to the "Import ABAP" phase and just hangs. SAPINST says it is still running, but there is no activity to suggest there is anything going on. There are no errors in the main logs, but after digging a little I did find these errors in the SAPSDIC.log file.
    (IMP) INFO: EndFastLoad failed with <2: BCP commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'BADI_CHAR_COND~0'.>
    (IMP) ERROR: EndFastload: rc = 2
    (DB) INFO: BADI_FILTER created
    (DB) INFO: BADI_FILTER~0 created
    (IMP) INFO: EndFastLoad failed with <2: BCP commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'BADI_FILTER~0'. Ca>
    (IMP) ERROR: EndFastload: rc = 2
    (DB) INFO: BADI_IMPL created
    (DB) INFO: BADI_IMPL~0 created
    (IMP) INFO: EndFastLoad failed with <2: BCP commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'BADI_IMPL~0'. Cann>
    (IMP) ERROR: EndFastload: rc = 2
    Anyone have any ideas as to what might be going on? I can't find anyone with this exact same error. And this is our first attempt at installing a system with Windows 2008 R2 and SQL Server 2008 R2. All of our other Windows SAP systems are on Windows 2003 and SQL Server 2005 and we're in the process of upgrading - this being the first system.
    Thanks in advance,
    Michael

    Set BCP_LOB=1 in your system environment
    Note 1156361 - R3load: Fastload doesn't support LOB-columns
    Markus

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

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

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

  • Am failing to install Java IDM in a Windows XP machine with SQL Server 2005

    Hi,
    I am new to Java IDM . I had downloaded IDM 7.0 and trying to install. But i am failing to install Java IDM in a Windows XP machine with SQL Server 2005.
    I used .,
    JDK 1.5
    Tomcat 6.0
    Microsoft SQL Server 2005
    Microsoft SQL Server 2005 JDBC driver
    I got the following error while trying to connect the waveset database with Repository type as SQL Server 2005(JDBC Driver)
    com.waveset.util.ConfigurationError:
    ==> com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'waveset'. The user is not associated with a trusted SQL Server connection.
    what name i can specify in JDBC ... is there any need to create DSN for that ...........
    The Parameters that I have given for connection are:
    URL: jdbc:sqlserver :1433;DatabaseName=
    JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Connect as User:
    Connect Password:

    Do you have your SQL server set to Windows Authentication mode only?
    You should change it to allow mixed authentication. You can do this in SQL Server Management Studio under Server Properties -> Security.

  • Problem: VSS error with 'SQL Server Backup to Windows Azure Tool' installed

    When 'SQL Server Backup to Windows Azure Tool' is installed, shadow copies cannot be enable and backups fail.  When attempting to enable shadow copies, we get a "volsnap" error:  "The shadow copies of volume X were aborted because
    of a failed free space computation".  After uninstalling the "Tool", VSS works.  Reinstalling "Tool" causes the problem to return.
    While the error suggests a space issue, there is plenty of space on the server's two volumes.  Additionally, another 100GB volume was added and VSS storage was allocated to it; still received the error.
    Issue seems to point to 'SQL Server Backup to Windows Azure Tool'.
    Environment:  Hyper-V guest:  "Windows Server 2012 R2 Standard" with "SQL Server 2008 R2 Standard".  Using "Azure Storage" for SQL backups.
    Suggestions?

    Hello,
    Yes, we have a confirmed interference between the tool and the VSS Framework. This was identified very recently and is under investigation by the product group. Since the issue is within the filter driver shipped by the tool, that unfortunately means that
    you currently need to choose between the tool and a working VSS Framework. If the latter is more important, then uninstall the tool (that will require a restart).
    We apolologize for the inconvenience. I'm going to try to get the home page of the tool updated to avoid other situations like yours. Hopefully we should see a new version of the tool soon.
    As a side note, recent versions of SQL Server can directly use Azure Storage as backup target, see
    http://msdn.microsoft.com/en-us/library/jj919148(v=sql.110).aspx.
    Regards,
    Guillaume Fourrat - Microsoft France

  • SQL 2012 install fails with 'Object reference not set to an instance of an object.'

    Hi, I'm trying to install SQL 2012 RTM Enterprise on a Windows 2008 R2 single node cluster.
    The installer starts goes through some checks and then fails with the message 'Object reference not set to an instance of an object.' It happens while the small 'wait while...' dialog box is
    showing, another window pops up briefly (I think the feature selection window - can't really tell as it doesn't draw before disappearing). Then the ‘Object reference not set’ message comes up.
    From the summary log file..
    Overall summary:
    Final result:                 
    Failed: see details below
    Exit code (Decimal):          
    -2147467261
    Exit facility code:           
    0
    Exit error code:              
    16387
    Exit message:                 
    Object reference not set to an instance of an object.
    Start time:                   
    2012-09-26 08:52:53
    End time:                     
    2012-09-26 08:54:08
    Requested action:             
    InstallFailoverCluster
    Exception help link:          
    http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x9AF1AE5E%400x44A889F9&EvtType=0x9AF1AE5E%400x44A889F9
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: System.NullReferenceException
    Message:
    Object reference not set to an instance of an object.
    Data:
    HelpLink.EvtType = 0x9AF1AE5E@0x44A889F9
    DisableWatson = true
    Stack:
    at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.ShouldRuleRun(Rule rule)
    at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.IsRuleSkipped(Rule rule)
    at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.LoadRule(String ruleId, List`1 ruleProperties, XmlSchema ruleSchema, XmlElementParserFactory elementParser)
    at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.LoadRules(IEnumerable`1 ruleIds)
    at Microsoft.SqlServer.Configuration.InstallWizard.RunRuleProgressController.Initialize()
    I have rebooted, tried different media, tried uninstalling the setup files and rerunning but always get the same result.
    Any help would be gratefully accepted.
    Thanks,
    Bruce.

    Hi Alberto,
    Whenever I am trying to install SQL 2012 with SP1 clustering, I am getting below error. Can you please advise on this. 
    Additional information are
    Windows Servers Version and Edition - Windows 2012 Strandedition
    SQL Server Version and Edition - SQL 2012 with SP1
    All the machines are running on Hyper-V and Passed the cluster validation test successfully. there is no issue. The servers' (Nodes) names are;
    DomainServerName - ACONDomainGroup (1gb ram allocated)
    Node1 - AconNODE1W2K12STD (2.5gb ram allocated )
    Node2 - AconNODE2W2K12STD (1.5 ram allocated allocated)
    WindowsClusterName - AconWinCLTR
    Below is  Summary.txt Error
      Update Source:                 MU
    User Input Settings:
      ACTION:                        InstallFailoverCluster
      AGTDOMAINGROUP:                <empty>
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                <empty>
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      ENU:                           true
      ERRORREPORTING:                false
      FAILOVERCLUSTERDISKS:          <empty>
      FAILOVERCLUSTERGROUP:          
      FAILOVERCLUSTERIPADDRESSES:    <empty>
      FAILOVERCLUSTERNETWORKNAME:    <empty>
      FEATURES:                      
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  false
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                <empty>
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140420_052344\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140420_052344\SystemConfigurationCheck_Report.htm
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: System.NullReferenceException
        Message: 
            Object reference not set to an instance of an object.
        HResult : 0x80004003
        Data: 
          HelpLink.EvtType = 0x9AF1AE5E@0x44A889F9
          DisableWatson = true
        Stack: 
            at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.ShouldRuleRun(Rule rule)
            at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.IsRuleSkipped(Rule rule)
            at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.LoadRule(String ruleId, List`1 ruleProperties, XmlSchema ruleSchema, XmlElementParserFactory elementParser)
            at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.LoadRules(IEnumerable`1 ruleIds)
            at Microsoft.SqlServer.Configuration.InstallWizard.RunRuleProgressController.Initialize()

  • Error While Installing IDES ECC6 with SQL Server 2005

    Dear Experts,
    I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
    I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
    I herewith pasted hereunder log files information
    Regards,
    B.Sudharsan
    ERROR 2008-01-17 18:38:47
    FCO-00011  The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
    INFO 2008-01-17 18:40:05
    An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
    ERROR 2008-01-17 18:38:47
    MDB-05053  Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

    Sudarshan,
    Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade.

  • What SQL server version should be installed in BW 3.5?

    Dear all,
    What SQL server version should be installed in BW 3.5?
    1.Does it must install with enterprice version? Or can it use standand version?
    2.SQL 2000 is ok? or must use SQL 2005?
    3.x32 is ok? or must use x64?
    Best regards!
    Brian
    Edited by: brian allen on Jun 24, 2009 9:22 AM

    > What SQL server version should be installed in BW 3.5?
    >
    > 1.Does it must install with enterprice version? Or can it use standand version?
    Read the installation guide - Enterprise version only.
    > 2.SQL 2000 is ok? or must use SQL 2005?
    Both work but I would go for SQL 2005 (or even SQL 2008).
    > 3.x32 is ok? or must use x64?
    You should use 64bit wherever possible on new installations.
    Makrus

  • What are the SQL server versions those are compatible with XI 3.0.

    Hi All,
    Please suggest,
    what are the SQL server versions those are compatible with XI 3.0.
    or with which SQL server versions XI 3.0 will interact using JDBC Adapter.

    Check in the [Product Availability Matrix |https://websmp201.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000192]in market place for more information on this
    Thanks
    SaNv...

Maybe you are looking for

  • Battery Issue in Macbook pro (mid 2012)

    Hi, I just purchased my MBP in June 2012. But its battery health is just 92% after 9 cycles. Please, let me know if battery calibration can help me out or should I visit Apple store? Honey

  • Photo Settings not working

    Hi - when I try to edit clip length or Ken Burns effect in the Photo Settings pane, my Preview screen is black, and the changes I try to make don't seem to be applied to the clip. I have tried different clips and tried adding a new clip to the projec

  • Documentation of Hierarchy Window

    Hy out there, I was trying to get an ordinary " File / Print Documentation " in an *.rtf file. Couldn't get the "Hierarchy Window" to be documented as an ordinary *bmp file, even not when using the Costum format where I selected VI Hierarchy /Destina

  • SAP Netweaver 7.01 ABAP Trial Version 的 License 问题

    大家好,我由于换了电脑,将原来的操作系统重新封装后,克隆到新电脑.ABAP Trial 的服务可以运行,但GUI登陆是提示授权检查错误,使用新的Active Hardware Key 申请的License文件后在导入时发现,License 文件中的 System Number 与原来的  System Number 不同. 请问有解决的方案吗?

  • Why can't I send picture messages and group messages with MMS?

    Picture messages fail to certain people with invalid destination address.  Then the group messages won't send unless I send them as individual texts.  Very frustrating.