SQL 2008 R2 Setup Scale out deployment issue

Hi All.
Just trying to add a new server to an existing SSRS installation in the form of scale out deployment, the installation is done the instance names called the same and now on the new server, within the scale out deployment section, I can see its status as
joined. On the old originals server, it doesn’t show the new server as joined.
When I run the command RSKeyMgmt.exe –l
I get the message
Unable to locate the Report Server Windows service for instance MSSQLSERVER.
When I go to the server i.e the new one and try navigate to the reports section. I get this error.
The permissions granted to user XXXXX are insufficient for performing this operation. (rsAccessDenied)
On the Report manager Section within Reporting services configuration manager, when I goto the link it simply prompts me with a username/password prompt and it never works even after supplying the correct credentials.
It appears as though I set it up such that it joined the scale out deployment before backing up the encryption keys from the existing server and then restoring it onto the new one. What I am now trying to do is delete the new server entry and start the process
again to restore the encryption key and then only join the scale out deployment.
The issue here is that RSKeyMgmt.exe –l isn’t showing that the server is registered.

Hi MrfLinstone,
According to your description, you get the above error when navigate to reports. Right?
Based on the error message, you may not assign the permission to the current use for accessing the target report server. So please follow the steps below to create a system-level role assignment.
If necessary, log on as a local administrator.
Open a browser window and type the Report Manager URL to start the application. For example http://<server name>/reportserver
Click Site Settings at the top of the page.
Click the Security tab at the side of the page. This page shows all system-level role assignments that are currently defined. On a new report server installation, only the two predefined roles, System Administrator and System User, are visible.
There is one built-in role assignment that is created automatically; it maps the built-in local administrators group to the System Administrator role
Click New Role Assignment.
In Group or user name, specify a domain group account that includes all of the users who require permissions to view report server content and subscribe to reports. Specify the account in this format:
domain\group. The account should be in the same domain or in a trusted domain. If you do not have a domain group that fits this description, you can specify individual domain user accounts instead.
Select System User.
Click OK.
Click New Role Assignment again.
In Group or user name, type the name of a domain user account for a user who has administrative responsibilities for this report server. Specify the account in this format:
domain\user. The account should be in the same domain as the report server or in a trusted domain.
Select System Administrator.
Click OK.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Similar Messages

  • SQL blocking during removal of report server from Scale-out-Deployment

    I recently removed a 2012 reporting service instance from the Reporting Service Scale-out-Deployment. After I removed the server, there was a lot of blocking  on the report DB for about 30 minutes. My report DB is on the same SQL instance as
    my TFS databases and the blocking caused web access for TFS and Visual Studio connections to fail during check-out/check-in.
    Should I expect blocking to happen every time I remove a report server out of the Scale-out-Deployment?
    Thanks,
    KA

    Hi KA,
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
    Thank you for your understanding and support.
    Regards,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • SQL Server 2012 - reporting services - scale-out-deployment

    I am facing an issue which is related to a scale out deployment. I am deploying a FIM reporting based on System Center and I have 2 sql servers in this scenario.
    Now the problem is that Reporting services configuration manager (from sql1) says that the scale out deployment has been established. Sql1 is joined and sql2 is waiting to join. I don't know why the servers has been appeared under the scale out deployment
    because I don't want to create the scale out deployment.
    So how can I remove the scale out deployment without breaking anything?
    Also if I look at the Reporting services configuration manager from sql2 the scale out deployment panel is empty like it should be.

    Hi 2xTsei,
    According to your description, two report server instances have been configured to a scale-out deployment, while you haven’t performed this configuration.
    In Reporting Services, a report server scale-out deployment is two or more report server instances that share a single report server database. To finish this configuration, we should use Reporting Services Configuration tool to connect to each report server
    to the shared database and join a new report server instance. So the scale-out deployment shouldn’t be configured automatically. It’s likely that someone has configured this deployment who can access those two instances.
    Reference:
    How to: Configure a Report Server Scale-Out Deployment (Reporting Services Configuration)
    If you have any question, please feel free to ask.
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support
    Hi and thanks for your reply.
    That is a little bit weird because I am 100% sure that we didn't manually configured scale out deployment. I need to inspect this more.

  • SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

    Hello,
    SSRS in SharePoint mode is driving me insane.
    We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
    2 SP Web FrontEnds
    2 SP Application Servers
    1 SQL Server
    At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
    We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, we get the following error:
    "Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm.  The SQL Server Reporting Services service cannot
    be started on this server unless it is stopped on all other servers in the farm. "
    Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
    Could someone please advise why SP might think this version of SSRS is not the correct one?
    Thanks in advance for your help.
    Regards,
    P.

    Hello,
    I'm afraid that is not it.
    After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
    The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
    As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
    Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
    There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
    to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
    I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
    Regards,
    P.

  • What does "Scale out deployment (Web Farms)" mean for SP2013 and SQL 2012 SSRS?

    Dear community,
    in the
    Feature List of Reporting Services 2012, it's written that "Scale out deployment (Web farms)" is not possible for SQL 2012 Standard edition. However, does this relate as well to SSRS in SP-integrated mode, or only to native mode?
    In other words: is it possible to deploy SSRS using SQL 2012 STANDARD on more than one server in a SP2013 farm?
    And just to be sure: am I right to assume that in both cases, you can create multiple SSRS Svc Applications (be they all running on the same server) and assign them to different web applications (through their proxy groups)?
    Cheers,
    C

    Hi CHinz, 
    According to your description, you want to configure scale-out deployment for SQL Server Reporting Services 2012 standard edition. Right?
    As you can see in the msdn liabrary, for SQL Server 2012, scale-out deployment is only supported in Enterprise and Business Intelligence editions. This is related to both native mode and sharepoint integrated mode.
    It's not supported to deploy a SSRS 2012 standard edition instance on more than one server.
    Since scale-out deployment is for different report server instance to share one report server database. You can use different web applications to access the same report in different report server instances.
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • SSRS in SharePoint Mode: Reporting Services scale-out deployment is not supported in this edition of Reporting Services [not true]

    Hello,
    We are experiencing some issues with SharePoint 2013 which is driving me insane.
    We have a deployment with two SQL Servers (HA groups) and four SharePoint servers: 2 Application servers, and 2 Web FrontEnd servers.
    We installed SSRS for SharePoint in both application servers. The disc I have used is the MSDN image of SQL Enterprise 2012 w/ SP2.
    ISO name: en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4685849.iso
    MD5: 003e14c55fa648ad15f8be1e2439bd06
    The installation completes without any problems. We can start the SSRS SharePoint Service in the first application server without any issues. However when we try to start the second one, we get the following error:
    Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the sql reporting services service in the farm. The SQL Server Reporting Services cannot be started on
    this server unless it is stopped on all other servers in the farm.
    Now I am at a loss here. As I mentioned, we have used an image of SQL Server Enterprise. This is the same image we used on other environment, which worked as expected (we got no such error).
    I have included the text related to the correlation error from the SP logs below.
    Has anyone ever seen this issue before? Very, very strange!
    Regards,
    P.
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=9.742 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 6t8h High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.23, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Web Controls 88wu High [Forced due to logging gap, Original Level: Verbose] SPGridView.OnRowCreated() - Row.RowType={0}, .RowState={1}, .RowIndex={2}, .DataItemIndex={3} 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General af4yd High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.28, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache. 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.43 OWSTIMER.EXE (0x1F10) 0x0B40 SharePoint Foundation Health abire Medium Failed to Sql Query data XEvent collector on sql-01. The error is Object reference not set to an instance of an object.
    01/29/2015 14:13:26.51 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 7034 Critical An attempt to start/stop instance of service Microsoft SQL Server Reporting Services Shared Service on server SPAP-01 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.40, Original Level: Verbose] SQL connection time: 0.0821 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88b9 High [Forced due to logging gap, Original Level: Verbose] Determining if the current user is a SharePoint Farm Administrator 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ReportingWebServiceInstance. Version: 1118292 Ensure: False, HashCode: 52212853, Id: 5a4058b9-2ecd-421e-b9ae-818bbc57c8c6, Stack: at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.57, Original Level: Verbose] SQL connection time: 0.0965 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88ch High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.84, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 8nca Medium Application error when access /_admin/Server.aspx, Error=Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.87 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Runtime tkau Unexpected System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.89 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,2 agb9s,9 b4ly,309 8xqz,331 8nca,15 tkau,8 ajlz0 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48)). Execution Time=712.2145 6f83e49c-cc03-d049-90f4-81439b542cf8

    Hi Wynn,
    I appreciate your attempt to address my concerns, but even your reply seems to ignore the fact that I have not only provided the name of the ISO, but the MD5 checksum of the ISO as well. Also this is the first time I am being asked to double-check the version
    of SSRS. The first reply I got to my query simply disregarded the version mismatch.
    As per your request, I have checked under the folder you have specified (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\LogFiles), but unfortunately there are no files under this folder in neither of my two application
    servers.
    We only have logfiles under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS 
    Is there a way I can turn those logs on?
    In the meantime, we run the SQL Server Discovery tool and I have attached the summary for you to see that it finds the Enterprise Edition of SQL Server:
    Final result: Passed
    Exit code (Decimal): 0
    Start time: 2015-01-29 15:17:44
    End time: 2015-01-29 15:17:56
    Requested action: RunDiscovery
    Machine Properties:
    Machine name: SP-AP-02
    Machine processor count: 4
    OS version: Future Windows Version
    OS service pack:
    OS region: United States
    OS language: English (United States)
    OS architecture: x64
    Process architecture: 64 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5058.0 No Yes
    SQL Server 2012 Reporting Services - SharePoint 11.2.5058.0 No Yes
    Package properties:
    Description: Microsoft SQL Server 2012
    ProductName: SQL Server 2012
    Type: RTM
    Version: 11
    SPLevel: 0
    Installation edition:
    User Input Settings:
    ACTION: RunDiscovery
    CONFIGURATIONFILE:
    ENU: true
    HELP: false
    IACCEPTSQLSERVERLICENSETERMS: false
    INDICATEPROGRESS: false
    QUIET: false
    QUIETSIMPLE: false
    UIMODE: Normal
    X86: false
    Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150129_151743\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file: The rule result report file is not available.
    The \Setup Bootstrap\Log folder also has several log files that indicates the version of SQL Server that has been installed. For instance here is an entry of the Detail.txt file:
    (01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : CreateSKUCookie succeeded, new checksum is 195 bytes.
    (01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : Updated skuCheckSumInfo -> daysLeft=0 sqlEdition='ENTERPRISE' (0x6B9471A8) fileTimeInstalled=0 timeBombValue=0 editionType='Enterprise Edition' edition='Enterprise Edition' writeEditionStrings='True' checkSum=195bytes
    (01) 2015-01-28 19:10:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    I hope this help while we don't have any logfiles in the folder you asked me to look into. Please advise me as in how to proceed if logfiles must be generated.
    Regards,
    P.

  • Scale-out deployment is not supported in this edition of reporting services

    Can the "scale-out deployment" option be turned off so that I can migrate SSRS databases from Enterprise edition to Standard?  After I attached databases from a SSRS 2005 Enterprise to SSRS 2012 Standard I am getting an error about
    scale-out deployment not supported.  Any way around this so I can migrate the databases, bringing the reports and report subscriptions to the new SSRS instance?
    Lee Markum

    Hi Lee,
    From the
    document, we can know that Scale out deployment is a feature that only supported in Enterprise and Business Intelligence editions in SQL Server 2012.
    In order to fix this issue, we can refer to the similar thread post by Ben:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/8eebf25f-2c40-40d3-9bb7-bb481fdafc12/is-this-a-scaleout-deployment-?forum=sqlreportingservices
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Scale-out restart issue

    I have a environment with 2 servers. I have done scale-out on server 2. When I do the Restart under coreapplication in EM, it fails to fully start coreapplication, but if I go to the Availability tab and start it there I have no issue. Does the Restart under coreapplication only apply to a single environment and once the environment is scaled it has to be done under availability tab?

    Hi J.A.M,
    This is a heads-up for those configuring scaleout using internet explorer 7.For the issue where Primary/Secondary Configuration Section of the Availability Tab is Not Visible in EM, do not use IE7, use another browser such as Google Chrome, Microsoft Internet Explorer 8 or Mozilla Firefox.After making this change, BI cluster controller will get started without any issue. Hope this answers your query.
    Rgds,
    Dpka

  • Server0 starts very slowly in PI 7.11 in Win 2008 / SQL 2008 MSCS config

    Hi all.
    I have a problem in our newly installed PI 7.11 system on Windows Server 2008 and MS SQL 2008 MSCS setup. The J2EE application server on the node where the SCS is running, takes about 1 hour to start. About 20 minutes after starting, it goes from starting framework to starting apps, and then remains in that status for another 40-50 minutes. I am unable to find anything in the log files that can explain this behaviour. The J2EE app server on the second cluster nodes starts within 5-6 minutes. If I fail over the SAP Cluster Group to the second node, the situation is reversed.
    We are using the latest 7.11 kernel and the latest available SPS.
    Has anyone experiences something similar?
    Regards,
    Thomas

    Hi.
    Thanks for your input!
    I found this document [Process Integration (PI) Performance Check - Analyzing Performance Problems and Possible Solution Strategies|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782?quicklink=index&overridelayout=true].
    I also remembered having read somewhere that the VMC should be turned off for PI. So I set the parameter vmcj/enable = off. If this really did the trick or not, I cannot guarantee, but now my server0 processes starts normally.
    Regards,
    Thomas

  • SQL Server 2008 Express Setup Issue SKU

    Hi,
    a  configuration file driven setup worked on roughly 30 machines without problems.
    However, on one certain machine (which is costumer owned in Saudi Arabia) the installation seems to
    be blocked at an early stage. Logfiles reporting something about "SKU", but this makes not clear for me
    what the problem is.
    The Summary.txt is pasted, below this Details.txt is placed (the bottom part which contains the error portion).
    Thanks for help in advance!
    Peter
    Summary.txt
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -213508975
      Exit facility code:            838
      Exit error code:               7313
      Exit message:                  sku
      Start time:                    2013-11-14 19:00:59
      End time:                      2013-11-14 19:03:07
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.2531.0%26EvtType%3d0xC16B698F%400x6AD84D9E
    Machine Properties:
      Machine name:                  F950DS1
      Machine processor count:       4
      OS version:                    Windows Vista
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1033                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1031                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1033                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1031                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      GESTRAVKP4030        MSSQL10.GESTRAVKP4030          Database Engine Services                
    1033                                      10.1.2531.0    
    No        
      Sql Server 2008      GESTRAVKP4030        MSSQL10.GESTRAVKP4030          Database Engine Services                
    1031                                      10.1.2531.0    
    No        
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      Installation location:         C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\x86\setup\
      Installation edition:          Invalid
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      True
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    True
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              True
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    GESTRAVKP4030
      INSTANCENAME:                  GESTRAVKP4030
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PCUSOURCE:                     C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\PCUSOURCE
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\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.ArgumentException
        Message:
            sku
        Data:
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
            at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
            at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
            at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
            at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore store)
            at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
            at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
            at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
            at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
            at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
            at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
            at System.EventHandler.Invoke(Object sender, EventArgs e)
            at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
            at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
            at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
            at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
            at System.Windows.Forms.Control.OnClick(EventArgs e)
            at System.Windows.Forms.Button.OnClick(EventArgs e)
            at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
            at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
            at System.Windows.Forms.Control.WndProc(Message& m)
            at System.Windows.Forms.ButtonBase.WndProc(Message& m)
            at System.Windows.Forms.Button.WndProc(Message& m)
            at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
            at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
            at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    Detail.txt
    2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
    2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value SharedCode
    2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.GESTRAVKP4030\Setup
    2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value ProductID
    2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value DigitalProductID
    2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Using edition 'Invalid' from existing instance 'GESTRAVKP4030'.
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: mapped to 3 target directories
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "SYSTEMDRIVE"; Disk Cost: "121559"kb
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTALLSHAREDDIR"; Disk Cost: "132"kb
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTANCEDIR"; Disk Cost: "181258"kb
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Error: Action "GatherUserSettings" threw an exception during execution.
    2013-11-14 19:01:44 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.WaitOne()
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2013-11-14 19:01:45 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2013-11-14 19:01:45 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2013-11-14 19:01:45 Slp:    --- End of inner exception stack trace ---
    2013-11-14 19:01:45 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2013-11-14 19:01:45 Slp: Received request to add the following file to Watson reporting: C:\Users\Administrator\AppData\Local\Temp\tmp5718.tmp
    2013-11-14 19:01:45 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2013-11-14 19:01:45 Slp: Inner exceptions are being indented
    2013-11-14 19:01:45 Slp:
    2013-11-14 19:01:45 Slp: Exception type: System.ArgumentException
    2013-11-14 19:01:45 Slp:     Message:
    2013-11-14 19:01:45 Slp:         sku
    2013-11-14 19:01:46 Slp:     Stack:
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore
    store)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.EventHandler.Invoke(Object sender, EventArgs e)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.OnClick(EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Button.OnClick(EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.ButtonBase.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Button.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    2013-11-14 19:02:13 Slp: Watson Bucket 1
     Original Parameter Values
    2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
    2013-11-14 19:02:13 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
    2013-11-14 19:02:13 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
    2013-11-14 19:02:13 Slp: Parameter 3 : System.ArgumentException@-2147024809
    2013-11-14 19:02:13 Slp: Parameter 4 : System.ArgumentException@-2147024809
    2013-11-14 19:02:13 Slp: Parameter 5 : GatherUserSettings
    2013-11-14 19:02:13 Slp:
     Final Parameter Values
    2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
    2013-11-14 19:02:13 Slp: Parameter 1 : 0xC16B698F
    2013-11-14 19:02:13 Slp: Parameter 2 : 0xC16B698F
    2013-11-14 19:02:13 Slp: Parameter 3 : 0x6AD84D9E
    2013-11-14 19:02:14 Slp: Parameter 4 : 0x6AD84D9E
    2013-11-14 19:02:14 Slp: Parameter 5 : GatherUserSettings
    2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2013-11-14 19:02:22 Slp: sku
    2013-11-14 19:02:23 Slp: Watson bucket for exception based failure has been created
    2013-11-14 19:02:23 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey
    2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2013-11-14 19:02:23 Slp: Sco: Attempting to get registry value DW0200
    2013-11-14 19:03:07 Slp: Submitted 1 of 1 failures to the Watson data repository
    2013-11-14 19:03:12 Slp:
    2013-11-14 19:03:12 Slp: ----------------------------------------------------------------------
    2013-11-14 19:03:12 Slp:
    2013-11-14 19:03:12 Slp: Error result: -213508975
    2013-11-14 19:03:12 Slp: Result facility code: 838
    2013-11-14 19:03:12 Slp: Result error code: 7313

    Hi,
    a  configuration file driven setup worked on roughly 30 machines without problems.
    However, on one certain machine (which is costumer owned in Saud Arabia) the installation seems to
    be blocked at an early stage. Logfiles reporting something about "Invalid edition ... SKU", but it not clear for me
    what the problem is. 
    The Summary.txt is shown here, below this I will paste Details.txt (the bottom part which contains the error portion).
    Thanks for help in advance!
    Peter
    Summary.txt
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -213508975
      Exit facility code:            838
      Exit error code:               7313
      Exit message:                  sku
      Start time:                    2013-11-14 19:00:59
      End time:                      2013-11-14 19:03:07
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.2531.0%26EvtType%3d0xC16B698F%400x6AD84D9E
    Machine Properties:
      Machine name:                  F950DS1
      Machine processor count:       4
      OS version:                    Windows Vista
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1033                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1031                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1033                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1031                 Express Edition      10.1.2531.0     No        
      Sql Server 2008      GESTRAVKP4030        MSSQL10.GESTRAVKP4030          Database Engine Services                
    1033                                      10.1.2531.0    
    No        
      Sql Server 2008      GESTRAVKP4030        MSSQL10.GESTRAVKP4030          Database Engine Services                
    1031                                      10.1.2531.0    
    No        
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      Installation location:         C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\x86\setup\
      Installation edition:          Invalid
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      True
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    True
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              True
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    GESTRAVKP4030
      INSTANCENAME:                  GESTRAVKP4030
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PCUSOURCE:                     C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\PCUSOURCE
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\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.ArgumentException
        Message:
            sku
        Data:
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
            at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
            at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
            at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
            at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore store)
            at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
            at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
            at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
            at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
            at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
            at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
            at System.EventHandler.Invoke(Object sender, EventArgs e)
            at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
            at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
            at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
            at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
            at System.Windows.Forms.Control.OnClick(EventArgs e)
            at System.Windows.Forms.Button.OnClick(EventArgs e)
            at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
            at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
            at System.Windows.Forms.Control.WndProc(Message& m)
            at System.Windows.Forms.ButtonBase.WndProc(Message& m)
            at System.Windows.Forms.Button.WndProc(Message& m)
            at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
            at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
            at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    Detail.txt
    2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
    2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
    2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value SharedCode
    2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.GESTRAVKP4030\Setup
    2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value ProductID
    2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value DigitalProductID
    2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Using edition 'Invalid' from existing instance 'GESTRAVKP4030'.
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: mapped to 3 target directories
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "SYSTEMDRIVE"; Disk Cost: "121559"kb
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTALLSHAREDDIR"; Disk Cost: "132"kb
    2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTANCEDIR"; Disk Cost: "181258"kb
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
    2013-11-14 19:01:44 Slp: Error: Action "GatherUserSettings" threw an exception during execution.
    2013-11-14 19:01:44 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
    2013-11-14 19:01:44 Slp:    at System.Threading.WaitHandle.WaitOne()
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
    2013-11-14 19:01:44 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2013-11-14 19:01:45 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2013-11-14 19:01:45 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2013-11-14 19:01:45 Slp:    --- End of inner exception stack trace ---
    2013-11-14 19:01:45 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2013-11-14 19:01:45 Slp: Received request to add the following file to Watson reporting: C:\Users\Administrator\AppData\Local\Temp\tmp5718.tmp
    2013-11-14 19:01:45 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2013-11-14 19:01:45 Slp: Inner exceptions are being indented
    2013-11-14 19:01:45 Slp:
    2013-11-14 19:01:45 Slp: Exception type: System.ArgumentException
    2013-11-14 19:01:45 Slp:     Message:
    2013-11-14 19:01:45 Slp:         sku
    2013-11-14 19:01:46 Slp:     Stack:
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore
    store)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.EventHandler.Invoke(Object sender, EventArgs e)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
    2013-11-14 19:01:46 Slp:         at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.OnClick(EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Button.OnClick(EventArgs e)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.ButtonBase.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Button.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    2013-11-14 19:01:46 Slp:         at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    2013-11-14 19:02:13 Slp: Watson Bucket 1
     Original Parameter Values
    2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
    2013-11-14 19:02:13 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
    2013-11-14 19:02:13 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
    2013-11-14 19:02:13 Slp: Parameter 3 : System.ArgumentException@-2147024809
    2013-11-14 19:02:13 Slp: Parameter 4 : System.ArgumentException@-2147024809
    2013-11-14 19:02:13 Slp: Parameter 5 : GatherUserSettings
    2013-11-14 19:02:13 Slp:
     Final Parameter Values
    2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
    2013-11-14 19:02:13 Slp: Parameter 1 : 0xC16B698F
    2013-11-14 19:02:13 Slp: Parameter 2 : 0xC16B698F
    2013-11-14 19:02:13 Slp: Parameter 3 : 0x6AD84D9E
    2013-11-14 19:02:14 Slp: Parameter 4 : 0x6AD84D9E
    2013-11-14 19:02:14 Slp: Parameter 5 : GatherUserSettings
    2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2013-11-14 19:02:22 Slp: sku
    2013-11-14 19:02:23 Slp: Watson bucket for exception based failure has been created
    2013-11-14 19:02:23 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey
    2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2013-11-14 19:02:23 Slp: Sco: Attempting to get registry value DW0200
    2013-11-14 19:03:07 Slp: Submitted 1 of 1 failures to the Watson data repository
    2013-11-14 19:03:12 Slp:
    2013-11-14 19:03:12 Slp: ----------------------------------------------------------------------
    2013-11-14 19:03:12 Slp:
    2013-11-14 19:03:12 Slp: Error result: -213508975
    2013-11-14 19:03:12 Slp: Result facility code: 838
    2013-11-14 19:03:12 Slp: Result error code: 7313

  • SQL Server Service Pack Install and SSRS Scale Out Environment

    We have an error in our SSRS environment that looks to be addressed in SQL Server 2008 R2 SP3. Our set up is a scale out environment, 2 SSRS app servers and 1 SSRS database server. For simplicity as we are moving to 2012 soon, I would like to only install
    the service pack on one of the SSRS app servers. Anyone aware of any reason besides keeping servers consistent to not do this? I don't want to go through the time to upgrade the SSRS SQL Server if I don't have to.
    Thanks

    Hello,
    If you apply the service pack on the database server first, front-ends may not be able to provide service again until you
    apply the SP to them too. I have no knowledge of other possible issue.
    Remember to backup SSRS databases and encryption key before applying the service pack.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Issue With Report Builder After Installing SP3 for SQL 2008 R2

    Hello.  We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend.  You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
          Server  : Microsoft-HTTPAPI/2.0
          X-AspNet-Version: 2.0.50727
     Application url   :
    http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
          Server  : Microsoft-HTTPAPI/2.0
          X-AspNet-Version: 2.0.50727
    IDENTITIES
     Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
     Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
    APPLICATION SUMMARY
     * Online only application.
     * Trust url parameter is set.
    ERROR SUMMARY
     Below is a summary of the errors, details of these errors are listed later in the log.
     * Activation of
    http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
      + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
    COMPONENT STORE TRANSACTION FAILURE SUMMARY
     No transaction error was detected.
    WARNINGS
     There were no warnings during this operation.
    OPERATION PROGRESS STATUS
     * [10/15/2014 9:35:56 AM] : Activation of
    http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
     * [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
     * [10/15/2014 9:36:29 AM] : Installation of the application has started.
     * [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
     * [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
     * [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
    processorArchitecture=msil.
     * [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
    processorArchitecture=msil.
     * [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
    ERROR DETAILS
     Following errors were detected during this operation.
     * [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
      - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
      - Source: System.Deployment
      - Stack trace:
       at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
       at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
       at System.Deployment.Application.ComponentVerifier.VerifyComponents()
       at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
    notification, DownloadOptions options)
       at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
       at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
       at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
       at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
    COMPONENT STORE TRANSACTION DETAILS
     No transaction information is available.

    Hi DMcGarveyt,
    This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
    Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • SQL 2008 R2 SP1 installation issue

    Hi,
    I have upgraded my SQL server 2008 R2 to SP1, and the installation does not return any error message and consider successful. However during the time I configure reporting services, it display an error message below. After troubleshoot for few days,
    only I found out my database engine is SP1, but my reporting service still remain as R2 version.
    Anyway to repair my reporting service to SP1 or I can just rerun the SP1 installer for reporting service? I got one database running inside this server, that's why I need be extra careful with the work I do.
    component SMS_SRS_REPORTING_POINT on computer reported:  The report server service is not running on Reporting Service Point server ; start the service to enable reporting.              
    Regards.

    Here is the log file summary.txt
    Overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Exit message:                  Passed
      Start time:                    2013-11-05 21:07:05
      End time:                      2013-11-05 21:24:25
      Requested action:              Patch
    Instance MSSQLSERVER overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Exit message:                  Passed
      Start time:                    2013-11-05 21:09:43
      End time:                      2013-11-05 21:24:19
      Requested action:              Patch
    Machine Properties:
      Machine name:                  MYSQL2
      Machine processor count:       8
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                
    1033                 Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                  
    1033                 Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text Search                        
    1033                 Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                       
    1033                 Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services                      
    1033                 Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Standard Edition    
    10.50.1765.0    No       
      Sql Server 2008 R2                                                      
    Management Tools - Complete              1033                 Standard Edition     10.50.1765.0   
    No       
      Sql Server 2008 R2                                                      
    Client Tools Connectivity                1033                 Standard Edition    
    10.50.1765.0    No       
      Sql Server 2008 R2                                                      
    Client Tools Backwards Compatibility     1033                 Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2                                                      
    Client Tools SDK                         1033                
    Standard Edition     10.50.1765.0    No       
      Sql Server 2008 R2                                                      
    Integration Services                     1033                 Standard Edition    
    10.50.1765.0    No       
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       1
      KBArticle:                     KB2528583
      KBArticleHyperlink:           
    http://support.microsoft.com/?kbid=2528583
      PatchType:                     SP
      AssociateHotfixBuild:          0
      Platform:                      x64
      PatchLevel:                    10.51.2500.0
      ProductVersion:                10.50.1600.1
      GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
      PackageName:                   SQLServer2008-KB2528583-x64.exe
      Installation location:         d:\ffbb86a2c14bdbf15b5d5fbb1bb582a1\x64\setup\
    Updated product edition:
      Instance             Edition            
      MSSQLSERVER          STANDARD           
    User Input Settings:
      ACTION:                        Patch
      ALLINSTANCES:                  False
      CLUSTERPASSIVE:                False
      CONFIGURATIONFILE:            
      ENU:                           True
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      PASSPHRASE:                    *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      UIMODE:                        Normal
      X86:                           False
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131105_210654\SystemConfigurationCheck_Report.htm

  • Win App Deployment include SQL 2008 Express - Check if any SQL Server version already exist

    Hi there
    I have a application that is deploying and installing correctly (Setup and Deployment Project in VS 2008) and has SQL 2008 Express as a pre-requisite. SQL Express installs fine if not found but I don't want it to be installed if any other version of SQL
    Server already exists on the target computer. What do I have to adjust in the Bootstrapper package (package.xml or product.xml)  for SQL Express to do this check? Is the change done within the Bootstrapper package? Do I have to create a Custom Action
    in my Deployment project for this check? Any help is appreciated.
    Thanks
    Dweezil

    Hi Dweezil,
    If you use SQL Express Bootstrapper, you can add the SqlExpressChk.exe package file in the product.xml to check that if SQL Server is already exists. 
    However, please note that SqlExpressChk.exe is limited to only the default instance name, SQLEXPRESS, it won't detect other named instances. A registry check is required when detecting existing SQL Server with custom instance name.
     For more details, please review this
    blog.
    There is also a similar thread for your reference.
    https://dotnetinstaller.codeplex.com/discussions/245326
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.

  • Linked server issue using SQLNCLI versions on SQL 2008 & 2014

    Hi all,
    Our product creates databases on a sql server 2008 instance and creates linked servers between them to use distributed queries.
    This looks like: "EXEC sp_addlinkedserver 'linkDatabaseA', '', 'SQLNCLI10', '.', NULL, NULL, 'DatabaseA'"".
    Distributed queries from second database to DatabaseA work fine in this scenario.
    As we want to support both SQL 2008 and SQL 2014 in the next product version, I changed this to SQLNCLI11 as the provider
    and tested on SQL 2008 after installation of the SQLNCLI11 driver.
    This resulted in following error message:
    Msg 468, Level 16, State 9, Line 7
    Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
    This is very suprising as the SQL Server 2008 instance and both DB's have "SQL_Latin1_General_CP1_CI_AS" as their collation sequence.
    Then I tried the opposite, installing SQLNCLI10 on SQL 2014. This gave exactly same error! Using SQLNCLI11 went fine ofcourse.
    Generation sp_addlinkedserver statements with correct driver based on SQL version, I'd rather not do (some of the calls are
    generated in SQL from settings in other db tables which are also used for external connx) and adding COLLATE to the queries also
    has consequences like performance degradation. Adding collate on SQL 2014 with SQLNCLI10 as linked server provider results in
    following error:
    Msg 7399, Level 16, State 1, Line 1617
    The OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA" reported an error. Access denied.
    Msg 7301, Level 16, State 2, Line 1617
    Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA".
    Q: Is there any way that SQLNCLI11 can be made to work for linked servers on SQL2008 (preferred solution) or SQLNCLI10 on SQL2014?
    Thx for any feedback.
    Regards, Jouke

    Hi Sofiya,
    Thx for replying.
    For the deployment reasons  mentioned above, I would prefer to use only one SQLNCLI version in both 2008R2 & 2012/2014 scenario's. Most preferred would ofcourse be SQLNCLI11 as this is the latest.
    This would mean that I'd like to be able to configure linked server in SQL2008R2 using SQLNCLI11 driver.
    I would expect that it would be downward compatible with SQLNCLI10 for all client usage, including linked server, which in essence is one SQL DB doing client access to another SQL DB either on same server instance or another. I suspect it requests DB
    metadata from remote DB in order to make decisions and this seems not to work in my setup. If this metadata API is part of the public API, this could indicate that medadata API has been broken in SQLNCLI11 (heavy speculation on my part here!), which could
    also affect other usage (eg. linked server between SQL2008(R2) and SQL2012/2014 instances, (I'll try to set this up and test this, might take a few days. If someone is volunteering, below are db table schemes and query, update @datasrc to point to remote sql
    server instance)).
    Regards, Jouke
    -- This script to run on SQL2008(R2). On SQL2012/2014, install SQLNCLI10 and change @provider in sp_addlinkedserver call.
    -- Pre:
    --   - DatabaseA and DatabaseB are created manually in SSMS
    --   - SQLNCLI11 has been installed
    USE [DatabaseA]
    GO
    CREATE TABLE [dbo].[DatabaseATable](
     [IdField] [int] NOT NULL,
     [LinkField] [nchar](10) NULL,
     CONSTRAINT [PK_DatabaseATable] PRIMARY KEY CLUSTERED
     [IdField] ASC
    ) ON [PRIMARY]
    GO
    EXEC master.dbo.sp_addlinkedserver @server = N'linkDatabaseA', @srvproduct=N'',@provider=N'SQLNCLI11', @datasrc=N'.', @catalog=N'DatabaseA'
    GO
    USE [DatabaseB]
    GO
    CREATE TABLE [dbo].[DatabaseBTable](
     [IdField] [int] NOT NULL,
     [LinkField] [nchar](10) NULL,
     CONSTRAINT [PK_DatabaseBTable] PRIMARY KEY CLUSTERED
     [IdField] ASC
    ) ON [PRIMARY]
    GO
    SELECT b.*, a.*
    FROM DatabaseBTable AS b WITH(NOLOCK)
    JOIN linkDatabaseA.DatabaseA.dbo.DatabaseATable AS a
      ON a.LinkField = b.LinkField
    Hi Jouke Numan,
    According to your description, I install SQL Native Client 11.0 OLE DB Provider in SQL Server 2008R2, and as you post, create two database on the same instance with collation in server default, then create Linked Server with SQLNCI11.0.
     When I run the query statement, it can execute well. It also do not occur the collation conflict. I still recommend you check the collation of server, database, or column and so on.
    SQL Server Native Client 11.0 provides OLE DB support to applications connecting to SQL Server versions 2005, 2008, 2008R2, 2012. So for the deployment reasons, you can choose the only SQLNCLI11.0 in both SQL Server 2008R2 and SQL Server 2012/2014.
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

Maybe you are looking for

  • '*' in the file name

    hi SAP gurus Can u please explain me what if a file name in the sender or receiver configuration of the communication channel for example health*.txt.pgp thanks

  • Multichannel sound through HDMI

    I have a late 2011 Mac Mini running Mountain Lion and being used as a media server connected to a Linn Akurate DSM. The HDMI output will only output stereo, and when using Audio Midi no choice is given to choose a multichannel output. Moreover for th

  • Bank Reconcilation statement Session creation

    Dear Experts, I have configured all the steps required to do manual bank reconcilation statement in SAP. I am able to save and post the statement. I have created my own variant for BRS and I have done the variant assignment in FF67(under  Setting-Spe

  • The library module in 4.3 version does not show all the images

    The library module in the version 4.3 of Lightroom does not show all the images. They are marked with gray boxes instead of images. This is especially true of the images which I tried to import to Lightroom since I downloaded 4.3 a few weeks ago. If

  • Extracting certain files from a jar

    I am creating a jar that when d-clicked on will extract its files to the computer the jar resides on. Here is my question: how do I get it to only extract certain files(ie. all files except the classes used to give the extraction command upon d-click