I have my server set to store conversations for 30 days.

When clicking on 'Stored Conversations' in IAdmin, it does nothing for 90 seconds (The default timeout on my server, a WIN2K Domain Controller) After 90 seconds, it will show a list of conversations just longer than a page, whereby I cannot see the bottom because there is no scrollbar in the main window, only in the stored conversation dialogue. In order to see the timeout message, if I rotate my screen so it is in portrait view, I can then see the message "Active Server Pages Error 'ASP 0113' "

The conversation it seems to have stalled on has been deleted to no avail. It makes no difference if I change the timout on the server.. 60 seconds or 300 seconds nets the same results. None of the sorts work, but the message id links that do show up work just fine. I really need this to work.. I have checked permissions probably 10 times now, all seem correct. I have verified the version of ASP I am using, and it is correct. I deleted any conversation logs over 50K to reduce the number of files and data to be queried, to no avail.

PLEASE HELP!

Thanks, Dave

So no luck hey? Nobody else has a similar problem? Weird. I have uninstalled and re-installed, and rechecked all permissions since my first post on this subject.

I have determined that if I change the saved conversations setting to 7 days, I can in fact get the page to display, without a script timeout error.. BUT none of the sorters work then.

The new iadmin is flaky at best, in more ways than one... is there any way one could use the old (Slower than hell) IM admin program to view the conversation store?

I have been having no luck getting the "ConversationStore.asp" script to load properly, either from a remote workstation or from a browser running on the local host where ICS is installed. I recently applied the 2006.03 update to this system in hopes that would provide some relief for this problem, but no-go there either.

I have gone as far as upping the allowed time in IIS settings for that script to run before it times out and generates the HTTP 500.100 internal server error from the script timing out at the default of 90 seconds. I have pushed this as high as 180 seconds and that has not made any difference whatsoever.

This is not a heavily loaded server. I have less than fifty IM users. We do not use the imail or workgroup applications. IM is the only task that this server performs. This is a medical facility, and I do need to be able to audit these files in order to comply with HIPAA regulations.

One thing that remains constant when I attempt to access the stored conversations is that one of the two instances of DLLHOST.EXE in the Windows task manager leaps up to 98% CPU utilization, the CPU time used ticks up in seconds in real-time, and the amount of RAM used by this process fluctuates upa nd down between 25 MB and 51 MB. This continues until the script times out and then the process falls flat to zero CPU utilization and then holds steady at 25MB RAM.

Background: P4 2.5 Gig, 512 MB RAM, Windows 2000 Advanced Server, patched to latest updates from both MS and Ipswitch. This is an "internal" server and is not accessible from the Internet.