ADS: Badly formed SStringKey found in StringKey

Question

Hello,
I have customizing the application TRM. There I'm using the the formular "ISR_FORM_SPI1". The formular call in the application "Tax Office Cockpit" from the taxagent in the Enterprise Portal. If I'm calling the application in language "en" it works fine. But If I'm calling it in languge "de" the webdynpro dumps with "WebDynpro Exception: Der Aufruf des ADS schlug fehl. Informationen zur Ursache finden Sie im error.pdf auf dem Applikationsserver".
I found with debugger the error message from ADS:
Begin operation: Render, elapsed time = 2 ms.#  
End operation: Render, elapsed time = 1763 ms.#  
Begin operation: Render Log, elapsed time = 1763 ms.#  
End operation: Render Log, elapsed time = 1818 ms.#  
om.aific error information:#   a file-system error has occurred (^0)#  
INTERNAL ERROR! Badly formed SStringKey found in StringKey::GetKey().#   ;
[Error Log file "2008.09.19.103624SAFPMSTURM.pdf" written  to /usr/sap/HAL/SYS/global//AdobeDocumentServices/renderErrorLog/errorFiles]#
In the 2008.09.19.103624SAFPMSTURM.pdf written:
Severity Message Id Date/Time Description
Warning 29203 19/09/08 10:36 AM Invalid node type: tags
Warning 29323 19/09/08 10:36 AM The fault occurred on line 2.
(and so on same message 9x)
An expressionless information...?
If I use an own formular (e.g. ZFORM) the error is:
  Processing exception during a "UsageRights" operation.#
  Request start time: Thu Sep 18 18:33:18 CEST 2008#
  com.adobe.ads.exception.FailedCreationException: ##
  Specific error information:#a file-system error has occurred (^0)#
  INTERNAL ERROR! Badly formed SStringKey found in StringKey::GetKey().###
  Exception Stack Trace:#
  com.adobe.ads.exception.FailedCreationException: ##
  Specific error information:#
  a file-system error has occurred (^0)#
Who know an answer of the two problems?
Reguards
Maik

Answer 1

Workaround
This may not work for all, but this is something that seem to work for us.
Instead of loading the pdf directly from the server like we normally do (using Response.Redirect or Server.Transfer etc).
Let the html page load and in the onload of the html page, call a javascript to set the window.location to the server path of the pdf and then when the pdf downloads and displays, it seem to work fine for us on all versions.
This is the general idea and the way I did in .Net was to use ClientScript.RegisterStartupScript and set the window.location as the pdf path instead of where the pdf was getting loaded from the server.
Hope this helps someone.