WCS Server.ScriptTimeout warnings in CE9

[gashandler]

Anyone have experience with WCS server.scripttimeout warnings in the event viewer? Since I moved my CE9 cluster into production last week I've been getting thousands of these warnings on one of the servers (there are two). I changed the scripttimeout key values to 360 from 90 and restarted the services and I'm hoping that fixes it. I log the cpu activity and from what I can tell I get the warnings regardless of how busy or not busy the server is. The cpu can basically be idle and I still get them. Anyone have any ideas? I never received these warnings when I was running CE85 on much weaker hardware.

Event Type: Warning
Event Source: Crystal_WebCompServer
Event Category: Performance
Event ID: 49855
Date: 2/4/2004
Time: 8:19:45 AM
User: N/A
Computer: DENCRYSTAL03
Description:
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout.

 

[gashandler]

I solved my own problem. It looks like the registry key setting fixed the issue.

 

[eo]

gashandler

Can you please let me know which reg key setting ficed your issue, I am getting the same error.

Regards,

Etienne Oosthuysen
Hertfordshire, England

 

[KingfisherINC]

H_L_M/Software/Crystal Decisions/10.0/Web Component Server/Components/csp/scripttimeout

Kingfisher

 

[eo]

Hi
Excuse my ignorance, but H_L_M? Maybe its just coz its Friday...




Etienne Oosthuysen
Hertfordshire, England

 

[KingfisherINC]

H_L_M = HKEY_LOCAL_MACHINE

Also, the same key exists for each WCS you have, you will need to check each of those components in the registry for the csp key.

Kingfisher

 

[eo]

Thanks,
I changed the scripttimeout from 90 to 360, still the same error. The strange thing is that it runs if you schedule it, but not if you view it - if you view it, the report does actually run, but when eventually displayed the whole screen is covered (in blue) with the "The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout" warning. Any ideas???

Etienne Oosthuysen
Hertfordshire, England

 

[Turkbear]

Hi,
Check the settings for the Web Site ( the IIS ) itself..There is a default timeout set for scripts in its configuration as well..

Sadly, I cannot remember exactly where it is set and I'm not near one at present.

 

[eo]

Hi Turkbear

I have looked into that and change the following setting:
Start/ settings/ control pannel/ Administrative tools, Internet services...then right click on the server and select properties, and in the IIS tab edit the Master Properties tab - to change the connection timeout field to 3600 seconds
Error still occurs, were you refering to somewhere else?

Mant thanks,
EO

Etienne Oosthuysen
Hertfordshire, England

 

[Turkbear]

Hi,
Open the Computer Management tool on the web server, right-click on the Default Web Site item ( under Internet Information Services ) choose Properties..Home Directory..App Options..check the setting for ASP script timeout ( it may not be affecting this, but it can )..

 

[pelajhia]

There are two spots to make the registry edit:
The one suggested as well as:
H_L_M\Software\Crystal Decisions\10.0\Web Component Server\Instances\MachineName\Components\csp\scripttimeout

You might consider something longer than 6 minutes (360).

 

[jcoleman]

I seem to be having the same problem, I have change the registry key on the server as well as the asp script timeout; still the same thing. Does any of this require a reboot?

 

[gashandler]

You need to at least restart the crystal services.

 

[ZENYO]

Just an update. I was also havingthe same issues. I have updated the registry keys to 360 and the IIS ASP script timeout to 360, as suggested in this thread. Everything is working good now!

Thanks.