Error after Data loading , name can not start with '>' character hexadecimal 0x3e

Question

Error after Data loading , name can not start with '>' character hexadecimal 0x3e

SJanki

SSCrazy

Points: 2847
More actions
July 26, 2012 at 1:34 pm

#278502

Hi
I loaded the data suing an SSIS package in a SQL Server 2008 database.
After the data load , I try to display records in the c#/.NET application(this uses a stored procedure to get data and create an XML file with the column names and data.)
I used the same package to load data 2 days before and everything was fine.
Nothing else in the server is changed (.NET applications, assemblies ,webservice etc) except that the data load was done.
One of the screens is getting data from a table and it gives error-->
name can not start with '>' character , hexadecimal value 0x3e.
All the other tables work fine.
I understand this is not a SQL forum question , pardon me for that.
But the error is coming only after data-load , I also did a DBCC checktable, but it displayed no errors.
My question is , is it possible if the table data got corrupted while loading.
I searched for '>' in all the columns/rows of the table but it doesnt appear in the data,
Can anyone tell me of any possible reason for the error from the data point of view.
Thanks.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

GSquared SSC Guru Points: 260824 More actions · Answer 1

Are any of the queries on it dynamic? Either full-on dynamic SQL, or Linq or anything like that?

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Jared SSC Guru Points: 61793 More actions · Answer 2

SJanki (7/26/2012)
name can not start with '>' character , hexadecimal value 0x3e.

1. What screen is giving this error? The appliction in your browser? SSMS? SSIS? VS?

2. This is clearly referring to a name, not data. So something is incorrect in your application, sored procedure, or ddl of the table. I can't tell without you telling me where the error is coming from...

Jared
CE - Microsoft

Jared SSC Guru Points: 61793 More actions · Answer 3

Also, I would go and run the stored procedure in SSMS instead of through the application. If it runs, you know it is the application. If it does not run, it will give an error that should be more specific.

Jared
CE - Microsoft

SJanki SSCrazy Points: 2847 More actions · Answer 4

SQLKnowItAll (7/26/2012)
Also, I would go and run the stored procedure in SSMS instead of through the application. If it runs, you know it is the application. If it does not run, it will give an error that should be more specific.

All the stored procedures related to the screen are giving data at the backend.

By screen I mean , a form in a c#-windows application that is displaying data.

I understand, this is an error in the application, but what puzzles me is I did not deploy any new version of the application on the server and it was running fine 2 days back after loading the same data.

I am trying to find the cause of the issue (in the application)

Will keep you all posted!

Thanks.

SJanki SSCrazy Points: 2847 More actions · Answer 5

GSquared (7/26/2012)
Are any of the queries on it dynamic? Either full-on dynamic SQL, or Linq or anything like that?

No, the queries are not dynamic.

Can a dynamic query be a reason for this error? Just trying to understand.

Thanks.

Jared SSC Guru Points: 61793 More actions · Answer 6

Well... If the data has not changed, the stored procs run fine on SSMS, then something had to change in the application. It is impossible not to. Or, if nothing changed in the application and the stored procs run fine in SSMS, then something had to change in the data. I mean, if nothing changed then how could you get this error? I understand you "think" nothing changed... but somehow, something did.

Jared
CE - Microsoft