IView error in XML Forms

Hello, I am currently working on the following tutorial for XML Forms: http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/creating xml forms 6.0
I have created the forms in XML. However, when I save my project, I get a message which says, "The consistency check reported errors or warnings. Do you want to Save anyway?", to which I hit "Yes". Then I went to "Content Administration" > "Portal Content" > "temp" and created an iView named "News Authoring". I did apply all the 4 settings mentioned in the tutorial. Then when I preview the iView, I get a message which says: "Item not found - /documents/myTest1". (myTest1 is the name of my project)
I checked under "/documents" and I could not see "myTest1". I am a bit new to iViews and Forms and hence I am not able to identify where exactly I am going wrong. Can anyone please help me?
Sincerely,
Sri

Thanks for all your help Patrick. I did go to "Documents" and create the folder. So now, when I preview the iView, I don't get any error message. I am working on XML Forms because I need to design an XML Form which accepts input from the user. When the user clicks on the "Send" button in the XML Form, the data needs to be sent by email as well as saved. Can you please point me in the right direction? Once again, thanks for all your valuable time and help.
Sincerely,
Sri
P.S. I have also created a seperate thread for this particular project I am working on. Thanks.

Similar Messages

Runtime error in XML form

Hi experts,
I have created xml form in XML form builder. One of the DataSchema is to browse document from KM Content but i got and error when try to browse the document. The error is:
Runtime Error
An exception occured while processing the request.
Additional information: null
Exception ID = 709f0fad-331d-2e10-a4b7-9257c0f4c0ed
Runtime Error
An exception occured while processing the request.
Additional information: null
Exception ID = 719f0fad-331d-2e10-ac94-9257c0f4c0ed
We are using SAP Netwever Portal 7.01EHP1. Please help me to solve this problem. TQ.
Rgds,
Nanie

we got our problem solved with Note 1534667 - NullPointerException when trying to preview/save an XML Form

Error in XML Forms Builder

Dear all,
I am trying to create News form in XML forms builder but XML form builder persitently throws following error.
Error: The edit form does not contain a save button or link
Warning: The name property is not referenced. A GUID will be used as the XML file name.
what may be the reason.
Regards,
Murali

Hi
1) data schema not expanding ?
check ur JRE version installed on ur computer.
some JRE version doesnot support XML Forms builder functions.
my JRE version is 1.5.0.70. It really works here .
upgrade or degrade the version of JRE in ur computer will solve ur problem.
2) Error: The edit form does not contain a save button or link
Warning: The name property is not referenced. A GUID will be used as the XML file name.
This is something to do with u.
have a look at the manual how to create the XML forms builder onceagain will solve ur problem.
Check these links:
http://help.sap.com/saphelp_nw04/helpdata/en/8f/fe743c74fa6449e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3f9a090-0201-0010-d4bb-bb3fc5e91cc5
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee639033-0801-0010-0883-b2c76b18583a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/7f99a69d-0701-0010-1783-cf847ec929f8
Regards,
Vijay.
Edited by: vijayakumar kanniah mohan on May 2, 2008 10:05 AM

Error in XML Form

Hi,
   I have created XML forms.After creating when im executing the forms im getting the following error:
XML - Forms
Error applying XSL stylesheet to XML
com.sapportals.wcm.WcmException: com.sap.engine.lib.xml.util.NestedException: org.w3c.dom.DOMException: Cannot append a text to a document node. -> org.w3c.dom.DOMException: Cannot append a text to a document node.
     at com.sapportals.wcm.service.pipeline.Pipeline.handle(Pipeline.java:284)
     at com.sapportals.wcm.service.pipeline.XSLTPipeline.handle(XSLTPipeline.java:118)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformer.pipeIt(Transformer.java:133)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformer.transform(Transformer.java:105)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformer.transform(Transformer.java:77)
     at com.sapportals.wcm.service.xmlforms.transformation.HtmlGenerator.getHtmlStream(HtmlGenerator.java:122)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:391)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:157)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.renderItemOrTemplate(Transformation.java:274)
     at com.sapportals.wcm.app.xmlforms.EditServlet.doGetAction(EditServlet.java:331)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doGet(XFBaseServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.service(XFBaseServlet.java:134)
     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:331)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
So please help me out in this error.
Regards
Ramalakshmi.S

Hi Ramalakshmi,
it is hard to help you by just reading your error message - but:
It seems that you mapped an XML node to some text control in your form.
Could you remove all mappings and try again? If it works, please add your mappings step by step and see when the error occurs.
HTH,
Carsten

Hi i am getting error in xml form builder

hi
i created edit,renderlistitem,show i haveadded buttons from extras-buttons
i am getting error as
Error:Edit form doenot contain save button or link
what could be the reason how to solve it
pls reply

Hi,
Have you gone through the link <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee639033-0801-0010-0883-b2c76b18583a">XML Form Builder</a>, if not read this. This link will help to do your requirement. Still you have any doubts, i'll help you.
Regards,
Venkatesh. K
/* Points are Welcome */

Error in XML form builder application

Hi SDN,
I have created a form builder application. I am able to create items from the application. But when i try to edit or delete the item...From the edit option if I try to save or preview or cancel or reset ....it is throwing the following error message
Runtime Error
An exception occured while processing the request.
Additional information: Exception during PageProcessorComponent.doContent()
Exception ID = a0d623c1-d35e-2b10-8ab7-f6c10479e59b
How to rectify the following issue....
Regards,
Ganesh N

Hi,
I have also encountered this problem the first time I did XML form builder.
A simple restart of my portal solved the problem.
Fabien.

Error in XML form builder

Dear Experts
When I am opening XML Form builder, both my form builder window and the EP window are closed.
Appreciate your response.
Regards
Shanmukha Rao Banisetti

Hi Shanmukha,
Login to the portal with administrator rights.
Replace the url with
http://host:portnumber/irj/go/km/docs/etc/xmlforms/xfcheck/xfbuildertest.html
You can access the XML form builder environment check.
Run the application and see if you miss something.
Good Luck!
Sandeep Tudumu

Problem in XML Form Builder development

I am developing some KM Navigation iView template with XML Form Builder . I create a label , when it be clicked , relative files will be download to local PC. But the caption of the label is the complete path of the file, not "file down" which I expected.
I need help, Regards.

Sonal,
You can check
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/fe743c74fa6449e10000000a11402f/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee639033-0801-0010-0883-b2c76b18583a
James

XML forms and KM folders

i want to enable users to create 3 forms which are saved to a folder where administrators can approve them. however the users shouldn't be able to see what is in the folder because it is likely to contain forms submitted by other users.
the only way i can see of doing this is to create a url iview containing the xml form (edit view). the url string contains the path to the folder where the forms are stored .i.e. /documents/client_forms/
but this is a bit messy and leaves us having to maintain the url in each environment.
i thought the com.sap.km.cm.xmlformedit iview was going to do the trick but you can't specify where the form is saved.
is there any other iview template which will do this? can i create a KM navigation iview with a null renderer or something so that it only shows the create forms associated with the folder and not the actual contents?

Hi,
Yes, you can create a custom layoutset and within it a custom Collection renderer that doesn't show any resources, just the create xml commands. copy the NewsExplorer layoutset and the NewsCollectionRenderer. in your new collection renderer set the properties: Folders Selection, Files Selection, Links Selection to Off, that way it won't show any resource. assign this collection renderer to your new layoutset instead of the original one and use it in your KM navigation iview.
Best regards,
Avishai Zamir

Error writing output with iview for xml form builder

Hi,
I created a Xml Form Builder's project in which I developed an "Edit" and "ListEdit" sheet.
I also created an iview for theese in which the code link is:"com.sap.km.cm.xmlform",and the field for Style Sheet for List and for single item are set up correctly,but when I tried the preview the following error message happened:
com.inqmy.lib.xsl.xslt.XSLOutputException: Error writing output. -> org.w3c.dom.DOMException: Root Element is already present, cannot be appended as a child.
could someone help me?
thank's a lot!
Nick.

Hi,
Now I'm confused,what do you mean with create new data? Are users editing existing documents
(as if they go to a document example.xml > edit) or they are creating new documents (as if they go
on folder > new > forms)?
The problem is, in both cases a user would need read/write permissions.
The normal flow content (data) is created in KM is as follows:
1. user is assigned to a role
2. role contains KM Navigation iView
3. KM Navigation iView executes com.sap.km.cm.navigation component
4. user chooses New > Form UI command (edit_xml_forms)
5. edit_xml_forms UI command executes its code (com.sapportals.wcm.rendering.uicommand.cm.UIXMLFormsCreateCommand) and open xml edit for the user
6. user fill the form and click Save, form is created into folder
For what I understood so far, your requirement basically asks you to go directly to step 5, it is
possible to pass a URL that goes directly to step 5, the UI command button, but if you do that
you won't have a context, so chances that it will work are slim, since a context is required to
fill the parameters asked by the app (like folder, user, permissions, etc). Even though, in some cases you can
still pass the parameters via post in the URL but you must know which service/parameters the
app asks for it, also a URL is static...
That was the create scenario, I think it's more cons than pros, users would still be
able to bypass the URL iView created for that, I'd suggest evaluating again if it's really
a problem having users access cm to manage data
kind regards,
Rafael

Error in news created in XML Form Builder

Dear Experts
I have created news in XML Form builder (three forms edit, rendered list and show). Created two iviews NewsExplorer and NewsBrowser.I have exposed these iviews for relevent users. Now the problem is the edit for and the show form of the XML news is not working for few users. While opening the edit form and show form for few users it is giving the below portal runtime message.
BEGINING OF ERROR MESSAGE----
Access denied (Object(s): com.sap.portal.system/security/sap.com/NetWeaver.KMC/low_safety/com.sap.km.cm/components/xmlformpreview).
END OF ERROR MESSAGE----
Appreciate your response.
Regards
Shanmukha Rao Banisetti

Try adding everyone group to the low_safety security zone...

Error after enabling lifetime on XML FORMS.

Hi all,
Ive created my article (XML FORMS) that was working fine. However, after add the lifetime properties (validfrom, validto) into the form, a message error Resource cannot be displayed with XMLResourceRenderer is showed when a new article is created. Does anyone know what could going wrong?
Any help will be appreciated,
Alcides Flach

Hi Alcides,
   In this folder, where you have created these xml files by mean form builder, do you have other kind of documents not created with form builder ?
   If you create other folder and then within it you create xml documents (form builder) after that display them using KM Navigation iview with a suitable layout set, do you have the same problem ?
   Have you tried to restart this server ?
   At last, you can enable debugging settings option in System Administration->System Configuration-KM-CM-User Interface-Settings-Advanced Options-Debuggings Options-edit and enter you user-id. After that refresh you browser.
   After that, when launch km navigation iview you are going to see a renderer link.
   Try with this link:
   https://www.sdn.sap.com/irj/sdn/thread?threadID=110919
Patricio.

Xml forms - Error handling HTTP request

Hello,
We have installed portal 6.0
I've made some forms with the xml form builder, imported them into IViews (KM navigation IView) and assigned the IViews to a role
The Iview shows the RenderListItem form
Every Iview (RenderListItem form) has a "new item" button
Every record of the iview has a edit-delete action
When I press the "new item" button or the edit button (or save button) I get the following error:
Error handling HTTP request. Check the log file for more information.
java.lang.RuntimeException: Context is unavailable!
     at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMConnection.(DMSRMConnection.java:83)
     at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMR3FunctionCalls.getGenericValueList(DMSRMR3FunctionCalls.java:6532)
     at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMR3FunctionCalls.getLaboratoryList(DMSRMR3FunctionCalls.java:6360)
     at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMLaboratoryValueProvider.getAllowedValues(DMSRMLaboratoryValueProvider.java:79)
     at com.sapportals.wcm.service.propertyconfig.config.MetaName.getAllowedValues(MetaName.java:781)
     at com.sapportals.wcm.service.propertyconfig.config.MetaName.allowedValueIterator(MetaName.java:472)
     at com.sapportals.wcm.service.xmlforms.ResourceProperties.appendAllowedValues(ResourceProperties.java:713)
     at com.sapportals.wcm.service.xmlforms.ResourceProperties.mergeProperty(ResourceProperties.java:682)
     at com.sapportals.wcm.service.xmlforms.ResourceProperties.mergePropertiesIntoDom(ResourceProperties.java:611)
     at com.sapportals.wcm.service.xmlforms.transformation.HtmlGenerator.getHtmlStream(HtmlGenerator.java:116)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:391)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:336)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:188)
     at com.sapportals.wcm.app.xmlforms.EditServlet.doGetAction(EditServlet.java:165)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doGet(XFBaseServlet.java:241)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doPost(XFBaseServlet.java:261)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.service(XFBaseServlet.java:134)
     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:331)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
This error doesn't always appear, there are times that the portal works correct and when I can add items, edit them and save my changes
Does anyone have an idea where the error comes from? In what direction I have to search? How I can solve this problem?
Thanks in advance, points will be distributed for helpfull answers

Hi,
I didn't place a save button on the RenderListItem but on the Edit form so this couldn't be the issue...
I solved the error I got when I wanted to save my form
The edit and delete buttons also work correct...
I only get the error mentioned above when I press the "new form" button, I created that button with the CreateXMLForms action group that I added in my Collection Grid renderer settings (option collection command group)
Then I changed my form availibility (System administration ->system configuration ->KM->CM->form based publishing->form availibility->folder settings)
I created the following folder settings:
foldername//priority//path//forms to exclude//forms to include
library//10 //documents/testlibrary//Smarties, QnA,SAP_APP_News//library
News //10 //documents/News//smarties, library, QnA// SAP_APP_News
QnA //10 //documents/testQuestionAnswer// SAP_APP_News, smarties, library //QnA
Smarties //10 /documents/testSmarties
Did I do something wrong here? What can cause this error? In what direction should I search?

Since installing the latest update, Firefox will not load; it gives me the following error -- XML Parsing Error: not well formed.

since installing the latest update, Firefox first operated with some errors but now will not load at all; it gives me the following error --
XML Parsing Error: not well formed
locations chrome://browser/content/browser.xml
Line Number 1191, column 20:
utton id="back-forward-dropmarker" type="menu" chromedir="&locale.dir;"-------------------
please note that the words "utton ID" are exactly as the error message gives it; and at the end of the message there are exactly 19 hyphens.
I don't know why this faulty code is referencing things to do with "chrome"... the Chrome browser is not installed on this PC or anywhere on our network.
Also, this is not the first problem I had after clicking Firefox's prompt for the latest update. Before Firefox retreated into this error message, it was loading but running with some faults...
1. the bookmark symbol was not appearing on the right hand side of the URL line, so I had always to click on "bookmark this page", after which the bookmark symbol did appear; however I don't know if the bookmarking function worked properly.
2. the back and forward buttons were not highlighted, as if I had not come from a previous page; so once I clicked on a link to a new page I could not go back to where I came from because Fiefox thought I hadn't come from anywhere.
3. there may have been other errors, but I did not find them.
How do I reinstate my Firefox program to work properly please? do I have to download the latest version and reinstal? if so, do I have to remove the old version first? or is there a fix?
Even to write this message I have been forced to use (yuk -- I don't like to say this!!!) Internet Explorer. So please -- I need help urgently.
Thanks,
NOEL

Some how I solved my problem by opening a user account and downloading Firefox 4.0 beta and installing it, I did try it, worked fine, so I did close the user account and did go back to my own account(switched user), the main page that I had problem with Firefox which would not open, I dabble click on Firefox it start working again!! I hope that solves your problem too.
firefox will not open, it gives me this cod and would not turn off, Error on switching in renew: NS_ERROR_UNEXPECTED, Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref] id: none

Error in Browser field of XML Form

Hi All,
We have recently upgraded our portal system from NW 7.00 (SP23) to NW 7.01 (SP09).
Post upgrade we are facing an issue in XML forms for file browser element.
On the XML forms we have an element u201Cfile browseru201D which we use for attaching documents as attachments in the XML forms.
After upgrade, when we select a document using this element u201Cfile browseru201D, the file path is getting uploaded in the field without the file name. Hence after saving the XML forms when we try to display it and open the attachment in the XML forms, it is giving the following error.
The folder you are looking for has no displayable content. You can try one of the following:
u2022 Access the folder using the Navigation user interface.
u2022 Access the folder as a Web folder. Your operating system and browser dictate whether or not this will work.
Example : Suppose we are attaching a file f1.xls in /documents/images folder, the path captured in the browser textbox is /documents/images (it should be /documents/images/f1.xls).
This was working fine before the upgrade to NW 7.01 SP09.
Our system is already running LIVE on production and we are facing major issues due to this problem. Kindly provide a solution at the earliest.
Regards,
Nitesh

It was a bug .
SAP released two new patches
EPBC209P_10-10005895
SAPJTECHS09P_16-10005886
issue resolved after patch application.
Regard,
Nitesh

IView error in XML Forms

Similar Messages

Maybe you are looking for