Hi
We are facing a very strange problem. We have windows 2003 server hosting a web application which uses sybase as database. The problem is the code executes fine if I host the web application on a xp machine but on 2003 server it gives the error :
Object Refernce not set to an isntance of an object.
The code and database are same in both instances.
The error being very common we have checked all the pieces of code referenced and nothing seems to be set to null after debugging. The error happens when it tries to execute a stored procedure. The strange thing being, the same function calls the same stored procedures twice, it executes perfectly the first time but throws the above exception second time. The parameters are excatly the same. Also, If i try to execute another stored procedure the second time, it too fails. We have checked for memory leaks, code that is executed prior to the above stored procedure, everything seems ok. We have even tried to excute the select command inside the stored procdure directly, but get the same issue. There is only one select command inside the stored procedure.
Thanks in advance for all the help.
I look forward to any help possible.
Thanks
We are facing a very strange problem. We have windows 2003 server hosting a web application which uses sybase as database. The problem is the code executes fine if I host the web application on a xp machine but on 2003 server it gives the error :
Object Refernce not set to an isntance of an object.
The code and database are same in both instances.
The error being very common we have checked all the pieces of code referenced and nothing seems to be set to null after debugging. The error happens when it tries to execute a stored procedure. The strange thing being, the same function calls the same stored procedures twice, it executes perfectly the first time but throws the above exception second time. The parameters are excatly the same. Also, If i try to execute another stored procedure the second time, it too fails. We have checked for memory leaks, code that is executed prior to the above stored procedure, everything seems ok. We have even tried to excute the select command inside the stored procdure directly, but get the same issue. There is only one select command inside the stored procedure.
Thanks in advance for all the help.
I look forward to any help possible.
Thanks