Server Management (Insight Manager 7)
cancel
Showing results for 
Search instead for 
Did you mean: 

Event ID: 17055 - 18278, Database log truncated: Database: INSIGHT_DB_V31.

Wayne Collins
Occasional Visitor

Event ID: 17055 - 18278, Database log truncated: Database: INSIGHT_DB_V31.


About once a day, I receive the following error in my
APPLICATION log:


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 17055
Date: 3/12/2003
Time: 9:27:32 AM
User: N/A
Computer: CIM7 Server
Description:
18278, Database log truncated: Database: INSIGHT_DB_V31.
Data:
0000: 00004766 00000010 0000000b 004f0044
0010: 00550048 004f0054 0059004c 00310030
0020: 000f0000 00490000 0053004e 00470049
0030: 00540048 0044005f 005f0042 00330056
0040: 00000031

Why would this happen? What's the problem here?

There is some info in Microsoft Q article: 308267, but I don't think so, or I'm not sure how or if it applies.

Thank you, Wayne
Help me OBI-WAN your my only hope!
4 REPLIES
Ernest_3
Occasional Visitor

Re: Event ID: 17055 - 18278, Database log truncated: Database: INSIGHT_DB_V31.

I just checked this event on www.eventid.net and it showed some possible solutions. Take a look at what it says there and see if any of it sounds useful.

Also, check Q173090, Q240853, Q272418. They might help you sort it out also.

E.
Andy Cudlip
Occasional Visitor

Re: Event ID: 17055 - 18278, Database log truncated: Database: INSIGHT_DB_V31.

Wayne

Did you ever solve this problem? We're seeing the same at our site.

Thanks

Andy
Darrin Rawls
Respected Contributor

Re: Event ID: 17055 - 18278, Database log truncated: Database: INSIGHT_DB_V31.

Not sure about this error, but when the transaction log gets to about 65% full, Insight Manager dumps the transaction log. Maybe there is some bug in a particular hot fix or SP. I assume you are running SP1.x, but with what version of SQL or MSDE?
Andy Cudlip
Occasional Visitor

Re: Event ID: 17055 - 18278, Database log truncated: Database: INSIGHT_DB_V31.

Thanks for that Darrin, I'll find out what SP we're on.

Meanwhile, I've doubled the size of my transaction log, maybe this will cure the problem (based on your comment about it being truncated at 65%). I've also set a SQL alert so that I get a full backup if the event occurs.

Andy