Alert: SQL Server Service Broker or Database Mirroring Transport stopped
Hi Team,
I got this error message even no one DB configured as mirroring ???
Alert: SQL Server Service Broker or Database Mirroring Transport stopped Priority: 0 Severity: 2 Resolution state: New
Alert description: The Database Mirroring protocol transport has stopped listening for connections.
Can you check the rule. By default the configurations are disabled state that is the reason you are getting the alert.
If it's not configured properly then you might need to override it
--Prashanth
Similar Messages
-
Monitor SQL Server service Broker queue status
I need to monitor SQL Server service Broker queue status. If the queue is disabled, send me an email alert.
Can you let me know what's the best way to accomplish it using SCOM?1) create a queue for notification
2) create a service on notification queue
3)Create an event notification for broker queue disable. Associate this with the queue that you are monitoring.
4)Create a procedure that send you and email with this event happens
Example:
---- Notification
CREATE
QUEUENotify_queue
-- Service
CREATE
SERVICE[http://queue_Notify]
ONQUEUENotify_queue([http://schemas.microsoft.com/SQL/Notifications/PostEventNotification]);
--Event
CREATE
EVENTNOTIFICATION[http://queue_Notify_event]
ONQUEUETarget_queue
FORBROKER_QUEUE_DISABLED
TOSERVICE'http://queue_Notify','current
database';
GO
procedure will be something like...
WAITFOR
RECEIVETOP(1)
@RecvReqMsgName=message_type_name,
@RecvReplyMsg=message_body,
@RecvReplyDlgHandle=conversation_handle
FROMNotify_queue),TIMEOUT5000
IF(@RecvReqMsgName='http://schemas.microsoft.com/SQL/Notifications/EventNotification')
BEGIN
DECLARE@cmdNVARCHAR(MAX)
SET@cmd='dbo.sp_send_dbmail
@profile_name="Name XYZ",
@recipients="[email protected]",
@body="CAST(@RecvReplyMsg as NVARCHAR(MAX)",
@subject="Queue Disabled Detected";'
EXEC
(@cmd)
END -
Hi All,
I have requirement to implement SQL server service broker in SQL server 2008, please guide me for that, how and why we use for that, then have any other option to achieve.
Please give any good stuff to learn service broker.
Thanks,
Jai.This is a very good book to learn about Service Broker:
http://www.amazon.com/Rational-Server-Service-Broker-Guides/dp/1932577270/ref=sr_1_1?ie=UTF8&qid=1418942042&sr=8-1&keywords=%22roger+wolter%22+%22service+broker%22&pebp=1418942044114
In difference from many other computer books, this is not a brick, but only 220 pages.
Also, Remus Rusanu's blog covers many important concepts with Service Broker:
http://rusanu.com/?s=service+broker
Erland Sommarskog, SQL Server MVP, [email protected] -
SQL Server Service Broker Updating Stored procedure
how can you update the service broker stored procedure. when i update the stored procedure the changes dont come into affect. i have tried to alter the queue, waited for all jobs to finish, but some how still the old stored procedure is running. is there any
way i can force changes to the stored procedure.
i have tried sql profiler tracing but that didnt show any changes.
I cannot alter the service broker stored procedure, when I update the stored procedure it does not show any error and successfully gets updated but the changes does not come into affect.
Is it because I need to stop the queue of the service broker on both databases before the changes could come into affect?
Note: the service broker stored procedures produce and read xmls.Presumably, this is because the procedure is executing when you alter the procedure. And if the procedure never exits, the old code will keep on running. One way to address this is to have the procedure to return if a new message has not been picked up in,
say, 1000 milliseconds.
Here is a repro to shows what I'm talking about.
------------------------------- Service Broker Objects ------------------------------------------
CREATE MESSAGE TYPE OrderRequest VALIDATION = NONE
CREATE MESSAGE TYPE OrderResponse VALIDATION = NONE
go
CREATE CONTRACT OrderContract
(OrderRequest SENT BY INITIATOR,
OrderResponse SENT BY TARGET)
go
CREATE QUEUE OrderRequests WITH STATUS = OFF
CREATE QUEUE OrderResponses WITH STATUS = ON
go
CREATE SERVICE OrderRequests ON QUEUE OrderRequests (OrderContract)
CREATE SERVICE OrderResponses ON QUEUE OrderResponses (OrderContract)
go
-- Procedure to send a message and receive a response.
CREATE PROCEDURE send_and_get_answer AS
DECLARE @handle uniqueidentifier,
@binary varbinary(MAX)
SELECT @binary = CAST (N'Kilroy was here' AS varbinary(MAX))
BEGIN DIALOG CONVERSATION @handle
FROM SERVICE OrderResponses
TO SERVICE 'OrderRequests'
ON CONTRACT OrderContract
WITH ENCRYPTION = OFF
;SEND ON CONVERSATION @handle
MESSAGE TYPE OrderRequest (@binary)
WAITFOR (RECEIVE TOP (1)
@handle = conversation_handle,
@binary = message_body
FROM OrderResponses)
SELECT cast(@binary AS nvarchar(MAX)) AS response
END CONVERSATION @handle
go
-- Procedure to process a message
CREATE PROCEDURE ProcessOrders AS
SET NOCOUNT, XACT_ABORT ON
DECLARE @DialogHandle uniqueidentifier,
@MessageType sysname,
@binarydata varbinary(MAX)
-- Get next message of the queue.
WAITFOR (
RECEIVE TOP (1) @DialogHandle = conversation_handle,
@MessageType = message_type_name,
@binarydata = message_body
FROM OrderRequests
SELECT @binarydata = CAST( reverse( CAST( @binarydata AS nvarchar(MAX) )) AS varbinary(MAX))
; SEND ON CONVERSATION @DialogHandle
MESSAGE TYPE OrderResponse (@binarydata)
END CONVERSATION @DialogHandle
go
-- Make this an activaton procedure.
ALTER QUEUE OrderRequests WITH
STATUS = ON,
ACTIVATION (STATUS = ON,
PROCEDURE_NAME = ProcessOrders,
MAX_QUEUE_READERS = 1,
EXECUTE AS OWNER)
go
-------------------------------- Send a message -------------------------------------------
EXEC send_and_get_answer
go
------------------------ Change the procedure --------------------------------
ALTER PROCEDURE ProcessOrders AS
SET NOCOUNT, XACT_ABORT ON
DECLARE @DialogHandle uniqueidentifier,
@MessageType sysname,
@binarydata varbinary(MAX)
-- Get next message of the queue.
WAITFOR (
RECEIVE TOP (1) @DialogHandle = conversation_handle,
@MessageType = message_type_name,
@binarydata = message_body
FROM OrderRequests
SELECT @binarydata = CAST( upper( CAST( @binarydata AS nvarchar(MAX) )) AS varbinary(MAX))
; SEND ON CONVERSATION @DialogHandle
MESSAGE TYPE OrderResponse (@binarydata)
END CONVERSATION @DialogHandle
go
-------------------------------- Send new message -------------------------------------------
EXEC send_and_get_answer -- Still produces a message in reverse.
EXEC send_and_get_answer -- Now we get the expected result.
go
DROP SERVICE OrderRequests
DROP SERVICE OrderResponses
DROP QUEUE OrderRequests
DROP QUEUE OrderResponses
DROP PROCEDURE ProcessOrders
DROP PROCEDURE send_and_get_answer
DROP CONTRACT OrderContract
DROP MESSAGE TYPE OrderRequest
DROP MESSAGE TYPE OrderResponse
go
Erland Sommarskog, SQL Server MVP, [email protected] -
Automatically start SQL Agent service after SQL Server service fails and starts.
Hi!
I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
As you can see, SQL Server service terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
to make the settings to start both of my services SQL Server and SQL Agent automatically after this. How can I set up this? How can I make my SQL Agent service starts after SQL Server service?Hello,
SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
select @@version
>>Then SQL Agent service tries to start SQL Server service.No this is not the case
>>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
SQl Server Installation failing for Database Engine and Its Services
Hi,
I was trying to install SQL SERVER 2008 R2 on VM having 500 GB hard disk and 16 GB RAM.
OS is Windows Server 2008
But it fails for Database Engine.
Installation Details are as Below.
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-10-13 18:41:01
End time: 2014-10-13 19:26:32
Requested action: Install
Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x476BF04A%400xBB814387
Machine Properties:
Machine name: KVS-IN-WFAN092
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: di-softwareSoftwaresSQLSQL_2008_R2_Enterprisex64setup
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITYLOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLServer
INSTANCENAME: SQLSERVER
ISSVCACCOUNT: NT AUTHORITYNetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: KRONOSENGsuperuser
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354SystemConfigurationCheck_Report.htm
And Error in log file are maily as below.
2014-10-13 19:26:27 Slp: Completed Action: SqlBrowserConfigAction_install_Startup_Cpu32, returned True
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11
dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_install_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There
are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are
2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Completed Action: PostMsiTimingConfigAction, returned True
2014-10-13 19:26:27 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2014-10-13 19:26:27 Slp: ----------------------------------------------------------------------
2014-10-13 19:26:27 Slp: Running Action: ExecuteExtendedTimingsWorkflow
Thanks,
MaheshI have uploaded detail.txt at below url.
http://m.uploadedit.com/b041/1413264342685.txt
Hi Mahesh,
According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
For more details about this error, please review the following similar thread.
http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
Thanks,
Lydia Zhang -
Email alert if SQL Server Services stop abruptly
Hi,
I am a SQL Server DBA and I am currently working on setting up email alerts in case if SQL Server services stop abruptly.I have currently written a VB script which runs every 1 hr and checks if a SQL Server Service is running or not. This VB Script runs
with the help of Windows Task Scheduler.In case if a SQL Server service has stopped, this VB script immediately sends an email via. SMTP Server.
Please let me know if this is a good solution or is there any other better solution or is there any feature available in SQL/windows using which the same can be achieved.
Environment:
SQL 2008 R2
OS: Windows Server 2008
Thanks a lot in advance :)
Regards,
Tauhid S ShaikhHi Tauhid,
I do have same requirement, please could you share the code.
Regards
Siraj Ahmed -
hi there:
I've experienced several sql server service crashes yesterday, service was brought up after a few secs as we have an autostart feature.
Today, I'd like to dig more into the errors and on the event viewer -> Application, I saw errors below
"Faulting application sqlservr.exe, version 2009.100.4302.0, time stamp 0x52f5d194, faulting module ntdll.dll, version 6.0.6001.18538, time stamp 0x4cb73957, exception code 0xc0000374, fault offset 0x00000000000a7857, process id 0x15ec, application
start time 0x01cfd7e72b2997d3.
People suggested to check dump file inside C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log
However, the lastest .mdmp file was on April 11, 2014. Do I need to turn on some settings on sql server in order to have this dump file?
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --Results after sp_readerrorlog 1
LogDate ProcessInfo
Text
2014-09-24 04:03:28.460 Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4302.0 (X64)
Feb 7 2014 17:23:24
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1)
2014-09-24 04:03:28.460 Server
(c) Microsoft Corporation.
2014-09-24 04:03:28.460 Server
All rights reserved.
2014-09-24 04:03:28.460 Server
Server process ID is 5612.
2014-09-24 04:03:28.460 Server
System Manufacturer: 'IBM', System Model: 'IBM System x3650 -[7979AC1]-'.
2014-09-24 04:03:28.460 Server
Authentication mode is MIXED.
2014-09-24 04:03:28.460 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG'.
2014-09-24 04:03:28.460 Server
This instance of SQL Server last reported using a process ID of 6780 at 9/24/2014 4:03:20 AM (local) 9/24/2014 11:03:20 AM (UTC). This is an informational message only; no user action is required.
2014-09-24 04:03:28.460 Server
Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\mastlog.ldf
2014-09-24 04:03:28.480 Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-24 04:03:28.480 Server
Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-24 04:03:28.480 Server
Cannot use Large Page Extensions: lock memory privilege was not granted.
2014-09-24 04:03:28.580 Server
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-24 04:03:28.700 Server
Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-09-24 04:03:28.870 spid7s
Starting up database 'master'.
2014-09-24 04:03:28.940 spid7s
1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:29.040 spid7s
CHECKDB for database 'master' finished without errors on 2014-09-20 12:00:01.697 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:29.050 spid7s
Resource governor reconfiguration succeeded.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008R2'.
2014-09-24 04:03:29.070 spid7s
SQL Trace ID 1 was started by login "sa".
2014-09-24 04:03:29.070 spid7s
Starting up database 'mssqlsystemresource'.
2014-09-24 04:03:29.090 spid7s
The resource database build version is 10.50.4302. This is an informational message only. No user action is required.
2014-09-24 04:03:29.600 spid10s
Starting up database 'model'.
2014-09-24 04:03:29.600 spid7s
Server name is 'BPWDB046\SQL2008R2'. This is an informational message only. No user action is required.
2014-09-24 04:03:29.880 spid13s
A new instance of the full-text filter daemon host process has been successfully started.
2014-09-24 04:03:29.960 spid14s
Starting up database 'msdb'.
2014-09-24 04:03:29.960 spid17s
Starting up database 'DW_Detail'.
2014-09-24 04:03:29.960 spid16s
Starting up database 'ReportServer_MSSQLSSRSTempDB'.
2014-09-24 04:03:29.960 spid13s
Starting up database 'Billing_Rep'.
2014-09-24 04:03:29.960 spid15s
Starting up database 'ReportServer_MSSQLSSRS'.
2014-09-24 04:03:29.960 spid18s
Starting up database 'BCBio_DW'.
2014-09-24 04:03:29.960 spid19s
Starting up database 'ODS'.
2014-09-24 04:03:29.960 spid20s
Starting up database 'ReportServer$SQL2008'.
2014-09-24 04:03:29.970 spid21s
Starting up database 'ReportServer$SQL2008TempDB'.
2014-09-24 04:03:29.970 spid22s
Starting up database 'Billing'.
2014-09-24 04:03:29.970 spid23s
Starting up database 'Billing_Snap'.
2014-09-24 04:03:29.970 spid24s
Starting up database 'DBA'.
2014-09-24 04:03:30.000 Server
A self-generated certificate was successfully loaded for encryption.
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv6> 52328].
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv4> 52328].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008R2 ].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008R2\sql\query ].
2014-09-24 04:03:30.010 Server
Server is listening on [ ::1 <ipv6> 52329].
2014-09-24 04:03:30.010 Server
Server is listening on [ 127.0.0.1 <ipv4> 52329].
2014-09-24 04:03:30.010 Server
Dedicated admin connection support was established for listening locally on port 52329.
2014-09-24 04:03:30.060 spid10s
CHECKDB for database 'model' finished without errors on 2014-09-20 12:00:17.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.060 spid10s
Clearing tempdb database.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:SQL2008R2 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:52328 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-24 04:03:30.480 spid21s
CHECKDB for database 'ReportServer$SQL2008TempDB' finished without errors on 2014-09-20 16:13:10.043 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.520 spid14s
2933 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.770 spid14s
CHECKDB for database 'msdb' finished without errors on 2014-09-20 12:00:18.473 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.950 spid10s
Starting up database 'tempdb'.
2014-09-24 04:03:30.990 spid52
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-09-24 04:03:31.010 spid52
Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_sqlagent_monitor'. This is an informational message only; no user action is required.
2014-09-24 04:03:31.060 spid14s
The Service Broker protocol transport is disabled or not configured.
2014-09-24 04:03:31.060 spid14s
The Database Mirroring protocol transport is disabled or not configured.
2014-09-24 04:03:31.070 spid14s
Service Broker manager has started.
2014-09-24 04:03:31.330 spid16s
CHECKDB for database 'ReportServer_MSSQLSSRSTempDB' finished without errors on 2014-09-20 12:00:39.873 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:31.500 spid20s
2 transactions rolled forward in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
0 transactions rolled back in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
Recovery is writing a checkpoint in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:32.150 spid20s
CHECKDB for database 'ReportServer$SQL2008' finished without errors on 2014-09-20 16:13:07.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.170 spid24s
CHECKDB for database 'DBA' finished without errors on 2014-09-20 16:22:41.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.600 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 1537 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:34.820 spid15s
CHECKDB for database 'ReportServer_MSSQLSSRS' finished without errors on 2014-09-20 12:00:32.067 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:48.290 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 1488 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:49.520 spid17s
1 transactions rolled forward in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
0 transactions rolled back in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery is writing a checkpoint in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery completed for database DW_Detail (database ID 7) in 5 second(s) (analysis 251 ms, redo 4314 ms, undo 44 ms.) This is an informational message only. No user action is required.
2014-09-24 04:03:50.520 spid22s
CHECKDB for database 'Billing' finished without errors on 2013-04-25 18:47:20.743 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:51.620 spid17s
CHECKDB for database 'DW_Detail' finished without errors on 2014-09-20 12:00:46.917 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:03.740 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 1493 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:13.040 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 8052 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:23.220 spid18s
Database BCBio_DW has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:23.420 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4664 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4954 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 3% complete (approximately 74 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.730 spid18s
Recovery of database 'BCBio_DW' (9) is 2% complete (approximately 98 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:26.000 spid18s
Recovery of database 'BCBio_DW' (9) is 12% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:28.000 spid19s
Database ODS has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:28.350 spid19s
CHECKDB for database 'ODS' finished without errors on 2014-09-20 16:07:22.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:29.370 spid18s
Recovery of database 'BCBio_DW' (9) is 19% complete (approximately 24 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:31.380 spid18s
Recovery of database 'BCBio_DW' (9) is 25% complete (approximately 22 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:32.490 spid18s
Recovery of database 'BCBio_DW' (9) is 32% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.150 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 9805 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.860 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 04:04:33.860 Logon
Login failed for user 'ETLAdmin'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.101.33]
2014-09-24 04:04:34.040 spid18s
Recovery of database 'BCBio_DW' (9) is 39% complete (approximately 15 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:35.600 spid18s
Recovery of database 'BCBio_DW' (9) is 46% complete (approximately 13 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:36.740 spid18s
Recovery of database 'BCBio_DW' (9) is 53% complete (approximately 10 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.220 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 10106 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.230 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 2587 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.360 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 3654 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.560 spid13s
Recovery of database 'Billing_Rep' (8) is 3% complete (approximately 1564 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.070 spid13s
Recovery of database 'Billing_Rep' (8) is 4% complete (approximately 1328 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.830 spid18s
Recovery of database 'BCBio_DW' (9) is 61% complete (approximately 8 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.080 spid13s
Recovery of database 'Billing_Rep' (8) is 5% complete (approximately 1268 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.680 spid18s
Recovery of database 'BCBio_DW' (9) is 69% complete (approximately 6 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:42.960 spid18s
Recovery of database 'BCBio_DW' (9) is 77% complete (approximately 4 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
3 transactions rolled forward in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:45.120 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
0 transactions rolled back in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery is writing a checkpoint in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery completed for database BCBio_DW (database ID 9) in 23 second(s) (analysis 2417 ms, redo 19227 ms, undo 1745 ms.) This is an informational message only. No user action is required.
2014-09-24 04:04:47.610 spid18s
CHECKDB for database 'BCBio_DW' finished without errors on 2014-09-20 14:02:10.680 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:47.820 spid23s
Database Billing_Snap has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:48.570 spid23s
CHECKDB for database 'Billing_Snap' finished without errors on 2014-09-20 16:13:11.037 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:52.970 spid13s
Recovery of database 'Billing_Rep' (8) is 6% complete (approximately 1247 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:05.540 spid13s
Recovery of database 'Billing_Rep' (8) is 7% complete (approximately 1224 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:17.980 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1202 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
1 transactions rolled forward in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.560 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.710 spid13s
CHECKDB for database 'Billing_Rep' finished without errors on 2014-09-20 13:25:01.597 (local time). This is an informational message only; no user action is required.
2014-09-24 04:05:22.720 spid13s
0 transactions rolled back in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.720 spid13s
Recovery is writing a checkpoint in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.730 spid13s
Recovery completed for database Billing_Rep (database ID 8) in 109 second(s) (analysis 63983 ms, redo 45211 ms, undo 154 ms.) This is an informational message only. No user action is required.
2014-09-24 04:05:22.750 spid7s
Recovery is complete. This is an informational message only. No user action is required.
2014-09-24 07:00:06.930 spid53
Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.
2014-09-24 07:00:07.720 spid53
AppDomain 2 (mssqlsystemresource.sys[runtime].1) created.
2014-09-24 07:13:38.590 spid51
SQL Server blocked access to STATEMENT 'OpenRowset/OpenDatasource' of component 'Ad Hoc Distributed Queries' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Ad
Hoc Distributed Queries' by using sp_configure. For more information about enabling 'Ad Hoc Distributed Queries', see "Surface Area Configuration" in SQL Server Books Online.
2014-09-24 07:13:53.870 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:53.870 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:56.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:56.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.460 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.460 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.950 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.950 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.410 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.410 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.960 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.960 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:34:13.330 spid54
Error: 17053, Severity: 16, State: 1.
2014-09-24 07:34:13.330 spid54
V:\log\templog.ldf: Operating system error 112(There is not enough space on the disk.) encountered.
2014-09-24 07:34:14.430 spid54
Error: 9002, Severity: 17, State: 4.
2014-09-24 07:34:14.430 spid54
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN -- -
Could not start Service Broker for database
Problem:
Could not start Service Broker for database id: 9. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
The windows and application logs do not give me any for information. I have checked the database instance and found that Database ID 9 does not exist in the sys.databases table. Could this be the reason?
How do I resolve it so that SQL Server does not try and start Service broker for a database ID that does not exist?
Any help will be greatly appreciated.
Thanks.Hello Affy
Solution/Fix: To avoid this alert, I have set the "Enable Disaster Recovery File Updates" parameter to 0 in the regedit at the below location.
MY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\SQL Server
For furher details you can refer my blog.
Regards,
Naveen Kumar Thandra -
Cannot start SQL Server Service (SQLEXPRESS).
Cannot start SQL Server (SQLEXPRESS). When i tried to start the SQL Server Services, the warning: This request failed or the service did not respond in a timely fashion. Consult the event log or other application error logs for details.
I opened the Event Viewer, Error is shown as : An error occurred in the Service Broker / Database Mirroring transport manager. Error: 9694, Stare 27.Here is the ERRORLOG
2015-03-16 11:20:30.50 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2015-03-16 11:20:30.50 Server (c) Microsoft Corporation.
2015-03-16 11:20:30.50 Server All rights reserved.
2015-03-16 11:20:30.50 Server Server process ID is 6816.
2015-03-16 11:20:30.50 Server System Manufacturer: 'LENOVO', System Model: '20C5A01K00'.
2015-03-16 11:20:30.50 Server Authentication mode is MIXED.
2015-03-16 11:20:30.50 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-03-16 11:20:30.50 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2015-03-16 11:20:30.50 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-03-16 11:20:30.50 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-03-16 11:20:30.64 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 11:20:30.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 11:20:30.64 Server Detected 7906 MB of RAM. This is an informational message; no user action is required.
2015-03-16 11:20:30.64 Server Using conventional memory in the memory manager.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 27.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server Error: 9643, Severity: 16, State: 1.
2015-03-16 11:20:30.75 Server An error occurred in the Service Broker/Database Mirroring transport manager: Error: 9694, State: 27.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 30.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server SQL Server Audit failed to record the SERVER SHUTDOWN action. -
Could not start Service Broker for database id
I am getting this message in the SQL Server error log:
Could not start Service Broker for database id: 10. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
It appears even when the broker is disabled on the database. How can I eliminate this error?
Thanks!In that case you're gonna have to contact Microsoft support, perhaps provide a copy of the database.
Typical reason why a broker cannot be started is that another database with the same service_broker_guid already exists in the instance (result of a file copy/attach or a double restore). However, in that case a message is given that states the reason. -
Sql server service will not start after server reboot:
2009-08-13 14:15:43.94 spid7s SQL Trace ID 1 was started by login "sa".
2009-08-13 14:15:43.97 spid7s Starting up database 'mssqlsystemresource'.
2009-08-13 14:15:43.97 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-08-13 14:15:44.30 Server A self-generated certificate was successfully loaded for encryption.
2009-08-13 14:15:44.30 spid7s Server name is 'WIN-37R9WFWAJIB\MSDB1'. This is an informational message only. No user action is required.
2009-08-13 14:15:44.32 spid10s Starting up database 'model'.
2009-08-13 14:15:44.32 Server Server is listening on [ 'any' <ipv6> 49167].
2009-08-13 14:15:44.33 Server Server is listening on [ 'any' <ipv4> 49167].
2009-08-13 14:15:44.33 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSDB1 ].
2009-08-13 14:15:44.33 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-08-13 14:15:44.35 spid10s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2009-08-13 14:15:44.38 Server Server is listening on [ ::1 <ipv6> 49168].
2009-08-13 14:15:44.38 Server Server is listening on [ 127.0.0.1 <ipv4> 49168].
2009-08-13 14:15:44.38 Server Dedicated admin connection support was established for listening locally on port 49168.
2009-08-13 14:15:44.39 spid10s Error: 927, Severity: 14, State: 2.
2009-08-13 14:15:44.39 spid10s Database 'model' cannot be opened. It is in the middle of a restore.
2009-08-13 14:15:44.49 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-08-13 14:15:44.50 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informa
there is plenty of room on the server, so i dont think its a disk space issue. i am able to start the service as such:
C:\Users\Administrator>net start MSSQL$MSDB1 /c /m /T3608
The SQL Server (MSDB1) service is starting.
The SQL Server (MSDB1) service was started successfully
sqlcmd -e
1> select name, status from sysdatabases;
2> go
select name, status from sysdatabases;
name
status
master
65544
tempdb
65544
model
65568
msdb
1073807368
SS_DBA_Dashboard
1073807368
(5 rows affected)
model is in RESTORING state and I dont know how to fix it. I am running simple backups, so I have a somewhat recent backup of model.bak but when I attempt to restore it I get an error:
1> restore database model
2> go
restore database model
Msg 3112, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
Cannot restore any database other than master when the server is in single user
mode.
Msg 3013, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 1
RESTORE DATABASE is terminating abnormally.
other forums suggest manually updating the status column but i dont know if my syntax is wrong or it just cant be done in sql server 2008:
1> begin transaction
2> update sysdatabases set status=16 where name='model'
3> ;
4> go
begin transaction
update sysdatabases set status=16 where name='model'
Msg 4406, Level 16, State 1, Server WIN-37R9WFWAJIB\MSDB1, Line 2
Update or insert of view or function 'sysdatabases' failed because it contains a
derived or constant field.
1>
yet another forum suggested taking a cleanly shut down model.mdf and model.ldf from another sql server 2008 instance and placing those in the data directory while moving the 'restoring' ones to a backup location. this didnt work either. any help is appreciated im new to sql server and this is very frustrating! thanks in advance!I have the same issue on SQL Server 2008R2, after a server reboot, but none of the NET START commands or command line attempts are successful to start the Service.
NET START command results in "Access Denied" "System Error 5" and the Command line attempts result in
Server Error: 17058, Severity: 16, State: 1.
Server initerrlog: Could not open error log file ''.
Any help?
SQL Error log file:
2011-03-29 16:50:49.40 Server (c) Microsoft Corporation.
2011-03-29 16:50:49.40 Server All rights reserved.
2011-03-29 16:50:49.40 Server Server process ID is 7292.
2011-03-29 16:50:49.40 Server System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T710'.
2011-03-29 16:50:49.40 Server Authentication mode is MIXED.
2011-03-29 16:50:49.40 Server Logging SQL Server messages in file 'E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-03-29 16:50:49.40 Server This instance of SQL Server last reported using a process ID of 7448 at 3/29/2011 4:30:06 PM (local) 3/29/2011 8:30:06 PM (UTC). This is an informational message only; no user action is required.
2011-03-29 16:50:49.40 Server Registry startup parameters:
-d E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
-T 4616
2011-03-29 16:50:49.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-03-29 16:50:49.42 Server Detected 24 CPUs. This is an informational message; no user action is required.
2011-03-29 16:50:49.84 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-03-29 16:50:49.84 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2011-03-29 16:50:49.86 Server Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.86 Server Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2011-03-29 16:50:49.89 spid9s Starting up database 'master'.
2011-03-29 16:50:49.95 spid9s CHECKDB for database 'master' finished without errors on 2011-03-18 08:46:34.257 (local time). This is an informational message only; no user action is required.
2011-03-29 16:50:49.95 spid9s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-03-29 16:50:49.97 spid9s SQL Trace ID 1 was started by login "sa".
2011-03-29 16:50:49.97 spid9s Starting up database 'mssqlsystemresource'.
2011-03-29 16:50:49.99 spid9s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-03-29 16:50:50.20 spid13s Starting up database 'model'.
2011-03-29 16:50:50.20 spid9s Server name is 'XXXX'. This is an informational message only. No user action is required.
2011-03-29 16:50:50.21 Server The certificate [Cert Hash(sha1) "C41DC20703F049763778AC2842C3C8A3A2C6EED4"] was successfully loaded for encryption.
2011-03-29 16:50:50.21 Server Server is listening on [ 'any' <ipv6> 1433].
2011-03-29 16:50:50.21 Server Server is listening on [ 'any' <ipv4> 1433].
2011-03-29 16:50:50.21 Server Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2011-03-29 16:50:50.21 Server Server named pipe provider is ready to accept connection on [
\\.\pipe\sql\query ].
2011-03-29 16:50:50.21 Server Server is listening on [ ::1 <ipv6> 1434].
2011-03-29 16:50:50.21 spid13s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-03-29 16:50:50.21 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-03-29 16:50:50.21 spid13s Error: 927, Severity: 14, State: 2.
2011-03-29 16:50:50.21 spid13s Database 'model' cannot be opened. It is in the middle of a restore.
2011-03-29 16:50:50.21 Server Dedicated admin connection support was established for listening locally on port 1434.
2011-03-29 16:50:50.22 spid13s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
the event log that may indicate why the tempdb files could not be initialized.
2011-03-29 16:50:50.22 spid13s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. -
I know this question has been asked before, but never for R2, that I can tell, and the posted fixes aren't working. I have just installed SCVMM 2008 R2 on a Windows Server 2008 R2 server, using a remote SQL 2008 SP1 database. When I attempt to connect to SCVMM, I get the following error:
"The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).
Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS. For more information, see "Some applications and APIs require access to authorization information on account objects" in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=121054.
ID: 2607"
What I've seen online is that this is usually becuase the domain account SCVMM is running as does not have the proper permissions on the SQL database. Here's what I've confirmed:
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still "doesn't have access to AD DS," which is obviously untrue)
5) Neither service account is locked out
Has anyone run in to this? It says in Technet that remote SQL 2008 is supported, as long as the SQL management studio is installed to the SCVMM server, and I installed and patched before I began the SCVMM installation. I just don't know what else to try - I have no errors in event logs, no issues during the installation itself...
Andrew ToppThat answer was very unhelpful fr33m4n. The individual mentions that they've received the error that points to the KB article. I currently receive the same error -- there seems to be no resolution. I've run the Microsoft VBS script to add TAUG to the WAAG
as suggested by 331951, and that made absolutely no difference.
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still
"doesn't have access to AD DS," which is obviously untrue)
The user is also a member of WAAG, the machines have delegated authority to each other. Is there any other solution? -
I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
Service it leads to Some other process failures.
RehaanKhan. MAfter all the Errors, When I am restarting the SQL Server its working correctly.
Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
The following are the Errors i got connecting to SQl Server.
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
Error-2:
Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303) OLE DB provider
"Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412). The step failed.
After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
for to fix above error i have followed the instructions in the following link,
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
Thank you.
RehaanKhan. M -
SQL Server Service won't start on SQL Server 2008
Hi everyone,
I'm having trouble starting SQL Server service after stopping and starting the service. Before this happened, I created a Stored Procedure for marking all tables at once along with a maintenance plan for differential backup on all my databases based on the
recommendation from this link, http://msdn.microsoft.com/en-us/library/ms253070.aspx.
When I realized that the differential backup failed with some databases displaying (Restoring...) post-fix to the database name, I decided to stop SQL Server service and start it up. That is when I won't be able to start the service again.
Is there a fix for starting the SQL Server service? Any help is very much appreciated.
Additional information:
- With administrator permission granted.
- Service Pack 1 for SQL Server 2008 installed.
- Using default database instance.
- Tried C:\Program Files\Microsoft SQL Server\MSSQL.....\Binn>net start MSSQLSERVER /T3608 ( return msg: System error 5 has occurred. Access is denied.
- When I start SQL Server service, I keep getting this dialog msg:
"Windowns could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1814."
The event log does not explain or provide any hint on how to fix the problem.
- Log msg:
2010-07-22 10:30:25.09 Server (c) 2005 Microsoft Corporation.
2010-07-22 10:30:25.09 Server All rights reserved.
2010-07-22 10:30:25.09 Server Server process ID is 6076.
2010-07-22 10:30:25.10 Server Authentication mode is MIXED.
2010-07-22 10:30:25.10 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2010-07-22 10:30:25.11 Server This instance of SQL Server last reported using a process ID of 5708 at 7/21/2010 3:27:01 PM (local) 7/21/2010 10:27:01 PM (UTC). This is an informational message only; no user action is required.
2010-07-22 10:30:25.11 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2010-07-22 10:30:25.14 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-07-22 10:30:25.14 Server Detected 4 CPUs. This is an informational message; no user action is required.
2010-07-22 10:30:25.23 Server Using locked pages for buffer pool.
2010-07-22 10:30:25.43 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-07-22 10:30:25.73 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2010-07-22 10:30:25.81 spid7s Starting up database 'master'.
2010-07-22 10:30:26.14 spid7s CHECKDB for database 'master' finished without errors on 2010-07-19 21:15:02.823 (local time). This is an informational message only; no user action is required.
2010-07-22 10:30:26.18 spid7s Resource governor reconfiguration succeeded.
2010-07-22 10:30:26.18 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.18 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2010-07-22 10:30:26.19 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-07-22 10:30:26.28 spid7s SQL Trace ID 1 was started by login "sa".
2010-07-22 10:30:26.29 spid7s Starting up database 'mssqlsystemresource'.
2010-07-22 10:30:26.31 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2010-07-22 10:30:26.43 spid10s Starting up database 'model'.
2010-07-22 10:30:26.43 spid7s Server name is 'XXXXXXXXXXXXXX'. This is an informational message only. No user action is required.
2010-07-22 10:30:26.47 spid10s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2010-07-22 10:30:26.47 spid10s Error: 927, Severity: 14, State: 2.
2010-07-22 10:30:26.47 spid10s Database 'model' cannot be opened. It is in the middle of a restore.
2010-07-22 10:30:26.59 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in
the event log that may indicate why the tempdb files could not be initialized.
2010-07-22 10:30:26.59 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.Hello,
Could you please copy the model.mdf and modellog.ldf from
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\Templates
To
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
Rebuilding the system databases you will lose lose logins, jobs, SSIS packages. You may have to restore or attach user databases.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Maybe you are looking for
-
After updating to iOS 8.3, my iPhone 5 no longer can connect to cellular service
After updating my iPhone 5 this morning to iOS 8.3, I am no longer able to get service. Upon rebooting the phone, or removing and replacing the SIM, it connects for about 30 seconds, then drops the network connectivity and is constantly 'Searching...
-
Received new iphone 5 for Christmas. Also Blueant Q2 blue tooth ear piece. Phone works great, blueant, not so. Have had numerous emails and phone calls to tech about dropping out. There is no active phone, you are connected and all I have to do is mo
-
Why do i have to pay £25 to end my contract?
Hiya I was wondering if anyone can tell me why i have to pay a £25 administration fee because my contract has come to an end and i dont want to continue it. Of course i am used to BTs hidden fees but i dont think this is fair as i cant see what i am
-
Creating Item Catalog Category in Product Information Management(PIM)
Hi all, I am new to oracle apps R12. now i am working on Product Information Management(PIM) module in R12. I want to create a new Item catalog category(ICC) under the root item catalog. It was used to adding my new items in the hierarchy. I could ab
-
How to set different bgcolors for rows int HtmlDatatable?
I have JSF HtmlDataTable on my page. I need to fill rows in table by different colors, according to row's data, but I can't find any method for it...... Should I use JavaScript in this case?