‎2009 Sep 08 8:24 AM
Hi
I am trying to edit test partner script from eca script, but i am getting one error 'ecatt error ECATT_STORE_BLOB(2)
saving of blob denied for security reasons. you may not be in the edit mode of ecatt ' when i click on ok button it is telling error during RFC connection and whatever changes i made in test partner is not saved.
How to solve this problem. Please help me.
‎2009 Sep 08 10:51 AM
Hi,
you may not be in the edit mode of ecatt ' when i click on ok button it is telling error during RFC connection and whatever changes i made in test partner is not saved.
1.You have opened the ecatt in display and editing the test partner , in this case above problem is shown.
please open the script in change mode and edit the test partner scripts.
best regards
vinay
‎2009 Sep 08 10:51 AM
Hi,
you may not be in the edit mode of ecatt ' when i click on ok button it is telling error during RFC connection and whatever changes i made in test partner is not saved.
1.You have opened the ecatt in display and editing the test partner , in this case above problem is shown.
please open the script in change mode and edit the test partner scripts.
best regards
vinay
‎2009 Sep 08 10:58 AM
Hi
Still i am getting the same RFC connection error, but this time i am not able to edit the script when i click on script it has opened the test partner and i am getting the error like 'import: failed to load/ parse xml data' and when i click on ok button i am getting 'error during RFC connection'.
‎2009 Sep 08 7:55 PM
If you need to use Test Partner in integrated mode, then two additional databases are required:
TP_EDIT.mdb for creating and editing Test Partner scripts
TP_EXEC.mdb for executing Test Partner scripts
Maintain DSN entries also for the same.....
Unlike stand-alone mode, these databases are not created during installation of Test Partner automatically and hence have to maintained/created manually....
‎2009 Sep 09 4:31 AM
Hi
Database already created. Still i am getting the same error.what could be the reason?
‎2009 Sep 09 6:50 AM
Is it working fine in the standalone mode?
Refer to the below checklist for trouble shooting:
1) Maintenance of DSN settings to the databases - TP_EDIT and TP_EXEC
2) Maintenance of R/3 connection parameters
3) Refer eCATT Security guide
4) Refer OSS note - 519858
Please note that for an integration Scenario, the connection and user information is required so that appropriate rights are established automatically.
Hope this helps!
‎2009 Sep 10 4:06 AM
Hi prasad,
whatever settings u told me to do we have already maintained. The problem is sometimes we are able to make changes in test partner script through tag library(in ecatt). but, sometimes it is throwing some error like 'RFC error ECATT_STORE_BLOB(101)'. So we need to resolve this problem. Do u have any idea or have u faced this type of error before?
Please help me to resolve this problem.
‎2009 Sep 10 6:21 AM
Hi Shyja,
We used to have tough time while workign with Test Partner and eCATT. Most of the times we used to delete and create new copies of the 2 TP mdb files to resolve the isues. Hope it would help u as well. Let me know if this worked.
Regards,
Justin
‎2009 Sep 10 6:26 AM
Hi prasad,
I tried with deleting and creating new databse access still i am getting the same error.
‎2009 Sep 10 8:09 AM
Dear Shyja,
I did not work extensively on Test Partner with eCATT nor did I encounter this error before.
If this issue is arising for only some of the scripts then have a good look at them and compare it with the ones that are working fine.
If this issue is arising once in a while and for all the scripts then ... there must really have been some serious RFC connection issues during that time.
Hope I could be of some help
‎2009 Sep 10 8:11 AM