Thread: Connection Time-out

From your description I can only guess that the session is timing out. I'm not an expert on that specifically. The only thing I can think of is to enable auto-refresh on the report and have it refresh every 20 or 30 minutes. This presumably would cause the session to refresh as well. The downside to this approach is that it results in more traffic on the server.

Is this a report that the users expect to update at a given interval?

So basically this is to accomodate users that leave their browser window open all day and want to be able to refer back to the report?

If the data does not change during the day, you might advise them to export the report instead of going with the auto-refresh.

Just my .02.

OK so I think I have figured out what you need to do.

1. Select your datasource and click on the edit button near the connection string text box.
2. A window called Connection Properties should appear.
3. Click the Advanced button, which displays the properties of your data source.
4. Scroll up to the Connect Timeout property.
5. Increase the number in the timeout property (maybe try five minutes or 300).

The problem you are having may be due to high server load or a slow connection to a remote server. Increasing the timeout should solve this (unless the DB is offline).

Good Luck!

The number you put in the timeout is the length of time that the connection will wait for a response. So increasing the number will give it longer to try and resolve. The error message is thrown when the connection timeout has been reached (for example if it takes more than 15 seconds and the timeout is set to 15, then the error appears).

So you'll want to make that number larger. Remember that whatever number you put there is the number of seconds the connection will attempt to resolve.

Hopefully this helps

The initial data connection to the server is the timeout I instructed you about earlier, and it is this timeout that must have a property (I tried unsetting it and it would not accept null). You probably would not want to set it that way anyway because that would mean that if your database was offline your connection would never close.

However, I believe the connection timeout for a dataset is not set by default; which means that once the database connection is made the query will try to execute until it gets a response from the server, but the initial connection must have a timeout property.

Therefore, if you just set it really high, such as 300 seconds, it should suffice. If your connection is taking longer than that you probably have another problem with the database.