The database could not be exclusively locked to perform the operation error 5030 - Исправление ошибок и поиск оптимальных решений проблем

I am trying to delete an existing database in SQL Server 2005. My first attempt produced the following error:

5030: The database could not be exclusively
locked to perform the operation.

I have since killed all processes that are accessing the database. I have also removed the replication subscription that it had previously been involved in.

Any thoughts on what else that could be holding the lock on it besides SQL Server processes and replication?

Update: I restarted the server, and that fixed it. I was trying to avoid that, since this is a production server, but hey what can you do?

asked Feb 8, 2009 at 5:14

A production server in which so many connections use the database yet you want to drop it?

None the less, how to kick out everybody from the database:

USE [dbname];
ALTER DATABASE [dbname] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

Then drop the database:

USE [master];
DROP DATABASE [dbname];

There is still a very small window of opportunity between the USE [master]; and DROP DATABASE ... where some other connection can grab the 1 single allowed lock on the database, but it usually not worth working around that.

answered Nov 23, 2009 at 20:05

Remus RusanuRemus Rusanu

286k40 gold badges430 silver badges565 bronze badges

I hate to say it, but a quick solution is to restart the system, make sure the sql server server service is not started, then you should be able to delete.

Also, is IIS stopped if you db is connected to a web ap?

answered Feb 8, 2009 at 5:19

Chris BallanceChris Ballance

33.5k26 gold badges103 silver badges151 bronze badges

You don’t happen to know if anyone left a transaction in an uncompleted rollback state (or otherwise uncompleted)? Might as well check the locks list, too.

answered Feb 8, 2009 at 5:34

dkretzdkretz

37.2k13 gold badges80 silver badges137 bronze badges

In the management studio, goto Management->Activity Monitor (right click) -> View Processes. That will give you a full list of everything running, you can sort the list by Database to see what is still attached, and you can also kill any connections. It’s easy to end up with orphaned connections that will prevent you from getting the exclusive access that you need.

answered Feb 8, 2009 at 5:19

MrTellyMrTelly

14.6k1 gold badge47 silver badges80 bronze badges

No One else should be using the DB, including yourself.

answered Feb 8, 2009 at 5:19

Why would we make a deleted DB to multi user mode.

ALTER DATABASE dbName SET MULTI_USER WITH ROLLBACK IMMEDIATE

Soner Gönül

96k102 gold badges205 silver badges356 bronze badges

answered Jun 13, 2014 at 7:55

To avoid this error, use the T-SQL script below in the master database. Make sure to run this (and modify the @dbname) for each database you are running the ALTER DATABASE command in.

«The database could not be exclusively locked to perform the
operation»

This «connection killer» script will work if Windows has established JDBC connections to the database. But this script is unable to kill off JDBC connections for Linux services (e.g. JBoss). So you’ll still get that error if you don’t stop JBoss manually. I haven’t tried other protocols, but please comment if you find out more information as you build new systems.

USE master;

DECLARE @dbname sysname

Set @dbname = 'DATABASE_NAME_HERE-PROD'

Declare @spid int
Select @spid = min(spid) from master.dbo.sysprocesses
where dbid = db_id(@dbname)
While @spid Is Not Null
Begin
        Execute ('Kill ' + @spid)
        Select @spid = min(spid) from master.dbo.sysprocesses
        where dbid = db_id(@dbname) and spid > @spid
End

answered Oct 28, 2015 at 20:26

MacGyverMacGyver

18k38 gold badges158 silver badges242 bronze badges

This error normally occurs when your database is in Multi User mode where users are accessing your database or some objects are referring to your database.
First you should set the database to single user mode:

ALTER DATABASE dbName
SET SINGLE_USER WITH ROLLBACK IMMEDIATE

Now we will try to delete the database

delete DATABASE ...

Finally set the database to Multiuser mode

ALTER DATABASE dbName
SET MULTI_USER WITH ROLLBACK IMMEDIATE

answered Sep 16, 2013 at 5:37

Источник

Содержание

Сообщение об ошибке при выполнении команды DBCC ПРОВЕРИТЬ в SQL Server: «базы данных не удалось заблокировать монопольно для выполнения операции»
Симптомы
Причина
Решение
Статус
Дополнительные сведения
Ms sql server error 5030
Answered by:
Question
Answers
All replies
Ms sql server error 5030
Answered by:
Question
Answers
All replies
Ms sql server error 5030
Все ответы

Сообщение об ошибке при выполнении команды DBCC ПРОВЕРИТЬ в SQL Server: «базы данных не удалось заблокировать монопольно для выполнения операции»

Симптомы

В Microsoft SQL Server может появиться сообщение об ошибке при выполнении команды DBCC:

ИНСТРУКЦИЯ DBCC CHECKDB

ИНСТРУКЦИЯ DBCC CHECKTABLE

ИНСТРУКЦИЯ DBCC CHECKALLOC

ИНСТРУКЦИЯ DBCC CHECKFILEGROUP

Сообщение об ошибке содержит следующий текст:

Сообщение 5030, уровень 16, состояние 12, 1 строки базы данных не удалось заблокировать монопольно для выполнения операции.
Сообщение 7926, уровень 16, состояние 1, строка 1
Инструкция проверки прервана. Не удалось вернуть базу данных не удалось создать моментальный снимок базы данных и базы данных или таблицы не может быть заблокирован. Дополнительные сведения, когда возникает данная ситуация и какие существуют обходные пути. Также см. Дополнительные сведения.

Если запланированные задачи плана обслуживания, которые выполняют проверку целостности базы данных в файл журнала для соответствующего плана может записать сообщение об ошибке, подобное приведенному ниже:

Версия программы (Юникод) обслуживание Microsoft(R) сервера 9.0.2047
Отчет был сформирован на « имя_компьютера».
План обслуживания: PlanForReadOnlyDb
Длительность: 00:00:52
Состояние: Предупреждение: не удалось выполнить одну или несколько задач.
Подробности:
Проверьте задача проверки целостности базы данных ( имя компьютера)
Проверить целостность базы данных на имя_компьютера
Базы данных: AdventureWorks, в базе данных msdb, PassDb, продажи, test1 включить индексы
Начало задачи:
Даты и времени.
Окончание задачи:
Даты и времени.
При выполнении запроса «DBCC CHECKDB параметр WITH NO_INFOMSGS Failed:(-1073548784)
«Ошибка со следующей ошибкой: «базы данных не удалось заблокировать монопольно для выполнения операции. Инструкция проверки прервана. Не удалось вернуть базу данных не удалось создать моментальный снимок базы данных и базы данных или таблицы не может быть заблокирован. Дополнительные сведения, когда возникает данная ситуация и какие существуют обходные пути. Также см. Дополнительные сведения.» Возможные причины сбоя: проблемы с запроса, «ResultSet» свойства заданы неправильно, параметры установлены неправильно или соединение не установлено правильно.

Причина

Эта проблема возникает, если выполняются следующие условия:

Хотя бы одно подключение используется база данных, в которой команда команда DBCC CHECK.

База данных содержит по крайней мере одну группу файлов, помечены как доступные только для чтения.

Начиная с SQL Server 2005, команда DBCC CHECK команды Создать и использовать моментальный снимок внутренней базы данных для сохранения согласованности при команда выполняет все проверки. Если группы только для чтения файл существует в базе данных, моментальный снимок внутренней базы данных не создается. Чтобы продолжить проверку, команда команда DBCC CHECK пытается получить блокировку базы данных EX. Если к базе данных подключены другие пользователи, это попытка получить блокировку EX завершается неудачей. Таким образом появляется сообщение об ошибке.

Решение

Чтобы устранить эту проблему, выполните следующие действия, вместо выполнения команды DBCC ПРОВЕРИТЬ в базе данных.

Создание моментального снимка базы данных, базы данных, для которого требуется выполнить проверку. Дополнительные сведения о способах создания моментального снимка базы данных приведены в разделе «Создание моментального снимка базы данных (Transact-SQL)» в электронной документации по SQL Server.

Выполните команду проверки DBCC для моментального снимка базы данных.

После завершения команды DBCC ПРОВЕРЬТЕ удалите моментальный снимок базы данных.

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

Дополнительные сведения

Дополнительные сведения об использовании команды проверки DBCC моментальный снимок внутренней базы данных приведены в разделе «DBCC (Transact-SQL)» в разделе «DBCC внутреннего использования базы данных моментальных снимков» в электронной документации по SQL Server 2005.

Чтобы воспроизвести эту проблему, выполните следующие команды в SQL Server:

Источник

Ms sql server error 5030

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I am trying to rename the database but i am getting below exception while doing it—>

Error: the database could not be exclusively locked to perform the operation.(Microsoft Sql Server,Error 5030)

Answers

Thats because someone else is accessing the database.. Put the database into single user mode the rename it.

Please mark answered if I’ve answered your question and vote for it as helpful to help other user’s find a solution quicker

Thats because someone else is accessing the database.. Put the database into single user mode the rename it.

Please mark answered if I’ve answered your question and vote for it as helpful to help other user’s find a solution quicker

Sounds like you have active connections to the database. You can verify this by running sp_who2, or through Activity Monitor and look for your database.

You could set the database to single user, i.e:

then do your sp_renamedb ‘myolddbname’, ‘mynewdbname’ or;

as mentioned earlier by both these users just wait for all the connections to go and then try- it will succed

or else if it is devUat environment & you can kill the conenctions — make the changes (use this as last option)

i was just wondering if you are connected to the same DB? If yes change your context to master(means connect to master DB ) and then issue this command.

Sarabpreet Singh Anand

This posting is provided , «AS IS» with no warranties, and confers no rights.

Please remember to click «Mark as Answer» and «Vote as Helpful» on posts that help you. This can be beneficial to other community members reading the thread.

Источник

Ms sql server error 5030

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I am trying to rename the database but i am getting below exception while doing it—>

Error: the database could not be exclusively locked to perform the operation.(Microsoft Sql Server,Error 5030)

Answers

Thats because someone else is accessing the database.. Put the database into single user mode the rename it.

Please mark answered if I’ve answered your question and vote for it as helpful to help other user’s find a solution quicker

Thats because someone else is accessing the database.. Put the database into single user mode the rename it.

Please mark answered if I’ve answered your question and vote for it as helpful to help other user’s find a solution quicker

Sounds like you have active connections to the database. You can verify this by running sp_who2, or through Activity Monitor and look for your database.

You could set the database to single user, i.e:

then do your sp_renamedb ‘myolddbname’, ‘mynewdbname’ or;

as mentioned earlier by both these users just wait for all the connections to go and then try- it will succed

or else if it is devUat environment & you can kill the conenctions — make the changes (use this as last option)

i was just wondering if you are connected to the same DB? If yes change your context to master(means connect to master DB ) and then issue this command.

Sarabpreet Singh Anand

This posting is provided , «AS IS» with no warranties, and confers no rights.

Please remember to click «Mark as Answer» and «Vote as Helpful» on posts that help you. This can be beneficial to other community members reading the thread.

Источник

Ms sql server error 5030

I have read a lot about this problem, but cant figure out mine.

First og all, I cant geet the MOMServer.MSI to run. Error messages in the MOMDB.log is diffrent from what the FF MOMDB.log reports.

I Run W2K3 R2, SQL 2005 Std, and SCE on a newly installed server. Here is what seems to be the most important lines in en MOMDB files:

Forefront — MOMDB.log

CPreReqUtil::LoadPropertyString: MsiViewFetch failed. HRESULT = -2147024637
LoadPropertyString failedfailed: hr: -2147024637
CPreReqVerifier::CheckMOMComponentVersion: Open key failed. HRESULT = -2147024894 SOFTWAREMission Critical SoftwareOnePointConfigurationsDefaultMcsApplicationsOperations ManagerInstall
CPreReqVerifier::Checkfailed: hr: -2147024894
CPreReqVerifier::CheckSp1Agent: Open key failed. HRESULT = -2147024894 SOFTWAREMission Critical SoftwareOnePoint
CPreReqVerifier::ExclusiveChecksfailed: hr: -2147024894
CPreReqVerifier::CheckInstallDir: Open key failed. HRESULT = -2147024894 SOFTWAREMicrosoftMicrosoft Operations Manager2.0Setup
CPreReqVerifier::ExclusiveChecksfailed: hr: -2147024894

CPreReqVerifier::CheckCurrentUserIsDBAdmin: Setup registry key not found. Error Code: 0x80070002.
CPreReqVerifier::ExclusiveChecksfailed: hr: -2147024894
CPreReqVerifier::ExclusiveChecksfailed: hr: -2147024894
CPreReqVerifier::Checkfailed: hr: -2147024894
CPreReqUtil::CopyFileFromMsi: Query: . HRESULT = 0 SELECT `Data` FROM `Binary` WHERE `Name`=’PreReq.dll’
CPreReqUtil::CopyFileFromMsi: Create failed. HRESULT = -2147024891
CPreReqUtil::LoadHTMLResourceFromMsiBin: CopyFileFromMsi failed. HRESULT = -2147024891
CReportWriter::WriteReport: CopyFileFromMsi failed. HRESULT = -2147024891
CReportWriter::WriteReport: Copy failed. HRESULT = -2147024894
CPreReqVerifier::Checkfailed: hr: -2147024894
VerifyPreReqs: Check failed. HRESULT = -2147024894
VerifyPreRequisites: Check failed. Error Code: 0x80070002.
VerifyPreRequisites: Function returned value. Error Code: 0x80070002.
Action ended 13:37:46: _VerifyPreRequisites. Return value 3.
Action ended 13:37:46: INSTALL. Return value 3.

MSI (s) (CC:10) [13:37:46:656]: Product: Microsoft Operations Manager 2005 — Installation failed.

MOMServer.MSI-MOMDB.log

MSI (c) (3C:80) [15:28:12:406]: Skipping action: _Set_MOMX_PRODUCT_FOUND_ExpressSameVersion (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Skipping action: _Set_MOMX_PRODUCT_FOUND_EvalSameVersion (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Skipping action: _AbortDowngradeProductAttempt (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Skipping action: _AbortInvalidUpgradeProductAttempt (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Skipping action: _AbortIncompatibleAgent (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Skipping action: CCPSearch (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Skipping action: RMCCPSearch (condition is false)
MSI (c) (3C:80) [15:28:12:406]: Doing action: CostInitialize
Action 15:28:12: CostInitialize. Determining disk space requirements
Action start 15:28:12: CostInitialize.
MSI (c) (3C:80) [15:28:12:406]: Machine policy value ‘MaxPatchCacheSize’ is 10
MSI (c) (3C:80) [15:28:12:406]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is ‘D:’.
MSI (c) (3C:80) [15:28:12:421]: PROPERTY CHANGE: Adding CostingComplete property. Its value is ‘0’.
Action ended 15:28:12: CostInitialize. Return value 1.
MSI (c) (3C:80) [15:28:12:421]: Doing action: FileCost
Action 15:28:12: FileCost. Determining disk space requirements
Action start 15:28:12: FileCost.
Action ended 15:28:12: FileCost. Return value 1.

Action start 15:28:18: _SetFeatureStatesForTypicalInstall.
MSI (c) (3C:9C) [15:28:18:796]: Invoking remote custom action. DLL: C:DOCUME

1TempMSI6A1.tmp, Entrypoint: SetFeatureStatesForTypicalInstall
MSI (c) (3C!88) [15:28:18:812]: Note: 1: 2727 2:
MSI (c) (3C!88) [15:28:18:968]: Disallowing installation of component: since the same component with higher versioned keyfile exists
MSI (c) (3C!88) [15:28:18:984]: Disallowing installation of component: <1a6d8713-9116-44ae-ba60-4cf0e8c1d58b>since the same component with higher versioned keyfile exists
MSI (c) (3C!88) [15:28:18:984]: Disallowing installation of component: since the same component with higher versioned keyfile exists
MSI (c) (3C!88) [15:28:19:000]: Disallowing installation of component: <1ca051b6-1b70-11d2-9add-006097c4e452>since the same component with higher versioned keyfile exists
MSI (c) (3C!88) [15:28:19:000]: Note: 1: 2727 2:
MSI (c) (3C!88) [15:28:19:000]: Note: 1: 2262 2: MIME 3: -2147287038
MSI (c) (3C!88) [15:28:19:031]: Disallowing installation of component: <1ca051b6-1b70-11d2-9add-006097c4e452>since the same component with higher versioned keyfile exists
MSI (c) (3C!88) [15:28:19:031]: Note: 1: 2727 2:
Action ended 15:28:19: _SetFeatureStatesForTypicalInstall. Return value 1.
MSI (c) (3C:3C) [15:28:19:031]: Doing action: _VerifyPreRequisites_Wizard
Action 15:28:19: _VerifyPreRequisites_Wizard.
Action start 15:28:19: _VerifyPreRequisites_Wizard.
MSI (c) (3C:C0) [15:28:19:046]: Invoking remote custom action. DLL: C:DOCUME

1TempMSI6A2.tmp, Entrypoint: VerifyPreRequisites
MSI (c) (3C!9C) [15:28:19:062]: Note: 1: 2711 2: MOMReporting
Action ended 15:28:19: _VerifyPreRequisites_Wizard. Return value 1.
MSI (c) (3C:3C) [15:28:19:234]: PROPERTY CHANGE: Modifying PREREQ_COMPLETED property. Its current value is ‘0’. Its new value: ‘1’.
Action 15:28:19: PreReqResultDlg. Dialog created

Hope someone have seen similar messages.

Все ответы

Are you attempting to run the MOMServer.msi manually? If so, please don’t — it will be launched properly as part of FCS Server setup

That said, none of the error messages below appear to be directly pointing out the problem. Can you run ServerSetup.exe and view the log file when it fails. From there, please post the first section that fails (it’s likely to be a 1603 error code)

Forefront Client Security PM

Did you solve a problem? I have the same issue:

MSI (s) (98:64) [21:29:37:659]: Note: 1: 1708
MSI (s) (98:64) [21:29:37:674]: Product: Microsoft Operations Manager 2005 — Installation failed.

MSI (s) (98:64) [21:29:37:674]: Cleaning up uninstalled install packages, if any exist
MSI (s) (98:64) [21:29:37:674]: MainEngineThread is returning 1603
MSI (s) (98:9C) [21:29:37:784]: Destroying RemoteAPI object.
MSI (s) (98:54) [21:29:37:784]: Custom Action Manager thread ending.
=== Logging stopped: 12/5/2007 21:29:37 ===
MSI (c) (3C:90) [21:29:37:784]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (3C:90) [21:29:37:784]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/5/2007 21:29:37 ===

Tasks started: [12/5/2007 9:29:20 PM]
Root Directory: C:distForefrontserver
Current Directory: C:distForefrontAUTORUN
[12/5/2007 9:29:20 PM] Task(Install the Collection Database)
Installing from this MSI: ‘c:distforefrontServerMOMServer.msi’
Log file: ‘C:Program FilesMicrosoft ForefrontClient SecurityServerLogsMOMDB.log’.
[12/5/2007 9:29:20 PM] Task(Install the Collection Database)
Starting Install the Collection Database.
[12/5/2007 9:29:20 PM] Task(Install the Collection Database)
Starting C:WINDOWSsystem32msiexec.exe.
[12/5/2007 9:29:20 PM] Task(Install the Collection Database)
Process command ‘C:WINDOWSsystem32msiexec.exe’
[12/5/2007 9:29:20 PM] Task(Install the Collection Database)

Process arguments ‘/i «c:distforefrontServerMOMServer.msi» /norestart /qn /l*v «C:Program FilesMicrosoft ForefrontClient SecurityServerLogsMOMDB.log» INSTALLDIR=»C:Program FilesMicrosoft ForefrontClient SecurityServerMicrosoft Operations Manager 2005″ ADDLOCAL=»MOMXDB» MOM_SERVER=.

[12/5/2007 9:29:37 PM] Task(Install the Collection Database)

[12/5/2007 9:29:37 PM] Task(Install the Collection Database)
The following process failed.
Process: C:WINDOWSsystem32msiexec.exe
Exit code: 1603Number of tasks completed: [12/5/2007 9:29:38 PM]

I am getting the SAME exact error when installing Forefront. I read other replies and increase my disk space. I now have 35GB free on all drives and still no luck. The account is the local admin as well and has full SQL access.

MS, Could you please help?

My ServerSetup_. file:

Number of verifications started: [12/27/2007 4:04:59 PM]

[12/27/2007 4:05:00 PM] Verification(Verifying operating system requirements)

[12/27/2007 4:05:00 PM] Verification(Verifying hardware requirements)

[12/27/2007 4:05:00 PM] Verification(Verifying software prerequisites)

[12/27/2007 4:05:01 PM] Verification(Verifying collection database)

[12/27/2007 4:05:01 PM] Verification(Verifying access to collection server)

[12/27/2007 4:05:02 PM] Verification(Verifying DAS account)

Number of verifications completed: [12/27/2007 4:05:02 PM]
Tasks started: [12/27/2007 4:05:07 PM]
Root Directory: C:. server
Current Directory: C:. AUTORUN
[12/27/2007 4:05:07 PM] Task(Install the Collection Database)
Installing from this MSI: ‘c:. ServerMOMServer.msi’
Log file: ‘C:Program FilesMicrosoft ForefrontClient SecurityServerLogsMOMDB.log’.
[12/27/2007 4:05:07 PM] Task(Install the Collection Database)
Starting Install the Collection Database.
[12/27/2007 4:05:07 PM] Task(Install the Collection Database)
Starting C:WINDOWSsystem32msiexec.exe.
[12/27/2007 4:05:07 PM] Task(Install the Collection Database)
Process command ‘C:WINDOWSsystem32msiexec.exe’
[12/27/2007 4:05:07 PM] Task(Install the Collection Database)
Process arguments ‘/i «c:documents and settingsasmforefrontdesktopforefrontServerMOMServer.msi» /norestart /qn /l*v «C:Program FilesMicrosoft ForefrontClient SecurityServerLogsMOMDB.log» INSTALLDIR=»C:. ServerMicrosoft Operations Manager 2005″ ADDLOCAL=»MOMXDB» MOM_SERVER=»NVFFDB» SQLSVR_INSTANCE=»NVFFDB» DAS_ACCOUNT=»TheAccount» DAS_PASSWORD=»*****» DAS_DOMAIN=»TheDomain» DB_SIZE=»15360″ CONFIG_GROUP=»ForefrontClientSecurity» DATA_DIR=»E:SQLDATA» LOG_DIR=»D:SQLLOG»‘
[12/27/2007 4:05:12 PM] Task(Install the Collection Database)

[12/27/2007 4:05:12 PM] Task(Install the Collection Database)
The following process failed.
Process: C:WINDOWSsystem32msiexec.exe
Exit code: 1603Number of tasks completed: [12/27/2007 4:05:13 PM]

My MOMDB.LOG file:

MSI (s) (BC:B8) [16:05:12:609]: Product: Microsoft Operations Manager 2005 — Installation failed.

MSI (s) (BC:B8) [16:05:12:640]: Cleaning up uninstalled install packages, if any exist
MSI (s) (BC:B8) [16:05:12:640]: MainEngineThread is returning 1603
MSI (s) (BC:A0) [16:05:12:750]: Destroying RemoteAPI object.
MSI (s) (BC:A4) [16:05:12:750]: Custom Action Manager thread ending.
=== Logging stopped: 12/27/2007 16:05:12 ===
MSI (c) (A4:E4) [16:05:12:828]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (A4:E4) [16:05:12:828]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/27/2007 16:05:12 ===

MSI (s) (BC:B8) [16:05:12:609]: Product: Microsoft Operations Manager 2005 — Installation failed.

seems like MOM 2005 installation failed.

I came across this previously and had to get more info abt the failure cause.

my problem previously was i changed my computer name after i installed SQL.

So to find out what’s failing:

Run momserver.msi, Click next until the Prerequisite Check.

there’s the log there that provides more info if it fails.

Hope this helps.

I think the problem is that you have SCE on the same box, which is not supported. I would recommend trying the install without SCE being on the same machine

Forefront Client Security PM

This is very strange from Microsoft. Basically, the SQL Collation Setting was set wrong. When installing, per documentation on TechNet, you have to choose a collation setting that is not case sensative. I had chosen that. BUT, the collation setting has to be Case sensative for this to work. I was on a call with MS for about 4 hours and no one figured it out untill I re-installed a new instance using the case-sensative collation and boom, everything worked.

I am getting a similar error installing MOM Reporting services.

Fresh installation 2008 32bit, SQl 2005 32bit, SSRS and SSIS up and running.

Источник

SQL Server 2014 Enterprise SQL Server 2014 Developer SQL Server 2014 Standard More…Less

Symptoms

Assume that you have a database that contains read-only filegroups in Microsoft SQL Server 2014. When you run DBCC CHECKDB on the database, the DBCC command can’t create a database snapshot for the database.

If there’s no other connection to the database, the DBCC operation is completed without errors. However, you receive the following error message:

DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.

If there are other connections to the database, the DBCC operation fails, and you receive the following error message:

Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.

Resolution

Cumulative Update information

The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 4 for SQL Server 2014 SP1

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2014 SP1

More Information

To reproduce this problem, run the following commands in SQL Server:

— Open a new query that is named conn1, and then create a new database.
CREATE DATABASE DbTest
GO
— Add a new file group.
ALTER DATABASE DbTest ADD FILEGROUP FGTest
GO
— Add a file to the new file group.
ALTER DATABASE DbTest ADD FILE (NAME=DbTest_Data2, FILENAME=’‘C:tempDbTest_Data2.ndf’)
TO FILEGROUP FGTest
GO
— Change the file group to read-only.
ALTER DATABASE DbTest MODIFY FILEGROUP FGTest READONLY
GO

— Run the DBCC CHECK command in the conn1 query.
DBCC CHECKDB (DbTest)

— The DBCC CHECK command runs correctly. However, you may receive the following message:
«DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.»

— Open a new query window that is named conn2, and then set the database as DbTest. This action opens a connection to the DbTest database.

— Return to the conn1 query, and run the DBCC command again.

DBCC CHECKDB (DbTest)
— Notice the error message that is mentioned in the «Symptoms» section.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

Need more help?

Источник

Сообщение об ошибке при выполнении команды DBCC ПРОВЕРИТЬ в SQL Server: «базы данных не удалось заблокировать монопольно для выполнения операции»

Симптомы

Причина

Решение

Статус

Дополнительные сведения

Ms sql server error 5030

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Answered by:

Question

Answers

Ms sql server error 5030

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Answered by:

Question

Answers

Ms sql server error 5030

Все ответы

Symptoms

Resolution

Cumulative Update information

Need more help?