InfoPath Dev

 I am trying to run Rules Injector 5.1 but I am receiving an error that I do not understand:

Removed the trustSetting attribute
Adding a file reference to Qdabra.Tools.RulesLibrary.dll
Adding a file reference to QdabraRules.xml
Adding a file reference to QdabraRules.xsd
Adding xsf2:managedCode node
scriptLanguage attribute already present, skipping
Creating the QdabraRules data object
Copying C:\Program Files (x86)\Qdabra Software\Qdabra Rules Library (Trial Version)\Browser\Qdabra.Tools.RulesLibrary.dll to C:\Users\q0pqxq7l\AppData\Local\Temp\ifkyfer0.zjz\Qdabra.Tools.RulesLibrary.dll
Copying C:\Program Files (x86)\Qdabra Software\Qdabra Rules Library (Trial Version)\QdabraRules.xml to C:\Users\q0pqxq7l\AppData\Local\Temp\ifkyfer0.zjz\QdabraRules.xml
Copying C:\Program Files (x86)\Qdabra Software\Qdabra Rules Library (Trial Version)\QdabraRules.xsd to C:\Users\q0pqxq7l\AppData\Local\Temp\ifkyfer0.zjz\QdabraRules.xsd
Adding an entry for the QdabraRules data connection to sample data
Injection complete.
Uma exceção foi acionada pelo destino de uma chamada.

The last sentense can be translated by "Exception has been thrown by the target of a call".

qRules 5.1 Trial was successfully installed and this form was running previously with qRules 4.3 Trial without any problem. As the old version has expired, then I deinstalled it and instlled the new versio 5.1.

My environment is Windows 8 + InfoPath 2010.

Any idea what is wrong ?

Best regards,

Hi,

I'm sorry you've run into issues. Would it be possible to include your form in the next reply, by using the Options tab?

We'll take a look and see what we find.

Thanks!

 Hi Ernesto,

please my form attached.

 Hi - the library we are using to extract and recompress the form files is having an issue with some of the characters in the template name. Can you try renaming it to something without any special characters to inject it, and then you can name it back to your current file name? I'll file a bug to look into other options we may have for handling this better.

 Hi Hilary,

Replacing special characters from the template name did work fine. I did not have this kind of issue in the previous release.

 Thanks a lot for your support.

 Best regards, 

 Thanks for letting me know - I've filed a case on it and we'll investigate further.

 Hi - what version were you using prior? I just tried to inject the same template with 4.3 and had the same error.

 Hi Hilary,

I was using 4.3 before and I do not remember to rename the template prior the injection.

Best regards,