Hi there
Smart CallBacks functionality of WebCombo v.8.2 gets frozen and generates the error: (paramater is incorrect). Debuging takes me to the following file and function:
webresource.axdparamater is incorrectigtbl_XSLTProcessor.prototype.transform=function(){ if(!this.input) return false; if(ig_csom.IsIE) { this.Processor.input=this.input; this.Processor.transform(); this.output=this.Processor.output; } else return this.outputDocument=this.Processor.transformToDocument(this.input); return true;};
Any help more than welcome
Regards
Elvis
This sounds like it's either a setup issue or a bug.
Can you reproduce this in an isolated sample application that we can run and debug? If so, then I suggest you submit a support request and attach that sample to your request. A Developer Support Engineer will investigate your issue and will work with you to resolve it.
Is there any resolution on this particular issue? I am experiencing the same error and location. We have an application that is being rolled out to production. In the training classroom, all of the computers in the rear row experienced the exact same error while the computers in the first two rows did not.Obviously there is some setup issue that is causing problems for the Infragistics control. What I don't know is what the problem actually is.Error message from IE: A runtime error has occurred. Do you wish to debug?
Line 11474Error: The parameter is incorrect.As this is a remote machine, I only had access to Microsoft Script Editor. It gave an additional error message of:MSXML3.dll: The paramter is incorrect.The code it is pointing to is:igtbl_XSLTProcessor.prototype.transform = function() { if (!this.input) return false; if (ig_csom.IsIE) { this.Processor.input = this.input; <== This is the line that is throwing the exception this.Processor.transform(); this.output = this.Processor.output; } else return this.outputDocument = this.Processor.transformToDocument(this.input); return true; };I will continue to work on this. I will post if I get a resolution. If not, I will try to reproduce in a simple app and send the code alonge in support request.
Hi,
We do occasionaly get bug reports like this one where some machines experience the problem and some don't. I believe this is a bug in Microsoft's msxml3.dll and the latest patch from them should be installed. Here is how:
http://support.microsoft.com/kb/308480/EN-US/
Thank you for your advice, but I got installed the latest SP9, file version 8.90.1101.0 of this dll on a few computers where this problem happens only on some of them. Any help more than welcome, cheers.
I did not realize it but a coworker was having the exact same issue for the past several days. After escalating up within Infragistics, he found a solution. On the grid there is a attribute called Browser. It was set to "Xml". He changed it to "Auto". This apparently triggers a path in the Javascript to be more sensitive to the version of the current browser. This got him around the same error message. I cannot test my problem at this time as those computers are being used for a class. I will post a followup if it works.
I was able to test this on the computers that were having the issue and they are now able to display the page without any problems. As a side note to Infragistics, if it helps with tracking down the problem for a possible permenant solution (other than causing developers hours of aggrevation while tracking this down) I have attached a report on the dlls for the problem machine. This was a quickie program I put together to compare the bad machine to the good machine. It lists all the .dlls and whether there is a difference. I thought it might help in tracking down why the problem is occuring.In the report...If the line begins with a space, the file occurs on both machines.
If the line begins with a minus, the file is not on the bad machine but it is on the good machine.
If the line begins with a plus, the file is on the bad machine but it is not on the good machine.
If the line begins with an asterix, both systems have the file but the versions are different. The first version number printed is the bad machine, the second version number printed is the good machine.
Hopefully this helps...
Scott
Wish I could help you Elvis but I don't have any experience with the WebCombo. Maybe one of the developers at Infragistics could help. I am thinking it is related to the issue that I ran into. Unfortunately I did a quick check and there is no "Browser" property like the Grid. I had hoped that our two problems were the same just because it did fail with the same error message at the same point in the JavaScript.
That was another problem you sorted out, we are looking at different issues, my WebCombo is outside a grid, inside a Panel on a Web Form, I haven't change many properties on the control, as you can see down:
this.WebComboParty.Editable = true; this.WebComboParty.EnableXmlHTTP = true; this.WebComboParty.ComboTypeAhead = Infragistics.WebUI.WebCombo.TypeAhead.Suggest; this.WebComboParty.DataTextField = "ShortName"; this.WebComboParty.DataValueField = "CCode"; this.WebComboParty.InitializeLayout += new Infragistics.WebUI.WebCombo.InitializeLayoutEventHandler(WebComboParty_InitializeLayout);
No, I did NOT synchronize the files. The only thing that I did to get it to work was to change the browser attribute on the grid from "Xml" to "Auto". This allowed things to work correctly.I gave the report between the good and bad machines to assist the developers in understanding why the "Xml" setting does not work on particular machines. I did nothing to actually move files around. I don't know if it will be useful or not but it's better to have too much information instead of too little.
Thanks for looking into this.