HTTP 500.100

[Ray Costanzo [MVP]]

What's on line 542 and the relevalent lines preceding it? And what does
your SQL query look like?


Ray at work

 

[David C]

I am getting the following error when trying to run an SQL insert in my ASP
page and I cannot find anything in TechNet that references this error.
Below are IIS messages:

HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services
Error Type:
Microsoft OLE DB Provider for SQL Server (0x80040E14)
Issue selected is no longer valid. Please select another issue.
/ActivityTrak/maintain/activityedit.asp, line 542

Thanks.
David

 

[David]

Line 542 is below.

objconn.Execute(strSQL)

The lines before it simply build an SQL INSERT command. I did a
Response.write to display the SQL and it all looks fine. Anytime I have
had bad SQL it gives me a different error than this one, so it must be
something else.

Just above this I am getting a "next number" using this same connection
and that works fine.

If you want the lines preceding 542 I can send them, but they are very
verbose.

David

 

[Ray Costanzo [MVP]]

Did you see this part? It's very important:
.... and the relevalent lines preceding it? And what does your SQL query
look like?

Also, http://www.aspfaq.com/5007

Ray at work

 

[Bob Barrows [MVP]]

Line 542 is below.

objconn.Execute(strSQL)

The lines before it simply build an SQL INSERT command. I did a
Response.write to display the SQL and it all looks fine. Anytime I
have had bad SQL it gives me a different error than this one, so it
must be something else.

Just above this I am getting a "next number" using this same
connection and that works fine.

If you want the lines preceding 542 I can send them, but they are very
verbose.

David

No, just show us the result of response.writing your sql statement, ie,

response.write strSQL

Assuming the statement runs correctly when you test it in Query Analyzer
(which should be your first step), and fails to run via ADO, then your
problem is likely related to the use of reserved keywords for names of your
database objects (columns and/or tables). See this for the list of words to
avoid:

http://www.aspfaq.com/show.asp?id=2080

If reserved keywords is not the problem, show us the faining sql statement.

Bob Barrows

 

[David]

Since this was not my database design, I looked at the triggers for this
table and the triggers were actually generating the ASP error message.
The triggers were requiring valid entries (exist on another table) and I
was trying to enter zeros into the field. Guess that is why I couldn't
find it on TechNet. Maybe someone else learned something new from this
also. Thank you all.

David