March 29, 2010 at 12:53 pm
Hi,
We have SQL Server 2005 EE x64 with SP3 and configured log shipping to run the log backups every 1 hr and I'm seeing the below message in event viewer when ever the log backup runs:
Event Type:Information
Event Source:MSSQLSERVER
Event Category:(6)
Event ID:18265
Date:3/29/2010
Time:11:00:00 AM
User:ABC\mssqlsrv
Computer:SQL
Description:
The description for Event ID ( 18265 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: WSS_Content_ABC, 2008/10/07, 12:42:16, 7773:77070:1, 7773:77516:1, 1, FILE=1, TYPE=DISK: {'\\SQLVS\LSBackups\WSS_Content_Abc.trn'}.
Is this normal message? Why it says The description for Event ID ( 18265 ) in Source ( MSSQLSERVER ) cannot be found?
Thanks
March 29, 2010 at 3:08 pm
Do yuo get the same info if you use the event viewer from the actual server itself? You usually get the "missing description" message if your local machine is missing a piece to understand the event.
That said - If you look up event 18265 for SQL Server you get this:
This would be an informational message confirming normal successful processing of the log backup.
You still want to ocnfirm that by logging onto the server itself and verifying that you get the message description mentioned on the link.
If you are still getting the "missing description from the server" then something isn't regstered correctly on the server itself.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 29, 2010 at 4:19 pm
Do yuo get the same info if you use the event viewer from the actual server itself? You usually get the "missing description" message if your local machine is missing a piece to understand the event
.
Yes, I'm seeing this message in the event viewer when ever log shipping backup job occurs on the actual server where SQL Server has installed
This message is only occuring in the event viewer NOt in SQL Server error log. In error log, it's writing the message as below:
Log was backed up. Database: WSS_Content_ABC, creation date(time): 2010/02/09(13:31:41), first LSN: 315:450487:1, last LSN: 315:452203:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\SQL1vs\LSBackups\WSS_Content_ABC_20100329220000.trn'}). This is an informational message only. No user action is required.
Still, we are missing something? and where to check for what is missing?
Thanks
March 29, 2010 at 8:31 pm
Try this:
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 30, 2010 at 12:35 am
Hi Matt,
I went through the given link and we are using Spot light for Monitoring our clustered SQL Server 2005 servers.It's showing normal message for log backups taken via log shipping backup job on other node but this message is occuring on only one node.
But what haapens if we igonre this message as we know that it's log backup job message? Is it going to harm anything, if we did not perform the registry setting as described in the link?
Thanks
March 30, 2010 at 8:50 am
The event status means the same in both cases. It's just that one of the nodes isn't geared to pulling up the right message description for you. The events you're seeing should be showing up on both nodes so you odn't have a huge problem.
In my mind - as long as you have one place to make sure the message is not a problem (i.e. the one node), you should be okay.
If you're stuck - you can always open up google and type in a query to get the message as well. Something like : "SQL Server eventID 18265" (or whatever eventID you need identify), which is what confirmed for me what you were looking at.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply