error handling flow: service

Showing posts with label service. Show all posts

Thursday, March 29, 2012

Error loading metadata....PLZZ HELP!!

My Analysis Service has this strange errors....

My Calculation tabs, KPI tabs, Action tabs....all showing this error message at it's Calculation Tools metadata tab....

"Error loading metadata: The cube could not be retrieved from the server. Verify that the server is running and that cube is processed."

previously i even had the problem of running the script organizer for the Calculation tabs.....after installing the SP2, it's fixed, but the metadata error still there.....

i tried on my friends PC and it works fine and deploy successfully whereas mine cannot at all with all kind of errors.....

Hello. I would recommend you to uninstall BIDS on you machine and reinstall it again with SP2.

Since you have a deployed cube you can always reverse engineer it to a project in BIDS when it is working.

Regards

Thomas Ivarsson

error installing standard edition on a windows 2003 server

I have a windows 2003 server with the latest service pack and patches. This server also acts a domain controller.
Is installing standard edition on a server that is a domain controller supported because it looks like install is trying to create and add to local groups which are not present on a server if it is a domain controller.

I tried installing the standard edition of sql server and I get the following error:
ITLE: Microsoft SQL Server 2005 CTP Setup

SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group SQLServer2005SQLBrowserUser.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1187.07&EvtSrc=setup.rll&EvtID=1603&EvtType=sqlca%5csqlsecurityca.cpp%40Do_sqlGroupMember%40Do_sqlGroupMember%40x735d

BUTTONS:

TITLE: Microsoft SQL Server 2005 CTP Setup

The setup has encountered an unexpected error while Installing Local Groups. The error is :The system cannot find the file specified.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1187.07&EvtSrc=setup.rll&EvtID=2&EvtType=Unknown%40Rollback_sqlGroupMember%40Unknown%40x0

BUTTONS:

Currently SQL Server 2005 will not install on a Domain Controller or on Windows Small Business Server. There is no known work around at this time other than installing on a machine that is not configured as a domain controller. This is a known issue and we're working on resolving it.

Dan|||is this fix now?|||

3.10 Installing SQL Server Express on a Windows Domain Controller

Security Note:

We recommend against running SQL Server Express on a domain controller.

It is possible to install SQL Server Express on a Windows domain controller; however, it cannot run on a Windows Server 2003 domain controller as Local Service or Network Service. SQL Server service accounts should run as Windows domain user accounts. It is also possible to install SQL Server service accounts to run as Local System, but this option is not recommended.

Do not change the role of the server after you install SQL Server Express. For example, if you install SQL Server Express on a member server, do not use the Dcpromo tool to promote the server to a domain controller. Or, if you install SQL Server Express on a domain controller, do not use Dcpromo to demote the server to a member server. Changing the role of a server after you install SQL Server Express can result in loss of functionality and is not supported.

error installing standard edition on a windows 2003 server

I tried installing the standard edition of sql server and I get the following error:
ITLE: Microsoft SQL Server 2005 CTP Setup

SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group SQLServer2005SQLBrowserUser.

BUTTONS:

TITLE: Microsoft SQL Server 2005 CTP Setup

The setup has encountered an unexpected error while Installing Local Groups. The error is :The system cannot find the file specified.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1187.07&EvtSrc=setup.rll&EvtID=2&EvtType=Unknown%40Rollback_sqlGroupMember%40Unknown%40x0

BUTTONS:

Dan|||is this fix now?|||

3.10 Installing SQL Server Express on a Windows Domain Controller

Security Note:

We recommend against running SQL Server Express on a domain controller.

Monday, March 26, 2012

Error Installing Service Pack 1

Hi all,
I tried to upgrade a clients site to Sp1 and got the following error:
"SQL Setup failed to connect to the database service for server
configuration. Refer to the Server error logs and setup logs for more
detailed error information."
I was just wondering if anyone else has come across this error and know any
ways to fix it?
Also does the account I am logged onto (or Term Served into) the box with
require access to the Configuration Database or the Database Server?
And I can't find any documentation on what security level is required for
applying the Service Pack ie. SQL System Administrator or just DBO of the
config database?
Thanks in advance.
Angus LoganJust like the original setup, the service pack uses integrated security to
update the ReportServer database. You need to have dbo privileges to the
database on the machine where setup is being run.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Angus Logan" <angus_logan@.data3.com.au> wrote in message
news:ebzCsMeWEHA.384@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I tried to upgrade a clients site to Sp1 and got the following error:
> "SQL Setup failed to connect to the database service for server
> configuration. Refer to the Server error logs and setup logs for more
> detailed error information."
> I was just wondering if anyone else has come across this error and know
> any
> ways to fix it?
> Also does the account I am logged onto (or Term Served into) the box with
> require access to the Configuration Database or the Database Server?
> And I can't find any documentation on what security level is required for
> applying the Service Pack ie. SQL System Administrator or just DBO of the
> config database?
> Thanks in advance.
> Angus Logan
>

Thursday, March 22, 2012

error in web service reporting

hi friends i created a web service for reporting service. When i try
to send the parameter i am getting error of "here is an error in the
query. Failed to execute web request for the specified URL." I am
pasting the web method and the xml query can u please help me out in
this i am new to this field.
<WebMethod()> _
Public Function GetUserID(ByVal User_ID As Integer) As DataSet2
Dim ta As New
DataSet2TableAdapters.core_ApplicationUserTableAdapter()
Dim ds As New DataSet2
Dim dt As New DataSet2.core_ApplicationUserDataTable
ta.ClearBeforeFill = True
ta.FillByUSerID(dt, User_ID)
ds.Merge(dt)
Return ds
End Function
<Query>
<Method Namespace="http://tempuri.org/" Name="GetUserID"/>
<SoapAction>http://tempuri.org/GetUSerID
</SoapAction>
<Parameters>
<Parameter Name="User_ID">
<Value>User_ID</Value>
</Parameter>
</Parameters>
<ElementPath IgnoreNamespaces="true">
GetUSerIDResponse{}/
GetUSerIDResult/diffgram{}/DataSet2/core_ApplicationUser
</ElementPath>
</Query>
Please help me outHi
The easiest way to resolve this issue is to use an HTTP tracer like
fiddler. As a starting point try creating a parameterless web method
and querying against that just to verify that you are hitting the end
point. If that works , the next step would be to check the element
path . I would look at the query being sent by using fiddler and then
compare it to the wsdl definition to see if the web service is getting
all its parameters in the format it expects. This article pertains to
using ssrs to query a MOSS webservice but should help you out.
http://rockstarguys.com/blogs/colin/archive/2006/11/10/accessing-sharepoint-list-items-with-sql-server-2005-reporting-services.aspx
Cheers
Shai
On Nov 19, 4:05 pm, ayrookuzhy <arujgeo...@.gmail.com> wrote:
> hi friends i created a web service for reporting service. When i try
> to send the parameter i am getting error of "here is an error in the
> query. Failed to execute web request for the specified URL." I am
> pasting the web method and the xml query can u please help me out in
> this i am new to this field.
> <WebMethod()> _
> Public Function GetUserID(ByVal User_ID As Integer) As DataSet2
> Dim ta As New
> DataSet2TableAdapters.core_ApplicationUserTableAdapter()
> Dim ds As New DataSet2
> Dim dt As New DataSet2.core_ApplicationUserDataTable
> ta.ClearBeforeFill = True
> ta.FillByUSerID(dt, User_ID)
> ds.Merge(dt)
> Return ds
> End Function
> <Query>
> <Method Namespace="http://tempuri.org/" Name="GetUserID"/>
> <SoapAction>http://tempuri.org/GetUSerID
> </SoapAction>
> <Parameters>
> <Parameter Name="User_ID">
> <Value>User_ID</Value>
> </Parameter>
> </Parameters>
> <ElementPath IgnoreNamespaces="true">
> GetUSerIDResponse{}/
> GetUSerIDResult/diffgram{}/DataSet2/core_ApplicationUser
> </ElementPath>
> </Query>
> Please help me out|||Tks buddy
Cheers
Aruj

Error in the login process when establishing connection

Hello,
I am trying to connect to a database through a web service. I am being able to connect to the databse through the server explorer in Visual Studio 2005, but when I try to do it with code in my application this is the message I get:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
My code looks like this:

SqlConnection thisConnection = new SqlConnection(@."Data Source=vse1092;Initial Catalog=CurrituckDB;Integrated Security=True;"); //User id=;Password=;");
thisConnection.Open();
I also tried putting my user id and password... but same message appears.
Any help will be greatly appreciated.
Thanks,
David
Do you have the upto date SQL server express, the one that corresponds with the version of Visual Studio
|||Try with VS.NET 2003|||Also, you can try looking in the server error log (by default at "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG") for an error message that might be more informative. Look for messages that correspond in time to the failed login attempts when you run the client application.

Hope this helps,
Vaughn|||Hi,
I faced a similar issue few days back. The issue was solved when I removed the Windows 2003 Service pack1 from my system. Try removing the service pack. If U have it installed or try removing security updates that U've recently installed.

By the way, are U able to connect to the database using the management studio ot enterprise manageer?|||In addition, please check out the SQL Protocols Blog (http://blogs.msdn.com/sql_protocols/) which contains a troubleshooting connectivity series.|||Hmmm... The best way to figure this out is by looking through the error log (as Vaughn suggested). If we had a bit more information about your configuration we could probably conjecture a bit more here.
One place we've seen this happen before is when the client stacks (in your case SQLClient) and the server are mismatched intermediate versions - for example, .Net Framework 2.0 beta 2 running against SQL Server 2005 beta 2. If you have mismatched intermediate releases, you'd see something like this.

There are other reasons you might see this. There's a swath of blogs up on http://blogs.msdn.com/sql_protocols that might have the answer your looking for.

Thanks.sql

Error in the login process when establishing connection

Hello,
I am trying to connect to a database through a web service. I am being able to connect to the databse through the server explorer in Visual Studio 2005, but when I try to do it with code in my application this is the message I get:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
My code looks like this:

SqlConnection thisConnection = new SqlConnection(@."Data Source=vse1092;Initial Catalog=CurrituckDB;Integrated Security=True;"); //User id=;Password=;");
thisConnection.Open();
I also tried putting my user id and password... but same message appears.
Any help will be greatly appreciated.
Thanks,
David
Do you have the upto date SQL server express, the one that corresponds with the version of Visual Studio|||Try with VS.NET 2003|||Also, you can try looking in the server error log (by default at "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG") for an error message that might be more informative. Look for messages that correspond in time to the failed login attempts when you run the client application.

There are other reasons you might see this. There's a swath of blogs up on http://blogs.msdn.com/sql_protocols that might have the answer your looking for.

Thanks.

Wednesday, March 21, 2012

ERROR IN SQL SERVER ENGINE

I have a problem starting my SQL Server engine.

Its service has been stopped. It was working properly till evening “December 8, 2006”.

But when I came to office at 10:00 AM, it did not start. When I checked the service in “Services.msc”, it was stopped. So, I tried to start the service “SQL Server (MSSQLSERVER)”, but it failed with message “Error 1069: The service did not start due to a logon failure”.

I opened “Event viewer” and looked the list in “Application” log to find out what had happened. There was an entry for “SQL Server” source with type “Failure Audit”. There was a message “Login failed for user sa”.

What went wrong….Can someone help me? Plz its urgent….

Restart the service and post the ERRORLOG file. You can find it in <sqlserver-install-folder>\MSSQL.1\MSSQL\log

Thanks,

Ron D.

|||Hi,

which service account did you use for the SQL Server Service ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I found errorlog file in folder as you wrote. This file has lines of logs. But even after referring to the file, I could not get what was the error. So I am pasting the entire file so may be you can find the problem and tell me.

ERROR LOG FILE Contents:

2006-12-04 19:06:10.85 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2006-12-04 19:06:10.89 Server (c) 2005 Microsoft Corporation.
2006-12-04 19:06:10.90 Server All rights reserved.
2006-12-04 19:06:10.92 Server Server process ID is 1796.
2006-12-04 19:06:10.93 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-12-04 19:06:10.96 Server This instance of SQL Server last reported using a process ID of 1848 at 12/4/2006 7:02:30 PM (local) 12/4/2006 1:17:30 PM (UTC). This is an informational message only; no user action is required.
2006-12-04 19:06:11.00 Server Registry startup parameters:
2006-12-04 19:06:11.01 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-12-04 19:06:11.01 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-12-04 19:06:11.01 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-12-04 19:06:11.32 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-12-04 19:06:11.34 Server Detected 4 CPUs. This is an informational message; no user action is required.
2006-12-04 19:06:12.35 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
2006-12-04 19:06:13.96 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.
2006-12-04 19:06:15.03 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2006-12-04 19:06:17.34 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2006-12-04 19:06:17.79 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-12-04 19:06:18.42 spid4s Starting up database 'master'.
2006-12-04 19:06:21.45 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-12-04 19:06:22.81 spid4s SQL Trace ID 1 was started by login "sa".
2006-12-04 19:06:22.96 spid4s Starting up database 'mssqlsystemresource'.
2006-12-04 19:06:26.68 spid4s Server name is 'ORS_SERVER'. This is an informational message only. No user action is required.
2006-12-04 19:06:26.68 spid9s Starting up database 'model'.
2006-12-04 19:06:28.82 spid9s Clearing tempdb database.
2006-12-04 19:06:29.28 Server The certificate was successfully loaded for encryption.
2006-12-04 19:06:29.67 Server Server is listening on [ 'any' <ipv4> 1433].
2006-12-04 19:06:29.71 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2006-12-04 19:06:29.71 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2006-12-04 19:06:29.73 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2006-12-04 19:06:29.73 Server Dedicated admin connection support was established for listening locally on port 1434.
2006-12-04 19:06:29.76 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2006-12-04 19:06:29.76 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-12-04 19:06:32.54 spid13s Starting up database 'TestPackage_db_ors'.
2006-12-04 19:06:32.54 spid12s Starting up database 'msdb'.
2006-12-04 19:06:32.54 spid23s Starting up database 'anil_ors'.
2006-12-04 19:06:32.54 spid24s Starting up database 'maharjan_main_ors'.
2006-12-04 19:06:32.54 spid25s Starting up database 'maharjan_db_ors'.
2006-12-04 19:06:32.54 spid26s Starting up database 'AnilMaharjan_main_ors'.
2006-12-04 19:06:32.54 spid27s Starting up database 'AnilMaharjan_db_ors'.
2006-12-04 19:06:32.56 spid22s Starting up database 'nabin_db_ors'.
2006-12-04 19:06:32.56 spid21s Starting up database 'dummy_test_main'.
2006-12-04 19:06:32.56 spid18s Starting up database 'TestPackage_main_ors'.
2006-12-04 19:06:32.56 spid19s Starting up database 'nabin_main_ors'.
2006-12-04 19:06:32.56 spid20s Starting up database 'loadtests'.
2006-12-04 19:06:32.59 spid15s Starting up database 'main_ors'.
2006-12-04 19:06:32.59 spid14s Starting up database 'db_ors'.
2006-12-04 19:06:32.59 spid16s Starting up database 'Authentication_db_ors'.
2006-12-04 19:06:32.65 spid17s Starting up database 'authentication_main_ors'.
2006-12-04 19:06:33.49 spid25s Starting up database 'preset_main_ors'.
2006-12-04 19:06:34.31 spid24s Starting up database 'testRkwagle'.
2006-12-04 19:06:34.32 spid13s Starting up database 'manager2_main_ors'.
2006-12-04 19:06:34.79 spid17s Analysis of database 'authentication_main_ors' (10) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2006-12-04 19:06:34.98 spid12s Starting up database 'manager2_db_ors'.
2006-12-04 19:06:35.14 spid14s Starting up database 'preset_db_ors'.
2006-12-04 19:06:35.15 spid27s Starting up database 'FirstPhaseRel_Main_ORS'.
2006-12-04 19:06:35.15 spid9s Starting up database 'tempdb'.
2006-12-04 19:06:35.32 spid26s Starting up database 'FirstPhaseRel_db_ORS'.
2006-12-04 19:06:35.45 spid15s Starting up database 'SecondPhaseRel_db_ORS'.
2006-12-04 19:06:35.70 spid17s Starting up database 'SecondPhaseRel_main_ORS'.
2006-12-04 19:06:35.81 spid13s Starting up database 'TestSecondPhaseRel_db_ORS'.
2006-12-04 19:06:36.29 spid12s Starting up database 'TestSecondPhaseRel_main_ors'.
2006-12-04 19:06:36.29 spid18s Starting up database 'TestDatabase_main_ors'.
2006-12-04 19:06:36.34 spid21s Starting up database 'TestDatabase_db_ors'.
2006-12-04 19:06:36.50 spid22s Starting up database 'TestRelease2_main_ors'.
2006-12-04 19:06:36.95 spid24s Starting up database 'TestRelease2_db_ors'.
2006-12-04 19:06:37.06 spid19s Starting up database 'testdb'.
2006-12-04 19:06:40.15 spid20s Analysis of database 'loadtests' (15) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2006-12-04 19:06:46.93 spid17s Analysis of database 'SecondPhaseRel_main_ORS' (36) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2006-12-04 19:06:48.98 spid13s Analysis of database 'TestSecondPhaseRel_db_ORS' (37) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2006-12-04 19:06:50.10 spid12s The Service Broker protocol transport is disabled or not configured.
2006-12-04 19:06:50.10 spid12s The Database Mirroring protocol transport is disabled or not configured.
2006-12-04 19:06:50.48 spid12s Service Broker manager has started.
2006-12-04 19:06:55.50 spid4s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2006-12-04 19:06:55.50 spid4s Recovery is complete. This is an informational message only. No user action is required.
2006-12-04 19:26:01.14 spid52 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2006-12-04 20:07:23.21 Logon Error: 18456, Severity: 14, State: 8.
2006-12-04 20:07:23.21 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.95]
2006-12-05 00:00:45.51 spid19s This instance of SQL Server has been using a process ID of 1796 since 12/4/2006 7:06:55 PM (local) 12/4/2006 1:21:55 PM (UTC). This is an informational message only; no user action is required.
2006-12-05 09:43:01.54 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 09:43:01.54 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-05 09:43:07.00 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 09:43:07.00 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-05 09:54:34.90 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 09:54:34.90 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-05 09:59:55.03 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 09:59:55.03 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-05 10:00:32.70 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 10:00:32.70 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-05 10:19:27.56 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 10:19:27.56 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-05 10:29:51.84 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 10:29:51.84 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.196]
2006-12-05 11:35:54.78 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 11:35:54.78 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-05 11:38:45.68 spid58 Starting up database 'Bipin_main_ors'.
2006-12-05 11:38:46.12 spid58 Setting database option ANSI_NULL_DEFAULT to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.14 spid58 Setting database option ANSI_NULLS to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.14 spid58 Setting database option ANSI_PADDING to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.14 spid58 Setting database option ANSI_WARNINGS to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.15 spid58 Setting database option ARITHABORT to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.15 spid58 Setting database option AUTO_CLOSE to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.17 spid58 Setting database option AUTO_CREATE_STATISTICS to ON for database Bipin_main_ors.
2006-12-05 11:38:46.17 spid58 Setting database option AUTO_SHRINK to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.17 spid58 Setting database option AUTO_UPDATE_STATISTICS to ON for database Bipin_main_ors.
2006-12-05 11:38:46.18 spid58 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.18 spid58 Setting database option CURSOR_DEFAULT to GLOBAL for database Bipin_main_ors.
2006-12-05 11:38:46.18 spid58 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.21 spid58 Setting database option NUMERIC_ROUNDABORT to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.21 spid58 Setting database option QUOTED_IDENTIFIER to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.21 spid58 Setting database option RECURSIVE_TRIGGERS to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.23 spid58 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.23 spid58 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database Bipin_main_ors.
2006-12-05 11:38:46.25 spid58 Setting database option PARAMETERIZATION to SIMPLE for database Bipin_main_ors.
2006-12-05 11:38:46.25 spid58 Setting database option READ_WRITE to ON for database Bipin_main_ors.
2006-12-05 11:38:46.25 spid58 Setting database option RECOVERY to FULL for database Bipin_main_ors.
2006-12-05 11:38:46.26 spid58 Setting database option MULTI_USER to ON for database Bipin_main_ors.
2006-12-05 11:38:46.26 spid58 Setting database option PAGE_VERIFY to CHECKSUM for database Bipin_main_ors.
2006-12-05 11:50:50.81 spid69 Starting up database 'Bipin_main_ors'.
2006-12-05 11:50:50.82 spid69 The database 'Bipin_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 11:50:51.00 spid69 Starting up database 'Bipin_main_ors'.
2006-12-05 11:50:51.34 Backup Database was restored: Database: Bipin_main_ors, creation date(time): 2006/12/03(20:16:25), first LSN: 41:343:89, last LSN: 41:380:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\bipin_db_setup\main_ors.bak'}). Informational message. No user action required.
2006-12-05 11:51:20.79 spid69 Starting up database 'Bipin_db_ors'.
2006-12-05 11:51:21.28 spid69 Setting database option ANSI_NULL_DEFAULT to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.29 spid69 Setting database option ANSI_NULLS to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.29 spid69 Setting database option ANSI_PADDING to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.31 spid69 Setting database option ANSI_WARNINGS to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.31 spid69 Setting database option ARITHABORT to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.32 spid69 Setting database option AUTO_CLOSE to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.34 spid69 Setting database option AUTO_CREATE_STATISTICS to ON for database Bipin_db_ors.
2006-12-05 11:51:21.34 spid69 Setting database option AUTO_SHRINK to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.34 spid69 Setting database option AUTO_UPDATE_STATISTICS to ON for database Bipin_db_ors.
2006-12-05 11:51:21.35 spid69 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.35 spid69 Setting database option CURSOR_DEFAULT to GLOBAL for database Bipin_db_ors.
2006-12-05 11:51:21.35 spid69 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.37 spid69 Setting database option NUMERIC_ROUNDABORT to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.37 spid69 Setting database option QUOTED_IDENTIFIER to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.39 spid69 Setting database option RECURSIVE_TRIGGERS to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.39 spid69 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.39 spid69 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database Bipin_db_ors.
2006-12-05 11:51:21.40 spid69 Setting database option PARAMETERIZATION to SIMPLE for database Bipin_db_ors.
2006-12-05 11:51:21.40 spid69 Setting database option READ_WRITE to ON for database Bipin_db_ors.
2006-12-05 11:51:21.40 spid69 Setting database option RECOVERY to FULL for database Bipin_db_ors.
2006-12-05 11:51:21.42 spid69 Setting database option MULTI_USER to ON for database Bipin_db_ors.
2006-12-05 11:51:21.42 spid69 Setting database option PAGE_VERIFY to CHECKSUM for database Bipin_db_ors.
2006-12-05 11:52:04.10 spid69 Starting up database 'Bipin_db_ors'.
2006-12-05 11:52:04.10 spid69 The database 'Bipin_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 11:52:04.29 spid69 Starting up database 'Bipin_db_ors'.
2006-12-05 11:52:04.60 Backup Database was restored: Database: Bipin_db_ors, creation date(time): 2006/12/03(13:03:10), first LSN: 27:195:37, last LSN: 27:211:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\bipin_db_setup\db_ors.bak'}). Informational message. No user action required.
2006-12-05 12:19:13.78 spid53 Starting up database 'TestManager_main_ors'.
2006-12-05 12:19:13.78 spid53 The database 'TestManager_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 12:19:13.98 spid53 Starting up database 'TestManager_main_ors'.
2006-12-05 12:19:14.28 Backup Database was restored: Database: TestManager_main_ors, creation date(time): 2006/12/03(20:16:25), first LSN: 41:343:89, last LSN: 41:380:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\db-setup-5dec\db-setup\main_ors.bak'}). Informational message. No user action required.
2006-12-05 12:19:58.09 spid53 Starting up database 'TestManager_db_ors'.
2006-12-05 12:19:58.09 spid53 The database 'TestManager_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 12:19:58.31 spid53 Starting up database 'TestManager_db_ors'.
2006-12-05 12:19:58.65 Backup Database was restored: Database: TestManager_db_ors, creation date(time): 2006/12/03(13:03:10), first LSN: 27:195:37, last LSN: 27:211:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\db-setup-5dec\db-setup\db_ors.bak'}). Informational message. No user action required.
2006-12-05 12:22:35.70 spid53 Setting database option TRUSTWORTHY to ON for database testManager_main_ors.
2006-12-05 12:22:52.26 spid53 Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\.
2006-12-05 12:23:33.70 spid76 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-05 12:23:34.03 spid76 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-05 12:23:34.06 spid76 Setting database option TRUSTWORTHY to ON for database testManager_main_ors.
2006-12-05 12:23:50.39 spid76 AppDomain 4 (TestManager_main_ors.dbo[runtime].3) created.
2006-12-05 12:54:56.79 spid77 Using 'xp_pcre.dll' version '0001.03.00' to execute extended stored procedure 'xp_pcre_replace'. This is an informational message only; no user action is required.
2006-12-05 13:34:03.45 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 13:34:03.45 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-05 13:34:13.09 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 13:34:13.09 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-05 13:39:29.84 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 13:39:29.84 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-05 13:42:28.92 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 13:42:28.92 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-05 13:44:23.18 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 13:44:23.18 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-05 13:50:42.64 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 13:50:42.64 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-05 14:12:35.51 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 14:12:35.51 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.21]
2006-12-05 15:04:57.62 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 15:04:57.62 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-05 15:05:24.64 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 15:05:24.64 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-05 15:06:02.06 Logon Error: 18456, Severity: 14, State: 8.
2006-12-05 15:06:02.06 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.82]
2006-12-05 16:39:22.03 spid101 Starting up database 'release_main_ors'.
2006-12-05 16:39:22.57 spid101 Setting database option ANSI_NULL_DEFAULT to OFF for database release_main_ors.
2006-12-05 16:39:22.59 spid101 Setting database option ANSI_NULLS to OFF for database release_main_ors.
2006-12-05 16:39:22.60 spid101 Setting database option ANSI_PADDING to OFF for database release_main_ors.
2006-12-05 16:39:22.60 spid101 Setting database option ANSI_WARNINGS to OFF for database release_main_ors.
2006-12-05 16:39:22.62 spid101 Setting database option ARITHABORT to OFF for database release_main_ors.
2006-12-05 16:39:22.63 spid101 Setting database option AUTO_CLOSE to OFF for database release_main_ors.
2006-12-05 16:39:22.65 spid101 Setting database option AUTO_CREATE_STATISTICS to ON for database release_main_ors.
2006-12-05 16:39:22.67 spid101 Setting database option AUTO_SHRINK to OFF for database release_main_ors.
2006-12-05 16:39:22.68 spid101 Setting database option AUTO_UPDATE_STATISTICS to ON for database release_main_ors.
2006-12-05 16:39:22.68 spid101 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database release_main_ors.
2006-12-05 16:39:22.70 spid101 Setting database option CURSOR_DEFAULT to GLOBAL for database release_main_ors.
2006-12-05 16:39:22.71 spid101 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database release_main_ors.
2006-12-05 16:39:22.73 spid101 Setting database option NUMERIC_ROUNDABORT to OFF for database release_main_ors.
2006-12-05 16:39:22.74 spid101 Setting database option QUOTED_IDENTIFIER to OFF for database release_main_ors.
2006-12-05 16:39:22.76 spid101 Setting database option RECURSIVE_TRIGGERS to OFF for database release_main_ors.
2006-12-05 16:39:22.78 spid101 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database release_main_ors.
2006-12-05 16:39:22.78 spid101 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database release_main_ors.
2006-12-05 16:39:22.79 spid101 Setting database option PARAMETERIZATION to SIMPLE for database release_main_ors.
2006-12-05 16:39:22.81 spid101 Setting database option READ_WRITE to ON for database release_main_ors.
2006-12-05 16:39:22.81 spid101 Setting database option RECOVERY to FULL for database release_main_ors.
2006-12-05 16:39:22.82 spid101 Setting database option MULTI_USER to ON for database release_main_ors.
2006-12-05 16:39:22.82 spid101 Setting database option PAGE_VERIFY to CHECKSUM for database release_main_ors.
2006-12-05 16:39:39.96 spid51 Starting up database 'release_db_ors'.
2006-12-05 16:39:40.32 spid51 Setting database option ANSI_NULL_DEFAULT to OFF for database release_db_ors.
2006-12-05 16:39:40.34 spid51 Setting database option ANSI_NULLS to OFF for database release_db_ors.
2006-12-05 16:39:40.35 spid51 Setting database option ANSI_PADDING to OFF for database release_db_ors.
2006-12-05 16:39:40.35 spid51 Setting database option ANSI_WARNINGS to OFF for database release_db_ors.
2006-12-05 16:39:40.37 spid51 Setting database option ARITHABORT to OFF for database release_db_ors.
2006-12-05 16:39:40.39 spid51 Setting database option AUTO_CLOSE to OFF for database release_db_ors.
2006-12-05 16:39:40.40 spid51 Setting database option AUTO_CREATE_STATISTICS to ON for database release_db_ors.
2006-12-05 16:39:40.40 spid51 Setting database option AUTO_SHRINK to OFF for database release_db_ors.
2006-12-05 16:39:40.42 spid51 Setting database option AUTO_UPDATE_STATISTICS to ON for database release_db_ors.
2006-12-05 16:39:40.43 spid51 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database release_db_ors.
2006-12-05 16:39:40.45 spid51 Setting database option CURSOR_DEFAULT to GLOBAL for database release_db_ors.
2006-12-05 16:39:40.46 spid51 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database release_db_ors.
2006-12-05 16:39:40.46 spid51 Setting database option NUMERIC_ROUNDABORT to OFF for database release_db_ors.
2006-12-05 16:39:40.48 spid51 Setting database option QUOTED_IDENTIFIER to OFF for database release_db_ors.
2006-12-05 16:39:40.50 spid51 Setting database option RECURSIVE_TRIGGERS to OFF for database release_db_ors.
2006-12-05 16:39:40.53 spid51 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database release_db_ors.
2006-12-05 16:39:40.54 spid51 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database release_db_ors.
2006-12-05 16:39:40.59 spid51 Setting database option PARAMETERIZATION to SIMPLE for database release_db_ors.
2006-12-05 16:39:40.62 spid51 Setting database option READ_WRITE to ON for database release_db_ors.
2006-12-05 16:39:40.64 spid51 Setting database option RECOVERY to FULL for database release_db_ors.
2006-12-05 16:39:40.65 spid51 Setting database option MULTI_USER to ON for database release_db_ors.
2006-12-05 16:39:40.65 spid51 Setting database option PAGE_VERIFY to CHECKSUM for database release_db_ors.
2006-12-05 16:40:38.76 spid51 Starting up database 'release_main_ors'.
2006-12-05 16:40:38.76 spid51 The database 'release_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 16:40:39.00 spid51 Starting up database 'release_main_ors'.
2006-12-05 16:40:39.29 Backup Database was restored: Database: release_main_ors, creation date(time): 2006/12/03(20:16:25), first LSN: 41:343:89, last LSN: 41:380:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\main_ors.bak'}). Informational message. No user action required.
2006-12-05 16:41:28.26 spid51 Starting up database 'release_db_ors'.
2006-12-05 16:41:28.26 spid51 The database 'release_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 16:41:28.54 spid51 Starting up database 'release_db_ors'.
2006-12-05 16:41:28.87 Backup Database was restored: Database: release_db_ors, creation date(time): 2006/12/03(13:03:10), first LSN: 27:195:37, last LSN: 27:211:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\db_ors.bak'}). Informational message. No user action required.
2006-12-05 16:47:08.25 Backup Database backed up. Database: release_main_ors, creation date(time): 2006/12/05(16:40:38), pages dumped: 411, first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-05 16:47:31.42 Backup Database backed up. Database: release_db_ors, creation date(time): 2006/12/05(16:41:27), pages dumped: 163, first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\db_ors.bak'}). This is an informational message only. No user action is required.
2006-12-05 17:04:58.14 spid74 Starting up database 'main_ors'.
2006-12-05 17:04:58.70 spid74 Setting database option ANSI_NULL_DEFAULT to OFF for database main_ors.
2006-12-05 17:04:58.73 spid74 Setting database option ANSI_NULLS to OFF for database main_ors.
2006-12-05 17:04:58.73 spid74 Setting database option ANSI_PADDING to OFF for database main_ors.
2006-12-05 17:04:58.73 spid74 Setting database option ANSI_WARNINGS to OFF for database main_ors.
2006-12-05 17:04:58.75 spid74 Setting database option ARITHABORT to OFF for database main_ors.
2006-12-05 17:04:58.75 spid74 Setting database option AUTO_CLOSE to OFF for database main_ors.
2006-12-05 17:04:58.75 spid74 Setting database option AUTO_CREATE_STATISTICS to ON for database main_ors.
2006-12-05 17:04:58.76 spid74 Setting database option AUTO_SHRINK to OFF for database main_ors.
2006-12-05 17:04:58.76 spid74 Setting database option AUTO_UPDATE_STATISTICS to ON for database main_ors.
2006-12-05 17:04:58.78 spid74 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database main_ors.
2006-12-05 17:04:58.78 spid74 Setting database option CURSOR_DEFAULT to GLOBAL for database main_ors.
2006-12-05 17:04:58.78 spid74 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database main_ors.
2006-12-05 17:04:58.79 spid74 Setting database option NUMERIC_ROUNDABORT to OFF for database main_ors.
2006-12-05 17:04:58.79 spid74 Setting database option QUOTED_IDENTIFIER to OFF for database main_ors.
2006-12-05 17:04:58.81 spid74 Setting database option RECURSIVE_TRIGGERS to OFF for database main_ors.
2006-12-05 17:04:58.81 spid74 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database main_ors.
2006-12-05 17:04:58.81 spid74 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database main_ors.
2006-12-05 17:04:58.82 spid74 Setting database option PARAMETERIZATION to SIMPLE for database main_ors.
2006-12-05 17:04:58.82 spid74 Setting database option READ_WRITE to ON for database main_ors.
2006-12-05 17:04:58.82 spid74 Setting database option RECOVERY to FULL for database main_ors.
2006-12-05 17:04:58.84 spid74 Setting database option MULTI_USER to ON for database main_ors.
2006-12-05 17:04:58.84 spid74 Setting database option PAGE_VERIFY to CHECKSUM for database main_ors.
2006-12-05 17:05:14.78 spid74 Starting up database 'db_ors'.
2006-12-05 17:05:15.14 spid74 Setting database option ANSI_NULL_DEFAULT to OFF for database db_ors.
2006-12-05 17:05:15.15 spid74 Setting database option ANSI_NULLS to OFF for database db_ors.
2006-12-05 17:05:15.15 spid74 Setting database option ANSI_PADDING to OFF for database db_ors.
2006-12-05 17:05:15.15 spid74 Setting database option ANSI_WARNINGS to OFF for database db_ors.
2006-12-05 17:05:15.17 spid74 Setting database option ARITHABORT to OFF for database db_ors.
2006-12-05 17:05:15.17 spid74 Setting database option AUTO_CLOSE to OFF for database db_ors.
2006-12-05 17:05:15.17 spid74 Setting database option AUTO_CREATE_STATISTICS to ON for database db_ors.
2006-12-05 17:05:15.18 spid74 Setting database option AUTO_SHRINK to OFF for database db_ors.
2006-12-05 17:05:15.18 spid74 Setting database option AUTO_UPDATE_STATISTICS to ON for database db_ors.
2006-12-05 17:05:15.21 spid74 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database db_ors.
2006-12-05 17:05:15.21 spid74 Setting database option CURSOR_DEFAULT to GLOBAL for database db_ors.
2006-12-05 17:05:15.23 spid74 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database db_ors.
2006-12-05 17:05:15.23 spid74 Setting database option NUMERIC_ROUNDABORT to OFF for database db_ors.
2006-12-05 17:05:15.25 spid74 Setting database option QUOTED_IDENTIFIER to OFF for database db_ors.
2006-12-05 17:05:15.25 spid74 Setting database option RECURSIVE_TRIGGERS to OFF for database db_ors.
2006-12-05 17:05:15.26 spid74 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database db_ors.
2006-12-05 17:05:15.26 spid74 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database db_ors.
2006-12-05 17:05:15.28 spid74 Setting database option PARAMETERIZATION to SIMPLE for database db_ors.
2006-12-05 17:05:15.28 spid74 Setting database option READ_WRITE to ON for database db_ors.
2006-12-05 17:05:15.29 spid74 Setting database option RECOVERY to FULL for database db_ors.
2006-12-05 17:05:15.29 spid74 Setting database option MULTI_USER to ON for database db_ors.
2006-12-05 17:05:15.29 spid74 Setting database option PAGE_VERIFY to CHECKSUM for database db_ors.
2006-12-05 17:09:19.25 spid96 Starting up database 'main_ors'.
2006-12-05 17:09:19.26 spid96 The database 'main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 17:09:19.48 spid96 Starting up database 'main_ors'.
2006-12-05 17:09:19.87 Backup Database was restored: Database: main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\main_ors.bak'}). Informational message. No user action required.
2006-12-05 17:10:22.28 spid96 Starting up database 'db_ors'.
2006-12-05 17:10:22.29 spid96 The database 'db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 17:10:22.60 spid96 Starting up database 'db_ors'.
2006-12-05 17:10:22.93 Backup Database was restored: Database: db_ors, creation date(time): 2006/12/05(16:41:27), first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\db_ors.bak'}). Informational message. No user action required.
2006-12-05 17:12:37.07 spid101 Starting up database 'manager_main_ors'.
2006-12-05 17:12:37.54 spid101 Setting database option ANSI_NULL_DEFAULT to OFF for database manager_main_ors.
2006-12-05 17:12:37.56 spid101 Setting database option ANSI_NULLS to OFF for database manager_main_ors.
2006-12-05 17:12:37.56 spid101 Setting database option ANSI_PADDING to OFF for database manager_main_ors.
2006-12-05 17:12:37.57 spid101 Setting database option ANSI_WARNINGS to OFF for database manager_main_ors.
2006-12-05 17:12:37.57 spid101 Setting database option ARITHABORT to OFF for database manager_main_ors.
2006-12-05 17:12:37.59 spid101 Setting database option AUTO_CLOSE to OFF for database manager_main_ors.
2006-12-05 17:12:37.59 spid101 Setting database option AUTO_CREATE_STATISTICS to ON for database manager_main_ors.
2006-12-05 17:12:37.60 spid101 Setting database option AUTO_SHRINK to OFF for database manager_main_ors.
2006-12-05 17:12:37.60 spid101 Setting database option AUTO_UPDATE_STATISTICS to ON for database manager_main_ors.
2006-12-05 17:12:37.60 spid101 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database manager_main_ors.
2006-12-05 17:12:37.62 spid101 Setting database option CURSOR_DEFAULT to GLOBAL for database manager_main_ors.
2006-12-05 17:12:37.62 spid101 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database manager_main_ors.
2006-12-05 17:12:37.64 spid101 Setting database option NUMERIC_ROUNDABORT to OFF for database manager_main_ors.
2006-12-05 17:12:37.64 spid101 Setting database option QUOTED_IDENTIFIER to OFF for database manager_main_ors.
2006-12-05 17:12:37.64 spid101 Setting database option RECURSIVE_TRIGGERS to OFF for database manager_main_ors.
2006-12-05 17:12:37.65 spid101 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database manager_main_ors.
2006-12-05 17:12:37.65 spid101 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database manager_main_ors.
2006-12-05 17:12:37.65 spid101 Setting database option PARAMETERIZATION to SIMPLE for database manager_main_ors.
2006-12-05 17:12:37.67 spid101 Setting database option READ_WRITE to ON for database manager_main_ors.
2006-12-05 17:12:37.67 spid101 Setting database option RECOVERY to FULL for database manager_main_ors.
2006-12-05 17:12:37.68 spid101 Setting database option MULTI_USER to ON for database manager_main_ors.
2006-12-05 17:12:37.68 spid101 Setting database option PAGE_VERIFY to CHECKSUM for database manager_main_ors.
2006-12-05 17:13:09.85 spid53 Starting up database 'manager_db_ors'.
2006-12-05 17:13:10.43 spid53 Setting database option ANSI_NULL_DEFAULT to OFF for database manager_db_ors.
2006-12-05 17:13:10.45 spid53 Setting database option ANSI_NULLS to OFF for database manager_db_ors.
2006-12-05 17:13:10.46 spid53 Setting database option ANSI_PADDING to OFF for database manager_db_ors.
2006-12-05 17:13:10.48 spid53 Setting database option ANSI_WARNINGS to OFF for database manager_db_ors.
2006-12-05 17:13:10.50 spid53 Setting database option ARITHABORT to OFF for database manager_db_ors.
2006-12-05 17:13:10.53 spid53 Setting database option AUTO_CLOSE to OFF for database manager_db_ors.
2006-12-05 17:13:10.54 spid53 Setting database option AUTO_CREATE_STATISTICS to ON for database manager_db_ors.
2006-12-05 17:13:10.56 spid53 Setting database option AUTO_SHRINK to OFF for database manager_db_ors.
2006-12-05 17:13:10.59 spid53 Setting database option AUTO_UPDATE_STATISTICS to ON for database manager_db_ors.
2006-12-05 17:13:10.59 spid53 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database manager_db_ors.
2006-12-05 17:13:10.60 spid53 Setting database option CURSOR_DEFAULT to GLOBAL for database manager_db_ors.
2006-12-05 17:13:10.64 spid53 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database manager_db_ors.
2006-12-05 17:13:10.64 spid53 Setting database option NUMERIC_ROUNDABORT to OFF for database manager_db_ors.
2006-12-05 17:13:10.65 spid53 Setting database option QUOTED_IDENTIFIER to OFF for database manager_db_ors.
2006-12-05 17:13:10.67 spid53 Setting database option RECURSIVE_TRIGGERS to OFF for database manager_db_ors.
2006-12-05 17:13:10.68 spid53 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database manager_db_ors.
2006-12-05 17:13:10.70 spid53 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database manager_db_ors.
2006-12-05 17:13:10.71 spid53 Setting database option PARAMETERIZATION to SIMPLE for database manager_db_ors.
2006-12-05 17:13:10.73 spid53 Setting database option READ_WRITE to ON for database manager_db_ors.
2006-12-05 17:13:10.73 spid53 Setting database option RECOVERY to FULL for database manager_db_ors.
2006-12-05 17:13:10.75 spid53 Setting database option MULTI_USER to ON for database manager_db_ors.
2006-12-05 17:13:10.76 spid53 Setting database option PAGE_VERIFY to CHECKSUM for database manager_db_ors.
2006-12-05 17:13:25.25 spid77 AppDomain 5 (maharjan_main_ors.dbo[runtime].4) created.
2006-12-05 17:15:01.32 spid53 Starting up database 'manager_main_ors'.
2006-12-05 17:15:01.32 spid53 The database 'manager_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 17:15:01.54 spid53 Starting up database 'manager_main_ors'.
2006-12-05 17:15:01.90 Backup Database was restored: Database: manager_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\main_ors.bak'}). Informational message. No user action required.
2006-12-05 17:15:37.68 spid53 Starting up database 'manager_db_ors'.
2006-12-05 17:15:37.68 spid53 The database 'manager_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 17:15:37.87 spid53 Starting up database 'manager_db_ors'.
2006-12-05 17:15:38.17 Backup Database was restored: Database: manager_db_ors, creation date(time): 2006/12/05(16:41:27), first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\db_ors.bak'}). Informational message. No user action required.
2006-12-05 17:16:16.18 spid53 Starting up database 'test_main_ors'.
2006-12-05 17:16:16.62 spid53 Setting database option ANSI_NULL_DEFAULT to OFF for database test_main_ors.
2006-12-05 17:16:16.64 spid53 Setting database option ANSI_NULLS to OFF for database test_main_ors.
2006-12-05 17:16:16.65 spid53 Setting database option ANSI_PADDING to OFF for database test_main_ors.
2006-12-05 17:16:16.65 spid53 Setting database option ANSI_WARNINGS to OFF for database test_main_ors.
2006-12-05 17:16:16.67 spid53 Setting database option ARITHABORT to OFF for database test_main_ors.
2006-12-05 17:16:16.67 spid53 Setting database option AUTO_CLOSE to OFF for database test_main_ors.
2006-12-05 17:16:16.67 spid53 Setting database option AUTO_CREATE_STATISTICS to ON for database test_main_ors.
2006-12-05 17:16:16.68 spid53 Setting database option AUTO_SHRINK to OFF for database test_main_ors.
2006-12-05 17:16:16.68 spid53 Setting database option AUTO_UPDATE_STATISTICS to ON for database test_main_ors.
2006-12-05 17:16:16.68 spid53 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database test_main_ors.
2006-12-05 17:16:16.70 spid53 Setting database option CURSOR_DEFAULT to GLOBAL for database test_main_ors.
2006-12-05 17:16:16.70 spid53 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database test_main_ors.
2006-12-05 17:16:16.71 spid53 Setting database option NUMERIC_ROUNDABORT to OFF for database test_main_ors.
2006-12-05 17:16:16.71 spid53 Setting database option QUOTED_IDENTIFIER to OFF for database test_main_ors.
2006-12-05 17:16:16.71 spid53 Setting database option RECURSIVE_TRIGGERS to OFF for database test_main_ors.
2006-12-05 17:16:16.73 spid53 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database test_main_ors.
2006-12-05 17:16:16.73 spid53 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database test_main_ors.
2006-12-05 17:16:16.75 spid53 Setting database option PARAMETERIZATION to SIMPLE for database test_main_ors.
2006-12-05 17:16:16.75 spid53 Setting database option READ_WRITE to ON for database test_main_ors.
2006-12-05 17:16:16.75 spid53 Setting database option RECOVERY to FULL for database test_main_ors.
2006-12-05 17:16:16.76 spid53 Setting database option MULTI_USER to ON for database test_main_ors.
2006-12-05 17:16:16.76 spid53 Setting database option PAGE_VERIFY to CHECKSUM for database test_main_ors.
2006-12-05 17:16:50.04 spid53 Starting up database 'test_db_ors'.
2006-12-05 17:16:50.38 spid53 Setting database option ANSI_NULL_DEFAULT to OFF for database test_db_ors.
2006-12-05 17:16:50.40 spid53 Setting database option ANSI_NULLS to OFF for database test_db_ors.
2006-12-05 17:16:50.40 spid53 Setting database option ANSI_PADDING to OFF for database test_db_ors.
2006-12-05 17:16:50.42 spid53 Setting database option ANSI_WARNINGS to OFF for database test_db_ors.
2006-12-05 17:16:50.43 spid53 Setting database option ARITHABORT to OFF for database test_db_ors.
2006-12-05 17:16:50.45 spid53 Setting database option AUTO_CLOSE to OFF for database test_db_ors.
2006-12-05 17:16:50.45 spid53 Setting database option AUTO_CREATE_STATISTICS to ON for database test_db_ors.
2006-12-05 17:16:50.46 spid53 Setting database option AUTO_SHRINK to OFF for database test_db_ors.
2006-12-05 17:16:50.46 spid53 Setting database option AUTO_UPDATE_STATISTICS to ON for database test_db_ors.
2006-12-05 17:16:50.46 spid53 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database test_db_ors.
2006-12-05 17:16:50.48 spid53 Setting database option CURSOR_DEFAULT to GLOBAL for database test_db_ors.
2006-12-05 17:16:50.48 spid53 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database test_db_ors.
2006-12-05 17:16:50.49 spid53 Setting database option NUMERIC_ROUNDABORT to OFF for database test_db_ors.
2006-12-05 17:16:50.49 spid53 Setting database option QUOTED_IDENTIFIER to OFF for database test_db_ors.
2006-12-05 17:16:50.51 spid53 Setting database option RECURSIVE_TRIGGERS to OFF for database test_db_ors.
2006-12-05 17:16:50.51 spid53 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database test_db_ors.
2006-12-05 17:16:50.53 spid53 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database test_db_ors.
2006-12-05 17:16:50.56 spid53 Setting database option PARAMETERIZATION to SIMPLE for database test_db_ors.
2006-12-05 17:16:50.63 spid53 Setting database option READ_WRITE to ON for database test_db_ors.
2006-12-05 17:16:50.63 spid53 Setting database option RECOVERY to FULL for database test_db_ors.
2006-12-05 17:16:50.65 spid53 Setting database option MULTI_USER to ON for database test_db_ors.
2006-12-05 17:16:50.68 spid53 Setting database option PAGE_VERIFY to CHECKSUM for database test_db_ors.
2006-12-05 17:23:24.67 spid64 Starting up database 'test_main_ors'.
2006-12-05 17:23:25.09 spid64 Setting database option ANSI_NULL_DEFAULT to OFF for database test_main_ors.
2006-12-05 17:23:25.10 spid64 Setting database option ANSI_NULLS to OFF for database test_main_ors.
2006-12-05 17:23:25.10 spid64 Setting database option ANSI_PADDING to OFF for database test_main_ors.
2006-12-05 17:23:25.10 spid64 Setting database option ANSI_WARNINGS to OFF for database test_main_ors.
2006-12-05 17:23:25.12 spid64 Setting database option ARITHABORT to OFF for database test_main_ors.
2006-12-05 17:23:25.12 spid64 Setting database option AUTO_CLOSE to OFF for database test_main_ors.
2006-12-05 17:23:25.13 spid64 Setting database option AUTO_CREATE_STATISTICS to ON for database test_main_ors.
2006-12-05 17:23:25.13 spid64 Setting database option AUTO_SHRINK to OFF for database test_main_ors.
2006-12-05 17:23:25.13 spid64 Setting database option AUTO_UPDATE_STATISTICS to ON for database test_main_ors.
2006-12-05 17:23:25.17 spid64 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database test_main_ors.
2006-12-05 17:23:25.17 spid64 Setting database option CURSOR_DEFAULT to GLOBAL for database test_main_ors.
2006-12-05 17:23:25.18 spid64 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database test_main_ors.
2006-12-05 17:23:25.18 spid64 Setting database option NUMERIC_ROUNDABORT to OFF for database test_main_ors.
2006-12-05 17:23:25.20 spid64 Setting database option QUOTED_IDENTIFIER to OFF for database test_main_ors.
2006-12-05 17:23:25.21 spid64 Setting database option RECURSIVE_TRIGGERS to OFF for database test_main_ors.
2006-12-05 17:23:25.21 spid64 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database test_main_ors.
2006-12-05 17:23:25.23 spid64 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database test_main_ors.
2006-12-05 17:23:25.23 spid64 Setting database option PARAMETERIZATION to SIMPLE for database test_main_ors.
2006-12-05 17:23:25.23 spid64 Setting database option READ_WRITE to ON for database test_main_ors.
2006-12-05 17:23:25.24 spid64 Setting database option RECOVERY to FULL for database test_main_ors.
2006-12-05 17:23:25.24 spid64 Setting database option MULTI_USER to ON for database test_main_ors.
2006-12-05 17:23:25.26 spid64 Setting database option PAGE_VERIFY to CHECKSUM for database test_main_ors.
2006-12-05 17:24:45.76 spid64 Starting up database 'test_main_ors'.
2006-12-05 17:24:45.76 spid64 The database 'test_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 17:24:46.06 spid64 Starting up database 'test_main_ors'.
2006-12-05 17:24:46.40 Backup Database was restored: Database: test_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\main_ors.bak'}). Informational message. No user action required.
2006-12-05 17:25:35.68 spid64 Starting up database 'test_db_ors'.
2006-12-05 17:25:35.70 spid64 The database 'test_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-05 17:25:35.88 spid64 Starting up database 'test_db_ors'.
2006-12-05 17:25:36.26 Backup Database was restored: Database: test_db_ors, creation date(time): 2006/12/05(16:41:27), first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\5dec\db_ors.bak'}). Informational message. No user action required.
2006-12-05 17:27:14.43 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-05 17:27:14.45 spid51 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-05 17:27:14.48 spid51 Setting database option TRUSTWORTHY to ON for database test_main_ors.
2006-12-05 17:27:30.87 spid51 AppDomain 7 (test_main_ors.dbo[runtime].6) created.
2006-12-05 17:27:47.76 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-05 17:27:47.82 spid51 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-05 17:27:47.84 spid51 Setting database option TRUSTWORTHY to ON for database manager_main_ors.
2006-12-05 17:27:49.34 spid51 AppDomain 9 (manager_main_ors.dbo[runtime].8) created.
2006-12-05 19:19:54.73 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 19:19:54.73 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.28]
2006-12-05 19:20:13.60 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 19:20:13.60 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.28]
2006-12-05 19:20:32.15 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 19:20:32.15 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.28]
2006-12-05 19:21:15.53 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 19:21:15.53 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.28]
2006-12-05 19:21:42.28 Logon Error: 18456, Severity: 14, State: 16.
2006-12-05 19:21:42.28 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.28]
2006-12-06 00:00:30.51 spid20s This instance of SQL Server has been using a process ID of 1796 since 12/4/2006 7:06:55 PM (local) 12/4/2006 1:21:55 PM (UTC). This is an informational message only; no user action is required.
2006-12-06 10:17:54.23 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 10:17:54.23 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.83]
2006-12-06 10:22:10.03 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 10:22:10.03 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 10:22:16.45 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 10:22:16.45 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 10:47:36.29 Backup Database backed up. Database: TestSecondPhaseRel_db_ORS, creation date(time): 2006/11/19(11:23:39), pages dumped: 8637, first LSN: 413:62890:37, last LSN: 413:62906:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\TestSecondPhaseRel\TestSecondPhaseRel_db_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:48:18.46 Backup Database backed up. Database: TestSecondPhaseRel_main_ors, creation date(time): 2006/11/19(11:24:48), pages dumped: 2599, first LSN: 301:12326:46, last LSN: 301:12346:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\TestSecondPhaseRel\TestSecondPhaseRel_main_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:49:11.95 Backup Database backed up. Database: TestPackage_db_ors, creation date(time): 2006/12/04(13:23:03), pages dumped: 2710, first LSN: 121:1233:230, last LSN: 121:1328:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\TestPackage_ors\TestPackage_db_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:49:50.56 Backup Database backed up. Database: TestPackage_main_ors, creation date(time): 2006/12/04(12:59:16), pages dumped: 2079, first LSN: 203:9834:215, last LSN: 203:9919:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\TestPackage_ors\testPackage_main_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:54:55.46 Backup Database backed up. Database: TestManager_db_ors, creation date(time): 2006/12/05(12:19:57), pages dumped: 651, first LSN: 89:865:223, last LSN: 89:956:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\manager_ors\TestManager_db_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:55:36.34 Backup Database backed up. Database: TestManager_main_ors, creation date(time): 2006/12/05(12:19:13), pages dumped: 678, first LSN: 58:407:104, last LSN: 58:451:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\manager_ors\TestManager_main_ors_6dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:55:41.00 spid61 AppDomain 4 (TestManager_main_ors.dbo[runtime].3) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
2006-12-06 10:55:41.01 spid61 AppDomain 4 (TestManager_main_ors.dbo[runtime].3) unloaded.
2006-12-06 10:56:31.45 Backup Database backed up. Database: TestRelease2_db_ors, creation date(time): 2006/12/03(15:23:17), pages dumped: 163, first LSN: 27:180:37, last LSN: 27:196:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\Test_release\TestRelease2_db_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:57:21.93 Backup Database backed up. Database: TestRelease2_main_ors, creation date(time): 2006/12/03(15:21:58), pages dumped: 757, first LSN: 58:197:37, last LSN: 58:213:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\Test_release\TestRelease2_main_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:58:57.00 Backup Database backed up. Database: TestDatabase_db_ors, creation date(time): 2006/11/22(12:40:53), pages dumped: 1153, first LSN: 77:400:37, last LSN: 77:416:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\TestDatabase\TestDatabase_db_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 10:59:36.76 Backup Database backed up. Database: TestDatabase_main_ors, creation date(time): 2006/11/22(12:39:36), pages dumped: 688, first LSN: 79:621:121, last LSN: 79:670:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\TestDatabase\TestDatabase_main_ors_6Dec_a.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:00:28.09 Backup Database backed up. Database: FirstPhaseRel_db_ORS, creation date(time): 2006/11/16(10:08:57), pages dumped: 6941, first LSN: 169:2259:37, last LSN: 169:2275:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\FirstPhaseRel_db_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:01:15.64 Backup Database backed up. Database: FirstPhaseRel_Main_ORS, creation date(time): 2006/11/16(10:08:25), pages dumped: 3248, first LSN: 1355:423:64, last LSN: 1355:449:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\FirstPhaseRel_main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:01:44.70 spid55 Setting database option SINGLE_USER to ON for database FirstPhaseRel_Main_ORS.
2006-12-06 11:02:28.60 Backup Database backed up. Database: dummy_test_main, creation date(time): 2006/11/26(19:52:44), pages dumped: 387, first LSN: 42:155:37, last LSN: 42:171:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\Others\dummy_test_main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:03:11.62 Backup Database backed up. Database: manager_db_ors, creation date(time): 2006/12/05(17:15:37), pages dumped: 163, first LSN: 27:260:43, last LSN: 27:278:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\manager_ors\manager_db_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:03:45.84 Backup Database backed up. Database: manager_main_ors, creation date(time): 2006/12/05(17:15:00), pages dumped: 451, first LSN: 43:134:145, last LSN: 43:194:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\manager_ors\manager_main_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:03:50.03 spid74 AppDomain 9 (manager_main_ors.dbo[runtime].8) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
2006-12-06 11:03:50.03 spid74 AppDomain 9 (manager_main_ors.dbo[runtime].8) unloaded.
2006-12-06 11:04:21.70 Backup Database backed up. Database: manager2_db_ors, creation date(time): 2006/12/03(12:48:54), pages dumped: 187, first LSN: 32:19:66, last LSN: 32:47:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\manager2_ors\manager2_db_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:04:59.60 Backup Database backed up. Database: manager2_main_ors, creation date(time): 2006/12/03(12:48:30), pages dumped: 621, first LSN: 57:241:257, last LSN: 57:345:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\manager2_ors\manger2_main_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:05:34.15 Backup Database backed up. Database: nabin_db_ors, creation date(time): 2006/11/02(11:19:26), pages dumped: 558, first LSN: 48:836:37, last LSN: 48:852:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\Others\nabin_db_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:06:05.90 Backup Database backed up. Database: nabin_main_ors, creation date(time): 2006/11/02(11:18:50), pages dumped: 519, first LSN: 59:523:37, last LSN: 59:539:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\nabin_main_ors_6Dec.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:07:27.68 Backup Database backed up. Database: preset_db_ors, creation date(time): 2006/11/02(13:36:10), pages dumped: 744, first LSN: 64:413:37, last LSN: 64:429:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\preset_db_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:08:17.50 Backup Database backed up. Database: preset_main_ors, creation date(time): 2006/11/02(13:35:15), pages dumped: 396, first LSN: 41:458:37, last LSN: 41:474:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\preset_main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:09:07.68 Backup Database backed up. Database: test_db_ors, creation date(time): 2006/12/05(17:25:35), pages dumped: 634, first LSN: 82:174:257, last LSN: 82:280:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\test_db_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:09:38.21 Backup Database backed up. Database: test_main_ors, creation date(time): 2006/12/05(17:24:45), pages dumped: 684, first LSN: 57:16:143, last LSN: 57:76:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\test_main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:10:06.07 spid55 Setting database option SINGLE_USER to ON for database test_main_ors.
2006-12-06 11:10:06.21 spid55 AppDomain 7 (test_main_ors.dbo[runtime].6) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
2006-12-06 11:10:06.21 spid55 AppDomain 7 (test_main_ors.dbo[runtime].6) unloaded.
2006-12-06 11:10:31.59 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:10:31.59 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.62]
2006-12-06 11:10:47.98 Backup Database backed up. Database: AnilMaharjan_db_ors, creation date(time): 2006/11/30(13:48:59), pages dumped: 645, first LSN: 49:58:46, last LSN: 49:77:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\AnilMaharjan_db_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:11:17.00 Backup Database backed up. Database: AnilMaharjan_main_ors, creation date(time): 2006/11/30(13:48:18), pages dumped: 675, first LSN: 106:120:195, last LSN: 106:197:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\AnilMaharjan_main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:11:53.31 Backup Database backed up. Database: Authentication_db_ors, creation date(time): 2006/11/10(12:01:30), pages dumped: 1743, first LSN: 530:48658:37, last LSN: 530:48674:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\Authentication_db_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:12:07.64 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:12:07.64 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.62]
2006-12-06 11:12:11.92 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:12:11.92 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.62]
2006-12-06 11:12:18.17 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:12:18.17 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.62]
2006-12-06 11:12:30.64 Backup Database backed up. Database: authentication_main_ors, creation date(time): 2006/11/10(12:10:54), pages dumped: 925, first LSN: 178:27216:37, last LSN: 178:27232:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\Authentication_main_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:13:03.25 Backup Database backed up. Database: anil_ors, creation date(time): 2006/11/28(15:16:33), pages dumped: 3093, first LSN: 106:76:37, last LSN: 106:92:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\December_backup\other\anil_ors.bak'}). This is an informational message only. No user action is required.
2006-12-06 11:14:31.17 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:14:31.17 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.15]
2006-12-06 11:14:45.34 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:14:45.34 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.15]
2006-12-06 11:15:20.57 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:15:20.57 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.15]
2006-12-06 11:16:24.25 spid56 Starting up database 'Developer_main_ors'.
2006-12-06 11:16:24.25 spid56 The database 'Developer_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:16:24.43 spid56 Starting up database 'Developer_main_ors'.
2006-12-06 11:16:24.68 Backup Database was restored: Database: Developer_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\main_ors.bak'}). Informational message. No user action required.
2006-12-06 11:17:10.71 spid62 Starting up database 'Developer_db_ors'.
2006-12-06 11:17:10.73 spid62 The database 'Developer_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:17:10.92 spid62 Starting up database 'Developer_db_ors'.
2006-12-06 11:17:11.18 Backup Database was restored: Database: Developer_db_ors, creation date(time): 2006/12/05(16:41:27), first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\db_ors.bak'}). Informational message. No user action required.
2006-12-06 11:17:44.68 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:17:44.68 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.15]
2006-12-06 11:18:00.95 spid62 Starting up database 'manager_db_ors'.
2006-12-06 11:18:00.96 spid62 The database 'manager_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:18:01.12 spid62 Starting up database 'manager_db_ors'.
2006-12-06 11:18:01.37 Backup Database was restored: Database: manager_db_ors, creation date(time): 2006/12/05(16:41:27), first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\db_ors.bak'}). Informational message. No user action required.
2006-12-06 11:19:08.06 spid62 Starting up database 'manager_main_ors'.
2006-12-06 11:19:08.07 spid62 The database 'manager_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:19:08.25 spid62 Starting up database 'manager_main_ors'.
2006-12-06 11:19:08.51 Backup Database was restored: Database: manager_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\main_ors.bak'}). Informational message. No user action required.
2006-12-06 11:20:01.64 spid69 Starting up database 'TestPacakge_main_ors'.
2006-12-06 11:20:01.65 spid69 The database 'TestPacakge_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:20:01.81 spid69 Starting up database 'TestPacakge_main_ors'.
2006-12-06 11:20:02.06 Backup Database was restored: Database: TestPacakge_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\main_ors.bak'}). Informational message. No user action required.
2006-12-06 11:20:24.18 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:20:24.18 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.197]
2006-12-06 11:20:27.89 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:20:27.89 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.197]
2006-12-06 11:20:52.78 spid69 Starting up database 'TestPackage_db_ors'.
2006-12-06 11:20:52.78 spid69 The database 'TestPackage_db_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:20:52.95 spid69 Starting up database 'TestPackage_db_ors'.
2006-12-06 11:20:53.20 Backup Database was restored: Database: TestPackage_db_ors, creation date(time): 2006/12/05(16:41:27), first LSN: 27:226:43, last LSN: 27:244:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\db_ors.bak'}). Informational message. No user action required.
2006-12-06 11:23:51.20 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:23:51.20 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.14]
2006-12-06 11:24:21.98 spid70 Starting up database 'TestPackage_main_ors'.
2006-12-06 11:24:22.00 spid70 The database 'TestPackage_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 11:24:22.17 spid70 Starting up database 'TestPackage_main_ors'.
2006-12-06 11:24:22.51 Backup Database was restored: Database: TestPackage_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\main_ors.bak'}). Informational message. No user action required.
2006-12-06 11:24:25.70 spid71 Setting database option TRUSTWORTHY to ON for database TestPackage_main_ors.
2006-12-06 11:24:41.50 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 11:24:41.50 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 11:24:43.82 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 11:24:43.82 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 11:25:01.21 spid62 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:01.23 spid62 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:01.24 spid62 Setting database option TRUSTWORTHY to ON for database TestPackage_main_ors.
2006-12-06 11:25:07.06 spid62 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:07.07 spid62 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:07.10 spid62 Setting database option TRUSTWORTHY to ON for database TestPackage_main_ors.
2006-12-06 11:25:08.42 spid62 AppDomain 12 (TestPackage_main_ors.dbo[runtime].11) created.
2006-12-06 11:25:23.12 spid71 Setting database option TRUSTWORTHY to ON for database Developer_main_ors.
2006-12-06 11:25:32.68 spid62 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:32.70 spid62 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:32.73 spid62 Setting database option TRUSTWORTHY to ON for database Developer_main_ors.
2006-12-06 11:25:34.10 spid62 AppDomain 15 (Developer_main_ors.dbo[runtime].14) created.
2006-12-06 11:25:48.85 spid71 Setting database option TRUSTWORTHY to ON for database manager_main_ors.
2006-12-06 11:25:55.35 spid62 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:55.37 spid62 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 11:25:55.40 spid62 Setting database option TRUSTWORTHY to ON for database manager_main_ors.
2006-12-06 11:25:56.73 spid62 AppDomain 18 (manager_main_ors.dbo[runtime].17) created.
2006-12-06 11:34:52.76 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 11:34:52.76 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-06 12:07:27.14 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:07:27.14 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-06 12:09:55.96 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:09:55.96 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.110]
2006-12-06 12:10:25.85 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:10:25.85 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.110]
2006-12-06 12:10:39.03 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:10:39.03 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-06 12:11:04.60 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:11:04.60 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.110]
2006-12-06 12:15:32.23 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:15:32.23 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.110]
2006-12-06 12:15:44.00 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:15:44.00 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.110]
2006-12-06 12:16:06.04 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:16:06.04 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.110]
2006-12-06 12:27:53.98 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:27:53.98 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-06 12:30:35.87 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:30:35.87 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.67]
2006-12-06 12:35:29.93 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:35:29.93 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-06 12:35:37.73 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 12:35:37.73 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-06 12:50:59.93 spid65 Starting up database 'sandeep_main_ors'.
2006-12-06 12:51:00.35 spid65 Setting database option ANSI_NULL_DEFAULT to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.37 spid65 Setting database option ANSI_NULLS to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.37 spid65 Setting database option ANSI_PADDING to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.37 spid65 Setting database option ANSI_WARNINGS to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.39 spid65 Setting database option ARITHABORT to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.39 spid65 Setting database option AUTO_CLOSE to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.39 spid65 Setting database option AUTO_CREATE_STATISTICS to ON for database sandeep_main_ors.
2006-12-06 12:51:00.40 spid65 Setting database option AUTO_SHRINK to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.40 spid65 Setting database option AUTO_UPDATE_STATISTICS to ON for database sandeep_main_ors.
2006-12-06 12:51:00.42 spid65 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.42 spid65 Setting database option CURSOR_DEFAULT to GLOBAL for database sandeep_main_ors.
2006-12-06 12:51:00.42 spid65 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.43 spid65 Setting database option NUMERIC_ROUNDABORT to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.43 spid65 Setting database option QUOTED_IDENTIFIER to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.45 spid65 Setting database option RECURSIVE_TRIGGERS to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.45 spid65 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.45 spid65 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database sandeep_main_ors.
2006-12-06 12:51:00.46 spid65 Setting database option PARAMETERIZATION to SIMPLE for database sandeep_main_ors.
2006-12-06 12:51:00.46 spid65 Setting database option READ_WRITE to ON for database sandeep_main_ors.
2006-12-06 12:51:00.46 spid65 Setting database option RECOVERY to FULL for database sandeep_main_ors.
2006-12-06 12:51:00.48 spid65 Setting database option MULTI_USER to ON for database sandeep_main_ors.
2006-12-06 12:51:00.48 spid65 Setting database option PAGE_VERIFY to CHECKSUM for database sandeep_main_ors.
2006-12-06 12:51:37.03 spid62 Starting up database 'sandeep_db_ors'.
2006-12-06 12:51:37.37 spid62 Setting database option ANSI_NULL_DEFAULT to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.39 spid62 Setting database option ANSI_NULLS to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.39 spid62 Setting database option ANSI_PADDING to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.40 spid62 Setting database option ANSI_WARNINGS to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.40 spid62 Setting database option ARITHABORT to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.40 spid62 Setting database option AUTO_CLOSE to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.42 spid62 Setting database option AUTO_CREATE_STATISTICS to ON for database sandeep_db_ors.
2006-12-06 12:51:37.42 spid62 Setting database option AUTO_SHRINK to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.42 spid62 Setting database option AUTO_UPDATE_STATISTICS to ON for database sandeep_db_ors.
2006-12-06 12:51:37.43 spid62 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.45 spid62 Setting database option CURSOR_DEFAULT to GLOBAL for database sandeep_db_ors.
2006-12-06 12:51:37.45 spid62 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.46 spid62 Setting database option NUMERIC_ROUNDABORT to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.46 spid62 Setting database option QUOTED_IDENTIFIER to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.48 spid62 Setting database option RECURSIVE_TRIGGERS to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.48 spid62 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.48 spid62 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database sandeep_db_ors.
2006-12-06 12:51:37.50 spid62 Setting database option PARAMETERIZATION to SIMPLE for database sandeep_db_ors.
2006-12-06 12:51:37.50 spid62 Setting database option READ_WRITE to ON for database sandeep_db_ors.
2006-12-06 12:51:37.50 spid62 Setting database option RECOVERY to FULL for database sandeep_db_ors.
2006-12-06 12:51:37.51 spid62 Setting database option MULTI_USER to ON for database sandeep_db_ors.
2006-12-06 12:51:37.51 spid62 Setting database option PAGE_VERIFY to CHECKSUM for database sandeep_db_ors.
2006-12-06 12:54:02.78 spid80 Starting up database 'sandeep_main_ors'.
2006-12-06 12:54:02.79 spid80 The database 'sandeep_main_ors' is marked RESTORING and is in a state that does not allow recovery to be run.
2006-12-06 12:54:02.95 spid80 Starting up database 'sandeep_main_ors'.
2006-12-06 12:54:03.20 Backup Database was restored: Database: sandeep_main_ors, creation date(time): 2006/12/05(16:40:38), first LSN: 42:17:132, last LSN: 42:71:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'G:\Developer\main_ors.bak'}). Informational message. No user action required.
2006-12-06 13:07:47.73 spid83 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 13:07:47.75 spid83 Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
2006-12-06 13:07:47.78 spid83 Setting database option TRUSTWORTHY to ON for database sandeep_main_ors.
2006-12-06 13:08:04.15 spid83 AppDomain 20 (sandeep_main_ors.dbo[runtime].19) created.
2006-12-06 14:02:50.26 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 14:02:50.26 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 14:13:09.00 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 14:13:09.00 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 14:51:53.46 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 14:51:53.46 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-06 14:58:41.82 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 14:58:41.82 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.60]
2006-12-06 14:59:12.12 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 14:59:12.12 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.60]
2006-12-06 15:17:30.21 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 15:17:30.21 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.196]
2006-12-06 15:17:35.18 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 15:17:35.18 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.196]
2006-12-06 16:40:24.04 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 16:40:24.04 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-06 16:42:38.32 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 16:42:38.32 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-06 16:43:33.03 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 16:43:33.03 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-06 16:43:37.62 Logon Error: 18456, Severity: 14, State: 16.
2006-12-06 16:43:37.62 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.27]
2006-12-06 16:57:47.07 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 16:57:47.07 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.47]
2006-12-06 17:51:01.35 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 17:51:01.35 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.83]
2006-12-06 17:51:02.15 Logon Error: 18456, Severity: 14, State: 8.
2006-12-06 17:51:02.15 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.83]
2006-12-07 00:00:15.51 spid14s This instance of SQL Server has been using a process ID of 1796 since 12/4/2006 7:06:55 PM (local) 12/4/2006 1:21:55 PM (UTC). This is an informational message only; no user action is required.
2006-12-07 09:58:06.54 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 09:58:06.54 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.83]
2006-12-07 09:58:41.07 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 09:58:41.07 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.83]
2006-12-07 09:58:41.51 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 09:58:41.51 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.83]
2006-12-07 10:32:16.18 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 10:32:16.18 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.75]
2006-12-07 10:32:22.45 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 10:32:22.45 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.75]
2006-12-07 11:54:48.85 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 11:54:48.85 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-07 11:57:54.81 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 11:57:54.81 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-07 11:58:00.68 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 11:58:00.68 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-07 11:58:08.60 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 11:58:08.60 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-07 11:58:15.50 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 11:58:15.50 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-07 11:58:50.46 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 11:58:50.46 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-07 11:59:05.04 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 11:59:05.04 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.204]
2006-12-07 12:14:21.84 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 12:14:21.84 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.47]
2006-12-07 15:12:46.01 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 15:12:46.01 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-07 15:25:29.56 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 15:25:29.56 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-07 15:31:30.20 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 15:31:30.20 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-07 15:38:06.14 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 15:38:06.14 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.21]
2006-12-07 15:38:12.56 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 15:38:12.56 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.21]
2006-12-07 15:38:22.26 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 15:38:22.26 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.21]
2006-12-07 16:00:18.76 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 16:00:18.76 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.45]
2006-12-07 16:34:24.46 Logon Error: 18456, Severity: 14, State: 16.
2006-12-07 16:34:24.46 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.45]
2006-12-07 17:40:38.29 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 17:40:38.29 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.127]
2006-12-07 17:40:42.07 Logon Error: 18456, Severity: 14, State: 8.
2006-12-07 17:40:42.07 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.127]
2006-12-07 17:47:36.48 Backup Database backed up. Database: Developer_main_ors, creation date(time): 2006/12/06(11:16:23), pages dumped: 914, first LSN: 98:169:185, last LSN: 98:246:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\developer_main_ors'}). This is an informational message only. No user action is required.
2006-12-07 17:48:06.31 Backup Database backed up. Database: Developer_db_ors, creation date(time): 2006/12/06(11:17:10), pages dumped: 1296, first LSN: 65:58:203, last LSN: 65:141:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'F:\db_Backup\developer_db_ors'}). This is an informational message only. No user action is required.
2006-12-08 00:01:00.53 spid19s This instance of SQL Server has been using a process ID of 1796 since 12/4/2006 7:06:55 PM (local) 12/4/2006 1:21:55 PM (UTC). This is an informational message only; no user action is required.
2006-12-08 12:17:05.62 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:17:05.62 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.25]
2006-12-08 12:55:30.68 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:55:30.68 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:35.75 Logon Error: 18456, Severity: 14, State: 16.
2006-12-08 12:55:35.75 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:39.87 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:55:39.87 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:41.32 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:55:41.32 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:42.45 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:55:42.45 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:44.17 Logon Error: 18456, Severity: 14, State: 16.
2006-12-08 12:55:44.17 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:45.87 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:55:45.87 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 12:55:47.78 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 12:55:47.78 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.42]
2006-12-08 13:28:12.48 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 13:28:12.48 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.74]
2006-12-08 13:28:21.79 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 13:28:21.79 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.74]
2006-12-08 13:41:52.76 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 13:41:52.76 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.48]
2006-12-08 13:41:53.29 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 13:41:53.29 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.48]
2006-12-08 13:45:54.65 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 13:45:54.65 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.48]
2006-12-08 13:45:54.84 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 13:45:54.84 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.48]
2006-12-08 14:07:08.84 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 14:07:08.84 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.45]
2006-12-08 14:07:24.51 Logon Error: 18456, Severity: 14, State: 8.
2006-12-08 14:07:24.51 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.45]
2006-12-08 16:35:19.75 Logon Error: 18456, Severity: 14, State: 16.
2006-12-08 16:35:19.75 Logon Login failed for user 'sa'. [CLIENT: 100.100.100.30]
2006-12-09 00:00:40.54 spid20s This instance of SQL Server has been using a process ID of 1796 since 12/4/2006 7:06:55 PM (local) 12/4/2006 1:21:55 PM (UTC). This is an informational message only; no user action is required.

|||

I didnot understand what do you mean by "which service account?"

Please be more specific.....

|||

Hi Ritesh,

It means the User Account which is used to start SQL Server Services cause the error .

Have you change the Password in recent history?! which account you used to start SQL Service Account ?

Hemantgiri S. Goswami

|||

No, I havenot changed the password....

I was using "sa" as dba account and everybody in our office are using this account (for we all are developer working in C# with SQL Server as backend). But no one uses sql server directly except me. They use this account for the sole purpose of connection with C# only.

|||
Hi,

beside that one mentioned time the service did not come up properly, your problem seems to be the failed Login attempts. The logging in the event log is based on the setting in the server properties of your server. You enabled the server to write failed login attempts to the event log, therefore these entries are generated. I would examine the sources of these logins attempts. Seems that someone is trying to logon with the wrong password for the sa. If this is a application of yours you should change the user account which accesses the Sql Server, as using the "sa" account is a bad practise. The failed login attempts can also be a sign of an intruder, trying to get in your system. That it is likely because the sa account exists on every SQL Server and present a good hacking approach as the hacker does not have to guess the username anymore.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

My company deals with many IT solutions like Selling branded computer (DELL), marketing softwares as distributor (ORACLE, SOLARIS, ARC INFO), works as ISP and also sales its own tailored made and ready made softwares (for TELECOMMUNICATION centers, Govn. Org. etc.). But server I was mentioning is solely for our software development section and data in this server is not so important. On the other hand, I have to give admin password to few of other team members (MAIN SYS ADMIN of our company, our Project Manager etc). I have no other alternative for this right now. I don't think these few people will change password without my permission. As an alternate, I have built another server recently in which only I know "sa" password.

But I need to recover this first server. So can you guys help me out? I am running on deadlines.

|||

Hi Ritesh,

the error message are for Failed Authentication, backup schedule,options configured , i suggest to configure Event Viewer for only Warning & Failed Event only.

Try your SQL Server Service / Agent's startup account by setting SystemAccount instead of Domain account if it works i don't think Domain Account failed to start , one more thing i would like to draw your attention go to the dependancy tab and see if any dependancy service fails to start!!!!

I would suggest to refer http://support.microsoft.com/kb/282254 & http://support.microsoft.com/kb/259733 for more.

HTH

Hemantgiri S. Goswami

|||

You'd better look the security log in the event viewer and choose to log only errors (not warnings or information)

this way the failed security audits will show which account uses the wrong password

You also don't need to give sa to everyone, either give sql rights to domain users so they can login via windows accounts to your sql server or create an sql account per group/person inside the sql server

Each user should get the exact info they need

|||

Ritesh -

I do not know if you have yet solved this, so I'll post a bit more on a possible solution I saw at the bottom of the thread... it sounds like maybe you or someone inadvertently changed a setting for what account starts the SQL server.

If you can access EM, you can check something and perhaps fix this.

Right click the server instance you are having problems with - for instance (local) (Windows NT).

Select Properties from the pull down menu. When the properties sheet is displayed, select the security tab.

At the bottom, check the setting for security account and make sure it is a valid login. One way to really cause yourself problems down the road is to NOT select the system account, instead select the 'this account' radio button, and then some time later that user either changes their password, or worse, they leave the company and the user account is deleted.

I usually either set up SQL boxes to use the system account or, worst case, this account = .\Administrator.

It sure looks like this might be the root of the problem... the only other thing I could think of would be if someone actually changed the sa password. The Error number should help you select which of these is the more probably cause of your particular problem, but those are the places I'd start.

(If somone changed sa, or this property setting, I'd say you have a security hole that needs plugged...)

Regards.

randyvol

|||

Hi randyvol,

First of all, thank you for giving your time to think about my problem. I think you are writting about SQL Server 2000. I have SQL Server 2005, so I donot have Enterprise manager tool.

I have installed another instance of Sql server (and given it a name - SECCOPY) and also recovered databases (which my co-worker 'developers' use). But I need to know solution of this problem so that I could be ready for future disaster.

So if you can, plz give me the solution for SQL Server 2005.

WIth regards

Ritesh

|||Hi Ritesh,

I think the problem is with your "sa" password. Since the password is mismatched, thats why the login fails. Second thing is that "sa" doesnt have access to some of the databases in that server.
So make sure the password for "sa" is correct.|||

Ritesh -

Sorry, I've been out of the office and did not see your post till now. Since so much time has expired, I assume you have solved the problem?

If not, email me ... jvolters@.sc.rr.com and let's see what's what in your 2K5 setup. that particular message pops up for a lot of reasons - I've seen it about 6 times during installs for various reasons. I still think it is permissions problems, just need to know where. If you do decide to email me, please send info on what you've done so far in config'ing the system - including how you set up aliases in SQL server config mgr, client protocols enabled, as well as how you set things up in the Surface Area Config Mgr.

Sorry for the delay... surely this must be fixed by now, but I thought I'd offer anyway.

randyvol

Thursday, March 29, 2012

Error loading metadata....PLZZ HELP!!

error installing standard edition on a windows 2003 server

3.10 Installing SQL Server Express on a Windows Domain Controller

error installing standard edition on a windows 2003 server

3.10 Installing SQL Server Express on a Windows Domain Controller

Monday, March 26, 2012

Error Installing Service Pack 1

Thursday, March 22, 2012

error in web service reporting

Error in the login process when establishing connection

Error in the login process when establishing connection

Wednesday, March 21, 2012

ERROR IN SQL SERVER ENGINE

error handling flow

Blog Archive

About Me