I have a devil of an intermittent problem that I have so far found nothing to help me solve.
I have a web application/module in Dotnetnuke that requires data for a simple form from another SQL server DB on a different server. The app uses a connection string in the web.config like this:
<add name="CompanyUpdate" connectionString="Data Source=mail.mydatabase.be;Initial Catalog=MA_Online;Persist Security Info=True;User ID=Gus;Password=xxxxxx" providerName="System.Data.SqlClient" />
The application calls a stored proc and most of the time data is returned as expected. There should always be a row returned from the SP. However, if the form is idle for a while or the module has only just loaded the call to the stored proc returns
as empty recordset. A 'table not found' error occurs.
There is no connection issue otherwise there would be a connection error instead of an empty recordset right?. But I cannot work out why sometimes no data is returned. I can go onto the server and run management studio and run the sp over and again and always
I don't have control over the target DB but the person who does thinks it's something to do with connection pooling. I tried turning this off in the connection string and found that I got an empty recordset every time the sp was called wit
View Complete Post