PL/SQL parser installation error

I tried to install the XML PL/SQL parser against Oracle 8.1.6 with JServer Release 8.1.6.0.0 and I received a large number of errors about invalid column names including the following:
Error while resolving class oracle/xml/parser/v2/FromDescendantAttributes
ORA-00904: invalid column name
Error while resolving class oracle/xml/parser/v2/XSLNode
ORA-00904: invalid column name
Error while resolving class oracle/xml/parser/v2/UnaryExpr
ORA-00904: invalid column name
Any suggestions?
Thanks

Hi Steven:
Yep...I just checked our install and there are no java classes in user_objects. We had the init*.ora file shared_pool_size set too low (as indicated under $ORACLE_HOME/javavm/doc/readme.txt).
So I'll get our DBA to try it again.
Thanks,
Derek
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Steven Muench ([email protected]):
This likely means that the database JavaVM is not properly installed in your Oracle8i database. You need to run the initjvm.sql script as detailed in the JServer documentation before any 'loadjava'
commands will work.<HR></BLOCKQUOTE>
null

Similar Messages

  • XML PL/SQL Parser Demo Error ORA-29516

    I'm trying to get the XML Plsql demo to work on the following
    system:
    Sun Solaris 8
    Oracle 8.1.7.0.0 64 bit
    using the $ORACLE_HOME/xdk/plsql/demo files
    I created an oracle user "xmldba" , granted javauserpriv to
    xmldba, granted javasyspriv to xmldba. I have run
    $ORACLE_HOME/xdk/plsql/parser/bin/load.sql. Then I try the
    demo -
    oracle8$ sqlplus xmldba/xmldba
    SQL*Plus: Release 8.1.7.0.0 - Production on Fri Nov 16 11:07:44
    2001
    (c) Copyright 2000 Oracle Corporation. All rights reserved.
    Connected to:
    Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production
    With the Partitioning option
    JServer Release 8.1.7.0.0 - 64bit Production
    SQL> @domsample
    Procedure created.
    No errors.
    SQL> execute domsample
    ('/home/oracle8/app/oracle/product/8.1.7/xdk/plsql/demo','family.
    xml','errors.txt');
    BEGIN domsample
    ('/home/oracle8/app/oracle/product/8.1.7/xdk/plsql/demo','family.
    xml','errors.txt'); END;
    ERROR at line 1:
    ORA-29516: Aurora assertion failure: Assertion failure at
    joncomp.c:127
    jtc_active_clint_init_ncomp_slots(oracle/xml/parser/v2/DTD, 0)
    returned 0
    ORA-06512: at "XMLDBA.XMLPARSERCOVER", line 0
    ORA-06512: at "XMLDBA.XMLPARSER", line 57
    ORA-06512: at "XMLDBA.DOMSAMPLE", line 72
    ORA-06512: at line 1
    Anyone have any ideas on what I might be missing or what could
    cause the problem?
    Thanks,
    Rhea

    These errors were due to not running initjvm etc. I have resolved all the jvm sqlj related problems now .
    I am still seeing resolver errors . Opened a new thread for those errors.
    Please respond on those
    Thanks
    null

  • 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.

  • 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

  • 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

  • SAP IDES ECC5.0 (SQL 2005 Database) installation Error at  Database instan.

    At the time IDES ECC 5.0 installation (SQL 2005 database), I was copy all DVD on Hard drive and start setup then at installation of database instance, following Errors are occured. so I cant continue with the installation, if anyone have installation guide/or solve the following error please mail me at [email protected]
    from Log file SAPCLUST
    Interface access functions from dynamic library dbmssslib.dll loaded.myCluster
    (3.5.Imp): 613: error when retrieving table description for physical table AABLG.
    myCluster (3.5.Imp): 614: return code received from nametab is 32
    myCluster (3.5.Imp): 296: error when retrieving physical nametab for table AABLG.
    (CNV) ERROR: code page conversion failed
                 rc = 2
    from sappool.log
    Interface access functions from dynamic library dbmssslib.dll loaded.failed to read short nametab of table ARCH_NUM     (rc=32)conversion failed for row 0 of table  VARKEY = &#8280;††††††††††††††††††††††††
    (CNV) ERROR: code page conversion failed
    So please send me solution/ or any configuration need for SQL 2005 / installation guide thanks

    This may be hard disk problem, some file not able to write on HDD.
    Regards
    Rajnish

  • SQL*Loader-925: Error while parsing a cursor (via ocisq)

    Receiving the following error message when trying to use SQLLoader (on NT) >>>
    SQL*Loader-925: Error while parsing a cursor
    (via ocisq)
    ORA-00942: table or view does not exist
    Trying to use the application for the first time, logon using userid for which sqlplus operates, and the table does exist under the user schema, as owner.
    ctl and dat file are correct. Log file gives me no further detail of the errors.
    Are there any configuration settings or something required for this app?
    Thanks

    Thanks Warren. I was concentrating more on the first line of the error.
    You are right. The issue was of insufficient privileges. The table did not have all the necessary grants provided.

  • 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

  • Logging errors in PL/SQL Parser

    Using PL/SQL Parser, is it possible to obtain the parsing errors
    output in other place than a file (ref: setErrorLog function)?
    as varchar variables or kind?
    null

    M Leclair (guest) wrote:
    : Using PL/SQL Parser, is it possible to obtain the parsing
    errors
    : output in other place than a file (ref: setErrorLog function)?
    : as varchar variables or kind?
    It is not possible at this time. It has been filed as an
    enhancement request.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • SQL*Loader-930: Error parsing insert statement for column

    we upload data on daily basis in application throug apps user and these table are invloved
    1. DEV_RA_INTERFACE_LINES_ALL(owner is a apps)
    2.RA_INTERFACE_LINES_ALL(owner is a AR)
    we do steps
    1 delete record from DEV_RA_INTERFACE_LINES_ALL table
    2 delete record from      RA_INTERFACE_LINES_ALL table
    3 load data using sql loader with apps user
    4 insert in RA_INTERFACE_LINES_ALL table
    we want to change user i mean these step do dataupload user not apps
    we give the proper rights to dataupload like select,delete and insert rights on these table to dataupload user but when i going to load data throug sql loader we receive error
    SQL*Loader-930: Error parsing insert statement for column APPS.DEV_RA_INTERFACE_
    LINES_ALL.ORIG_SYSTEM_BILL_ADDRESS_ID.
    ORA-00904: "F_ORIG_SYSTEM_BILL_ADDR_REF": invalid identifier
    and if i insert data through apps then done.

    make sure that u have no speces left
    between lines.
    give the path of control file path correctly.

  • SQL*Loader-929: Error parsing insert statement for table

    Hi,
    I get the following error with SQL*Loader:
    Table MYTABLE loaded from every logical record.
    Insert option in effect for this table: INSERT
    Column Name Position Len Term Encl Datatype
    IDE FIRST * ; CHARACTER
    SQL string for column : "mysequence.NEXTVAL"
    CSI_NBR 1:10 10 ; CHARACTER
    POLICY_NBR 11:22 12 ; CHARACTER
    CURRENCY_COD 23:25 3 ; CHARACTER
    POLICY_STAT 26:27 2 ; CHARACTER
    PRODUCT_COD 28:35 8 ; CHARACTER
    END_DAT 44:53 10 ; CHARACTER
    FISCAL_COD 83:83 1 ; CHARACTER
    TOT_VAL 92:112 21 ; CHARACTER
    SQL*Loader-929: Error parsing insert statement for table MYTABLE.
    ORA-01031: insufficient privileges
    I am positive that I can SELECT the sequence and INSERT into the table with the user invoking sql*loader.
    Where does that "ORA-01031" come from?
    Regards
    ...

    Options:
    1) you are wrong about privileges OR
    2) you have the privilege only when you connect via SQL*Plus (or whichever other tool you used to test the insert).
    Is it possible that during your test you enabled the role which granted you the INSERT privilege - and that SQL*Loader doesn't do this?
    Can you see the table in this list?
    select *
    from user_tab_privs_recd
    where table_name='MY_TABLE'
    and owner='table owner whoever';
    select *
    from user_role_privs;Any roles where DEFAULT_ROLE is not YES?
    HTH
    Regards Nigel

  • Reportings Services in a 2-Tier Architecture / (Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key. )

    Hello,
    we want to install Reporting Services in a 2-Tier Architecture. The Servers are the following:
    SERVER1: Windows Server 2012 and SQL Server 2012
    SERVER2: SharePoint 2013 (WFE)
    Reporting Server is installed on SERVER1 and running. On SERVER2 the registration of the service through Powershell was done but it does not start. An Error when starting the Service on the server occurs with the message:
    "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key."
    I have found the following in msdn stating that a minimal of the same SharePoint Installation must exist on the Reporting Server. The article is for SQL Server 2008 R2 and SharePoint 2010. Is this the case also for SQL Server 2012 and SharePoint 2013 and
    the root of the problem? http://msdn.microsoft.com/en-us/library/bb510781%28v=sql.105%29.aspx
    If so does this mean that I require for the installation another License?!?!
    Thank you in advance!

    Hi,
    According to your post, my understanding is that you wanted to install Reporting Services in a 2-Tier Architecture.
    As the article
    say, if you use Two-Computer Deployment, the first computer hosts an instance of a SharePoint product. The Reporting Services Add-in is installed on this computer. The second computer hosts SQL Server Reporting Services and the Database Engine.
    The steps to install in a  two-tier environment are very similar to a standalone environment hence you can go to refer to the ' Install Reporting Services SharePoint Mode for SharePoint 2013' article at http://msdn.microsoft.com/en-us/library/jj219068(v=sql.110).aspx
    To install in a  two-tier environment, you can refer to:
    How to setup, configure and test
    SQL 2012 SP1 SSRS with SharePoint 2013 SP1
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • SQL Parsing Errors

    We are running htmldb 1.5. We have an application running without problems on the development server. When we export the application and then import it on another server (QA or Production) we sometimes get the following errors in report regions that are retrieving data based on a page item:
    failed to parse SQL query:
    ORA-06502: PL/SQL: numeric or value error: NULL index table key value
    The form with the page item is displaying the value for the item, but the reports based on the page item fail. If we go into the htmldb development environment and edit the page for viewing purposes, the problem appears to disappear from that point on. We do not make any changes to the page.
    Is there a problem with the export/import process? Is there a way to make sure the page item has the value expected? We are using DML processing to fetch the record for the page. The fetch occurs 'After the Header'. Should the fetch be 'Before the Header'. Should we force a computation that reads the value into the page item again? If so, at what point?
    Usually we invoke the page and set the page item values with a url that looks like:
    f?p=&APP_ID.:510:#APP_SESSION#:UPDATE::510:P510_CLASS_ID:#CLASS_ID#
    Thanks for your help,
    Peter

    M Leclair (guest) wrote:
    : Using PL/SQL Parser, is it possible to obtain the parsing
    errors
    : output in other place than a file (ref: setErrorLog function)?
    : as varchar variables or kind?
    It is not possible at this time. It has been filed as an
    enhancement request.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • SQL Server 2005 Installation Error

    I am installine ECC6 on SQL Serer 2006. I have started the SQL Server installation, using the SQL4SAP.vbs and after about 10 minutes the installation stops with an error. I am pointed to a fine Summary.txt but the details in the file do not give a clue on the problem:
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
    SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
    Time            : Mon Dec 03 09:09:38 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SCC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_WI.log

    Hi Rajeev,
    Indeed it was a typo error I am attempting SQL Server 2005.
    I am using the 32 bit installation, that has been checked.
    Here are the details from C:\Windows\SQL4SAP.log
    Customized installation of SQL Server 2005 for SAP *
    Log File: C:\WINDOWS\SQL4SAP.log
    Script started 03/12/2007 08:46:25 on SAPDEMO
    System settings:
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_ComputerSystem.SystemType=X86-based PC
      Win32_OperatingSystem.OSType=18
      Win32_OperatingSystem.Version=5.2.3790
      Win32_OperatingSystem.ServicePackMajorVersion=2
      Win32_OperatingSystem.Caption=Microsoft(R) Windows(R) Server 2003, Standard Edition
      Win32_OperatingSystem.ProductType=3
      Win32_OperatingSystem.OSProductSuite=272
      Win32_OperatingSystem.OSLanguage=1033
    Windows version:
      OSVersion         = 5.2
      OSFamily          = Windows2003
      OSServicePack     = 2
      OSEdition         = Server
      OSSystemType      = X86
      OSProductSuite    = Terminal Server
      OSMsiVersion      = 3.1.4000.4042
      OSMdacVersion     = 2.82.3959.0
      OSLanguage        = English – United States
      OSLanguageID      = 1033
    Environment on SAPDEMO:
      userDir           = C:\Documents and Settings\Administrator\
      tmpDir            = C:\DOCUME1\ADMINI1\LOCALS~1\Temp\1\
      rootDir           = C:\WINDOWS\
      prgDir            = C:\Program Files\
      prgDirX86         = \
    SQL4SAP version:
      version:          ' v3.2.44    Mar 2007: SQL2005 SP2, Windows2003 SP2
      size:             86124
      created:          30/11/2007 16:59:31
      modified:         20/03/2007 13:36:44
      exe:              C:\WINDOWS\system32\cscript.exe
      script:           C:\SAP_CD\CD2\SQL4SAP.vbs
      C:                C:
    Script path:
      myRoot            = C:\SAP_CD\CD2\
      myDir             = C:\SAP_CD\CD2\x86\
      myDirUNC          = C:\SAP_CD\CD2\x86\
    Script settings:
      SqlAuthInstall    = False
      SilentInstall     = False
      DeEditionOnly     = False
      DeEditionPossible = False
      SapItMsgBox       = False
      SilentRtmSetup    = True
    Service Account:
      "C:\SAP_CD\CD2\x86\SqlCmd\GetSidName.exe" S-1-5-18 =>NT AUTHORITY\SYSTEM
      OSSystemAccount= NT AUTHORITY\SYSTEM
    03/12/2007 08:46:28
    Input Box "Select SQL Server instance"
    No SQL Server instance was found.
    SQL Server Native Client               not installed
    SQL Server 2005 Client Tools           not installed
    Enter a new or existing instance name.
    - for a Default Instance, enter:     (default)   or   .
    - for a Named Instance, enter:       <SID>
    To install SQL Client Tools Only, press Cancel.
    Result: (default)
    Registry settings (1/2):
    HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer
    READ: 2.82.3959.0
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\Version
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\PatchLevel
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CurrentVersion
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CSDVersion
    READ:
    03/12/2007 08:46:32
    Message Box "Confirmation"
    You have chosen to install the new instance
    SQL Instance:       (default)
    SQL Version:        9.00.3042
    SQL Edition:        2005 Enterprise Edition
    SQL Collation:      SQL_Latin1_General_CP850_BIN2
    Authentication:     Windows only
    Login sa:           random password, login disabled
    =======================================
    The installation may take 15 minutes or longer
    =======================================
    Do you want to start the installation now?
    Result: vbOK
    03/12/2007 08:46:34
    installing SQL Server 2005 Enterprise Edition on X86 - build 9.00.1399 ...
      Log File:    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
      Command:     "C:\SAP_CD\CD2\x86\EnterpriseEdition\Servers\setup.exe" /qn USERNAME="SAP ISV Royalty Licensing Program" ADDLOCAL=Connectivity,SQL_Tools90,SQLXML,Tools_Legacy,SQL_Documentation,SQL_BooksOnline,SQL_Data_Files,SQL_FullText PERSEAT=50 INSTANCENAME=MSSQLSERVER SQLCOLLATION=SQL_Latin1_General_CP850_BIN2 AGTAUTOSTART=1 SQLACCOUNT="NT AUTHORITY\SYSTEM" AGTACCOUNT="NT AUTHORITY\SYSTEM" SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxxxxxxxxxxxxx
      Return Code: 1605
    03/12/2007 08:48:41
    Log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
    Microsoft SQL Server 2005 9.00.1399.06
    ==============================
    OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
    Time            : Mon Dec 03 08:46:48 2007
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server VSS Writer
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server 2005 Books Online (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
    SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
    Time            : Mon Dec 03 08:48:39 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SCC.log
    service MSSQLSERVER does not exist
    03/12/2007 08:48:41
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: SQL Server - build 9.00.1399
      Return Code:       1605
      Log File:          C:\WINDOWS\SQL4SAP.log
    Check the log file above!
    See also SAP note 896566 for known issues
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\MSSQLSERVER
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg0
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg1
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg2
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg3
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg4
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg5
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg6
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg7
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg8
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg9
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg10
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg11
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg12
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg13
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg14
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg15
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg16
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg17
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg18
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg19
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg20
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLSERVER\Setup\SQLPath
    READ:
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    03/12/2007 08:48:47
    Quit script with return code 1

  • Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"

    Hello,
    I have a big problem.
    I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".
    I already tried all solutions from Google for this problem but nothing works.
    Can someone help me plase?
    My System: Window 8 Pro with Visual Studio 2012.
    Thanks
    Sven

    Would you please uplaod/share SQL Server setup logs
    C:\Program
    Files\Microsoft
    SQL Server\110\Setup
    Bootstrap\Log\20130125_133342
    to file sharing service like SkyDrive.com
    FAQ
    Regards,
    Ahmed Ibrahim
    SQL Server Setup Team
    My Blog
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
    "Mark as Answer" and "Vote as Helpful"
    on posts that help you.
    This can be beneficial to other community members reading the thread.

Maybe you are looking for