Showing posts with label message. Show all posts
Showing posts with label message. Show all posts

Tuesday, March 27, 2012

Excel Exporting results in MIME message

I reviewed all post but have not seen the problem I have.
When exporting a report to Excel (regardless if I save or open the file) my
output is a multi-part MIME message. I get only one worksheet (there are 4
pages in the report) and it has the name of the exported report.
There is a section for each page in this message and a StyleSheet section.
Did I miss something in the report Services set-up?
Thanks
ShawnI took a better look at the rest of the posts and did find some with the same
problem. One of them suggested installation of SP1 in MS Office 2000. My
problem now is that I did install SP1 and nothing changed. If anyone has
another suggestion it will be greatly appreciated.
Thanks
Shawn
"Shawn Kralj" wrote:
> I reviewed all post but have not seen the problem I have.
> When exporting a report to Excel (regardless if I save or open the file) my
> output is a multi-part MIME message. I get only one worksheet (there are 4
> pages in the report) and it has the name of the exported report.
> There is a section for each page in this message and a StyleSheet section.
> Did I miss something in the report Services set-up?
> Thanks
> Shawn|||Close, it is not SP1. It is SP1 for Reporting Services that has the fix. SP1
no longer uses the MIME format.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Shawn Kralj" <ShawnKralj@.discussions.microsoft.com> wrote in message
news:FE6555D6-71F4-4C29-90F4-DA92604B4816@.microsoft.com...
> I took a better look at the rest of the posts and did find some with the
same
> problem. One of them suggested installation of SP1 in MS Office 2000. My
> problem now is that I did install SP1 and nothing changed. If anyone has
> another suggestion it will be greatly appreciated.
> Thanks
> Shawn
> "Shawn Kralj" wrote:
> > I reviewed all post but have not seen the problem I have.
> >
> > When exporting a report to Excel (regardless if I save or open the file)
my
> > output is a multi-part MIME message. I get only one worksheet (there are
4
> > pages in the report) and it has the name of the exported report.
> >
> > There is a section for each page in this message and a StyleSheet
section.
> >
> > Did I miss something in the report Services set-up?
> >
> > Thanks
> >
> > Shawn|||Thanks Bruce. That worked. Installing SP1 for Reporting Services fixed the
problem.
Looks great.
Shawn
"Bruce L-C [MVP]" wrote:
> Close, it is not SP1. It is SP1 for Reporting Services that has the fix. SP1
> no longer uses the MIME format.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Shawn Kralj" <ShawnKralj@.discussions.microsoft.com> wrote in message
> news:FE6555D6-71F4-4C29-90F4-DA92604B4816@.microsoft.com...
> > I took a better look at the rest of the posts and did find some with the
> same
> > problem. One of them suggested installation of SP1 in MS Office 2000. My
> > problem now is that I did install SP1 and nothing changed. If anyone has
> > another suggestion it will be greatly appreciated.
> >
> > Thanks
> >
> > Shawn
> >
> > "Shawn Kralj" wrote:
> >
> > > I reviewed all post but have not seen the problem I have.
> > >
> > > When exporting a report to Excel (regardless if I save or open the file)
> my
> > > output is a multi-part MIME message. I get only one worksheet (there are
> 4
> > > pages in the report) and it has the name of the exported report.
> > >
> > > There is a section for each page in this message and a StyleSheet
> section.
> > >
> > > Did I miss something in the report Services set-up?
> > >
> > > Thanks
> > >
> > > Shawn
>
>

Friday, March 23, 2012

Excel Data Mining Add-In Query Wizard Error Message

Hello Experts,

I have an error message I was wondering if anyone else has seen and resolved. When I open excel and click on the query wizard on the Data Mining Ribbon, I get an error message that says "Input String not in Correct Format"

After I close this dialog box the 'Welcome to Query .... ' wizard will open, but when I select the Advance button my process aborts due to the input string error.

I have only ran association models on the computer.

The Manage Models and Browse buttons work fine.

The error came up on Friday, but it wasn't there on Thursday. There were no changes done to the machine (no installation of new software).

I have tried reinstalling the add-in.

Thank you all for your help,

Davy

I have pasted the SQL syntax below that I get from the error dialog box after the query wizard closes.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.DataMining.Office.Excel.QueryBuilder.QueryBuilderParameters.UpdateNestedColumnName()
at Microsoft.SqlServer.DataMining.Office.Excel.XLClientUIManager.DisplayAdvancedQueryBuilder(Object sender, WizardPageEventArgs e)
at Microsoft.SqlServer.DataMining.Office.Excel.Wizard.WizardPageBase.OnWizardPageAdvanced(WizardPageEventArgs e)
at Microsoft.SqlServer.DataMining.Office.Excel.Wizard.WizardForm.btnAdvanced_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.DataMining.Office.Excel.DMClient
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3154.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataMining.Office.Excel.DMClient/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataMining.Office.Excel.DMClient.dll
-
Extensibility
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase: file:///C:/WINDOWS/assembly/GAC/Extensibility/7.0.3300.0__b03f5f7f11d50a3a/Extensibility.dll
-
office
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1014
CodeBase: file:///C:/WINDOWS/assembly/GAC/office/12.0.0.0__71e9bce111e9429c/office.dll
-
Microsoft.SqlServer.DataMining.Office.Common
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3154.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataMining.Office.Common/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataMining.Office.Common.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.DataMining.Office.Excel.DMClientControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3154.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataMining.Office.Excel.DMClientControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataMining.Office.Excel.DMClientControls.dll
-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
-
zd8aixcw
Assembly Version: 9.0.242.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
stdole
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase: file:///C:/WINDOWS/assembly/GAC/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
-
Microsoft.Office.Interop.Excel
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1014
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.Office.Interop.Excel/12.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Excel.dll
-
Microsoft.SqlServer.DataMining.Office.Excel.TableAnalytics
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3154.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataMining.Office.Excel.TableAnalytics/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataMining.Office.Excel.TableAnalytics.dll
-
Microsoft.SqlServer.DataMining.Office.Excel.Wizard
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3154.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataMining.Office.Excel.Wizard/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataMining.Office.Excel.Wizard.dll
-
Microsoft.AnalysisServices.AdomdClient
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices.AdomdClient/9.0.242.0__89845dcd8080cc91/Microsoft.AnalysisServices.AdomdClient.dll
-
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
-
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
-
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
-
Microsoft.DataWarehouse.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.DataWarehouse.Interfaces/9.0.242.0__89845dcd8080cc91/Microsoft.DataWarehouse.Interfaces.dll
-
Microsoft.AnalysisServices.Viewers
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server%202005%20DM%20Add-Ins/Microsoft.AnalysisServices.Viewers.dll
-
Microsoft.DataWarehouse
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server%202005%20DM%20Add-Ins/Microsoft.DataWarehouse.DLL
-
Microsoft.AnalysisServices.Graphing
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server%202005%20DM%20Add-Ins/Microsoft.AnalysisServices.Graphing.DLL
-
Microsoft.AnalysisServices.Controls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server%202005%20DM%20Add-Ins/Microsoft.AnalysisServices.Controls.DLL
-
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.2047.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
-
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll
-
Microsoft.AnalysisServices.OleDbDM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server%202005%20DM%20Add-Ins/Microsoft.AnalysisServices.OleDbDM.DLL
-
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
-

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Can you try creating another non-association model (e.g. classification) and see if this problem goes away? It won't solve the real problem, but it will give us more insight.

Thanks

-Jamie

|||

Hello, Davy

You said:"I have pasted the SQL syntax below that I get from the error dialog box after the query wizard closes.", but I cannot see the SQL statement in the post. Sorry if I just missed it, do you mind posting it again?

On another note:

- is there any model visible in your current connection?

- what kind of model is selected by default when launching the query editor?

|||

Sorry about the confusion, but there is no SQL syntax...only what i pasted above.

I tried creating a model with another algorithm, but that does not change anything.

There are models visible with the current connection.

The model selected by default depends on which model i clicked on last in the manage wizard.

I believe this problem stems from the .Net Framework since the error dialog says:

Microsoft .NET Framework

Unhandled exception has occurred in a component in you application. If you click Continue, the applicaiton will ignore this error and attempt to continue.

Object reference not set to an instance of an object.

Details Continue

I currently have .NET 2.0 and .NET 1.1 installed on the computer. According to Add/Remove Program in the Control Panel, the last time .NET 2.0 was used was sometime last year. The Add/Remove Program has an option to repair .NET 2.0 . Should I use this?

Excel automation

Hi,

I tried to add column headers and delete all rows to excel database
which is a linked server to my sql server db.

I got an error message, "delete data through linked server is not
supported by Isam".

I tried to use FSO to write to the excel file, but seems like FSO
support write to only text file.

the last time I tried to create an excel applicaiton object and temper
with its cell, I hang my Excel application and had to reinstall it.

Have any ideas,

Thank you very much"dlakme" <dthuyuyen@.yahoo.com> wrote in message
news:7bdc161c.0408030437.3ce04385@.posting.google.c om...
> Hi,
> I tried to add column headers and delete all rows to excel database
> which is a linked server to my sql server db.
> I got an error message, "delete data through linked server is not
> supported by Isam".
> I tried to use FSO to write to the excel file, but seems like FSO
> support write to only text file.
> the last time I tried to create an excel applicaiton object and temper
> with its cell, I hang my Excel application and had to reinstall it.
> Have any ideas,
> Thank you very much

I have no idea about your specific error, but it may be easier to use a
client-side tool to pull the data from MSSQL, then use the Excel COM
interface to put that into Excel as you want.

Simonsql

Friday, March 9, 2012

ex.Message in debug mode is much shorter

Exception ex.Message I am getting in debug mode calling AcquireConnection is much shorter than the logged message in run time because all the errors come to output window in debug. Is there any way to get all these errors description from exception object in debug time to be able to parse it?

Thanks.

What you are saying does not make sense. The exception details will always bee the same debug or otherwise. The exception will only have one message, but you suggest there should be more. You could check the InnerException property of the caught exception, that may give something. I really do not understand how you are describing the two modes, with all errors or otherwise.

Is this perhaps to do with a UI? If so try the IErrorCollectionService interface. This allows you to get details of the fire error, warning methods called from the IDTSComponentMetaData90.

|||

Thanks for your reply and sorry for not making this question clear.
Will try to explain what actually I am actually looking for.

Below the simplified piece of my code in script task
Try
connection = connMgr.AcquireConnection(Nothing)
Catch ex As Exception
'Dts.Events.FireError(1, ex.TargetSite.ToString, ex.Message, "", 0)
MsgBox(ex.Message)
Dts.TaskResult = Dts.Results.Failure
End Try

Deliberately providing wrong psw for the connection and running the package in debug (F5)
In the msgbox reading the message "Exception from HRESULT: 0xC0202009".

Running the same package in "Start Without Debugging" (ctrl+F5), getting the more informative msgbox:


Error: 0xC0202009 at EnvConfig, Connection manager "DB_SOURCE": An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'DTSUSE'.".

The message looks like as a collection that what I am actually looking for to get access to. I need to extract only latest description like "Login failed for user 'DTSUSE'" and log it.

Thanks, Vadim.

|||

Ok, now I see. This is not a SSIS issue, rather a .Net programming issue, in so much as it is actually bad practice to just catch the general Exception type. It is also very common, we all do it! Really you should catch targeted exceptions as they are richer classes that have more information relevant to the exception thrown.

If you catch the SqlException type you can get access to the Errors collection, that is a property on the SqlException class. That will give you that extra level of detail, both for the messages and things like the source.

Evt ID: 17055 : Flush Failure on Backup device

I'm currently having an issue with getting consistant backup:
I'm getting the follow error message:
18210:
BackupVirtualDeviceFile:RequestDurableMedia:Flush failure on backup device
"DBASQL70TID1800VD0". Operating system error 995 (The I/0 operation has been
aborted because of either a thread exit or an application request.
Any Ideas'
Thanks
DaleHi,
Do u have enough space on ur disk.
Hope this help
from
Killer|||Hi,
Yes, we have plentiy of space...
Thanks,
"doller" wrote:
> Hi,
> Do u have enough space on ur disk.
> Hope this help
> from
> Killer
>

Everything that will cause a queue to shut down

I have a queue that, after running fine for several days will mysteriously turn off. It doesn't seem to be related to a poison message because I can restart the queue and processing resumes just fine. What are all the scenarios that would cause a queue to turn itself off, so I can 1) take preemptive action to prevent it from happening in the first place and 2) respond appropriately when it occurs.

Also, how to properly setup and verify that the BROKER_QUEUE_DISABLED is working properly. This is the SQL that I have so far, but is there a more direct way to raise the event other than writing an activated stored procedure that rolls back 5 times?

CREATE QUEUE [EventNotificationsQueue];

GO

CREATE SERVICE [EventNotificationsService]

ON QUEUE [EventNotificationsQueue]

([http://schemas.microsoft.com/SQL/Notifications/PostEventNotification]);

GO

CREATE EVENT NOTIFICATION [QueueDisabled]

ON QUEUE [MyQueue]

FOR BROKER_QUEUE_DISABLED

TO SERVICE 'EventNotificationsService', 'MyDatabase';

GO

I certainly can't give you that list... Maybe Remus.

However, I did have something similar happen to me. It turned out it was my poison message handling mechanism.

Here's what I did...

Enable Queue (not activate)

Remove top message (the poison message)

write poison message to a log table

Re-Enable Queue & Activate

Works great, just don't do it all in the same transaction. I pulled the Re-Enable and & activate outside of the trans and it worked fine. I was able to track this down from error message written to the SQL Server Log. Looking at the SQL Server log may help you.

Gary

|||

The only thing that can take a queue offline is five consecutive rollbacks of a RECEIVE

As about testing the event notification, you can simply execute this five times to trigger it:

BEGIN TRANSACTION

RECEIVE * FROM ...

ROLLBACK;

|||

OK, then is this pattern incrorrect or susceptible to unnecessary rollbacks? I suspect that something other than a poison message is causing the rollback because I can restart the queue with existing messages and it runs just fine.

So, for example, if the queue in the following sample does not receive a message for 2+ seconds, will it take the queue offline? Maybe I need to decrease my timeout OR COMMIT instead of ROLLBACK if rowcount = 0?

WHILE (1=1)

BEGIN

BEGIN TRANSACTION;

SAVE TRANSACTION rollbackReceive ;

WAITFOR(RECEIVE TOP(5)

conversation_handle,

message_type_name,

message_body

FROM [MyQueue]

INTO @.tableMessages), TIMEOUT 500;

IF (@.@.ROWCOUNT = 0)

BEGIN

ROLLBACK TRANSACTION;

BREAK;

END

|||

The ROLLBACK of an empty RECEIVE will no trigger the poison message, only ROLLBACK of RECEIVEs that returned messages.

You need to monitor the execution of the stored proc to see why is rolling back the messages. The fact that later it succeeds indicates that the cause of the rollbacks is transient, but does not indicate that no rollbacks happen.

|||

why not move your transaction savepoint following by the Receive Statement. and alway rollback to the savepoint, this can avoid you to shutdown the queue.

WAITFOR(RECEIVE TOP(5)

conversation_handle,

message_type_name,

message_body

FROM [MyQueue]

INTO @.tableMessages), TIMEOUT 500;

SAVE TRANSACTION rollbackReceive ;

suggeste, nevel rollbek the receive statement, you can log the error message and then process it. also you can use try/Catch block.|||

Although this makes some sense, it goes against all the other recommendations I have seen from Remus and others. What about cases where you really do need to rollback the receive? In your example, I assume you would have some counter to determine how many times you have rolled back, in order to perform some action? It seems there should be some happy medium between the two approaches.

|||

I think it really depends on what you are trying to do. For the highest possible performance you must avoid rollbacks at (almost) all cost especially when you are working with large batches of messages. That said, we do have some stuff that if the message is not processed, there is no point in processing any further so a rollback is permitted. If your system is pretty mature and you are fairly certain if you rollback the chance of repeat processing of the message will fail why not just go ahead and do whatever you would do if the recieve rolled back 5 times, poison message got activated. You can always get a timeout though and at times a retry will be successful. It may be possible (although more complicated) to retry without an expensive rollback.

Gary

Wednesday, March 7, 2012

eventvwr.msc message

I keep getting this message in the event viewer -- how can I uninstall reportserver ?
Event Type: Information
Event Source: MSSQL$SQLEXPRESS
Event Category: (2)
Event ID: 17137
Date: 10/22/2006
Time: 10:49:57 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: ********************
Description:
Starting up database 'ReportServerTempDB'.I'm not sure about SQL Express, but on the SQL 2005 installer you can launch
the uninstall from the Add/Remove Programs select change and during the
uninstall select what component (Reporting Services) you would like to
uninstall.
Steve MunLeeuw
"Jon Paal" <Jon[ nospam ]Paal @. everywhere dot com> wrote in message
news:uhJBURg9GHA.1168@.TK2MSFTNGP03.phx.gbl...
>I keep getting this message in the event viewer -- how can I uninstall
>reportserver ?
> Event Type: Information
> Event Source: MSSQL$SQLEXPRESS
> Event Category: (2)
> Event ID: 17137
> Date: 10/22/2006
> Time: 10:49:57 AM
> User: NT AUTHORITY\NETWORK SERVICE
> Computer: ********************
> Description:
> Starting up database 'ReportServerTempDB'.
>
>

Eventlog replication queue is full

I keep receiving the warning message in the event viewer
that the Eventlog replication queue is full.
Error:
EventLog replication queue OUTQ is full. 3 event(s) is
(are) discarded of (total) size 2612.
What should I do to resolve this error?
Thank You,
Dan
Assuming the actual message is "Event Log replication queue OUTQ is full.",
see:
283078 Event Log Replication on Cluster Node Generates Event ID 1137
http://support.microsoft.com/?id=283078
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

EventID 18456 Login failed for SA

I installed SQL server 2005 Beta2 on my Home Destop machine.
I keep getting the follwoing error message .
I tried running SQL profiler to see what is causing this error.
I found osql-32 as client trying to login to SQL server.
Could not find any process named osql-32 in the task manager.
My computer is not on any network. It runs Road runner.
Is there any way to trace this problem ?
Thanks for your help
Event Type:Failure Audit
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:18456
Date:1/9/2005
Time:12:49:29 PM
User:N/A
Computer:SRINIVAS
Description:
Login failed for user 'sa'. [CLIENT: 219.76.192.221]
Data:
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 09 00 00 00 53 00 52 00 ...S.R.
0010: 49 00 4e 00 49 00 56 00 I.N.I.V.
0018: 41 00 53 00 00 00 07 00 A.S....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...
You mention that your computer is not on a network, however the error
mentions an IP address for the client, 219.76.192.221.
Is 'Road Runner' your internet access and when connected to the internet is
your computer protected by a firewall? Could someone externally be accessing
your computer?
Stuart Fish
www.technologic.co.nz
"srinivasa rao Nanduru" <srinivasa rao Nanduru@.discussions.microsoft.com>
wrote in message news:821F173D-8768-4427-9A4B-B92E1FD4CB41@.microsoft.com...
>I installed SQL server 2005 Beta2 on my Home Destop machine.
> I keep getting the follwoing error message .
> I tried running SQL profiler to see what is causing this error.
> I found osql-32 as client trying to login to SQL server.
> Could not find any process named osql-32 in the task manager.
> My computer is not on any network. It runs Road runner.
> Is there any way to trace this problem ?
> Thanks for your help
>
> Event Type: Failure Audit
> Event Source: MSSQLSERVER
> Event Category: Logon
> Event ID: 18456
> Date: 1/9/2005
> Time: 12:49:29 PM
> User: N/A
> Computer: SRINIVAS
> Description:
> Login failed for user 'sa'. [CLIENT: 219.76.192.221]
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H.....
> 0008: 09 00 00 00 53 00 52 00 ...S.R.
> 0010: 49 00 4e 00 49 00 56 00 I.N.I.V.
> 0018: 41 00 53 00 00 00 07 00 A.S....
> 0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
> 0028: 74 00 65 00 72 00 00 00 t.e.r...
>

EventID 18456 Login failed for SA

I installed SQL server 2005 Beta2 on my Home Destop machine.
I keep getting the follwoing error message .
I tried running SQL profiler to see what is causing this error.
I found osql-32 as client trying to login to SQL server.
Could not find any process named osql-32 in the task manager.
My computer is not on any network. It runs Road runner.
Is there any way to trace this problem ?
Thanks for your help
Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: Logon
Event ID: 18456
Date: 1/9/2005
Time: 12:49:29 PM
User: N/A
Computer: SRINIVAS
Description:
Login failed for user 'sa'. [CLIENT: 219.76.192.221]
Data:
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 09 00 00 00 53 00 52 00 ...S.R.
0010: 49 00 4e 00 49 00 56 00 I.N.I.V.
0018: 41 00 53 00 00 00 07 00 A.S....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...You mention that your computer is not on a network, however the error
mentions an IP address for the client, 219.76.192.221.
Is 'Road Runner' your internet access and when connected to the internet is
your computer protected by a firewall? Could someone externally be accessing
your computer?
Stuart Fish
www.technologic.co.nz
"srinivasa rao Nanduru" <srinivasa rao Nanduru@.discussions.microsoft.com>
wrote in message news:821F173D-8768-4427-9A4B-B92E1FD4CB41@.microsoft.com...
>I installed SQL server 2005 Beta2 on my Home Destop machine.
> I keep getting the follwoing error message .
> I tried running SQL profiler to see what is causing this error.
> I found osql-32 as client trying to login to SQL server.
> Could not find any process named osql-32 in the task manager.
> My computer is not on any network. It runs Road runner.
> Is there any way to trace this problem ?
> Thanks for your help
>
> Event Type: Failure Audit
> Event Source: MSSQLSERVER
> Event Category: Logon
> Event ID: 18456
> Date: 1/9/2005
> Time: 12:49:29 PM
> User: N/A
> Computer: SRINIVAS
> Description:
> Login failed for user 'sa'. [CLIENT: 219.76.192.221]
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H.....
> 0008: 09 00 00 00 53 00 52 00 ...S.R.
> 0010: 49 00 4e 00 49 00 56 00 I.N.I.V.
> 0018: 41 00 53 00 00 00 07 00 A.S....
> 0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
> 0028: 74 00 65 00 72 00 00 00 t.e.r...
>

EventID 18456 Login failed for SA

I installed SQL server 2005 Beta2 on my Home Destop machine.
I keep getting the follwoing error message .
I tried running SQL profiler to see what is causing this error.
I found osql-32 as client trying to login to SQL server.
Could not find any process named osql-32 in the task manager.
My computer is not on any network. It runs Road runner.
Is there any way to trace this problem ?
Thanks for your help
Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: Logon
Event ID: 18456
Date: 1/9/2005
Time: 12:49:29 PM
User: N/A
Computer: SRINIVAS
Description:
Login failed for user 'sa'. [CLIENT: 219.76.192.221]
Data:
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 09 00 00 00 53 00 52 00 ...S.R.
0010: 49 00 4e 00 49 00 56 00 I.N.I.V.
0018: 41 00 53 00 00 00 07 00 A.S....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...You mention that your computer is not on a network, however the error
mentions an IP address for the client, 219.76.192.221.
Is 'Road Runner' your internet access and when connected to the internet is
your computer protected by a firewall? Could someone externally be accessing
your computer?
--
Stuart Fish
www.technologic.co.nz
"srinivasa rao Nanduru" <srinivasa rao Nanduru@.discussions.microsoft.com>
wrote in message news:821F173D-8768-4427-9A4B-B92E1FD4CB41@.microsoft.com...
>I installed SQL server 2005 Beta2 on my Home Destop machine.
> I keep getting the follwoing error message .
> I tried running SQL profiler to see what is causing this error.
> I found osql-32 as client trying to login to SQL server.
> Could not find any process named osql-32 in the task manager.
> My computer is not on any network. It runs Road runner.
> Is there any way to trace this problem ?
> Thanks for your help
>
> Event Type: Failure Audit
> Event Source: MSSQLSERVER
> Event Category: Logon
> Event ID: 18456
> Date: 1/9/2005
> Time: 12:49:29 PM
> User: N/A
> Computer: SRINIVAS
> Description:
> Login failed for user 'sa'. [CLIENT: 219.76.192.221]
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H.....
> 0008: 09 00 00 00 53 00 52 00 ...S.R.
> 0010: 49 00 4e 00 49 00 56 00 I.N.I.V.
> 0018: 41 00 53 00 00 00 07 00 A.S....
> 0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
> 0028: 74 00 65 00 72 00 00 00 t.e.r...
>

Sunday, February 26, 2012

Event Notification vs. Triggers

Hi,
Event Notifications can send a message to particular service while this can
be done exactly in a trigger. I mean the DDL/DML trigger can send required
message to a service for asynchronous processing. So what's the advantage of
using Event Notification?
Thanks,
Leila
See if this helps.
http://www.awprofessional.com/articl...&seqNum=5&rl=1
AMB
"Leila" wrote:

> Hi,
> Event Notifications can send a message to particular service while this can
> be done exactly in a trigger. I mean the DDL/DML trigger can send required
> message to a service for asynchronous processing. So what's the advantage of
> using Event Notification?
> Thanks,
> Leila
>
>

Event Notification vs. Triggers

Hi,
Event Notifications can send a message to particular service while this can
be done exactly in a trigger. I mean the DDL/DML trigger can send required
message to a service for asynchronous processing. So what's the advantage of
using Event Notification?
Thanks,
LeilaSee if this helps.
http://www.awprofessional.com/artic...4&seqNum=5&rl=1
AMB
"Leila" wrote:

> Hi,
> Event Notifications can send a message to particular service while this ca
n
> be done exactly in a trigger. I mean the DDL/DML trigger can send required
> message to a service for asynchronous processing. So what's the advantage
of
> using Event Notification?
> Thanks,
> Leila
>
>

Event Notification vs. Triggers

Hi,
Event Notifications can send a message to particular service while this can
be done exactly in a trigger. I mean the DDL/DML trigger can send required
message to a service for asynchronous processing. So what's the advantage of
using Event Notification?
Thanks,
LeilaSee if this helps.
http://www.awprofessional.com/articles/article.asp?p=327394&seqNum=5&rl=1
AMB
"Leila" wrote:
> Hi,
> Event Notifications can send a message to particular service while this can
> be done exactly in a trigger. I mean the DDL/DML trigger can send required
> message to a service for asynchronous processing. So what's the advantage of
> using Event Notification?
> Thanks,
> Leila
>
>

Event Notification Syntax Error

Hi

I have a simple question regarding event notification in sql 2005. I keep up getting a message indicating a syntax error when trying to execute the following script. I also tried with [ instead of '.

CREATE EVENT NOTIFICATION NotifyCT
ON DATABASE
FOR CREATE_TABLE
TO SERVICE 'NotifyService'

Msg 102, Level 15, State 1, Line 4
Incorrect syntax near 'NotifyService'.

I cannot find any error in my syntax. Please help

Thanks

You need to specify the broker instance for the service. Ex:

CREATE EVENT NOTIFICATION NotifyCT
ON DATABASE
FOR CREATE_TABLE
TO SERVICE 'NotifyService', '<broker_instance_guid>'

-- or

CREATE EVENT NOTIFICATION NotifyCT
ON DATABASE
FOR CREATE_TABLE
TO SERVICE 'NotifyService', 'current database'

See Books Online "CREATE EVENT NOTIFICATION" topic for more details.

Event log error message: Database log truncated: Database

Hi there,
Every few days (4 to 7 days), I got this error message. I have included the
complete error below. Is this something to do with my
maintenance/backup/recovery plan setting?
Thanks to your help.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 17055
Date: 1/3/2005
Time: 10:00:04 PM
User: NT AUTHORITY\SYSTEM
Computer: BELDISP2
Description:
18278 :
Database log truncated: Database: PowerBiz.
Data:
0000: 66 47 00 00 10 00 00 00 fG.....
0008: 09 00 00 00 42 00 45 00 ...B.E.
0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
0018: 50 00 32 00 00 00 09 00 P.2....
0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
0028: 65 00 72 00 42 00 69 00 e.r.B.i.
0030: 7a 00 00 00 z...What recovery mode is this DB in? Are there any scheduled jobs that are
issuing a Truncate Log or Backp Log with Truncate?
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included
> the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (6)
> Event ID: 17055
> Date: 1/3/2005
> Time: 10:00:04 PM
> User: NT AUTHORITY\SYSTEM
> Computer: BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>|||First of all, this is NOT an error message, it is an Application Event log
event entry. Informational. Issued by SQL Server.
The message says that the System explicitly truncated the transaction log.
Depending on your current database recovery mode setting, this may or may no
t
be an issue.
If the database is currently set to SIMPLE recovery, then there would be no
need to truncate the transaction log--it would happen automatically with
every checkpoint process.
On the other hand, if you are in Bulk_Logged or Full recovery, then
truncating the transaction log could render your database unrecoverable.
You'd have to restore the database from backup.
There are two possible recommendations:
1. Create a Full backup immediately after a truncate log action.
2. Initiate a transaction log backup schedule and stop truncating the log
entirely.
Sincerely,
Anthony Thomas
"Abel Chan" wrote:

> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included t
he
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (6)
> Event ID: 17055
> Date: 1/3/2005
> Time: 10:00:04 PM
> User: NT AUTHORITY\SYSTEM
> Computer: BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>|||Hi Andrew and Anthony,
Thanks to you both for the prompt response. Really appreciate this level of
support.
I think this event log is related to the way we create our maintenance plan
as I stated in another request:
http://msdn.microsoft.com/newsgroup...exp=&sloc=en-us
Currently, our maintenance plan combines both master and the User databases
together. It also selects Transaction Log Backup option. Transaction Log
Backup always failed under the SQL Server Agent Jobs list.
Since disk space is not an issue at this point, I am thinking to restructure
the maintenance plan. Please let me know if you would also recommend the
following measure to protect our data. If you have a better idea which I
believe you definitely have, please let me know also. Again, thanks so much
for your help and support.
Maintenance Plan for System databases
---
1. Select Recovery mode Simple for master.
2. Select Recovery mode Full for model.
3. Select Recovery mode Simple for msdb.
4. Create a maintenance plan for these system databases.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
except backup the transaction log.
Maintenance Plan for the User database
---
1. Select Recovery mode Full for the User database.
2. Create a maintenance plan for the User database.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
including backup the transaction log.
Additional information: We have a Raid 5 disk array on our production
database server. We copy the database backup into a backup library and
another backup server.
"Andrew J. Kelly" wrote:

> What recovery mode is this DB in? Are there any scheduled jobs that are
> issuing a Truncate Log or Backp Log with Truncate?
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
>
>|||That is fine with a few exceptions. There is no need to do the
optimizations on the system dbs since the maint plan uses DBREINDEX which is
not valid for system tables anyway. Make sure you don't have it set to
shrink the databases or logs as part of the MP or as an option for the DB's.
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...[vbcol=seagreen]
> Hi Andrew and Anthony,
> Thanks to you both for the prompt response. Really appreciate this level
> of
> support.
> I think this event log is related to the way we create our maintenance
> plan
> as I stated in another request:
> http://msdn.microsoft.com/newsgroup...exp=&sloc=en-us
> Currently, our maintenance plan combines both master and the User
> databases
> together. It also selects Transaction Log Backup option. Transaction Log
> Backup always failed under the SQL Server Agent Jobs list.
> Since disk space is not an issue at this point, I am thinking to
> restructure
> the maintenance plan. Please let me know if you would also recommend the
> following measure to protect our data. If you have a better idea which I
> believe you definitely have, please let me know also. Again, thanks so
> much
> for your help and support.
> Maintenance Plan for System databases
> ---
> 1. Select Recovery mode Simple for master.
> 2. Select Recovery mode Full for model.
> 3. Select Recovery mode Simple for msdb.
> 4. Create a maintenance plan for these system databases.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> except backup the transaction log.
> Maintenance Plan for the User database
> ---
> 1. Select Recovery mode Full for the User database.
> 2. Create a maintenance plan for the User database.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> including backup the transaction log.
> Additional information: We have a Raid 5 disk array on our production
> database server. We copy the database backup into a backup library and
> another backup server.
> "Andrew J. Kelly" wrote:
>|||Got it!!!
Thanks so much for your help.
You are really a MVP - quick, care, and to the point.
Abel Chan
"Andrew J. Kelly" wrote:

> That is fine with a few exceptions. There is no need to do the
> optimizations on the system dbs since the maint plan uses DBREINDEX which
is
> not valid for system tables anyway. Make sure you don't have it set to
> shrink the databases or logs as part of the MP or as an option for the DB'
s.
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...
>
>

Event log error message: Database log truncated: Database

Hi there,
Every few days (4 to 7 days), I got this error message. I have included the
complete error below. Is this something to do with my
maintenance/backup/recovery plan setting?
Thanks to your help.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(6)
Event ID:17055
Date:1/3/2005
Time:10:00:04 PM
User:NT AUTHORITY\SYSTEM
Computer:BELDISP2
Description:
18278 :
Database log truncated: Database: PowerBiz.
Data:
0000: 66 47 00 00 10 00 00 00 fG.....
0008: 09 00 00 00 42 00 45 00 ...B.E.
0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
0018: 50 00 32 00 00 00 09 00 P.2....
0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
0028: 65 00 72 00 42 00 69 00 e.r.B.i.
0030: 7a 00 00 00 z...
What recovery mode is this DB in? Are there any scheduled jobs that are
issuing a Truncate Log or Backp Log with Truncate?
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included
> the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (6)
> Event ID: 17055
> Date: 1/3/2005
> Time: 10:00:04 PM
> User: NT AUTHORITY\SYSTEM
> Computer: BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>
|||First of all, this is NOT an error message, it is an Application Event log
event entry. Informational. Issued by SQL Server.
The message says that the System explicitly truncated the transaction log.
Depending on your current database recovery mode setting, this may or may not
be an issue.
If the database is currently set to SIMPLE recovery, then there would be no
need to truncate the transaction log--it would happen automatically with
every checkpoint process.
On the other hand, if you are in Bulk_Logged or Full recovery, then
truncating the transaction log could render your database unrecoverable.
You'd have to restore the database from backup.
There are two possible recommendations:
1. Create a Full backup immediately after a truncate log action.
2. Initiate a transaction log backup schedule and stop truncating the log
entirely.
Sincerely,
Anthony Thomas
"Abel Chan" wrote:

> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type:Error
> Event Source:MSSQLSERVER
> Event Category:(6)
> Event ID:17055
> Date:1/3/2005
> Time:10:00:04 PM
> User:NT AUTHORITY\SYSTEM
> Computer:BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>
|||Hi Andrew and Anthony,
Thanks to you both for the prompt response. Really appreciate this level of
support.
I think this event log is related to the way we create our maintenance plan
as I stated in another request:
http://msdn.microsoft.com/newsgroups...xp=&sloc=en-us
Currently, our maintenance plan combines both master and the User databases
together. It also selects Transaction Log Backup option. Transaction Log
Backup always failed under the SQL Server Agent Jobs list.
Since disk space is not an issue at this point, I am thinking to restructure
the maintenance plan. Please let me know if you would also recommend the
following measure to protect our data. If you have a better idea which I
believe you definitely have, please let me know also. Again, thanks so much
for your help and support.
Maintenance Plan for System databases
1. Select Recovery mode Simple for master.
2. Select Recovery mode Full for model.
3. Select Recovery mode Simple for msdb.
4. Create a maintenance plan for these system databases.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
except backup the transaction log.
Maintenance Plan for the User database
1. Select Recovery mode Full for the User database.
2. Create a maintenance plan for the User database.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
including backup the transaction log.
Additional information: We have a Raid 5 disk array on our production
database server. We copy the database backup into a backup library and
another backup server.
"Andrew J. Kelly" wrote:

> What recovery mode is this DB in? Are there any scheduled jobs that are
> issuing a Truncate Log or Backp Log with Truncate?
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
>
>
|||That is fine with a few exceptions. There is no need to do the
optimizations on the system dbs since the maint plan uses DBREINDEX which is
not valid for system tables anyway. Make sure you don't have it set to
shrink the databases or logs as part of the MP or as an option for the DB's.
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...[vbcol=seagreen]
> Hi Andrew and Anthony,
> Thanks to you both for the prompt response. Really appreciate this level
> of
> support.
> I think this event log is related to the way we create our maintenance
> plan
> as I stated in another request:
> http://msdn.microsoft.com/newsgroups...xp=&sloc=en-us
> Currently, our maintenance plan combines both master and the User
> databases
> together. It also selects Transaction Log Backup option. Transaction Log
> Backup always failed under the SQL Server Agent Jobs list.
> Since disk space is not an issue at this point, I am thinking to
> restructure
> the maintenance plan. Please let me know if you would also recommend the
> following measure to protect our data. If you have a better idea which I
> believe you definitely have, please let me know also. Again, thanks so
> much
> for your help and support.
> Maintenance Plan for System databases
> 1. Select Recovery mode Simple for master.
> 2. Select Recovery mode Full for model.
> 3. Select Recovery mode Simple for msdb.
> 4. Create a maintenance plan for these system databases.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> except backup the transaction log.
> Maintenance Plan for the User database
> 1. Select Recovery mode Full for the User database.
> 2. Create a maintenance plan for the User database.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> including backup the transaction log.
> Additional information: We have a Raid 5 disk array on our production
> database server. We copy the database backup into a backup library and
> another backup server.
> "Andrew J. Kelly" wrote:
|||Got it!!!
Thanks so much for your help.
You are really a MVP - quick, care, and to the point.
Abel Chan
"Andrew J. Kelly" wrote:

> That is fine with a few exceptions. There is no need to do the
> optimizations on the system dbs since the maint plan uses DBREINDEX which is
> not valid for system tables anyway. Make sure you don't have it set to
> shrink the databases or logs as part of the MP or as an option for the DB's.
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...
>
>

Event log error message: Database log truncated: Database

Hi there,
Every few days (4 to 7 days), I got this error message. I have included the
complete error below. Is this something to do with my
maintenance/backup/recovery plan setting?
Thanks to your help.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 17055
Date: 1/3/2005
Time: 10:00:04 PM
User: NT AUTHORITY\SYSTEM
Computer: BELDISP2
Description:
18278 :
Database log truncated: Database: PowerBiz.
Data:
0000: 66 47 00 00 10 00 00 00 fG.....
0008: 09 00 00 00 42 00 45 00 ...B.E.
0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
0018: 50 00 32 00 00 00 09 00 P.2....
0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
0028: 65 00 72 00 42 00 69 00 e.r.B.i.
0030: 7a 00 00 00 z...What recovery mode is this DB in? Are there any scheduled jobs that are
issuing a Truncate Log or Backp Log with Truncate?
--
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included
> the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (6)
> Event ID: 17055
> Date: 1/3/2005
> Time: 10:00:04 PM
> User: NT AUTHORITY\SYSTEM
> Computer: BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>|||First of all, this is NOT an error message, it is an Application Event log
event entry. Informational. Issued by SQL Server.
The message says that the System explicitly truncated the transaction log.
Depending on your current database recovery mode setting, this may or may not
be an issue.
If the database is currently set to SIMPLE recovery, then there would be no
need to truncate the transaction log--it would happen automatically with
every checkpoint process.
On the other hand, if you are in Bulk_Logged or Full recovery, then
truncating the transaction log could render your database unrecoverable.
You'd have to restore the database from backup.
There are two possible recommendations:
1. Create a Full backup immediately after a truncate log action.
2. Initiate a transaction log backup schedule and stop truncating the log
entirely.
Sincerely,
Anthony Thomas
"Abel Chan" wrote:
> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (6)
> Event ID: 17055
> Date: 1/3/2005
> Time: 10:00:04 PM
> User: NT AUTHORITY\SYSTEM
> Computer: BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>|||Hi Andrew and Anthony,
Thanks to you both for the prompt response. Really appreciate this level of
support.
I think this event log is related to the way we create our maintenance plan
as I stated in another request
http://msdn.microsoft.com/newsgroups/managed/default.aspx?query=abel+chan&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
Currently, our maintenance plan combines both master and the User databases
together. It also selects Transaction Log Backup option. Transaction Log
Backup always failed under the SQL Server Agent Jobs list.
Since disk space is not an issue at this point, I am thinking to restructure
the maintenance plan. Please let me know if you would also recommend the
following measure to protect our data. If you have a better idea which I
believe you definitely have, please let me know also. Again, thanks so much
for your help and support.
Maintenance Plan for System databases
---
1. Select Recovery mode Simple for master.
2. Select Recovery mode Full for model.
3. Select Recovery mode Simple for msdb.
4. Create a maintenance plan for these system databases.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
except backup the transaction log.
Maintenance Plan for the User database
---
1. Select Recovery mode Full for the User database.
2. Create a maintenance plan for the User database.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
including backup the transaction log.
Additional information: We have a Raid 5 disk array on our production
database server. We copy the database backup into a backup library and
another backup server.
"Andrew J. Kelly" wrote:
> What recovery mode is this DB in? Are there any scheduled jobs that are
> issuing a Truncate Log or Backp Log with Truncate?
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
> > Hi there,
> >
> > Every few days (4 to 7 days), I got this error message. I have included
> > the
> > complete error below. Is this something to do with my
> > maintenance/backup/recovery plan setting?
> >
> > Thanks to your help.
> >
> > Event Type: Error
> > Event Source: MSSQLSERVER
> > Event Category: (6)
> > Event ID: 17055
> > Date: 1/3/2005
> > Time: 10:00:04 PM
> > User: NT AUTHORITY\SYSTEM
> > Computer: BELDISP2
> > Description:
> > 18278 :
> > Database log truncated: Database: PowerBiz.
> >
> > Data:
> > 0000: 66 47 00 00 10 00 00 00 fG.....
> > 0008: 09 00 00 00 42 00 45 00 ...B.E.
> > 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> > 0018: 50 00 32 00 00 00 09 00 P.2....
> > 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> > 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> > 0030: 7a 00 00 00 z...
> >
>
>|||That is fine with a few exceptions. There is no need to do the
optimizations on the system dbs since the maint plan uses DBREINDEX which is
not valid for system tables anyway. Make sure you don't have it set to
shrink the databases or logs as part of the MP or as an option for the DB's.
--
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...
> Hi Andrew and Anthony,
> Thanks to you both for the prompt response. Really appreciate this level
> of
> support.
> I think this event log is related to the way we create our maintenance
> plan
> as I stated in another request:
> http://msdn.microsoft.com/newsgroups/managed/default.aspx?query=abel+chan&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> Currently, our maintenance plan combines both master and the User
> databases
> together. It also selects Transaction Log Backup option. Transaction Log
> Backup always failed under the SQL Server Agent Jobs list.
> Since disk space is not an issue at this point, I am thinking to
> restructure
> the maintenance plan. Please let me know if you would also recommend the
> following measure to protect our data. If you have a better idea which I
> believe you definitely have, please let me know also. Again, thanks so
> much
> for your help and support.
> Maintenance Plan for System databases
> ---
> 1. Select Recovery mode Simple for master.
> 2. Select Recovery mode Full for model.
> 3. Select Recovery mode Simple for msdb.
> 4. Create a maintenance plan for these system databases.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> except backup the transaction log.
> Maintenance Plan for the User database
> ---
> 1. Select Recovery mode Full for the User database.
> 2. Create a maintenance plan for the User database.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> including backup the transaction log.
> Additional information: We have a Raid 5 disk array on our production
> database server. We copy the database backup into a backup library and
> another backup server.
> "Andrew J. Kelly" wrote:
>> What recovery mode is this DB in? Are there any scheduled jobs that are
>> issuing a Truncate Log or Backp Log with Truncate?
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
>> news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
>> > Hi there,
>> >
>> > Every few days (4 to 7 days), I got this error message. I have
>> > included
>> > the
>> > complete error below. Is this something to do with my
>> > maintenance/backup/recovery plan setting?
>> >
>> > Thanks to your help.
>> >
>> > Event Type: Error
>> > Event Source: MSSQLSERVER
>> > Event Category: (6)
>> > Event ID: 17055
>> > Date: 1/3/2005
>> > Time: 10:00:04 PM
>> > User: NT AUTHORITY\SYSTEM
>> > Computer: BELDISP2
>> > Description:
>> > 18278 :
>> > Database log truncated: Database: PowerBiz.
>> >
>> > Data:
>> > 0000: 66 47 00 00 10 00 00 00 fG.....
>> > 0008: 09 00 00 00 42 00 45 00 ...B.E.
>> > 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
>> > 0018: 50 00 32 00 00 00 09 00 P.2....
>> > 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
>> > 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
>> > 0030: 7a 00 00 00 z...
>> >
>>|||Got it!!!
Thanks so much for your help.
You are really a MVP - quick, care, and to the point. :)
Abel Chan
"Andrew J. Kelly" wrote:
> That is fine with a few exceptions. There is no need to do the
> optimizations on the system dbs since the maint plan uses DBREINDEX which is
> not valid for system tables anyway. Make sure you don't have it set to
> shrink the databases or logs as part of the MP or as an option for the DB's.
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...
> > Hi Andrew and Anthony,
> >
> > Thanks to you both for the prompt response. Really appreciate this level
> > of
> > support.
> >
> > I think this event log is related to the way we create our maintenance
> > plan
> > as I stated in another request:
> > http://msdn.microsoft.com/newsgroups/managed/default.aspx?query=abel+chan&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> >
> > Currently, our maintenance plan combines both master and the User
> > databases
> > together. It also selects Transaction Log Backup option. Transaction Log
> > Backup always failed under the SQL Server Agent Jobs list.
> >
> > Since disk space is not an issue at this point, I am thinking to
> > restructure
> > the maintenance plan. Please let me know if you would also recommend the
> > following measure to protect our data. If you have a better idea which I
> > believe you definitely have, please let me know also. Again, thanks so
> > much
> > for your help and support.
> >
> > Maintenance Plan for System databases
> > ---
> > 1. Select Recovery mode Simple for master.
> > 2. Select Recovery mode Full for model.
> > 3. Select Recovery mode Simple for msdb.
> > 4. Create a maintenance plan for these system databases.
> > 5. Select all options (Reorganize data and index pages, check database
> > integrity, back up the database as part of the maintenance plan and etc)
> > except backup the transaction log.
> >
> > Maintenance Plan for the User database
> > ---
> > 1. Select Recovery mode Full for the User database.
> > 2. Create a maintenance plan for the User database.
> > 5. Select all options (Reorganize data and index pages, check database
> > integrity, back up the database as part of the maintenance plan and etc)
> > including backup the transaction log.
> >
> > Additional information: We have a Raid 5 disk array on our production
> > database server. We copy the database backup into a backup library and
> > another backup server.
> >
> > "Andrew J. Kelly" wrote:
> >
> >> What recovery mode is this DB in? Are there any scheduled jobs that are
> >> issuing a Truncate Log or Backp Log with Truncate?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> >> news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
> >> > Hi there,
> >> >
> >> > Every few days (4 to 7 days), I got this error message. I have
> >> > included
> >> > the
> >> > complete error below. Is this something to do with my
> >> > maintenance/backup/recovery plan setting?
> >> >
> >> > Thanks to your help.
> >> >
> >> > Event Type: Error
> >> > Event Source: MSSQLSERVER
> >> > Event Category: (6)
> >> > Event ID: 17055
> >> > Date: 1/3/2005
> >> > Time: 10:00:04 PM
> >> > User: NT AUTHORITY\SYSTEM
> >> > Computer: BELDISP2
> >> > Description:
> >> > 18278 :
> >> > Database log truncated: Database: PowerBiz.
> >> >
> >> > Data:
> >> > 0000: 66 47 00 00 10 00 00 00 fG.....
> >> > 0008: 09 00 00 00 42 00 45 00 ...B.E.
> >> > 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> >> > 0018: 50 00 32 00 00 00 09 00 P.2....
> >> > 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> >> > 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> >> > 0030: 7a 00 00 00 z...
> >> >
> >>
> >>
> >>
>
>

Friday, February 24, 2012

Event id: 416 - String message: Session idle timeout over, tearing

Does anyone know what this info message means'Is the event ID actually 4156 with a source of MSDTC?
If so, check the following for more information:
[url]http://www.eventid.net/display.asp?eventid=4156&eventno=695&source=MSDTC&phase=1[/
url]
-Sue
On Mon, 8 Aug 2005 07:15:05 -0700, Nick Pennisi
<NickPennisi@.discussions.microsoft.com> wrote:

>Does anyone know what this info message means'

Event id: 416 - String message: Session idle timeout over, tearing

Does anyone know what this info message means?
Is the event ID actually 4156 with a source of MSDTC?
If so, check the following for more information:
http://www.eventid.net/display.asp?e...SDTC& phase=1
-Sue
On Mon, 8 Aug 2005 07:15:05 -0700, Nick Pennisi
<NickPennisi@.discussions.microsoft.com> wrote:

>Does anyone know what this info message means?