DumpEvt - End Of File Issue

[Guest]

I am having an issue where the End Of File marker may not be happening during the creation of the eventlogdump.csv.

When the Bulk Insert into SQL Server fires off and start to import the eventlogdump.csv file, it bombs out with the error that the EOF is not found.

When I open the csv file and delete the last row and save the file, the Bulk Insert has no more issues with the csv file and impots it without a problem.

Is there something I can do to make sure this EOF marker is created in the eventlogdump.csv file that DumpEvt is creating.

Thanks again!

[Guest]

Re: DumpEvt - End Of File Issue

Here is the Bulk Insert error I get:

Msg 4832, Level 16, State 1, Line 33
Bulk load: An unexpected end of file was encountered in the data file.

Msg 7399, Level 16, State 1, Line 33
The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.

Msg 7330, Level 16, State 2, Line 33
Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".

Thanks for the help!

[cmccullough]

Re: DumpEvt - End Of File Issue

There is a cr/lf written on each line, so you may need to examine the file with an editor or something that will show you the bytes in the actual file. There might be an entry that is too long or something that is causing it to truncate the line.

[Guest]

Re: DumpEvt - End Of File Issue

Its actually the last line of the file that the cr\lf is not happeneing. It happens for any of the Win Event Logs (App,Sec,Sys) and also happening on different servers.

So if I open the file, delete the last line and rerun the Bulk Insert it works.

Its almost as if DumpEvt is not placing the last cr\lf on the last line as its wrapping up.

[kstanush]

Re: DumpEvt - End Of File Issue

Like we asked, you need to look at the file with an editor than can see the bytes in the file. I quickly created a file and opened it with Word, turned on all text markers, and can see a final line. What I can't see with this approach is any EOF marker, but Word, Notepad, and Write had no problem with the file, and you can see the last line is terminated like the rest.

You may be inadvertently 'fixing' the problem the way you are opening the file and removing the last line, which is not really a line but the editor placing you after the last cr/lf.

There should be freeware applications out there that would let you see every byte of the file.

[Guest]

Re: DumpEvt - End Of File Issue

Thanks again for the info!

Even if I find the conflicting line in the event log(s) I am having issues with, I cannot do this for all the logs that are encountering this problem especially if I am dealing with 3 Win event logs per my 100 servers on a daily basis.

I needed to have this process automated so that I did not have to open the file rouge, delete the last line and re-run the nightly batch job from the point of failure until it failes once more. I would be spending my whole day trying to get all 300+ logs into the DB.

I guess I need to move on to another app like DumpEvt that can handle my issue.

I have to say DumpEvt looked very promising and got me 99% of the way.

Thanks again for all of your help.

J Kusch

[kstanush]

Re: DumpEvt - End Of File Issue

You are misunderstanding what I am saying. I'm trying to determine what, if anything, is missing from the file or is not 'right' with respect to your SQL process.

If you have a file that works with your procedure and have saved it with a different name than the original, it needs to be determined what the difference is. I see a cr/lf at the end of the last record, so its impossible thats the problem. It might be the EOF marker, or SQL wanting something different. I don't have SQL to test with, and there are a lot of users using DumpEvt with SQL, so I need you to see what is different between a file that works and one that does not.