For the benefit of our readers, it should be pointed out that you signed up for the Axosoft Community profile today, seemingly just to add this comment to a 6-month old thread.  But, I’d like to respond anyway… The OnTime application is not supposed to take 50 seconds in order for the page to load. If you are currently experiencing ...

How can I adjust the timeout setting for the desktop windows client? I just imported about 6,000 customers into the system via SQL/CSV File as I read there is no built-in customer import, but now the Customers tab just times out trying to load the list. I can do a 'Tools --> Customer Portal --> Manage Customers' and that will list the ...

I've been experiencing intollerable slowness in both the Windows client and the Web client using version 7.1.1.7329. Here are some timings: Click on any project in the project tree:  19-30 seconds. Double-click a feature, defect, or task:  19-25 seconds. Pretty much anything I clicked on took between 19 and 35 seconds.  ...

The other possible cause to slow performance could be related to a possible bottle neck on the local network where the SQL database is hosted at. Can you tell me if the SQL server is hosting multiple databases by any chance? Are there any other applications that are experiencing the same or similar performance problem by any chance? ...

Hi all,We are running OnTime v7.1  on a box with a P4 3.2Ghz CPU, 1 gig of RAM and 3 x 160 gig 7200 rpm SATA hard drives with RAID 5. I know that 1 gig of RAM is listed as the recommended amount and we meet that so I would expect it to be running okay. We have configured OnTime to use the Features tab to manage all of our work so Defects, ...

A few comments on OnTime web performance: The bulk of the performance issues with OnTime web is due to the javascript, HTML payload and network speeds.  The OnTime database is pretty well optimized and whether you have 50 or 500 issues won't make much of a difference.  For extremely large databases (10K+ records), there would be ...

Just a few features (3 to be exact) on the grid here. Either clicking an item or just arrowing up or down from item to item is sloooooooooooowwwww. Clicking the item to edit is slowwwwwwwwwww too. Based on the other posts and seeing the behavior of the grid, one can surmise that there's a problem with the  windows client grid ...

Andreas, Would it be possible if I could take a look at this performance problem that you have been experiencing with OnTime over a gotomeeting remote session? We should be able to pin point the performance problem in your local environment. Please let me know. Thank you,

Hello Dragan, thank you for the quick reply. Yes all three users have the performance problem. We all connect through the SQL connection method to the server.  I've allready checked the SQL Server. The Server has nothing to do. I made a trace and the only querries are about ontime (three users) and reporting services (for the same three ...

oh sorry I forgot about that, we are all using the windows version with the versionumber 7.0.2.7191...Any other information you need?    regards Andreas

Recently we have noticed that when updating the table statistics of the SQL database, the OnTime application performance seems to be much better. The following SQL command will update all of the table statistics in the database which should increase the performance of queries that the SQL server performs on daily basis. This command can be used in ...

Hello,   we've just bought a starter pack of OnTime for testing since 1 month. There are about 20 Projects and 30 Features in. The Features have no Attachements etc. There are only Worklogentrys, about 500 items. The start of OnTime takes a long time, about 6 seconds. Thats ok, there is caching. Why not, we are not startig all the ...

Changing the timeout value for the application pool will not make any performance difference in the OnTime 2007 web edition. By default the application pool is configured to recycle after a 20 minute period. Our development team recommends that the application pool timeout should actually be set to 60 minutes instead for the OnTime 2007 web ...

So should I assume the answer is no? 

That is correct. The OnTime 2007 Web client works with .Net Framework 2.0. Please make sure that the ASP.Net tab for the virtual directory of OnTime 2007 web is set to use the .net 2.0 version. Thank you,