Often users try to load an ASCII file in the SQL Server native format. This leads to misinterpretation of the hexadecimal values in the ASCII file. The "unexpected end of file" error message is very common in this instance. The proper way to load the ASCII file is to represent the fields as a character string and let SQL Server do the data conversion.