Hi Veenu,

If you're using SmartWebResources, make sure you've configured it properly and the correct version of Resource assemblies are used.

You can also trace whether all client resources are downloaded properly by using HttpWatch tool. Given your issue, I suspect some javascript files may not be loaded properly.

Hope this helps,
James.

Hi James,

I tried with HttpWatch after cleaning all temporary IE files on my machine.

- every resource is downloaded perfectly, and fetched from Cache in subsequent page loading.

No issues there.

Edit: I'd like to let you know that I tried to open the same page with Firefox from the cloud.

Again Edit: I checked that all works fine with IE6 also - issue located with IE7+ only!!!

The looks were not so good, since application doesn't support Firefox, but clicking on WebGrid (e.g. for sorting) was refreshing the whole page but there was no 403 error in that case.

As I said above, has the reported JS error something to do with this issue?

Or, Some other idea...what else can be checked? :(

Regards,

Veenu Munjal

Hi Veenu,

Thanks for submitting more information about your case.

I think the JS error may have something to do with the error during FlyPostBack, since the JS initialization have not been completed in this case. Could you check whether you're running the latest WebGrid 6 build? Alternatively, have you also check using latest WebUI Framework build and latest WebGrid 7 build?

- James

Hi James,

I checked that the WebGrid version on the server is 6.0.7200.103.

There has been no hotfix applied afterwards on this file i.e. it is the DLL as delivered with v2008R2SP2.

Trying Latest WebUI Framework is not an option as the server is production.

The only thing that troubles me here is that the problem is only with the cloud when accessed with IE7 (and I feel like pulling my hair off!)

Best Regards,

Veenu Munjal

Hi James,

It was surprising for me that I'm the first to report this issue. It appeared only on WebGrid on events.

But I located that in my case, we're also using Telerik Library and this error has been reported with Telerik handlers. So I think this is not actually an Intersoft issue anymore.

I haven't located a fix yet with them but you needn't dig into it anymore for now. In case it persists with Telerik removed, I'll get back to you.

Sorry to bother you guys...Thanks a lot for your support, effort and time.

Best Regards,

Veenu Munjal