Login
Latest Development Blogs
Forum Topics Post
Browse By Tag
Hello,
I’m intermittently (frequently) getting the following error only when using WebCombo in IE9…
Block where exception happens:
if (ve0720.readyState ==4) { var vca977 =ve0720.getResponseHeader("Content-Type");
Error:
SCRIPT575: Could not complete the operation due to error c00c023f. 305000772, line 11 character 48153
My web research lead me to the abort() command running prematurely and causing this error.
Please let me know about your findings.
Thank you.
The sample attached on my previous post shows how to implement requery method using traditional DataSource. Since the older data binding mechanism is chosen as the scenario, the data source initialization is set in code behind in InitializeDataSource.
The re-query is handled manually, so we need to disable the AllowAutoQueryHandler property.
DataTextField and DataValueField properties are set to a field from its data source respectively.
The UseDefaultStyle is enabled. Default Style is a feature in WebCombo. It is different with Predefined Style. Default Style feature marks the instance to use the default style that come with WebCombo. You are not recommended to customize any of the styles when using Default Style feature.
The other properties are related to the layouting of WebCombo. Hope this helps.
This error message is quite odd and we have not receivedsuch reports so far. Could you confirm whether you are using the latest build version of WebCombo 5? I tried to reproduce the problem in my local tests by creating a simple sample of WebCombo based-on your given snippet code but my efforts were not successful -- everything worked smoothly and the WebCombo was accessed without any issues.
I am willing to advise you further but in order to do so I would need you to elaborate on your specific scenario and possibly give us a step-by-step guide that we can use to observe the problematic behavior.
Thanks Yudi for your replay.
I'm running version 5.0.7200.3 of WebCombo. It was a fresh install of WebUI Studio 2011 R1 SP1.
There is really nothing specific about that sample. The exception is thrown before _InitializeDataSource is called. As I have mentioned this is intermittent problem and sometimes it takes like 20 attempts to surface. Error is pointing to ISCore.js. There are no steps to reproduce that error it just happens when you start typing in the textbox.
I’m attaching picture of Locals from Debug maybe that helps a bit.
Thank you
I enclosed a simple sample of WebCombo to be tested on your end. Please let us know whether the issue is reproducible using the sample or not.
The build version of WebCombo on my local end is identical.
Hi Yudi,
I’m able to run your sample without getting any errors. Please indicate which parts of your sample are essential to be included in my code to address the issue. Our data backend is SQL and data access is via Stored Procedures only.
I have the same problem: the web combo always aris ethe error "Could not complete the operation due to error c00c023f", but it happens to me only with HTML5 doctype: <!DOCTYPE html>. I can only use this doctype, could you please help me?
Regards,
Vince
I tried to reproduce the problem in my local test by viewing the FirstExperience.aspx sample of WebCombo (check the live version of this sample in here) in browser but my efforts were not successful -- everything worked smoothly and the page was accessed without any issues.
For your information, the testing was conducted using WebCombo 6 build 250 which bundled in Intersoft WebUI Studio 2012 R2. Any information regarding the WebCombo's version and build number; browser type and version might help.
I'm willing to advice you further but in order to do so I would need you to elaborate on your specific scenario and possibly give us step-by-step guide that we can use to observe the problematic behavior.
Thank you very much for the video. It really helps to figure out the step-by-step to reproduce the reported problem.
I was able to reproduce the reported problem. It has been forwarded to WebCombo development team for further investigation. I will keep this thread updated with any news I heard from the team regarding the progress of this bug.
The reported problem is already queued in our work item and reported under Bug 1181. The team is currently working to fix this and expected to be included the next release of hotfix.
When ready, I may be able to provide you with the pre-release hotfix to be evaluated on your end. Please feel free to ping me at any time regarding Bug 1181.