locked
SQL Express fails in VS2010 installation on Windows 7 SP1 RRS feed

  • Question

  • Hello,

    I have obtained two warnings and numerous errors when installing Visual Studio 2010 Ultra on Windows 7 SP1. Slipstremed SQL 2008 Express SP1 failed with these warnings and errors:

    TWO WARNINGS:

    A provider, SQLServerEventProvider, has been registered in the Windows Management Instrumentation namespace root\Microsoft\SqlServer\ServerEvents\SQLEXPRESS to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
    Application
    WMI
    Warning
    W28\MAGIC

    NUMEROUS ERRORS

    Cannot find the object 'fulltext_stopwords', because it does not exist or you do not have permission.
    Application
    MSSQL$SQLEXPRESS
    15151
    Error

    AND ANALOGOUS ERRORS WITH THESE ITEMS

    'fulltext_stoplists'
    'fulltext_index_fragments'
    'database_audit_specification_details'
    'database_audit_specifications'
    'conversation_priorities'
    'change_tracking_tables'
    'spatial_index_tessellations'
    'spatial_indexes'
    'function_order_columns'
    'table_types'
    'system_sql_modules'
    'plan_guides'
    'module_assembly_usages'
    'type_assembly_usages'
    'fulltext_index_catalog_usages'
    'service_queue_usages'
    'parameter_type_usages'
    'column_type_usages'
    'message_type_xml_schema_collection_usages'
    'parameter_xml_schema_collection_usages'
    'column_xml_schema_collection_usages'
    'asymmetric_keys'
    'internal_tables'
    'certificates'
    'crypt_properties'
    'key_encryptions'
    'symmetric_keys'
    'xml_schema_collections'
    'transmission_queue'

    etc.

    (I consider using hotfix 976899, but local MS has not call me back yet.)

    Your help is appreciated.

    Regards,

    Milos

     

    • Moved by Andrew.Wu Wednesday, September 14, 2011 3:06 AM (From:Visual Studio Setup and Installation)
    Tuesday, September 13, 2011 10:19 AM

Answers

  • Hi Milos

    According to the error message, it might be the installation is not fully configured before the upgrade. You can try to work around this issue with the following steps:

    1. Uninstall the failed slipstream installation.
    2. Run the SQL Server 2008 SP1 CU6 package to install or upgrade the setup support files before you run the slipstream installation package.
    3. Install the slipstream package again. Alternatively, you can build a new slipstream package that includes SQL Server 2008 SP1 CU6 and then install the package.

    For more information, please refer to this KB article: FIX: A slipstream installation of SQL Server 2008 fails intermittently
    Best Regards,
    Stephanie Lv

    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    • Marked as answer by Milos Puchta Thursday, September 15, 2011 6:17 AM
    Wednesday, September 14, 2011 7:31 AM
  • I have found this statement:

    The .NET Runtime Optimization Service is only activated when the native image of an .NET application has become invalidated, usually because the application itself or its dependencies has been updated.

     

    and solution - stopping the CLR optimization

    sc.exe stop clr_optimization_v4.0.30319_32

    More information is here http://blogs.msdn.com/b/davidnotario/archive/2005/04/27/412838.aspx 

    • Marked as answer by Stephanie Lv Thursday, September 15, 2011 12:54 AM
    Wednesday, September 14, 2011 8:20 PM

All replies

  • Hi Milos,

    Thanks for your post.

    Although the problem occur while installing Visual Studio 2010, according to the error messages, it appears that this issue is more related with SQL Server setup. Therefore, I'll help move this post to the SQL Server Express Forum for better support.

    Thanks for your understanding.

    Best Regards,


    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, September 14, 2011 3:06 AM
  • Hi Milos

    According to the error message, it might be the installation is not fully configured before the upgrade. You can try to work around this issue with the following steps:

    1. Uninstall the failed slipstream installation.
    2. Run the SQL Server 2008 SP1 CU6 package to install or upgrade the setup support files before you run the slipstream installation package.
    3. Install the slipstream package again. Alternatively, you can build a new slipstream package that includes SQL Server 2008 SP1 CU6 and then install the package.

    For more information, please refer to this KB article: FIX: A slipstream installation of SQL Server 2008 fails intermittently
    Best Regards,
    Stephanie Lv

    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    • Marked as answer by Milos Puchta Thursday, September 15, 2011 6:17 AM
    Wednesday, September 14, 2011 7:31 AM
  • Hi Stephanie,

    I have applied CU6 on the vanilla plain Windows 7 and subsequently installed VS2010. All errors have disappered, warnings are still there.

    After this I have installed SP1 (web version). The old errors disappeared and new ones piled in event log. Here is one sample;

    .NET Runtime Optimization Service (clr_optimization_v4.0.30319_32) -
    Failed to compile:
    Microsoft.SqlServer.SmoExtended, Version=10.0.0.0, Culture=neutral,
    PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070005

    Application
    .NET Runtime Optimization
    1101
    Error

    Thank you in advance for your help

    Regards

    Milos

    Wednesday, September 14, 2011 3:25 PM
  • I have found this statement:

    The .NET Runtime Optimization Service is only activated when the native image of an .NET application has become invalidated, usually because the application itself or its dependencies has been updated.

     

    and solution - stopping the CLR optimization

    sc.exe stop clr_optimization_v4.0.30319_32

    More information is here http://blogs.msdn.com/b/davidnotario/archive/2005/04/27/412838.aspx 

    • Marked as answer by Stephanie Lv Thursday, September 15, 2011 12:54 AM
    Wednesday, September 14, 2011 8:20 PM