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.
Similar Messages
-
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-81439b542cf8Hi 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. -
Hello all,
I have SQL express 2014 advance edition installed ..
and i am connecting SQl server 2008 r2 instance which is in network
while creating datasource in Reportserver which has Express installed ..
got this error ..
please help me how to connect to remote server
Dilip Patil..Error message says it all.
With SQL Express, Data source should be local SQL DB.
With SQL Enterprise, Standard, BI edition, you can create Data soruce which are hosted on other servers.
Please refer similar thread:
https://social.msdn.microsoft.com/Forums/en-US/c0468e3f-bad7-47a7-a695-75c13762280a/the-feature-the-edition-of-reporting-services-that-you-are-using-requires-that-you-use-local-sql?forum=sqlreportingservices
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP] -
We had deployed Reporting Services / PowerPivot /Powerview for a customer and everything was tested and appeared to be working fine . However after installing the November CU we now get the following error :
"The feature Power View is not supported in this edition of Reporting Services"
Initially PowerPivot wasn't working either but that got resolved after re-installing the rssharepoint and sppowerpivot msi files. Has anyone faced this issue?Hi,
According to your description, my understanding is that the PowerView not work after installing the November CU Updates.
I check the November CU updates, it have no affects on the PowerView or PowerPivot.
The reason for this issue may occur when the PowerPivot Service Application is not running after installing the CU updates.
Here is a detailed article for your reference:
http://support2.microsoft.com/default.aspx?scid=kb;EN-US;2889944
Best Regards
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jerry Guo
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. -
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,
CHi 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 -
SQL 2012 SP1 installation quick questions
I am installing my first SQL 2012 SP1 Enterprise Core (x64). The installation failed to install some services due to an error installing .Net framework 3.5. It was able to install successfully several features including Analysis Services
and Integration services, but not the Database Engine, Management tools and Reporting services.
Note: I ran the set up and my user is an administrator in the target server, but I did not right clicking on setup.exe and "Run as administrator" .
I have two questions
1) Did I had to run the setup by Right clicking on setup.exe and "Run as administrator"?
2) Now that my installation failed. After installing the missing requirements....Do I:
a) Uninstall the current failed installation
b) Do I attempt to install again "on top of the existing installation".
c) Redo the whole server and start fresh.
I am open to expert suggestions. Please help
PaulinoHello,
1. If you are already logged in as Administrator, there is no need to use the Run as Administrator option.
2. I would choose to uninstall everything and install again. Since were are installing from the Command Prompt, and we do not have the
GUI, and we are not familiar with the command line options.
Please use the following article to install SQL Server 2012 on Windows Server Core:
http://www.sqlcoffee.com/SQLServer2012_0005.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
when I tried to open document library in Windows explorer view by click 'Open with Explorer', it popped up “Your client does not support opening list with windows explorer”
OS: Windows Server 2008 Enterprise x64
IE: 9.0 32bit
webcient service is runing
HKLM\System\CurrentControlSet\services\WebClient\Parameters and changed the BasicAuthLevel to 2 instead of 1.
Anybody knows how?
Thanks.Did you add your site to trusted site list?
http://sharepoint.stackexchange.com/questions/15098/your-client-does-not-support-opening-this-list-with-windows-explorer
--Cheers -
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,
KAHi 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 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 -
SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?
Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites: Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites: Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace: at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace: at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session EndedHi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li -
Reporting Services install on SQL 2012 SP1 instance blank
Sorry for the duplicate . . . didn't think the first on posted due to VDI locking up.
I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.Hi,
How are things going? Please let us know if there is any progress.
Regards.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Critical SMS_NOTIFICATION_SERVER ERROR sccm 2012 R2 WITH SQL 2012 SP1
Environement
SCCM 2012 R2
SQL 2012 SP1
On the same server
In sccm console i have in Monitoring - System Status - Component Status
critical SMS_NOTIFICATION_SERVER ERROR
Here are the two error that keep popping up
ERROR 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Folowing message
ERROR 4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
Here are the 2 logs
bgbsetuplog
<02/28/14 09:00:53> ====================================================================
<02/28/14 09:00:53> SMSBGB Setup Started....
<02/28/14 09:00:53> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<02/28/14 09:00:53> Installing Pre Reqs for SMSBGB
<02/28/14 09:00:53> ======== Installing Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Found 1 Pre Reqs for Role SMSBGB
<02/28/14 09:00:53> Pre Req SqlNativeClient found.
<02/28/14 09:00:53> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<02/28/14 09:00:53> Pre Req SqlNativeClient is already installed. Skipping it.
<02/28/14 09:00:53> ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Installing the SMSBGB
<02/28/14 09:00:53> Passed OS version check.
<02/28/14 09:00:53> IIS Service is installed.
<02/28/14 09:00:53> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<02/28/14 09:00:53> New SMSBGB is the same product code. This is a minor upgrade.
<02/28/14 09:00:53> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<02/28/14 09:00:53> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<02/28/14 09:01:01> bgbisapi.msi exited with return code: 0
<02/28/14 09:01:01> Installation was successful.
<02/28/14 09:01:01> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:04> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:04> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:07> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:07> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<02/28/14 09:01:07> Fatal MSI Error - bgbisapi.msi could not be install
bgpisapi.log
MSI (s) (00:60) [09:01:01:660]: Product: BGB http proxy -- Configuration completed successfully.
MSI (s) (00:60) [09:01:01:661]: Windows Installer reconfigured the product. Product Name: BGB http proxy. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (00:60) [09:01:01:665]: Deferring clean up of packages/files, if any exist
MSI (s) (00:60) [09:01:01:665]: MainEngineThread is returning 0
MSI (s) (00:04) [09:01:01:670]: RESTART MANAGER: Session closed.
MSI (s) (00:04) [09:01:01:670]: No System Restore sequence number for this installation.
=== Logging stopped: 2/28/2014 9:01:01 ===
MSI (s) (00:04) [09:01:01:674]: User policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:04) [09:01:01:675]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:677]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (00:04) [09:01:01:678]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:678]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:04) [09:01:01:679]: Destroying RemoteAPI object.
MSI (s) (00:B8) [09:01:01:679]: Custom Action Manager thread ending.
MSI (c) (3C:B8) [09:01:01:686]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (3C:B8) [09:01:01:686]: MainEngineThread is returning 0
MSI (c) (3C:B0) [09:01:01:690]: RESTART MANAGER: Session closed.
=== Verbose logging stopped: 2/28/2014 9:01:01 ===Problem not fixed SORRY GUY'S
Environement
1 SERVER
WINDOWS SERVER 2012 R2
SQL SERVER 2012 SP1
SCCM 2012 R2
ERROR in system center
Message ID 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Message ID
4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
BGPSETUP.LOG
<03/05/14 09:49:33> ====================================================================
<03/05/14 09:49:33> SMSBGB Setup Started....
<03/05/14 09:49:33> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<03/05/14 09:49:33> Installing Pre Reqs for SMSBGB
<03/05/14 09:49:33> ======== Installing Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Found 1 Pre Reqs for Role SMSBGB
<03/05/14 09:49:33> Pre Req SqlNativeClient found.
<03/05/14 09:49:33> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<03/05/14 09:49:33> Pre Req SqlNativeClient is already installed. Skipping it.
<03/05/14 09:49:33> ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Installing the SMSBGB
<03/05/14 09:49:33> Passed OS version check.
<03/05/14 09:49:33> IIS Service is installed.
<03/05/14 09:49:33> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<03/05/14 09:49:33> New SMSBGB is the same product code. This is a minor upgrade.
<03/05/14 09:49:33> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<03/05/14 09:49:33> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<03/05/14 09:49:41> bgbisapi.msi exited with return code: 0
<03/05/14 09:49:41> Installation was successful.
<03/05/14 09:49:41> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:43> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:43> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:45> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:45> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<03/05/14 09:49:45> Fatal MSI Error - bgbisapi.msi could not be installed.
<03/05/14 09:49:45> ~RoleSetup().
BGBISAPI.LOG
=== Verbose logging started: 3/5/2014 9:49:33 Build type: SHIP UNICODE 5.00.9600.00 Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
MSI (c) (08:C0) [09:49:33:974]: Resetting cached policy values
MSI (c) (08:C0) [09:49:33:974]: Machine policy value 'Debug' is 0
MSI (c) (08:C0) [09:49:33:974]: ******* RunEngine:
******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
******* Action:
******* CommandLine: **********
MSI (c) (08:C0) [09:49:33:974]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (08:C0) [09:49:33:974]: Grabbed execution mutex.
MSI (c) (08:C0) [09:49:34:021]: Cloaking enabled.
MSI (c) (08:C0) [09:49:34:021]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (08:C0) [09:49:34:025]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C4:E4) [09:49:34:039]: Running installation inside multi-package transaction D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E4) [09:49:34:039]: Grabbed execution mutex.
MSI (s) (C4:E8) [09:49:34:045]: Resetting cached policy values
MSI (s) (C4:E8) [09:49:34:045]: Machine policy value 'Debug' is 0
MSI (s) (C4:E8) [09:49:34:045]: ******* RunEngine:
******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
******* Action:
******* CommandLine: **********
MSI (s) (C4:E8) [09:49:34:047]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C4:E8) [09:49:34:053]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:057]: SRSetRestorePoint skipped for this transaction.
MSI (s) (C4:E8) [09:49:34:058]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (C4:E8) [09:49:34:060]: File will have security applied from OpCode.
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi' against software restriction policy
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi has a digital signature
MSI (s) (C4:E8) [09:49:34:067]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (C4:E8) [09:49:34:067]: MSCOREE not loaded loading copy from system32
MSI (s) (C4:E8) [09:49:34:077]: End dialog not enabled
MSI (s) (C4:E8) [09:49:34:077]: Original package ==> D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E8) [09:49:34:077]: Package we're running from ==> C:\Windows\Installer\3897f9.msi
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:094]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisablePatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:096]: Transforms are not secure.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log'.
MSI (s) (C4:E8) [09:49:34:096]: Command Line: REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR=D:\Program Files\SMS_CCM CCMSERVERDATAROOT=D:\Program Files\Microsoft Configuration Manager USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE
SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CURRENTDIRECTORY=D:\Program Files\Microsoft Configuration Manager\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=5384
MSI (s) (C4:E8) [09:49:34:096]: Product Code passed to Engine.Initialize: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table before transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table after transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product registered: entering maintenance mode
MSI (s) (C4:E8) [09:49:34:096]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:096]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:096]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C4:E8) [09:49:34:096]: Specifed source is already in a list.
MSI (s) (C4:E8) [09:49:34:096]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'DisableBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Adding new sources is allowed.
MSI (s) (C4:E8) [09:49:34:097]: Package name retrieved from configuration data: 'bgbisapi.msi'
MSI (s) (C4:E8) [09:49:34:099]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'DisableMsi' is 1
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:099]: Running product '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}' with elevated privileges: Product is assigned.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALL property. Its value is 'ALL'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'vmaus'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMINSTALLDIR property. Its value is 'D:\Program Files\SMS_CCM'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMSERVERDATAROOT property. Its value is 'D:\Program Files\Microsoft Configuration Manager'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSPORTS property. Its value is '80'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSLPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLPORTS property. Its value is '443'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSL property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLSTATE property. Its value is '0'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMENABLELOGGING property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGLEVEL property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXSIZE property. Its value is '1000000'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXHISTORY property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5384'.
MSI (s) (C4:E8) [09:49:34:100]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '1ea81ab83bbb7c48a58c04b46f112051'.
MSI (s) (C4:E8) [09:49:34:104]: RESTART MANAGER: Session opened.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:104]: TRANSFORMS property is now:
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Favorites
MSI (s) (C4:E8) [09:49:34:108]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Documents
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (C4:E8) [09:49:34:110]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (C4:E8) [09:49:34:112]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Local
MSI (s) (C4:E8) [09:49:34:114]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Pictures
MSI (s) (C4:E8) [09:49:34:124]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:128]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:129]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:131]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:132]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (C4:E8) [09:49:34:135]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:137]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:138]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:139]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:141]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (C4:E8) [09:49:34:144]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting AdminUser property to 1 because the product is already installed managed and per-machine
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\3897f9.msi'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi'.
MSI (s) (C4:E8) [09:49:34:156]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
MSI (s) (C4:E8) [09:49:34:159]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (C4:E8) [09:49:34:159]: Machine policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: User policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding QFEUpgrade property. Its value is '1'.
=== Logging started: 3/5/2014 9:49:34 ===
MSI (s) (C4:E8) [09:49:34:161]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:161]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:161]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (s) (C4:E8) [09:49:34:163]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (C4:E8) [09:49:34:163]: Doing action: INSTALL
Action start 9:49:34: INSTALL.
MSI (s) (C4:E8) [09:49:34:165]: Running ExecuteSequence
MSI (s) (C4:E8) [09:49:34:165]: Doing action: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61
MSI (s) (C4:E8) [09:49:34:166]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI (s) (C4:E8) [09:49:34:167]: PROPERTY CHANGE: Adding SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
MSI (s) (C4:E8) [09:49:34:167]: Doing action: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61
Action ended 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
MSI (s) (C4:E8) [09:49:34:169]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI -
SQL 2012 SP1 and SCCM 2012 SP1
Hi,
I am installing SCCM 2012 SP1 with SQL 2012 SP1 in Stand-Alone mode. But I am receiving error:"the service broker endpoint cannot listen on port 4022 because it is in use by another process"
I saw in SQL (SQL Server Configuration Manager) that I am using port 4022 without dinamic port.
Thaks.
Lessandro Zampieri - http://lezampieri.comThanks for the reply.
C:\>netstat -ano
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 780
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:4022 0.0.0.0:0 LISTENING 4664
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 528
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 836
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 900
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49217 0.0.0.0:0 LISTENING 616
TCP 0.0.0.0:49219 0.0.0.0:0 LISTENING 4184
TCP 0.0.0.0:49389 0.0.0.0:0 LISTENING 2056
TCP 0.0.0.0:49627 0.0.0.0:0 LISTENING 5060
TCP 127.0.0.1:49390 0.0.0.0:0 LISTENING 2056
TCP 127.0.0.1:49628 0.0.0.0:0 LISTENING 5060
TCP 127.0.0.1:57593 0.0.0.0:0 LISTENING 4664
TCP 192.168.100.30:139 0.0.0.0:0 LISTENING 4
TCP 192.168.100.30:445 192.168.100.20:49420 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49421 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49422 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49423 ESTABLISHED 4
TCP 192.168.100.30:4022 192.168.100.30:61430 ESTABLISHED 4664
TCP 192.168.100.30:4022 192.168.100.30:61496 ESTABLISHED 4664
TCP 192.168.100.30:49627 192.168.100.40:55914 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55915 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55921 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55922 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55926 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55927 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55928 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55929 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55930 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55967 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55992 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55998 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56001 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56002 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56009 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56077 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56211 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56656 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56687 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56817 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56891 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56946 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56959 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57027 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57072 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57223 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57240 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57248 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57268 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57292 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57293 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57294 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57311 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57312 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57314 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57320 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57340 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57342 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57343 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57369 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57372 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57379 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57385 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57386 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57387 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57388 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57389 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57390 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57391 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57392 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57393 ESTABLISHED 5060
TCP 192.168.100.30:61430 192.168.100.30:4022 ESTABLISHED 4112
TCP 192.168.100.30:61496 192.168.100.30:4022 ESTABLISHED 4112
TCP 192.168.100.30:61537 192.168.100.10:49158 TIME_WAIT 0
TCP [::]:80 [::]:0 LISTENING 4
TCP [::]:135 [::]:0 LISTENING 780
TCP [::]:443 [::]:0 LISTENING 4
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:4022 [::]:0 LISTENING 4664
TCP [::]:5985 [::]:0 LISTENING 4
TCP [::]:47001 [::]:0 LISTENING 4
TCP [::]:49152 [::]:0 LISTENING 528
TCP [::]:49153 [::]:0 LISTENING 836
TCP [::]:49154 [::]:0 LISTENING 900
TCP [::]:49155 [::]:0 LISTENING 624
TCP [::]:49156 [::]:0 LISTENING 624
TCP [::]:49217 [::]:0 LISTENING 616
TCP [::]:49219 [::]:0 LISTENING 4184
TCP [::]:49389 [::]:0 LISTENING 2056
TCP [::]:49627 [::]:0 LISTENING 5060
TCP [::1]:49390 [::]:0 LISTENING 2056
TCP [::1]:49628 [::]:0 LISTENING 5060
TCP [::1]:57593 [::]:0 LISTENING 4664
UDP 0.0.0.0:123 *:* 948
UDP 0.0.0.0:500 *:* 900
UDP 0.0.0.0:1434 *:* 3000
UDP 0.0.0.0:4500 *:* 900
UDP 0.0.0.0:5355 *:* 124
UDP 127.0.0.1:51181 *:* 4132
UDP 127.0.0.1:51338 *:* 124
UDP 127.0.0.1:55475 *:* 900
UDP 127.0.0.1:59835 *:* 1628
UDP 127.0.0.1:60840 *:* 3596
UDP 127.0.0.1:62010 *:* 1816
UDP 127.0.0.1:62390 *:* 4112
UDP 127.0.0.1:64129 *:* 624
UDP 192.168.100.30:137 *:* 4
UDP 192.168.100.30:138 *:* 4
UDP [::]:123 *:* 948
UDP [::]:500 *:* 900
UDP [::]:1434 *:* 3000
UDP [::]:4500 *:* 900
All things are correct?
Att.,
Lessandro Zampieri - http://lezampieri.com -
Hi,
Please help. I was trying to remove a SQL 2012 SP1 two node clustered instance using setup (Mantenance -> Remove Node)
I started by doing this on passive node (and was successful) but when I ran setup on active node just before finishing successfully I got this error:
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
The resource 'BCK_SG1DB' could not be moved from cluster group 'SQL Server (SG1DB)' to cluster group 'Available Storage'.
Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015.
Description: The operation failed because either the specified cluster node is not the owner of the resource, or the node
is not a possible owner of the resource.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE8049925%25400x42B4DED7
BUTTONS:
OK
I noticed that SG1DB instance was removed on both nodes but on Failover Cluster Manager -> Services and Applications the SQL server instance for SG1DB is still there. So I tried to delete it but got the error:
Failed to delete SQL Server SG1DB. An error was encountered while deleting the cluster service or
application SQL Server SG1DB. Could not move the resource to available storage. An error occured
while moving the resource BCK_SG1DB to the clustered service or application Available Storage
Any ideas why it failed or how could I delete the SQL server instance from Clauster?
ThxHello,
Please read the following resource.
https://support.microsoft.com/en-us/kb/kbview/313882?wa=wsignin1.0
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Maybe you are looking for
-
Handbrake Version 0.9.4 x86_64 No H.264 Support
I gave my iPod 30GB Video 5G to my daughter. Before doing so I wanted to put some of her favorite movies on it. I worked for hours trying to figure out why the films wouldn't transfer to the iPod, even after consulting with Apple Support. (BTW, The L
-
Show an image on Url address in oracle form
hi all i use oracle 10g form i want show a dynamic image that create by cgi program on a url address i used READ_IMAGE_FILE but by url address function din not wolrked plz help me how can i show this type on image?
-
"Get add-ons" page on "add-ons manager" in russian instead of english.What to do?
"Get add-ons" page on "add-ons manager" in russian instead of english. How can i change that specific page back to English.
-
AE CS6 and tearing of XD CAM EX Mp4 source footage
Hi I'm getting tearing artifacts in CS6 when using XD CAM EX MP4 source footage. This does NOT occur on a colleague's CS5.5 install with the same files. I found a discussion from last year at http://forums.adobe.com/thread/1009064 , where the issue w
-
Ios 7.0 upgrading problem
I just updated my ipad to ios 7.0 and i cant open my ipad now coz the picture says connect to itunes and when i connect to itunes in my laptop says need to restore my ipad. when i restore it it says again that my ipad is not connected to internet. ho