Home Dashboard Directory Help
Search

SQL Server 2008 R2 - Installing Service Pack 1 removes registry data, causing Event ID 274 by RobertPA


Status: 

Closed
 as By Design Help for as By Design


1
0
Sign in
to vote
Type: Bug
ID: 696610
Opened: 10/25/2011 8:14:45 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Installing Service Pack 1 removes data from
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS\ServiceConfigFile


Fresh install of MS SQL server 2008 R2 Standard RTM (with SSIS selected) populates the above registry key with "C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.ini.xml"

Installing Service Pack 1 for MS SQL Server 2008 R2 REMOVES the data, causing SSIS to log Event 274 in the Aplication log

Log Name:     Application
Source:        SQLISService100
Date:         25.10.2011 12:48:15
Event ID:     274
Task Category: Service Control
Level:         Warning
Keywords:     Classic
User:         N/A
Computer:     SRV-DB-04.company.com
Description:
Microsoft SSIS Service:
Registry setting specifying configuration file does not exist.
Attempting to load default config file.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SQLISService100" />
    <EventID Qualifiers="0">274</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-25T10:48:15.000000000Z" />
    <EventRecordID>1303</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SRV-DB-04.company.com</Computer>
    <Security />
</System>
<EventData>
</EventData>
</Event>
Details
Sign in to post a comment.
Posted by Gaz50 on 2/25/2012 at 10:45 PM
Re-adding the default path results in the warning becoming an error. It is best to leave it as is.
Posted by Microsoft on 12/8/2011 at 8:35 AM
Hi Robert,

We’re closing this behavior as “By Design.” Because the default path is not required, the behavior was changed in SP1 to remove it from the registry rather than including it. To remove the warning message, you can re-add the default path to the registry.

Matthew
Sign in to post a workaround.