Error while exporting PAR file

Hi,
I am getting an error "Build of project failed" while exporting a PAR file to the project folder and it is showing that "The project was not built due to classpath errors (incomplete or involved in cycle)." I am very new to this technology, so please help me in this.

Check if the required JAR files under /dist/lib or /dist/private/lib are added in the project structure.
Refer http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d58bb490-0201-0010-64a1-9e5165e5dbac?QuickLink=index&overridelayout=true
~ Dhanz

Similar Messages

Error while deploying PAR files for JSPDynPage & HTMLB

Hi,
I am facing following error while exporting the PAR file.
PAR upload failed:
*Please make sure the server ***** is running. HTTPS protocol is not supported, please ensure this server is not using HTTPS.*
I checked with the server. It is running fine.
Please help..
Regards,
Niraj

hi niraj,
Login into portal System Administration->support->portal runtime->Browse Deployment
select web-inf (Browse)-deployment(Browse) check you par file...
Other way around...
go to portal content -> create iveiw ->using Par (not using template)->select ur par file....and done..
Regards
parth

Error while importing PAR file from local system.

Hi Experts,
While importing PAR file into my NWDS, I am encountered by some strange error.
Please refer below screenshot for your reference.
After clicking on "OK" button of the above error popup, another popup emerge with different error, please find below the screenshot for this error.
Please let me know the reason and resolution of this error. It will be very helpful for me.
Thanks in advance.
Thanks and Regards,
sarvesh Agarwal

Hi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks,

Error while deploying .par file through system admin

I have tried to modify logon.par file but when I was try deploy that file again through system admin then I got this error...................
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com.sapportals.portal.ume.component.logon.SAPMLogonComponent.
Exception id: 10:19_11/05/07_0006_13454550
See the details for the exception ID in the log file
Please help me out I am using sneak preview 7.0
Detailed Error Log & Trace
=========================================================
Exception ID:08:55_11/05/07_0002_13454550
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.support.browse.default
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
     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)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonComponent of Portal Component com.sap.portal.support.browse.default because: Could not find implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:242)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 26 more
Caused by: java.lang.ClassNotFoundException: com.sapportals.portal.ume.component.logon.SAPMLogonComponent
Found in negative cache
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@3389d1]
Parent loader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@1b7a6fa]
References:
   not registered!
No resources !
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 30 more

Hi,
      Open ur PAR file then double click on PORTAL-INF -> lib->Select 2 jar files
         1.com.sap.portal.runtime.logon_api.jar
         2.umelogonbase.jar
Copy those jar file & paste in to lib in ur application.
Regards,
Senthil kumar K.

Error while importing par file

dear Experts,
i am facing a problem while importing par.bak file. the error message comes
"indexed store transactions did not commit properly"
Reason
sorry an error occurred creating new project
then once i click ok
i get the error
com.sap.portal.plugins.config-archiver caused exception during the "unpack" operation
any one has the solution for this

Hi ,
Are u trying to import with .bak extension ? If so please rename the file and remove .bak extension and try.
x.par is enough to import not x.par.bak.
Thanks,

Error While uploading PAR File into NWDS

Hi Experts,
I have been to this location:
Server(D)\usr\sap\P64(SID)\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
I have copied this file com.sap.portal.runtime.logon.par.bak and pasted on my desktop.
Changed the name to com.mycompany.portal.runtime.logon.par
I tried to upload the file to NWDS(File --> Import --> Par file) and I am getting the fallowing error.
http://imageshack.us/photo/my-images/853/error1un.png/
and when i click OK on above Error
i get this errors : http://imageshack.us/photo/my-images/571/error2v.png/
I am unable to upload the Par file did i miss something?
Regards,
Siva

Dear Siva,
that is indeed strange.
Still don't know if this could be an issue with your NWDS or the PAR itself.
So let's do 2 tests
===============================================
TEST NR. 1
Let's try and check the NWDS first by creating a custom PAR.
Don't worry, it's easy.
Just open your NWDS and go to the top menu
File > New > Project
Inside the popup window that will open please choose
Portal Application (on the left) and Create a Portal Application Project (on the right)
Then give any name you would like (no spaces or dots, etc...)
You now have a Portal project created on NWDS ( you will see a folder on the left side with your project name)
Click on that folder with your LEFT mouse button and choose EXPORT
Choose PAR File
Choose your Project
Choose a path where you want your PAR file to be saved. (uncheck the deploy PAR file, but check the include the source code).
And click Finish.
Now delete the project you have created (by clicking on the folder with your LEFT mouse button again, but chose DELETE project)
Now you're ready to re-import the PAR file.
===============================================
TEST NR. 2
Maybe your standard PAR file that you've downloaded doesn't have the source code included or is corrupted.
Please try to open it with a ZIP program and check what type of structure/files you have there.
Have you also checked your NWDS log ?
You could also share here that log, so that I can better help you.
Kindest Regards
/Ricardo

Error while exporting metadata file /iam-features-ldap-sync/LDAPUser.xml

Hi All,
i am trying to export /iam-features-ldap-sync/LDAPUser.xml metadata file with the weblogic properties mentioned below
# Weblogic Server Name on which OIM application is running
wls_servername=oim_server1
# If you are importing or exporting any out of box event handlers, value is oim.
# For rest of the out of box metadata, value is OIMMetadata.
# If you are importing or exporting any custom data, always use application name as OIMMetadata.
application_name=OIMMetadata
# Directory location from which XML file should be imported.
# Lets say I want to import User.xml and it is in the location /scratc/asmaram/temp/oim/file/User.xml,
# I should give from location value as /scratc/asmaram/temp/oim. Make sure no other files exist
# in this folder or in its sub folders. Import utility tries to recursively import all the files under the
# from location folder. This property is only used by weblogicImportMetadata.sh
metadata_from_loc=@metadata_from_loc
# Directory location to which XML file should be exported to
metadata_to_loc=D:/MDS
# For example /file/User.xml to export user entity definition. You can specify multiple xml files as comma separated values.
# This property is only used by weblogicExportMetadata.sh and weblogicDeleteMetadata.sh scripts
metadata_files=/metadata/iam-features-ldap-sync/LDAPUser.xml
# Application version
application_version=11.1.1.3.0
i get the following error
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting export metadata script ....
Please enter your username [weblogic] :weblogic
Please enter your password [welcome1] :
Please enter your server URL [t3://localhost:7001] :t3://hostname:7001
Connecting to t3://hostname:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'OIMDOMAIN'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBea
n as the root.
For more help, use help(domainRuntime)
Problem invoking WLST - Traceback (innermost last):
File "C:\Oracle\Middleware\Oracle_IDM1\server\bin\weblogicExportMetadata.py";,
line 22, in ?
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 134, i
n exportMetadata
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 568, i
n executeAppRuntimeMBeanOperation
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 538, i
n getMDSAppRuntimeMBean
UserWarning: MDS-91002: MDS Application runtime MBean for "OIMMetadata" is not available. "exportMetadata" operation failure.
i have exported these files multiple times, it never gave an errror, but this time i see this error, please help.
Thanks in advance

Glad that worked.
Working with MDS, another way is to use the EM console for exporting/importing data from/to MDS. This I find lot easier rather than working with the OOTB script.
Steps are:
http://ADMINSTRATION_SERVER/em
Navigate to Identity and Access, oim. Right-click and navigate to System MBean Browser.
Under Application Defined MBeans, navigate to oracle.mds.lcm, Server:oim_server1, Application:oim, MDSAppRuntime.
To export the configuration files:
•     Click the Operations tab, and then click exportMetaData.
•     In the toLocation field, enter /tmp or the name of another directory.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This exports the file specified in the docs field to the directory specified in the toLocation field.
To import the configuration files:
•     Click importMetaData
•     In the fromLocation field, enter /tmp or the name of the directory in which you have the configuration files.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element. For example, /db/oim-config.xml.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This imports the file specified in the docs field to MDS in the toLocation field.
HTH

Error while uploading par file

Hi,
I am trying to upload par file for the first time. When I try to deploy the par file, I am getting message saying, 'Operation failed: Please make surethe server 'Myportal' (host:port) is running or check the log( sap-plugin.log) for more details'/
I have tried to open the portal http://host:port/irj/portal. I am able to open the portal and can login successfully also. This means that the portal is running ( Am I right ?).
I have tried to upload the par file directly from the portal using
system admin>support>portal runtime>Administration console--Archive uploader.
I got the error messages as given below.
INFO: Detected Portal Archive File: HelloProject.par
INFO: Deployment failed - exception caught: Application upload failed: HelloProject.par - more detail at: E:\usr\sap\IN1\JC01\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\HelloProject.par.log
Please guide me about what could be the pbm and how to solve this.
Thanks in advance.
Regards,
Vishnu Priya

Hi Vishnu,
Are you trying to upload a PAR file from the NWDS?
if then you need to configure the J2EE engine correctly before doing so
for that matter you need the port number and also have that the SDM password for deployement
Once these are ready ...go to the J2EE engine tab available on the bottom corner.And make sure the J2EE engine is working. or the server is up.Is this what you are looking for.....if yes.....just reply...I can continue with the deployment..
Regards
Arun

Re: Error while uploading par file .

Hi ,
When I m trying to uploading my par file i m getting this err pop-up .
par upload failed :
please check the log (sap-plugin.log) for more detail
2009-02-23_14-20-27
Application upload failed: P&G_Test.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: P&G_Test.par
     at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
     at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
     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)
Caused by: javax.naming.InvalidNameException: Character not allowed: '&' in 'P&G_Test.par'
     at com.sapportals.portal.pcd.pl.PcdName.checkComponent(PcdName.java:54)
     at com.sapportals.portal.pcd.pl.PcdName.checkComponents(PcdName.java:69)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:453)
     at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1221)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:502)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:663)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:668)
     at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeArchive(ApplicationRepositoryService.java:373)
     at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:299)
     ... 34 more
Thanks in advance

Hi,
The error shows clearly
> Caused by: javax.naming.InvalidNameException: Character not allowed: '&' in 'P&G_Test.par'
As suggested, rename the project, rebuild it and then upload the par to server. That should work.
Regards,
Harini S

Error while exporting .epa file to transport request

Hi Experts,
I got a problem while exporting the transport package to transport request. In the last step of the export process, I am getting a status message as
"Could not release BIPortalContent.epa to transport request ABCD900005; consult your system administrator."
Can anyone help me in diagnosing this problem? I could not get a solution for this and due to this, the export process is stopped. I have tried with different transport requests and different authorizations, but result is the same.
I would appreciate your help in resolving this issue.
Thank You.
Regards,
Murthy J N.

Hi Bala,
Yes, I am using CTS
and I have tried all possibilities but the export to the transport request is not successful.
Regards,
Murthy.

Error while importing .par file into NWDS

Hi Experts,
For my query I saw a similar thread in sdn forum. the link is given below.
/thread/382306 [original link is broken]
I have unzipped the par file and inside this there is no other par file. So I have to import this par file only.
Can anybody give some alternate way to resolve this.
Thanks a lot in advance.
Edited by: Srini on Nov 22, 2010 10:46 PM

Hi Experts,
Please reply on this.
Thanks a lot in advance.

Getting Error while exporting EAR file from Weblogic workshop 10.3

Hi All,
I have one Enterprise project with reference to one Web services web module.
When I tried to export web module it export correctly but when I try to export the Enterprise project then it throws following error.
!ENTRY com.bea.workshop.wls.ui 4 0 2009-04-15 11:14:12.801
!MESSAGE The selected archive: C:\RNEAR.ear does not exist.
!ENTRY org.eclipse.wst.common.frameworks 4 0 2009-04-15 11:14:13.035
!MESSAGE Extended Operation failure: org.eclipse.jst.j2ee.internal.archive.operations.EARComponentExportOperation
!STACK 0
org.eclipse.core.commands.ExecutionException: Error exportingEAR
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.execute(J2EEArtifactExportOperation.java:103)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizard$1$CatchThrowableRunnableWithProgress.run(DataModelWizard.java:211)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException: Error opening archive for export..
at org.eclipse.jst.j2ee.internal.archive.operations.EARComponentExportOperation.export(EARComponentExportOperation.java:66)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.execute(J2EEArtifactExportOperation.java:95)
... 10 more
Caused by: org.eclipse.jst.jee.archive.ArchiveSaveFailureException: java.lang.NullPointerException
at org.eclipse.jst.jee.archive.AbstractArchiveSaveAdapter.save(AbstractArchiveSaveAdapter.java:66)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.save(ArchiveFactoryImpl.java:114)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.saveArchive(ArchiveFactoryImpl.java:76)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.saveArchive(J2EEArtifactExportOperation.java:247)
at org.eclipse.jst.j2ee.internal.archive.operations.EARComponentExportOperation.export(EARComponentExportOperation.java:43)
... 11 more
Caused by: java.lang.NullPointerException
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.isEJBArchive(JavaEEArchiveUtilities.java:466)
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.refineForJavaEE(JavaEEArchiveUtilities.java:362)
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.openArchive(JavaEEArchiveUtilities.java:267)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.openArchive(ArchiveFactoryImpl.java:45)
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.openArchive(JavaEEArchiveUtilities.java:115)
at org.eclipse.jst.j2ee.internal.archive.EARComponentArchiveLoadAdapter.addModulesAndUtilities(EARComponentArchiveLoadAdapter.java:78)
at org.eclipse.jst.j2ee.internal.archive.EARComponentArchiveLoadAdapter.getArchiveResources(EARComponentArchiveLoadAdapter.java:54)
at org.eclipse.jst.jee.archive.internal.ArchiveImpl.getArchiveResources(ArchiveImpl.java:167)
at org.eclipse.jst.jee.archive.AbstractArchiveSaveAdapter.getArchiveResourcesForSave(AbstractArchiveSaveAdapter.java:74)
at org.eclipse.jst.jee.archive.AbstractArchiveSaveAdapter.save(AbstractArchiveSaveAdapter.java:40)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.save(ArchiveFactoryImpl.java:114)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.saveArchive(ArchiveFactoryImpl.java:76)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.saveArchive(J2EEArtifactExportOperation.java:248)
... 12 more
!SUBENTRY 1 org.eclipse.wst.common.frameworks 4 0 2009-04-15 11:14:13.035
!MESSAGE Extended Operation failure: org.eclipse.jst.j2ee.internal.archive.operations.EARComponentExportOperation
!STACK 0
org.eclipse.core.commands.ExecutionException: Error exportingEAR
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.execute(J2EEArtifactExportOperation.java:103)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizard$1$CatchThrowableRunnableWithProgress.run(DataModelWizard.java:211)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException: Error opening archive for export..
at org.eclipse.jst.j2ee.internal.archive.operations.EARComponentExportOperation.export(EARComponentExportOperation.java:66)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.execute(J2EEArtifactExportOperation.java:95)
... 10 more
Caused by: org.eclipse.jst.jee.archive.ArchiveSaveFailureException: java.lang.NullPointerException
at org.eclipse.jst.jee.archive.AbstractArchiveSaveAdapter.save(AbstractArchiveSaveAdapter.java:66)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.save(ArchiveFactoryImpl.java:114)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.saveArchive(ArchiveFactoryImpl.java:76)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.saveArchive(J2EEArtifactExportOperation.java:247)
at org.eclipse.jst.j2ee.internal.archive.operations.EARComponentExportOperation.export(EARComponentExportOperation.java:43)
... 11 more
Caused by: java.lang.NullPointerException
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.isEJBArchive(JavaEEArchiveUtilities.java:466)
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.refineForJavaEE(JavaEEArchiveUtilities.java:362)
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.openArchive(JavaEEArchiveUtilities.java:267)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.openArchive(ArchiveFactoryImpl.java:45)
at org.eclipse.jst.j2ee.internal.archive.JavaEEArchiveUtilities.openArchive(JavaEEArchiveUtilities.java:115)
at org.eclipse.jst.j2ee.internal.archive.EARComponentArchiveLoadAdapter.addModulesAndUtilities(EARComponentArchiveLoadAdapter.java:78)
at org.eclipse.jst.j2ee.internal.archive.EARComponentArchiveLoadAdapter.getArchiveResources(EARComponentArchiveLoadAdapter.java:54)
at org.eclipse.jst.jee.archive.internal.ArchiveImpl.getArchiveResources(ArchiveImpl.java:167)
at org.eclipse.jst.jee.archive.AbstractArchiveSaveAdapter.getArchiveResourcesForSave(AbstractArchiveSaveAdapter.java:74)
at org.eclipse.jst.jee.archive.AbstractArchiveSaveAdapter.save(AbstractArchiveSaveAdapter.java:40)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.save(ArchiveFactoryImpl.java:114)
at org.eclipse.jst.jee.archive.internal.ArchiveFactoryImpl.saveArchive(ArchiveFactoryImpl.java:76)
at org.eclipse.jst.j2ee.internal.archive.operations.J2EEArtifactExportOperation.saveArchive(J2EEArtifactExportOperation.java:248)
... 12 more
!ENTRY com.bea.workshop.webservices.export 2 2 2009-04-15 11:32:13.836
!MESSAGE Skipping Annotation Manifest Generation since control required classes are not on the build path.
Any help on this is really appreciable
Regards,
Kal.

Hi All,
problem is resolved for me.
After removing unnecessary jar from APP-INF/lib folder it resolve my problem.
Regards,
kal.
Edited by: kalyan Pasupuleti on May 17, 2009 10:28 AM

NWDS 7.0 Error during Quick PAR Upload and while trying Exporting PAR-File

Hello,
I am trying to use the functions "Export as PAR-File" and "Quick PAR Upload" in NWDS 7.0.
Unfortunately I got an error every time when I am trying to use this functions. I am using the package explorer in the Java perspectiv in NWDS for starting this functions. The error tells me the following:
"Unable to connect to the Portal"
"Operation failed: Please make sure the server "XY" is running or check the log (sap-plugin.log) for more detail"
Thats all.
When I am looking in the log-file I can read the following messages:
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: GET_VIEW:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: IS_VIEW_EXISTS:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: SIZE_OF_VIEW:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: READ_ENTRY:ALL]"
LOGIN.ERROR|null|| Login Method=[default] UserID=[user_Admin] IP Address=[192.168.xxx] Reason=[Cannot authenticate the user]
I have tried this with several users and their passwords. All of the users have admin-rights at least in the portal. One of them even in the SDM.
I can sucessfully deploy webdynpros from NWDS into the same Portal with this users.
We are using SAP Logon Tickets and SSO is configured working fine between Portal and backend.
We have imported Key Store File in NWDS unter Window --> Preferences --> Java Development Infrastructure.
And we are not using the NWDI.
Who knows why I cannot even export par-files? Are their any configurations missing?
Best regards,
Iris

It is mentioning about authentication.
check whether you have access to deploy directly or not ? maybe direct deployment into portal disabled .
I think you have to follow the procedure of checkout and activate procedure.
Can you clarify few things
1) Are you using NWDI Based Transports in your landscape?
Login Method=default UserID=user_Admin IP Address=http://192.168.xxx Reason=Cannot authenticate the user
http://192.168.xxx is it your development portal?
Did you clarify with admin people whether direct deployment disabled?
Koti Redd

EXPORT XFA error while writing XFA files

Hello Experts,
We are facing an error while exporting to PDF from BEx report.
We are on EP7 SP14. BI on SP16.
After the report is displayed and Export to PDF button is clicked, a new window opens which shows following:
1. Error:
Message: No message was provided.
Stack trace: java.lang.NullPointerException
at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
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:645)
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:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Message: EXPORT XFA error while writing XFA files
Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: EXPORT XFA error while writing XFA files
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:311)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
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:645)
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:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NullPointerException
at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
2. Message:
No metadata is available for "DISABLE_NAVIGATION":
<parameterList>
<param name="BI_COMMAND_TYPE" value="OPEN_DIALOG_DISABLE_NAVIGATION"/>
<param name="TARGET_DIALOG_REF" value="DISABLE_NAVIGATION"/>
</parameterList>
In this window, complete screen of report is displayed as an image instead of PDF.
Please let me know if anybody faced similar issue earlier.
It was working perfect earlier, but suddenly error started.
regards
Kedar Kulkarni

No proper findings, but issue resolved.
Problem i found that we got a domain change and service values were not refreshed until we apply new patch.
So when we applied patch level 6 on BI WEBAPP& BI BASE S URL for ADS got refreshed and we faced the issue.
After resetting the URL to new domain problem got resolved.
Regards
Kedar Kulkarni

Error "Encountered an error while exporting the data. View the lof file (DPR-10126)

Hello,
I would like to have sugestions and help to solve a problem in IS 4.2.
I've created a view from two tables, joined together with the key from each one.
Then i've binded the rule with the view (mentioned above) created and calculated score for it.
The calculation is successful, however when i try to export all failed data i have the following error:
"Encountered an error while exporting the data. View the lof file (DPR-10126)"
When exporting failed data from calculations made directly to the datasources i do not encounter any problem, but when i try to export all data to CSV file (not only the 500 results limit) i have this kind of error.
However, when i visualize the data from the view created, it is also possible to export to csv file.
Resuming, the error occurs only when exporting all failed data from the view.
Can anyone help with this issue?
Thx
Best Regards,

Hello,
Your information is correct.
I've just confirmed it in the 4.2 SP3 Release Notes and they specifically refer to this issue.
A user who has 'View objects' rights for the project and a failed rule connection cannot export the failed data. This issue has been fixed in this release.
Thank you very much for your input.
Best Regards,

Error while exporting PAR file

Similar Messages

Maybe you are looking for