2012 Guest Clustered SQL instance - Upgrade platform

Currently I have several working 2012 Guest clusters for various functions. I'm now looking at upgrading my "SQL Guest Cluster" which has 2 nodes (VMs) at Server 2012, 2 SQL 2012 instances, and is connected to shared storage through Virtual
Fiber Channel.
I know I can't have mixed OS levels in a Failover Cluster, which is what is making this difficult.
What would be the best method for upgrading the 2 nodes to Server 2012 r2 (ie no-minimum downtime)?
For a file share guest cluster I was able to evict a node, remove failover role, upgrade node, create new cluster ("name_r2_cluster"), migrate File Server Role to new cluster using cluster tool...however SQL is not supported for the copy function.
Thanks in advance!

Hi,
Hyper-V live migration has been updated to support migrating Hyper-V virtual machines in Windows Server 2012 to Hyper-V in Windows Server 2012 R2. You can use the cross-version
live migration migrate the vms.
The related KB:
What’s New in Hyper-V for Windows Server 2012 R2
http://technet.microsoft.com/en-us/library/dn282278.aspx#bkmk_live_migration
Migrate Hyper-V to Windows Server 2012 R2 from Windows Server 2012
http://technet.microsoft.com/en-us/library/dn486799.aspx
Hyper-V Cluster Using Cluster Shared Volumes (CSV) Migration
http://technet.microsoft.com/en-us/library/dn486822.aspx
The similar thread:
Windows Server 2012 Failover Cluster Virtual Fibre Channel Adapter Live Migration Error
http://social.technet.microsoft.com/Forums/fr-FR/2512d82e-7dda-4bb9-a96d-533bea79b2cb/windows-server-2012-failover-cluster-virtual-fibre-channel-adapter-live-migration-error?forum=winserverhyperv
Hope this helps.
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.

Similar Messages

SCOM 2012 Installation problem - SQL Instance name

Hi All
Strange problem here, I wonder if anyone else has had the same issue.
I have a two-node SQL Server 2014 (Enterprise) Database server configured with a "SQL AlwaysOn Availability Group & Listener". The listener DNS name is: sql-ag-listener
On a separate server VM I attempted to install SCOM 2012 R2 - but when it came to the setup prompt to enter the "Servername & Instance" for the SQL server / Databases it will not accept my SQL AG Listener DNS name. However if I enter any
of the two individual SQL node names (SQL1 or SQL2) then it does accept those values and proceeds with the setup wizard. I do have a DNS entry for the SQL AG name.
All VMs are hosted in Azure. The SQL Servers are in their own Cloud Service and the SCOM MS Servers are in their own Cloud service.
I tried moving one of the SCOM MS Servers to the same Cloud Service container as the SQL Servers - still the same result.
Interestingly (as a test) - I started the SCOM 2012 Installation wizard on one of the SQL Servers and it DID accept the SQL AG value as the "Servername & Instance".
No firewalls are on. The VM endpoints allow SQL port 1433. Also, I can Telnet to the SQL Servers using 'telnet > O sql-ag-listener 1433' - response = Connected....
Not sure why this wont accept my virtual SQL AG name....?
thanks

Hi,
As when you install SCOM on one of your SQL server, then the AG name can be resolved, so it seems like this issue related with network resolution.
On the server where you want to run SCON setup, please use NSLOOKUP command to make sure it can the AG name to an IP address.
In addition, when you run the setup, don't select reporting server, as reporting server role need to install on a SQL server holding SSRS.
We still can install SCOM on normal database, and then add them into availability group later:
Add SCOM Databases to Availability Groups
http://www.tech-coffee.net/alwayson-part-8-methods-to-add-database-scom/
Regards,
Yan Li
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]

SCCM 2012 Reporting point server instance blank

I have installed SCCM 2012 With remote SQL database server successfully, at the time of Reporting service point role installation, its verified the SCCm database successfully but SQL server service instance is blank, what would be the reason....
Below my SCCM architecture:
1. Created one Database in Remote server SQL server is in failover cluster active passive mode
2. Configured Reporting services in active mode.
3. at the time of reporting point role installed failover cluster database name given and its successfully verified with SCCM_123 database.
4. on the instance name showing blank.
Please help me if anyone facing this type of problem.
Thanks in advance.
Rishi!!
Regards, Rishi

It is not totally intuitive when installing the Reporting Point role with a cluster. When installing a Failover Cluster, SSRS can only get put on one node or on its own box, as it uses NLB for scale-out not FoC. SSRS is also not configured by
default if you use it with a clustered SQL instance, so you have to open SSRS Configuration Tool and make sure the ReportServerDB is created, and that the URLs can be browsed. Once that is done, then try adding it in CfgMgr:
In CfgMgr, In the Administration workspace, expand Site Configuration, and then click
Servers and Site System Roles.
Select the node that has SSRS installed on it (not the Failover Cluster virtual computer account). If SSRS is on its own box, first you have to go to
New site system and add the SSRS box.
Then, on the Home tab, in the Server group, click
Add Site System Role. The Add Site System Roles Wizard opens. Choose Reporting Point, and after verifying the connection to the CfgMgr DB, the instance name should populate.
http://technet.microsoft.com/en-us/library/gg712698#BKMK_InstallReportingServicesPoint
http://social.technet.microsoft.com/Forums/en-HK/configmanagerdeployment/thread/390a6ea8-8a24-47d0-b6ad-2e1063bbc72d

SQL Server Upgrade Advisor 2014 - Database Compatibility Level checking

I have the following scenario... I have a database server running SQL Server 2008 R2 (10.50.4260). On that server I restored a database from SQL Server 2005. Looking at the compatibility level through the properties of the database (using SSMS) and
by querying against sys.databases, I can see the database has the compatibility level of 90, which is what I expected.
In looking to bring this database over to a SQL Server 2014 database server, I have run the SQL Server Upgrade Advisor 2014 tool as well as the SQL Server Upgrade Advisor 2012 tool. With the 2014 tool, my expectation would be that it would warn me
that the compatibility level will be upgraded to 10 (or something), however, I received no such warning. I ran the 2012 version of the tool as well, expecting that I might get a deprecation warning (or something), no such luck. I have run the 2014
tool from my computer and from another one, same results.
Does the upgrade advisor not check for the compatibility level? Or does my configuration maybe have something to do with it (having it on a 2008 R2 server)? From looking at screenshots of when other people have ran the tool, I was under the impression
it checked this. See the link below for an example...
http://blogs.msdn.com/b/mspfe/archive/2012/12/06/sql-server-upgrade-advisor-considerations-when-upgrading-from-sql-2000-to-sql-2012.aspx
Thoughts anyone?

Lydia,
I agree with regards to the 2012 version. However, in SQL Server 2014, upgrading a database with a compatibility level of 90 sets
the database to compatibility level 100. See link below...
https://technet.microsoft.com/en-us/library/bb510680.aspx
Shouldn't the 2014 version of the advisor tool issue the same warning seen in the screenshot of the msdn blog post we both mentioned? As in... "After upgrade, compatibility levels <list of levels>, will be set to 100".
Hi JJordheim,
According to my test, SQL Server 2014 Upgrade Advisor also only raise warning when database compatibility level is less than 90 in the “SQL Server Parameters” page.
From your description, when database compatibility level is set to 90, SQL Server 2014 Upgrade Advisor should also raise warning, right? If so , this is a design issue of SQL Server 2014 Upgrade Advisor, personally, I recommend you
submit a feedback to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback . Your feedback enables Microsoft to offer the best software and deliver superior services.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation. The documentation takes me windows 2008 R2 which is different than 2012!
Tired and trying to pick myself up off the floor!
Greg
Gman

In general, DTC is not required for SQL 2012. But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum. They would be more likely to know those situations where FTC might be needed by SharePoint.
.:|:.:|:. tim

MS SQL 2005 clustered database instance.

Short Text
MS SQL cluster database instance - ONLY!
Long Text
Hi,
If possible could you please confirm that our planned landscape
migration is supported by SAP.
At present our PRD SAP system is a standalone instance that consists of
the database & central instance running on the same "HOST".
Current SAP PRD version:
ERP 2004 ECC 5.0 32 bit
MS SQL 2000 32 bit
both running on same host with OS Windows 2003 32 bit
We plan to upgrade/migrate our PRD SAP system to new 64 bit hardware
AND to move to a "Distributed" landscape installation i.e. database
instance & central instance installed on different HOSTS. Also, the
database instance WILL be clustered but the central instance will NOT
be clustered. There are also multiple NON-SAP MS SQL databases that
will run in the same cluster as the PRD SAP database instance.
SAP PRD version after migration:
SAP ERP 2004 ECC 5.0 64bit (running on X86_64 AMD64 hardware) on HOST'X'
MS SQL 2005 64 bit (running on IA64 hardware) on clustered HOST'Y'
Both running on Windows 2003 64 bit
My questions are:
1) Does SAP support a clustered MS SQL 2005 database instance that is
running on a clustered HOST along with NON-SAP MS SQL databases?
2)During the migration our PRD SAP MS SQL database will be upgraded
from MS SQL 2000 32 bit to MS SQL 2005 64 bit IA64, is this also
supported in a clustered istallation (database instance ONLY)?
3) The central PRD SAP instance will be running on x86_64 AMD64
hardware & the database instance will be running on 64 bit IA64
hardware. Is this configuration supported?
Thanking you inadvance.

Hi Greg,
Have you figured out the answer? We are trying do the exactly the same thing -- Move our SAP WAS 6.40 clustered central instance to a 64-bit hardware/SQL 2005/Clustered system. And this system has several non-SAP database on there. The biggest concern we have is whether SAP support this architecture. I posted a message here last year and several experts like Clas Hortien, N. P. C, in this form suggest NOT go to this architecture because SAP will not support it. One example, is that SAP/SQL requires server collation setting to SQL_Latin1_General_CP850_BIN2 and other databases may work on different collations.
Migrate SAP SQL Server database to co-exist with others
Anyway, if you or anyone in this form have some more information please share here.
Thanks,
Yujun Ran

Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.

We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR

SCCM 2012 R2 SQL Database Upgrade Fails : Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.

Hi Friends,
We have planned to upgrade our SCCM 2012 SP1 infrastructure to SCCM 2012 R2 so we have setup test environment to test SQL database upgrade before doing same in production.
But while testing SQL database upgrade on test machine, it is getting failed with below error.
ConfigMgrSetupWizard.log
ConfigMgrSetupWizard Verbose: 1 : Scripted setup failure handling callback called. Failure: 29.
ConfigMgrSetupWizard Verbose: 1 : Received error [Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.] from native code.
ConfigMgrSetup.log
ERROR: SQL Server error: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'ContentDistribution_PK'. Cannot insert duplicate key in object 'dbo.ContentDistribution'. The duplicate key value is (921). :
tr_ContentDistributionNotification_insert
ERROR: Failed to execute SQL Server command: ~-- ~-- Rebuild ContentDistribution tables ~-- ~IF (EXISTS(SELECT TOP 1 1 FROM dbo.SMSData WHERE SMSBuildNumber <= 7900) AND dbo.fnIsSecondary() != 1) ~BEGIN ~ exec spRebuildContentDistribution
@TruncateTables=0 ~END
Failed to create process of SetupWpf.exe.
Can anyone please help to get this resolved.
Thanks.

We found out that there were duplicate entries in the PkgStatus_G and the PkgServers_G tables in the SCCM DB. We identified them, deleted them , and then we were able to run the /TESTDBUPGRADE command and it went through fine. We performed
all of this on a COPY of the PROD DB and then moved the changes in PROD. Hope this helps someone.
- Dave

SCOM 2012 - How does SQL MP "know" which instances are available and active?

Using SCOM 2012 R2 with Microsoft's SQL MP 6.5.1.
Getting alerts occasionally for issues with SQL instances which are later found to be not active any more or removed from the SQL server.
Can someone explain how the MP determines which SQL instances are available? Is it a matter of simply reading folder structures on the various mount points, reading registry? Much appreciated for any tips.

SCOM SQL MP will using discovery to discovery SQL instance. Once the SQL instance is discovery, the SQL instance object persist in the database even though the SQL instance is removed.
Solution:
To clean up the objects you can run the Remove-SCOMDisabledClassInstance Powershell cmdlet. Then all the relationships that involve objects related to a disabled discovery is deleted.
Roger

Multiple SQL instance's in Web Platform installer

Hi Team,
Why it is not possible to install multiple instance's in Microsoft Web Platform Installer?
Or any options to customize the SQL Instance name during the installation through Web platform installer?
Kind Regards,
Arun

Hi Arun,
Microsoft Web Platform Installer runs a basic default installation, when you install SQL Server through Web Platform Installer, it uses default configuration values in installing process , including using the default instance name ’SQLExpress’. If you want
to change the SQL Server instance name or install additional SQL Server instances on your computer, you will need to perform a custom installation, then you can obtain SQL Server Express from the
Microsoft Download Center. For more details, please review this blog:
How should I Install SQL Server 2008.
In addition, if you have other questions about Web Platform Installer. I suggest you post the question in the Web Platform Installer forums at
http://forums.iis.net/1155.aspx/1?Web+Platform+Installer . It is appropriate and more experts will assist you.
Thanks,
Lydia Zhang

When to user Availability Group versus traditional Clustered SQL Server

Hi...
I'm trying to get my arms around when to use an SQL Server 2014 Availability Group. Here are the characteristics about my platform:
2 physical servers (Windows Server 2012 / SQL Server 2014)
Both servers connected to same LAN
External SAN storage connected DIRECTLY to each physical server via fibr3-channel. (No fibre-channel switch)
Database resides on SAN storage.
I've set up a failover cluster between the 2 physical servers.
I've created a high availability group with a Primary/Secondary and synchronization.
Both Primary/Secondary are green and show synchronized. The concern I have is that the Primary says Synchronizing (No Data Loss) and the Secondary says Not Synchronizing (Data Loss). When I use the Failover Wizard to failover, it tells me that I will have
data loss on the Secondary.
So my questions are these, do you need more than one Secondary node to have an effective Availability Group? If I only plan to have the 2 physical servers, should I be setting up a traditional Clustered SQL Server installation.
I've used the traditional Clustered SQL Server in the past and used the Active/Passive licensing for the SQL Server software but the Always On Availability Group looked interesting to me, but NOT if it requires more than 2 physical servers and more
than 2 SQL Instances (and licenses) to provide proper failover capability.
All input will be appreciated.
Thanks,
Brett

Hi Brett,
An AlwaysOn Availability Group is created between several standalone SQL Server instances, you don’t need to set up a traditional clustered SQL Server installation when configuring AlwaysOn Availability Group. Also you can have an effective Availability Group
with only one Secondary node.
From your description, you have an synchronous-commit availability secondary replica
and it says Not Synchronizing. This issue can be caused by the following:
•The availability replica might be disconnected.
•The data movement might be suspended.
•The database might not be accessible.
•There might be a temporary delay issue due to network latency or the load on the primary or secondary replica.
Please resolve any connection or data movement suspend issues. You can check the events for this issue using SQL Server Management Studio, and find the database error.
Reference:
Data synchronization state of some availability database is not healthy
Availability databases in unhealthy data synchronization state (Error: 35285, Severity: 16, State: 1.)
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Can remove agentless managed sql instances from machines that no longer exist

We have a couple of clustered sql servers that are no longer powered on.
They had several sql instances on them.
We are not able to remove the sql servers from SCOM 2012 SP1 because they have agent less managed devices (the sql instances)
We can remove the sql instances either so there is not way to remove these. We also cant reassign the proxy agent. It seems to do nothing.
How can we remove these?
Thanks Lance

You may use powershell cmdlet Remove-SCOMDisabledClassInstance t remove cluster instance
http://om2012.wordpress.com/2011/12/21/om-12-rc-powershell-cmdlet-remove-scomdisabledclassinstance/
OR
You may follow Rick Jury's Blog on removing cluster instance with MS SQL statement
http://rickjury.blogspot.hk/2011/02/operations-manager-scom-2007-how-to.html
Roger

Cannot install Windows Azure Storage Emulator - 3.0 Error: No available SQL Instance was found

When trying to install Windows Azure SDK for .NET (VS 2013) - 2.3 from Web Platform Installer 4.6, the install fails because Windows Azure Storage Emulator - 3.0 (Dependency) does not install successfully.
Possibly relevant lines from the install log are:
CAQuietExec: Entering CAQuietExec in C:\WINDOWS\Installer\MSI1223.tmp, version 3.6.3303.0
CAQuietExec: "C:\Program Files (x86)\Microsoft SDKs\Windows Azure\Storage Emulator\WAStorageEmulator.exe" init -forcecreate -autodetect
CAQuietExec: Windows Azure Storage Emulator 3.0.0.0 command line tool
CAQuietExec: Error: No available SQL Instance was found.
CAQuietExec: Error 0xfffffff6: Command line returned an error.
CAQuietExec: Error 0xfffffff6: CAQuietExec Failed
CustomAction RunInitialize returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:50:13: InstallFinalize. Return value 3.
Action ended 11:50:13: INSTALL. Return value 3.
In terms of SQL Instance, SQL LocalDB is installed and working properly. SQL Server 2012 is also installed and working properly.

Hi,
It is a SDK version issue. I suggest you could remove all azure sdk form your PC and use WPI to install the latest version again.
If you have any questions, please let me know.
Regards,
Will
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.
Click
HERE to participate the survey.

System Center 2012 R2 install: SQL server Data file and log file

This might be a dumb question, but I can't find the answer anywhere.
I'm installing a new instance of System Center 2012 R2 on a new server, I'm stuck on the SQL Server data file section. Everytime I put in a path, it says that tne path does not exist. I'm I supposed to be creating some sort of SQL Server
data file and log file before this installation, I didn't get this prompt when installing System Center 2012 SP1 or hen I upgraded from System Center 2012 SP1 to System Center 2012 R2
My SQL is on a different server
Thank you in advanced

Have you reviewed the setup.log?
On a side note, why would you put the database file on the same drive as the OS? That defeats the whole purpose of having a remote SQL Server. Why use a remote SQL Server in the first place.
Jason | http://blog.configmgrftw.com

New SSRS 2012 Service Application Fails to Upgrade ReportServer Database

Hi -
I am in the middle of an SSRS upgrade from 2008R2 to 2012, SP 2010 integrated, without upgrading the database engine. This is on my DEV environment. I am running into problems when I add the new SQL Server Reporting Services Service Application through Central
Administration. I am keying in the previous db names, so they will be upgraded, "ReportServer". After clicking OK, a screen pops up notifying me that "ReportServer" and "ReportServerTempDB" will be upgraded. So far so good
right? Well as it is processing, it returns with the error found at the bottom:
The correlationID is nowhere to be found in the ULS Logs. I turned on Verbose logging and still no luck. I have restored the ReportServer database from a backup from 3 days ago and tried again. Same error, different correlation ID, not found
in ULS logs. NOTE: I first encountered a specific permissions error for the service account I was using. That was nice and descriptive :). Changed the permissions to db_owner and sys_admin (for overkill) and now this non-descriptive error appears. I
have a few questions:
1. I have gone through the same process of adding a new service application and let a new set of the 3 SSRS db's be created with a different name. But that means I lose all previous subscriptions, data source connections
to the rdls, etc. Is there a way to port/migrate over the previous ReportServer db contents to the newly created db's? I tried a simple SSIS transfer of each table, and as expected I immediately received FK contraint errors, ID Inserts and so forth.
2. Why wouldn't the correlation ID be showing up with verbose tracking?
3. Does anyone know common reasons why the previous RS databases would not be successfully upgraded???
Thank you for any and all help. I am in the position of being able to roll back to snapshots created Thursday morning of the entire SP farm, but we are now at the point of having consultant work being lost so I am really trying hard to get this upgrade to
be successful and done in our DEV environment.

I restored to a backup of the databases REportServer and ReportServerTempDB that I took last night before I tried to manually update them with writing out the SQL File via Powershell. I tried to have the Service Application upgrade the database
again, knowing it would fail, which it did, and am now reviewing the logs in the location you mentioned above. For the 2 minutes that the failure could have happened during, all I see is OWSTIMER.EXE (0x07CC) errors, which I'm fairly positive
are unrelated, mainly cause they keep occurring round the clock and a caching error? Again, I am trying to simply find out why the Service Application upgrade the db's and have reverted back to a previous state. I felt the collation errors i was troubleshooting
above were too far down the rabbit hole.
Batch Read on counter \servername\SharePoint Foundation\*\Process ID get 3 instances
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.91 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
84yj Medium
Performance Counter OS (pdh) call failed with error code PDH_CSTATUS_BAD_COUNTERNAME.
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.91 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
ff69 Medium
PDH failure on counter \servername\SharePoint Publishing Cache\\Publishing cache hit ratio with error Unknown error (0xc0000bc0)
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
563a Medium
Unable to create system performance counter servername\SharePoint Publishing Cache\Publishing cache hit ratio\. The following exception was thrown: System.ComponentModel.Win32Exception: Unknown error (0xc0000bc0) at Microsoft.SharePoint.Win32.SPPdh.CheckReturnValue(PDH_STATUS
status, Boolean throwOnError) at Microsoft.SharePoint.Utilities.SPPerformanceCounter.Initialize() at Microsoft.SharePoint.Utilities.SPPerformanceCounter.NextValue(Int32 retry, Int32 retryInterval) at Microsoft.SharePoint.Utilities.SPPerformanceCounterMonitorInternal.UpdateValue()
at Microsoft.SharePoint.Utilities.SPPerformanceCounterMonitorInternal.Create(String computer, String category, String counter, String instance)
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
84yj Medium
Performance Counter OS (pdh) call failed with error code PDH_CSTATUS_BAD_COUNTERNAME.
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)

2012 Guest Clustered SQL instance - Upgrade platform

Similar Messages

Maybe you are looking for