PDA

View Full Version : IIS 5.01 crashes on use of TABS



vagelis
28 May 2007, 9:05 PM
I have included in ASP scripts that read from a db tabs lib. IIS crashes with no reason and no error. When I remove it it works with no errors. Script was tested before with other javascript tabs with no problem. Does anyone has faced any similar situation before?

Best regards

Vagelis

brian.moeskau
28 May 2007, 10:09 PM
IIS, or IE??

vagelis
28 May 2007, 10:16 PM
IIS, or IE??
Hi Bryan,

I'm testing on IE 7 and Firefox 2. On IE7 sometimes it works ok but IIS (local Information Server) crashes, while same script on Firefox does not displays TABS at all. On refresh of page in Firefox IIS crashes too.

jack.slocum
28 May 2007, 11:07 PM
Why is this in the Ext JS bugs forum? Ext does nothing on the server. It is a JavaScript file.

brian.moeskau
28 May 2007, 11:18 PM
Are you serving up javascript code from inside your server-side ASP tags? If so, I would assume that you have some malformed code that is causing IIS to choke (not sure how that's possible, but if you say it's happening, I believe you). But as Jack said, this is not Ext-specific and is certainly not an Ext bug. IIS can only crash from code that is executed on the server, and Ext code is executed in the browser. If there's a problem, it's in your server code.

vagelis
29 May 2007, 1:39 PM
In firebug when I run code and expect TABS to be displayed on Firefox I have the following errors and IIS crash. On IE7 it works ok with no crash of IIS. When I remove this code and use some other TAB script it works with no errors (Javascript or Nitobi tabs). I like better ext tabs and ext grid and if I can use it with no errors then I'm thinking of buying a licence.

this.el has no properties
TabPanel("tabs1", undefined)tabs.js (line 9)
init()test_tabs.js (line 12)
Observable()ext-core.js (line 15)
EventManager()ext-core.js (line 17)
[Break on this error] Ext.TabPanel=function(_1,_2){this.el=Ext.get(_1,true);if(_2){if(typeof _2=="bool...

tryanDLS
29 May 2007, 1:46 PM
Once again, what does this have to do with IIS. IIS is a webserver - it has nothing to do with your clientside javascript code that is failing.

There are several threads here discussing debugging and also links to videos regarding how to use Firebug. I would suggest you read the sticky threads in the Help forum, then post a question that give others enough info to try and help you.