Report is hanging server

[zmcanally]

I am using ASP.NET and the version of crystal reports that is embedded into VS.NET (I believe it's a watered down version of 9) I can run all my reports great, and I display them as PDF files in a new widown instead of using the report viewer. I can run each report individually fine, but while doing some concurrent testing (since there is a 5 users limitation on this version) I have noticed that after running a few consecutive reports (one right after the other), it stops displaying the reports. The page seems to hang and never displays anything - All I get is a hourglass and progress bar - no errors. I've let it sit for as long as 45 minutes. Once I restart IIS, they run fine again until I run a few more consecutively. Any suggestions? Is there a log I can check to see what's going on? I can post code if needed

Thanks,
Zack

 

[Turkbear]

Hi, Check the available space in the directory that CE is using for its TEMP files....If it fills, all will stop.

 

[zmcanally]

How do I determine what directory that is? BTW, the server in question only has 1 partition and it has 8 gigs free on it. Thanks -

Zack

 

[Turkbear]

Hi, For CR ( if it is running on your desktop), it would be your temp file location [ often C:\temp] , but, on the web server is may be different.
Look at the server's environment variables to see if it is specified.

With Crystal Enterprise, it is shown in the CMC under the Manage Servers tab ...

However, with 8gig free, I doubt this is the problem, unless it is using the client temp location...
It could possibly be a Resource limitation on the web server with that many complex displays ( multiple PDFs use a lot of graphics space ).

 

[zmcanally]

Thanks - I'll try and view them in the report viewer to see what happens. On a similar note, Would it help any if I release the report object from memory when I get rid of it? (ie: reportobject = nothing) Here is a snippet of the code I use to show the report


StartDate = Request.QueryString.GetValues("StartDate")(0)
StopDate = Request.QueryString.GetValues("StopDate")(0)
Dim rptPDF As rptTechSummary = New rptTechSummary
Dim crExportOptions As ExportOptions
Dim crDiskFileDestOptions As DiskFileDestinationOptions
Dim fName As String
fName = "c:\Exports\" & System.Guid.NewGuid.ToString & ".pdf"
crDiskFileDestOptions = New DiskFileDestinationOptions
crDiskFileDestOptions.DiskFileName = fName
crExportOptions = rptPDF.ExportOptions
crExportOptions.DestinationOptions = crDiskFileDestOptions
crExportOptions.ExportDestinationType = ExportDestinationType.DiskFile
crExportOptions.ExportFormatType = ExportFormatType.PortableDocFormat
rptPDF.SetParameterValue(0, StartDate)
rptPDF.SetParameterValue(1, StopDate)
rptpdf.SetDatabaseLogon("myusername", "mypassword")
rptPDF.Export()
'show pdf file
Response.ClearContent()
Response.ClearHeaders()
Response.ContentType = "application/pdf"
Response.WriteFile(fName)
Response.Flush()
Response.Close()
'remove pdf file
System.IO.File.Delete(fName)

thanks - Zack

 

[Turkbear]

Hi,
It is always a good idea to release resources when no longer needed - especially any database connection objects.

The resources I refered to are Windows Graphics resources and they can be a limiting factor in some cases ( although if you are using XP Pro or W2K Advanced Server it is less likely)