Could not create mountpoint for SC

Hi..
For customising the ESS package I have installed and configured NWDI , Now after configuring the CMS when I try to "import configuration" I get the following error.(But some links are seen under the tracks in active and local dc's)
com.sap.tc.devconf.SyncException: Could not create mountpoint for SC in compartment saphr.com_ESSMSSCOMP_1: Could not create remote path /dtr/ws/ESSMSSTR/saphr.com_ESSMSSCOMP/cons/inactive/SCs/saphr.com/ESSMSSCOMP/_comp/TopLevelDCs/ (Internal Server Error [(pre||post)-condition failed: Internal Server Error]).
And when I try to delete the track(remove configuration) I get the following error
com.sap.tc.devconf.SyncException: Unable to remove local file or folder. Error when asking for folder item "D:\Documents and Settings\k.mukundan\.dtc\1\SCs\saphr.com\ESSMSSCOMP\_comp\": Getting VFS manager for client J2E_ESSMSSTR_D failed: Activity report (get open activities for current repository and user) failed: Internal Server Error
it was also written in some of the thread that it was the problem with 2004 server
Is there a solution?
Could some one please help me with this...
Thanks in advance

Hi Krishnagopal,
make sure you have the JDI roles assigned, assign yourself the Administrator and Developer role. see if this makes a difference.
Raj

Similar Messages

NW2004s SP9 Java Trial - "Could not create mountpoint for SC in ..."

Hi
I have installed the Sneak Preview NW2004s SP9 Java Trial on a W2003 Server Macheine and everything is looking fine.
When trying the Tutorial 2: Development with a Track it cames to the point where i have to Import a Development Configuration from the SLD. I get the error:
Could not create mountpoint for SC in compartment chynet.at_APPLICATION_1: Could not create remote path /dtr/ws/APPL/chynet.at_APPLICATION/dev/inactive/SCs/chynet.at/APPLICATION/_comp/TopLevelDCs/ (Internal Server Error [(pre||post)-condition failed: Internal Server Error]).
     at com.sap.tc.devconf.impl.DTRClientErrorMapper.toSyncException(DTRClientErrorMapper.java:65)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2758)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.createMountPointsForSCs(DevelopmentConfiguration.java:3046)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.goOnline(DevelopmentConfiguration.java:5207)
     at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:773)
     at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:698)
     at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:669)
     at com.sap.ide.eclipse.component.wizard.DevConfWizard.addDevConf(DevConfWizard.java:505)
     at com.sap.ide.eclipse.component.wizard.DevConfWizard.access$100(DevConfWizard.java:67)
Can anybody tell me what is going wrong or where i can investigate the error?
LG
Michael

Hi There !
Run SDM RemoteGui.
Log in.
Go to deployment tab.
Find sap.comtcdtr~dbschema.sda in root directory under SDM.
Adjust deployment configuration to Update deployed SDAs/SCAs that have any version.
Complete the wizard.
this works !
rajendra

Could not create mountpoint for SC error in during import configuration

Hi,
I have succesfully created a tack in NW7 and during the import of the configuration in developer studio I get the following error on the last step of import
com.sap.tc.devconf.SyncException: Could not create mountpoint for SC in compartment example.org_APPLICATION_1: Could not create remote path /dtr/ws/APPL/example.org_APPLICATION/dev/inactive/SCs/example.org/APPLICATION/_comp/TopLevelDCs/ (Internal Server Error [(pre||post)-condition failed: Internal Server Error]).
     at com.sap.tc.devconf.impl.DTRClientErrorMapper.toSyncException(DTRClientErrorMapper.java:65)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2758)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.createMountPointsForSCs(DevelopmentConfiguration.java:3046)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.goOnline(DevelopmentConfiguration.java:5207)
     at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:773)
     at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:698)
     at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:669)
     at com.sap.ide.eclipse.component.wizard.DevConfWizard.addDevConf(DevConfWizard.java:505)
     at com.sap.ide.eclipse.component.wizard.DevConfWizard.access$100(DevConfWizard.java:67)
     at com.sap.ide.eclipse.component.wizard.DevConfWizard$1.run(DevConfWizard.java:348)
     at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
     at com.sap.ide.eclipse.component.wizard.DevConfWizard.performFinish(DevConfWizard.java:346)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at com.sap.ide.eclipse.component.provider.actions.DevConfNewAction.run(DevConfNewAction.java:46)
     at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:229)
     at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
     at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1391)
     at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
     at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
     at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
     at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
     at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
     at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     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.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: com.tssap.dtr.client.lib.vfs.config.ConfigurationException: Could not create remote path /dtr/ws/APPL/example.org_APPLICATION/dev/inactive/SCs/example.org/APPLICATION/_comp/TopLevelDCs/ (Internal Server Error [(pre||post)-condition failed: Internal Server Error]).
     at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.assureRemotePathExists(RepositoryServer.java:230)
     at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2748)
     ... 47 more
Caused by: com.tssap.dtr.client.lib.deltavlib.DeltavException: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
     at com.tssap.dtr.client.lib.deltavlib.impl.PersistentResourceFactoryImpl.createCollection(PersistentResourceFactoryImpl.java:233)
     at com.tssap.dtr.client.lib.deltavlib.impl.PersistentResourceFactoryImpl.createCollection(PersistentResourceFactoryImpl.java:79)
     at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.assureRemotePathExists(RepositoryServer.java:216)
     ... 48 more
Caused by:
[VFS version: 7.00 645_VAL_REL 0010 (2006-08-26 16:27:43 CEST)] com.tssap.dtr.client.lib.vfs.config.ConfigurationException: Could not create remote path /dtr/ws/APPL/example.org_APPLICATION/dev/inactive/SCs/example.org/APPLICATION/_comp/TopLevelDCs/ (Internal Server Error [(pre||post)-condition failed: Internal Server Error]).
    at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.assureRemotePathExists(RepositoryServer.java:230)
    at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2748)
    at com.sap.tc.devconf.impl.DevelopmentConfiguration.createMountPointsForSCs(DevelopmentConfiguration.java:3046)
    at com.sap.tc.devconf.impl.DevelopmentConfiguration.goOnline(DevelopmentConfiguration.java:5207)
    at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:773)
    at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:698)
    at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:669)
    at com.sap.ide.eclipse.component.wizard.DevConfWizard.addDevConf(DevConfWizard.java:505)
    at com.sap.ide.eclipse.component.wizard.DevConfWizard.access$100(DevConfWizard.java:67)
    at com.sap.ide.eclipse.component.wizard.DevConfWizard$1.run(DevConfWizard.java:348)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at com.sap.ide.eclipse.component.wizard.DevConfWizard.performFinish(DevConfWizard.java:346)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
    at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
    at org.eclipse.jface.window.Window.open(Window.java:563)
    at com.sap.ide.eclipse.component.provider.actions.DevConfNewAction.run(DevConfNewAction.java:46)
    at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:229)
    at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
    at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1391)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
    at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    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.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
    at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
    at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    +++ Nested exception part 1/1
    com.tssap.dtr.client.lib.deltavlib.DeltavException: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
        at com.tssap.dtr.client.lib.deltavlib.impl.PersistentResourceFactoryImpl.createCollection(PersistentResourceFactoryImpl.java:233)
        at com.tssap.dtr.client.lib.deltavlib.impl.PersistentResourceFactoryImpl.createCollection(PersistentResourceFactoryImpl.java:79)
        at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.assureRemotePathExists(RepositoryServer.java:216)
        at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2748)
        ... 47 more

Hi There !
Run SDM RemoteGui.
Log in.
Go to deployment tab.
Find sap.comtcdtr~dbschema.sda in root directory under SDM.
Adjust deployment configuration to Update deployed SDAs/SCAs that have any version.
Complete the wizard.
this works !
rajendra

Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST

Hi ,
I am getting the below error:
Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.eligibilitymodel1.EligibilityModel1. The SSO ticket needed for authentication to WD_MODELDATA_DEST has expired. Close all applications and logon anew!
Regards
Anumit

Anumit,
when will you get this error?
if you are getting this while using adaptive rfc model follow this link Could not create JCOClientConnection for logical System:
if it doesnot work
try to reimport the certificate or restart the server
Thanks
Bala Duvvuri

Could not create JCOClientConnection for logical System:

Hi,
I am facing a wierd problem in using the JCO destinations.
I created a page where it is using some JCO destinations say SAP_R3_HumanResources.
when i open the page it is working for the first time .without closing the page if i open the same page again it is giving the following error
Error connecting using JCO.Client: null
Error connecting using JCO.Client: null
Pernr:Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.swissre.CustomData. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
Please let me know how to solve this issue
Thanks
Bala Duvvuri

Hi Bala,
It seems that this is a custom webdynpro application which when executed causes such problem. This might be due to JCO connection not released back to the pool.
Please refer to the following threads and that might be helpful.
Re: JCO Connection close
How to close a model object connection for Adaptive RFC?
You might have to call disconnectIfAlive method on your model.
Regards,
Jigar

Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA

Hi,
I am facing a big problem...I have created WebDynpro Application & when I am running that application from WebDynpro, it's showing the page but giving me the error message as:-
Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA - Model: class com.bcone.bcool.musa.model.MUSABAPI. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
What do I do? what connections I have to check?
pls help.

Hey if you are connecting to SAP system making use of adaptive RFC model you hav to create logical systems(JCOs).So while creating the model you have to specify 2 logical system names(one for model data or on for the meta data).If you have not created the JCOs or if the JCOs are not active then you are going to get this type of error.To activate those JCOs ask your administrator to activate the JCO for metadata of your application.If you are having proper credentials then log on to portal
System administration>webdynpro>expand the local directory>select your project>click on maintain JCOs and activate the JCO for the metadata.
Or else change the logical system in your application.

Could not create JCOClientConnection for logical System: SAP_R3_HumanResour

Hi,
For all the standard ESS (sap.com) the JCo connection used is SAP_R3_HumanResources .
All the applications are working fine.
I am trying to add a test Component in one of the (sap.com~eepro) for testing a standard BAPI call for getting user details.
I have used the same Model and the same SAP_R3_HumanResources destination name.
But i get the following error when i try to execute the standard BAPI_USER_GETDetails (non - HR).The other applications for standard components (Vc ) work when i run the application.
My question here is why a custom , local webdynpro when try to make a RFC call using the running already existing JCO connection throws such error.
How could this be solved.Note the connection is running and working fine for all the ESS webdynpros!!
Error:
Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.test.hr.model.Test. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
Your experience would be worthy enough.
Regards,
Swathi

Hi Swathi,
Here are some suggestions to trace down to the actual problem.
1) First check if all users are having this issue. (All other applications working and only one application giving problem)
2) If no, then take list of users having this problem and check their portal and SAP accounts
3) If yes, then concentrate on testing the JCo connections and the user account mapped in JCo settings
Possible things u can check is user's portal account (locked or not), SAP account (lock or validity), pernr mapped (validity), JCo user (check for lock), ping and test JCo connections
If none of them are issue, check the logs if there are any trace for this issue. I believe there must be certainly one. That can help u going further.
Regards,
Harini S

Can you play this url? (JMF error 'could not create player for')

Hello,
I can play this url in Windows Media Player
http://anon.vht.com.edgesuite.net/dl/deg18-062405-2425.wmv
However when I try to play it in JMStudio 2.1.1e, I get error "could not create player for deg18-062405-2425.wmv"
Any help appreciated,
thanks,
Anil

please login and vote for this bug to be fixed - 4 years old!!!
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4670412

ADF Faces: !-- ERROR: could not create stylesheet for oracle-desktop.xss

Hi,
I'm using ADF Faces EA6. Sometimes when I create the EAR, it doesn't include the file "oracle-desktop-ea6-ie-6-windows.css" which muest be present in the "adf/styles/cache" directory. If I check the source code from the browser, it starts like this:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html dir="ltr" lang="es-ES">
<head><title>Sistema de Seguridad</title><meta name="generator" content="Oracle ADF Faces"><script type="text/javascript" src="/fmv/adf/jsLibs/Commonea6.js"></script><script type="text/javascript">_defaultTZ()</script></head>
Please note the comment: 
Does somebody know the reason?
TIA,
Brian

If everything is set up properly the css will get generated if it doesn't exist. You do not have to be running in the IDE for the css to be correctly generated. Running the app first is generating the css before you deploy, so you've taken away the symptom but not solved the problem. If you try running on another browser, for example, you'll probably run into the same problem.
Does your ear get unzipped when you deploy? Do you have a writable file system for the css to get written to? There is a known issue with WebLogic where it doesn't expand the EAR.
Please check to see if there are errors in the logs.

Could not create remote for an EJB

Hello,
We have deployed an App on Sun One 7 that has web as well ejb modules integarted into it. The app deploys properly, However as soon as I try to call a servlet which in turn looks up an EJB (say ClientBean ) it gives me the followign error --->
"Could not create remote for Client Bean"
The entries in the xml files are as follows -
1) In ejb-jar.xml -
<session>
<ejb-name>EUClientBean</ejb-name>
<home>com..ejb.EUClientHomeIF</home>
<remote>com..ejb.EUClientRemoteIF</remote>
<ejb-class>com.ejb.EUClsClientBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<resource-ref>
<description>database ref</description>
<res-ref-name>test/db</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>
2) in sun-ejb-jar.xml --
<ejb>
<ejb-name>EUClientBean</ejb-name>
<jndi-name>ejb/EUClientBean</jndi-name>
<ejb-ref>
<resource-ref>
<res-ref-name>test/db</res-ref-name>
<jndi-name>jdbc/test/db</jndi-name></resource-ref>
<pass-by-reference>true</pass-by-reference>
<bean-pool>
<pool-idle-timeout-in-seconds>0</pool-idle-timeout-in-seconds></bean-pool>
</ejb>
3) In sun-web.xml -
<ejb-ref>
<ejb-ref-name>ejb/test/client</ejb-ref-name>
<jndi-name>ejb/EUClientBean</jndi-name>
</ejb-ref>
4) In web.xml --
<ejb-ref>
<ejb-ref-name>ejb/test/client</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.ejb.EUClientHomeIF</home>
<remote>com.ejb.EUClientRemoteIF</remote>
<ejb-link>EUClientBean</ejb-link>
</ejb-ref>
Actually the same app was working on IAS 6.5.
Any ideas what cud have gone wrong?

Hi Mandar,
Can you post the exception you're getting in your servlet code? Does it happen when the servlet is looking up the ejb or when it tries to create it?
Regards,
Ken

"Could not create JCOClientConnection for logical System" error

I get this error each day around 3 PM, like the JCO connections where never released...
What should be the JCO settings for this simple app, can someone help me understanding the way to configure JCO connections (or a pool) properly?
- 1 application (expirationTime 1 hour, logon using SSO ticket);
- Uses 4 RFC models : A (calls one R/O RFC function), B (calls one R/O RFC function), C (calls one R/O RFC function) & D (calls one R/O RFC function and one update RFC function);
- all the 4 models uses the same JCO destinations : WD_MODELDATA_R3_STANDARD and WD_RFC_METADATA_R3_STANDARD;
- users : 10 (who could possibly work in up to 4 windows);
Note that I've added these lines in the CC of the models, good idea or not?
- CC of Model B (before the RFC call) : reuse of the the ModelA connection using "Model1.setConnectionProvider(Model2)" command.
- CC of Model C (before the RFC call) : reuse of the the ModelA connection using "Model1.setConnectionProvider(Model2)" command.
- CC of Model D (after the RFC call of the update function) : "model.disconnectIfAlive();" command.
Thanks for your help!

Seems that the « Reuse connection » command is essential to assure that an application use ONLY ONE Jco. I get rid of the disconnectIfAlive.
Recommendation 1: Put all the BAPIs that you call in the same system into the same model!
Recommendation 2: If you canu2018t follow recommendation 1, make sure that the two models synchronize their (JCo) connections!
// two separate model instances are created ...
MyFirstModelTypemodelMyFirst= (MyFirstModelType) WDModelFactory.getModelInstance(
MyFirstModelType.class,
WDModelScopeType.APPLICATION_SCOPE);
MyOtherModelTypemodelMyOther= (MyOtherModelType) WDModelFactory.getModelInstance(
MyOtherModelType.class,
WDModelScopeType.APPLICATION_SCOPE);
// ... but the first model manages and provides the
// connection for the other model
modelMyOther.setConnectionProvider(modelMyFirst);
Edited by: Emanuel Champagne on Jun 27, 2008 2:38 PM

ERROR: could not create stylesheet for blaf.xss

I am suddenly getting this error when trying to run a jsp using the following tag in 9.0.3 :
<uix:styleSheet>
Any ideas as to why and how I can fix this problem?
-Teri

Teri,
Can you please post some of the source for the UIX-JSP? Are you defining the uix namespace?
Thanks,
Ryan

Could not create JCOClientConnection for logical Systems

Louis,
is there any jco connection with this name Z_GZD_YYGS_MODEL_DEST
Thanks
Bala Duvvuri

Hi,
Make sure that you have mentioned the New JCo destinations name in new WD Project JCo references
Tab.
And you are able to ping And Test the New JCo Dest in Webdynpro Content Admin
Siddharth

"Could not create SSOToken" error while setting agent for SSO

Hello,
I configured my agent as follows:
Version: 3.0
Build Date: 20071212
Application Server Config Directory : C:\Sun\SDK\domains\domain1\config
Application Server Instance name : server
Access Manager URL : http://juno:6140/opensso
Domain Administration Server Host is remote : false
Agent URL : http://juno:8080
Deployment URI for the Agent Application : /agentapp
Encryption Key : J+KQLOM+s6gAQb1Y1H8uJoej3bzKBAEN
Agent Profile name : asagent
Agent Profile Password file name : c:\temp\password.TXT
Agent installed on the DAS host for a remote instance : false
The AM and the sample applications are both running on separate domains.
Following steps I performed:
1. I started my SSO domain (domain2) first and then the application domain where my agent is installed (domain1).
2. I deployed the agentsample.ear file after compilation through build.xml file
When I try to access the URL (http://localhost:8080/agentsample/index.html), it throw the following exception (recorded in amSSO log file located in the Agent_001
12/14/2007 11:16:16:242 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
12/14/2007 11:16:16:242 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
could not create SSOTOken for token ID AQIC5wM2LY4SfcykqWPzOYlM/mkFg8E9ozYLBizVono/kDE=@AAJTSQACMDE=#
com.iplanet.dpro.session.SessionException: Service URL not found:session
     at com.iplanet.dpro.session.Session.refresh(Session.java:1133)
     at com.iplanet.dpro.session.Session.getSession(Session.java:808)
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:154)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
     at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
     at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
     at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.identity.common.PropertiesFinder.getProperty(PropertiesFinder.java:49)
     at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:255)
     at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:298)
     at com.iplanet.dpro.session.SessionID.<clinit>(SessionID.java:90)
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:153)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
     at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
     at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
     at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.identity.common.configuration.ConfigurationBase.isLegacy(ConfigurationBase.java:180)
     at com.sun.identity.common.configuration.ConfigurationObserver.createAttributeMapping(ConfigurationObserver.java:62)
     at com.sun.identity.common.configuration.ConfigurationObserver.<init>(ConfigurationObserver.java:58)
     at com.sun.identity.common.configuration.ConfigurationObserver.<clinit>(ConfigurationObserver.java:50)
     at com.sun.identity.common.DebugPropertiesObserver.<clinit>(DebugPropertiesObserver.java:44)
     at com.sun.identity.agents.arch.AgentConfiguration.bootStrapClientConfiguration(AgentConfiguration.java:587)
     at com.sun.identity.agents.arch.AgentConfiguration.initializeConfiguration(AgentConfiguration.java:1008)
     at com.sun.identity.agents.arch.AgentConfiguration.<clinit>(AgentConfiguration.java:1321)
     at com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:622)
     at com.sun.identity.agents.filter.AmAgentBaseFilter.initializeFilter(AmAgentBaseFilter.java:217)
     at com.sun.identity.agents.filter.AmAgentBaseFilter.getAmFilterInstance(AmAgentBaseFilter.java:279)
     at com.sun.identity.agents.filter.AmAgentBaseFilter.doFilter(AmAgentBaseFilter.java:64)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:270)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
     at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:361)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
12/14/2007 11:32:28:916 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
12/14/2007 11:32:28:916 AM EST: Thread[httpSSLWorkerThread-8080-0,10,Grizzly]
could not create SSOTOken for token ID AQIC5wM2LY4SfcyqQ1KVtRFCVm5y4qGBf7JcHCnC6du58xk=@AAJTSQACMDE=#
com.iplanet.dpro.session.SessionException: Service URL not found:session
     at com.iplanet.dpro.session.Session.refresh(Session.java:1133)
     at com.iplanet.dpro.session.Session.getSession(Session.java:808)
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:154)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
     at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
     at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
     at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.identity.common.PropertiesFinder.getProperty(PropertiesFinder.java:49)
     at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:255)
     at com.iplanet.am.util.SystemProperties.get(SystemProperties.java:298)
     at com.iplanet.dpro.session.SessionID.<clinit>(SessionID.java:90)
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:153)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:300)
     at com.sun.identity.authentication.AuthContext.getSSOToken(AuthContext.java:1105)
     at com.sun.identity.security.SystemAppTokenProvider.getAppSSOToken(SystemAppTokenProvider.java:87)
     at com.sun.identity.security.AdminTokenAction.run(AdminTokenAction.java:222)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.identity.common.configuration.ConfigurationBase.isLegacy(ConfigurationBase.java:180)
     at com.sun.identity.common.configuration.ConfigurationObserver.createAttributeMapping(ConfigurationObserver.java:62)
     at com.sun.identity.common.configuration.ConfigurationObserver.<init>(ConfigurationObserver.java:58)
     at com.sun.identity.common.configuration.ConfigurationObserver.<clinit>(ConfigurationObserver.java:50)
     at com.sun.identity.common.DebugPropertiesObserver.<clinit>(DebugPropertiesObserver.java:44)
     at com.sun.identity.agents.arch.AgentConfiguration.bootStrapClientConfiguration(AgentConfiguration.java:587)
     at com.sun.identity.agents.arch.AgentConfiguration.initializeConfiguration(AgentConfiguration.java:1008)
     at com.sun.identity.agents.arch.AgentConfiguration.<clinit>(AgentConfiguration.java:1321)
     at com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:622)
     at com.sun.identity.agents.filter.AmAgentBaseFilter.initializeFilter(AmAgentBaseFilter.java:217)
     at com.sun.identity.agents.filter.AmAgentBaseFilter.getAmFilterInstance(AmAgentBaseFilter.java:279)
     at com.sun.identity.agents.filter.AmAgentBaseFilter.doFilter(AmAgentBaseFilter.java:64)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:270)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
     at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
     at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:361)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
I spent lot of time refering the supporting document but could not find any solution.
Your assistance will be greatly appreciated.
Thanks,
Vinit

Seems that the « Reuse connection » command is essential to assure that an application use ONLY ONE Jco. I get rid of the disconnectIfAlive.
Recommendation 1: Put all the BAPIs that you call in the same system into the same model!
Recommendation 2: If you canu2018t follow recommendation 1, make sure that the two models synchronize their (JCo) connections!
// two separate model instances are created ...
MyFirstModelTypemodelMyFirst= (MyFirstModelType) WDModelFactory.getModelInstance(
MyFirstModelType.class,
WDModelScopeType.APPLICATION_SCOPE);
MyOtherModelTypemodelMyOther= (MyOtherModelType) WDModelFactory.getModelInstance(
MyOtherModelType.class,
WDModelScopeType.APPLICATION_SCOPE);
// ... but the first model manages and provides the
// connection for the other model
modelMyOther.setConnectionProvider(modelMyFirst);
Edited by: Emanuel Champagne on Jun 27, 2008 2:38 PM

Could not create JCOClientConnection

Hello,
I've created a WD application that use JCO connection.
I successfully run it from the web dynpro content administrator.
and the ping/test for the MODELDATA is successful.
but If I copy the app. url an paste it to different browser,
or if I try to run it from the developer studio, I'me getting a JCO connection problem with the following error:
Could not create JCOClientConnection for logical System: BI_MODELDATA - Model: class com.model.BIQuery. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
Any idea what might be the problem?
Thanks
Ami

Hi
After creating new JCO connections, try to test and ping it.
Metadata logical system name is used for Dictionary Objects(WD_RFC_METADATA_DEST)
and Model data(WD_MODELDATA_DEST) is for Application.
As you told that it works fine previously.
I think you have chosen wrong logical system names for model data and meta data while creating models. I mean logical system for application instances is used for meta data instances and vice versa.
Just confirm this thing.
Mandeep Virk

Could not create mountpoint for SC

Similar Messages

Maybe you are looking for