M
Martin Schaech
Hello all I have an interesting problem which is causing me to lose
sleep. I have a vb.net app in use by approximately 100 people on a
daily basis. This app is mission critical for the business. I'm
using windows server 2003 for the web front end, SQL server 2k for the
backend, and a mixture of winXP and w2k PCs as clients. The app works
100% except for one strange behavior: Once in approximately 300
instances, one of my sql insert statements fail - I'm using a stored
procedure to insert a record in the SQL DB. I process / verify the
data on the front end to ensure nulls, empty values, and data types
are handled correctly. The exact failure is my
connection.executescalar() function returns "0". Regardless of how
many times I resubmit the failing request, the function returns 0
(which rules out locking issues). I have no connectivity problems
between the DB, web server, and the clients (pings are always solid).
Now here is the strange part. If I close the internet explorer
window, reopen IE and give the SAME input, the function will return
the @@identity like it should. I am using sessions but I've verified
the particular session value which is inserted using this function is
intact when the 0 is returned (by writing just that session value to
another table). I'm not sure posting code would help given the
parameters of this problem. Has anyone heard of this before?? Help
Please!
sleep. I have a vb.net app in use by approximately 100 people on a
daily basis. This app is mission critical for the business. I'm
using windows server 2003 for the web front end, SQL server 2k for the
backend, and a mixture of winXP and w2k PCs as clients. The app works
100% except for one strange behavior: Once in approximately 300
instances, one of my sql insert statements fail - I'm using a stored
procedure to insert a record in the SQL DB. I process / verify the
data on the front end to ensure nulls, empty values, and data types
are handled correctly. The exact failure is my
connection.executescalar() function returns "0". Regardless of how
many times I resubmit the failing request, the function returns 0
(which rules out locking issues). I have no connectivity problems
between the DB, web server, and the clients (pings are always solid).
Now here is the strange part. If I close the internet explorer
window, reopen IE and give the SAME input, the function will return
the @@identity like it should. I am using sessions but I've verified
the particular session value which is inserted using this function is
intact when the 0 is returned (by writing just that session value to
another table). I'm not sure posting code would help given the
parameters of this problem. Has anyone heard of this before?? Help
Please!