Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a reindexing plan failing with error message:

Refresh failed for PhysicalPartition '1'

(Details: SQL Server Enterprise edition running in cluster.)

Searching through BOL and other online resources gave no pointers at all. What could this be related to?

share|improve this question

closed as unclear what you're asking by Mark Storey-Smith, Paul White, StanleyJohns, dezso, swasheck Jul 22 '13 at 14:45

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

What do you mean by reindexing plan? A SQL Server maintenance plan? SELECT * FROM sys.messages where text like '%Refresh failed%' doesn't return any results for me so not sure that error actually comes directly from SQL Server. Maybe you could try tracing the queries and error messages for the plan to see what exactly is failing. – Martin Smith Feb 17 '13 at 13:06
@MartinSmith, thank you. Yes it is a server maintenance plan. Any handy pointers on how to setup a trace on a maintenance plan. – Unreason Mar 6 '13 at 14:42

It appears that the issue occurs on the cluster node where the physical disk resource did not come online.

@Unreason: Before this problem started did u install any security update for Symantec Endpoint Protection.

  1. Check the events are logged in the Windows Server
  2. Check the Cluster log.

If you figure out it is because of the Symantec update. The Solution is


Symantec has released a product to resolve this issue. The fix has been included in Symantec Endpoint Protection 11 RU6.

Note: SEP 11 RU5 was the first client with official support for Windows 2008 R2. Migrate up to SEP 11 RU6 to resolve this issue, or downgrade to SEP11 MR4 MP2 if your policies require you to test with the newly released support products before introducing them in your production environment. SEP11 MR4 MP2 can be installed to Sever 2008 R2, but you first must install Liveupdate (lusetup.exe), and then install the MR4 MP2 client.

References Location to download Microsoft Handle tool -

share|improve this answer
Thanks for the attempt, but not we do not use Symantec. Will try to use handle to dig deeper. It is already helpful to better understand where to look for. – Unreason May 28 '13 at 13:12

Not the answer you're looking for? Browse other questions tagged or ask your own question.