cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error opening Adobe Form after changes made

Former Member
0 Likes
3,506

Hello experts,

I'm getting an error when trying to open an Adobe Interactive form in the web browser after making some changes to the form in transaction SFP.  The error message is  "WebDynpro Exception: The ADS call has failed.  You can find information about the cause in the error.pdf on the application server".

We have several other Adobe forms on our system and they are all working fine - so ADS is running and working correctly.

I was able to get copies of the error log files specified in the message but they all have "No Errors Reported".

This started in our DEV system after making the change to the form.  The change was just adding a few lines of Java script - extending an IF condition that was already in there.  I tried moving the changes to QAS to see if the issue was specific to the DEV system, but the error is occurring in QAS now too (the form was working in QAS before transporting the changes).  The error is not user or computer specific - happens for all users, all web browsers, etc.  The SAP ID I am using in DEV has SAP ALL, so shouldn't be a security/authorization issue.

I have tried the following to resolve the error, but none of these have worked:

- removed the code that was added to the form

- used version management to retrieve the previous version of the form in DEV

- downloaded the form from Production and uploaded back into DEV

- restarted Java and ABAP services on the application server

- stopped and restarted applicable services in transaction SICF (ADS, the form service itself)

- saved/activated/compiled the form, interface, and webdynpro components (multiple times for each)

- deleted the form and interface and uploaded the Production versions to replace them

We've made similar changes to other interactive forms in the system lately and they are all still working correctly.  Only this one form has the error.

I really need to be able to make the changes to this form.  Any ideas on how to correct this error?

Thanks,

Ryan

View Entire Topic
Florian
SAP Champion
SAP Champion
0 Likes

Hi Ryan,

With what designer is the form been created in the past.

I read somewhere, that there are problems, if the designer differs in the version.

Did you already tried to install an older version of the formbuilder and get a version back.

That could perhaps solve this problem.

I'm sorry, I do not find the content where this issue was discussed, because I didn't thought this would happen to SAP-AdobeForms.

Regards

Florian

Former Member
0 Likes

Florian,

Thanks for the reply.  I'm not sure what version of designer was used to create the form initially.  Some of my co-workers have also been working on other forms in the system with no issues - I'll check if they are using a different version than me and let you know if that makes a difference or not.

Ryan

Former Member
0 Likes

Please check your form interface carefully. Looks like some unknown data type is referred in there. Also can you please try checking if any file is being created on the application server with name error.pdf ?

Try testing the service standalone in SICF tcode - /sap/bc/webdynpro/sap/zadobe_ex_form/

Former Member
0 Likes

The form interface is actually pretty basic.  The import/export parameters all reference standard SAP data types and they do exist in the system.

Testing the service via SICF produces the same error - it opens a web browser session to the same link/url.

The error.pdf portion of the message is a bit misleading, it actually ends up with a different file name than that ( I found that in another thread), it ends up with a date/time stamp and user ID as part of the file name.  We were able to retrieve the files from the server, there is one error file generated each time we call the form.  They all just have "No Errors Reported" though.

Former Member
0 Likes

I did check the designer versions - there are a couple of us working on forms in the system and we do have different versions of the designer installed (8.0 vs 9.0).  I had my co-worker try reloading the form using the older version, but the error is still there.