CM Repository manager in FSDB mode failed to start

Hi ,
I am creating a CM repository manager with persistent mode as FSDB.I have created a network path to access a remote server which will act as the file system repository.I am giving a user which has full control in that machine.
When I am checking in the component monitor the repository manager is failing to start and gives the following error message.
Startup Error:  Error occured while retrieving canonical name for folder '(java.io.IOException: Logon failure: unknown user name or bad password
Please help.
Regards
Nayeem

You might have a look at
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/92322ab24e11d5993800508b6b8b11/frameset.htm">this documentation</a>.
The CM repository in mode FSDB keeps the namespace structure of the repository in the database just as it does in the other modes. Any change is done parallel in the file system and in the internal database.
Since we have mode FSDB and the file system might change at any time by external processes, there is a component called synchronizer that checks with every lookup if the file system and the internal structure are still in sync. To determine this it looks at the modification date for folders and at modification date and size for plain files.
If any of these do not match then the synchronizer overwrites and modifies the internal data to reflect again the status of the external file system.
Now in your portal the synchronizer itself is working OK. That's because your repositories run fine locally.
With your remote file systems I can think of some possible explanations.
The caches might deliver responses after immediate file system changes. We ruled out this one already.
The synchronizer might not recognize the changes in the file system's meta data. This is why I'd like you to try and compare the behaviour of the file system repository, see above.
The synchonizer might run into some error when it tries to access the remote file system. This should be visible in the logs.
Michael

Similar Messages

  • CM Repository manager in FSDB mode

    Hi ,
    I am creating a CM repository manager with persistent mode as FSDB.I have created a network path and given a username which is having full control in the remote machine.
                                 But when I am checking in component monitor it is giving the folowing error and the repository manager fails to start.
    Startup Error:  Error occured while retrieving canonical name for folder '
    172.17.1.249\Portal_KM_Store\Data' (java.io.IOException: Logon failure: unknown user name or bad password
    Please help
    Regards
    Nayeem

    You might have a look at
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/92322ab24e11d5993800508b6b8b11/frameset.htm">this documentation</a>.
    The CM repository in mode FSDB keeps the namespace structure of the repository in the database just as it does in the other modes. Any change is done parallel in the file system and in the internal database.
    Since we have mode FSDB and the file system might change at any time by external processes, there is a component called synchronizer that checks with every lookup if the file system and the internal structure are still in sync. To determine this it looks at the modification date for folders and at modification date and size for plain files.
    If any of these do not match then the synchronizer overwrites and modifies the internal data to reflect again the status of the external file system.
    Now in your portal the synchronizer itself is working OK. That's because your repositories run fine locally.
    With your remote file systems I can think of some possible explanations.
    The caches might deliver responses after immediate file system changes. We ruled out this one already.
    The synchronizer might not recognize the changes in the file system's meta data. This is why I'd like you to try and compare the behaviour of the file system repository, see above.
    The synchonizer might run into some error when it tries to access the remote file system. This should be visible in the logs.
    Michael

  • Problem with CM repository manager in FSDB mode

    Hi all,
    I have configured a CM repository in FSDB mode.The file system which is configured in the CM repository manager is on a network and not on the Portal Server. The problem that I am facing is as follows -
    1. When i create the file manually in the file system , the file does not appear in the KM Content.
    2. When i create the file from KM, it's created in the file server and now the previously create files in 1, are also visible.
    3. When I delete the file from the fle server , I am still able to see the file name in KM content, but when I click on it it says resource not found.
    I tried everying from clearing the cache to having no cache entries, but nothing seems to work.
    Please help, I am really stuck with this.
    Will definitely reward points for helpfull answers.
    Thanks in advance,
    Vivek

    You might have a look at
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/92322ab24e11d5993800508b6b8b11/frameset.htm">this documentation</a>.
    The CM repository in mode FSDB keeps the namespace structure of the repository in the database just as it does in the other modes. Any change is done parallel in the file system and in the internal database.
    Since we have mode FSDB and the file system might change at any time by external processes, there is a component called synchronizer that checks with every lookup if the file system and the internal structure are still in sync. To determine this it looks at the modification date for folders and at modification date and size for plain files.
    If any of these do not match then the synchronizer overwrites and modifies the internal data to reflect again the status of the external file system.
    Now in your portal the synchronizer itself is working OK. That's because your repositories run fine locally.
    With your remote file systems I can think of some possible explanations.
    The caches might deliver responses after immediate file system changes. We ruled out this one already.
    The synchronizer might not recognize the changes in the file system's meta data. This is why I'd like you to try and compare the behaviour of the file system repository, see above.
    The synchonizer might run into some error when it tries to access the remote file system. This should be visible in the logs.
    Michael

  • CM Repository created in fsdb mode does not displaying in KM Content

    Dear KMC friends
    CM Repository created in fsdb mode does not displaying in KM Content.
    Any extra confiugration i need to do?
    plz reply me
    kantha

    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/284
    Message was edited by:
            Hadar Morchi

  • 2 services ( ms filtering management and exchange transport) failed to start!

     Hello ,
    I'm trying to install Exchange server 2013 in Win Server 2012 , all is fine and done but the probleme is with the activation of two services that one (Exchange transport) depend the second (filtering management) . I tried to resolve the problem, looked for
    a solution but nothing, so I need your help please, below are the errors:
    1-Exchange transport: error 1068:the dependency service or group failed to start ==> that is normal because filtering management is down
    2-filtering management: source: SCM event ID: 7023
    Thank you all,

    Hi Amir_Ali,
    Please refer to the following article, and then review the Event logs to check if you can find some related
    events that have been logged by the Service Control Manager (SCM) Eventlog Provider.
    Event ID 7023 — Service Stop Operations
    http://technet.microsoft.com/en-us/library/dd349413(v=WS.10).aspx
    Meanwhile, please run
    Server Health and Performance to check Exchange Server.
    Hope this helps.
    Best regards,
    Justin Gu

  • Cm repository manager (FSDB)  vs File System Repository

    Hi folks,
    I want to access the documents in a folder using portal and manage it using KM iviews. I was going through a list of repository managers avaialble and got confused with the cm repository manager in FSDB mode and File System repository manager. would like to know which one is suitable for my scenario and why.
    Please help me in this regard.
    Regards...

    Hi Yogi,
    the File System Repository Manager has following restriction: You can not use Predefined Properties, versioning, lock documents and create links.
    With the CM Repository in FSDB mode you could use metadata like locks and predefined properties, which would be then saved in the DB, but you have to make sure that you don't allow access on FS level (so without portal). Furthermore you can use resource properties like Description, Read-only, and Hidden which is not supported by the file system repository manager.
    Hope this helps,
    Robert

  • CM Repository Manager

    Hello,
    I tried to set up a CM Repository Manager in FSDB mode to connect to a file system. I went through the steps of this blog <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0449c90-0201-0010-7590-dd30845754ef">https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0449c90-0201-0010-7590-dd30845754ef</a> but I can't see in KM-Content my created repository. Any suggestions?
    Note: I don't want to use a file system repository!
    Best regards,
    Denis

    Hi Senthil,
    > Yes , after creating Repository you have to Restart
    > ur Server its necessary. You wont get any meaasge for
    > restart. Try this it will appear.
    That's not correct! When you first created a new repository with correct parameters, the repository framework will recognize it and show it under /root. Only if you change some parameters in the Repository Manager configuration you will need a restart to see the changes. The relevant parameters are marked with a special symbol. For example if you change the "Windows System Landscape" value, you would need a J2EE restart.
    Denis,
    >1. Repository ID in Database: I don't know what to type here.
    >Can I type anything I want?
    Yes (no special characters of course), but it's important that you use a unique name, as stated in the Weblog.
    >2. Windows Landscape System: In the blog there is mentioned, that I have to specify
    > the network path. As far as I know, File System Repositories have the same property.
    > But I have to enter my Windows System here, not the network path.
    The parameter is used if you want to integrate a file system and you want to use the permission from the file system in the portal. For that you have additionally to select W2kSecurityManager for the Security Manager parameter. In this parameter filed, you have to type the System ID, that you have defined in the [url=http://help.sap.com/saphelp_nw04/helpdata/en/c2/88e3d471640f43b3e81608b8c3b2e9/content.htm]Windows System Configuration[url].
    If you don't want to use the permissions from the file system, you should only need to specify the Root Directory for example like this: "//myserver/myshare/somedir".
    Hope this helps,
    Robert
    PS: Again, if you do now changes in the available Repository Manager configuration, you  need a restart. If you duplicate the configuration settings, and create a new repository (with different ID) you should see it without a restart!

  • Error in CM Repository with FSDB mode

    Hi All,
    My objective is to connect to an external file system using CM repository Manager.Heres what I have done:
    Created CM repository Manager with persistence mode FSDB
    Specified Network path for file server
    But in Component Monitor i am getting following error message:
    Startup Error:  folder '
    172.17.50.54\' has no canonical file
    Do let me know if you have encountered similar problem and/or have a solution.

    Hi all,
    I have successfully configured a CM repository manager which points to a file system on the network.
    My problem is that if i manually create a file in the file system, it does not appear in KM.
    If I create a file from KM , then it gets created in the network file server.
    I have also another repository manager which points to a file system on the Portal server itself, that's working perfectly fine.
    It's not working only when the file system is in the network.
    Can anyone please help me with this.
    PS - I read about the parameter "Disable Automatic FSDB Synchronization " in the CM repository, but its not present in tne CM repository manager configuration. I am in SP 14.
    Thanks in advance for the help,
    Regards,
    Vivek

  • Intel(r) Management Engine Interface fails to start

    HP G62 Notebook PC running 8 Gig of Memory and Windows 7 Professional 64 bit.
    Get message in Device Manager of this device failing to start.   with code 0000000A.  Have done Bios upgrade and checked for latest driver and the system tells me I have it already, yet this error still persists.

    Hi,
    It seems your machine has motherboard with Intel chips. And this problem occurs if you install a driver via Windows Update. You could try to upgrade the latest version driver from Intel, then this problem would be solved. Here is some information about Intel
    Management Engine:
    http://www.intel.com/en_US/Assets/PDF/general/ug_Intel_MEBX.pdf
    Notice: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this.
    “Also getting update failure on Microsoft SQL Server 2005 Service Pack 4 (KB2463332).”
    This is a Service Pack for SQL server. Since this is a SQL server related issue, I suggest you could post this problem to Microsoft SQL Server forum.
    http://social.technet.microsoft.com/Forums/en-US/category/sqlserver/
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
    William Tan
    TechNet Community Support

  • OBIEE 11.1.1.6 Scheduler Server fails to start

    When the server is rebooted we often have failures in start up of the scheduler server in bipublisher. It is always connect to a MBEAN failure. During operations when it does come up we see a lot of error messages about MBEAN errors as well. I would like to know why, and what, is causing the failures. When it was installed we did a standard install with basic configuration. Here is a listing of the error when it occurs. Sometimes it can be correct by restarting ALL the servers. Other times we have to reboot the server. It is a windows server.
    Message ID OBI-SYSMAN-1016
    Message Level 1
    Relationship ID 1:17002
    Component AdminServer
    Module oracle.bi.management.adminservices
    Host INF-BIP-PRD03
    Host IP Address 172.16.1.64
    User weblogic
    Thread ID Thread-97
    ECID 335286e7f84b3bef:7b38227c:141091813aa:-8000-000000000000014f
    Message MBean operation failed.
    Supplemental Detail oracle.bi.management.adminservices.model.ProcessManagementException: Failed to start J2EE BI component: AdminServer:bipublisher#11.1.1
    at oracle.bi.management.adminservices.deployment.JavaDeployments._startSingleDeployment(JavaDeployments.java:179)
    at oracle.bi.management.adminservices.deployment.JavaDeployments._startDeployments(JavaDeployments.java:148)
    at oracle.bi.management.adminservices.deployment.JavaDeployments.startAll(JavaDeployments.java:349)
    at oracle.bi.management.adminservices.deployment.JavaDeployments.startAll(JavaDeployments.java:322)
    at oracle.bi.management.adminservices.mbeans.impl.BIInstanceMBeanImpl.startJavaComponents(BIInstanceMBeanImpl.java:509)
    at oracle.bi.management.adminservices.mbeans.impl.BIInstanceMBeanImpl.localStart(BIInstanceMBeanImpl.java:296)
    at oracle.bi.management.adminservices.mbeans.impl.BIInstanceMBeanImpl.start(BIInstanceMBeanImpl.java:246)
    at oracle.bi.management.adminservices.mbeans.impl.BIInstanceMBeanImpl.start(BIInstanceMBeanImpl.java:284)
    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:597)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:1012)
    at oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java:104)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
    at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalInvoke(AbstractMBeanSecurityInterceptor.java:190)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
    at oracle.security.jps.ee.jmx.JpsJmxInterceptor$2.run(JpsJmxInterceptor.java:358)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
    at oracle.security.jps.ee.jmx.JpsJmxInterceptor.internalInvoke(JpsJmxInterceptor.java:374)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
    at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:103)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
    at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartInterceptor.internalInvoke(MBeanRestartInterceptor.java:116)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
    at oracle.as.jmx.framework.generic.spi.interceptors.LoggingMBeanInterceptor.internalInvoke(LoggingMBeanInterceptor.java:524)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.invoke(OracleStandardEmitterMBean.java:924)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:349)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:263)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
    at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
    at javax.management.remote.rmi.RMIConnectionImpl_1035_WLStub.invoke(Unknown Source)
    at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
    at weblogic.management.remote.wlx.ClientProvider$WLXMBeanServerConnectionWrapper.invoke(ClientProvider.java:291)
    at weblogic.management.remote.wlx.ClientProvider$WLXMBeanServerConnectionWrapper.invoke(ClientProvider.java:291)
    at oracle.sysman.emai.model.bi.impl.JmxUtil.invokeMethod(JmxUtil.java:184)
    at oracle.sysman.emai.model.bi.impl.InstanceMBeanHelper.start(InstanceMBeanHelper.java:126)
    at oracle.sysman.emai.model.bi.impl.InstanceModelAdaptor.restart(InstanceModelAdaptor.java:335)
    at oracle.sysman.emai.view.bi.SystemStartStopView.restart(SystemStartStopView.java:82)
    at oracle.sysman.emai.view.bi.AvailabilityView.restartAllComponents(AvailabilityView.java:359)
    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:597)
    at oracle.sysman.emas.sdk.progress.WorkWrapper.run(WorkWrapper.java:96)
    at java.lang.Thread.run(Thread.java:662)
    I would like some guidance if we need to reinstall OBIEE, reinstall the server, or another way to stop the problems.
    Thanks

    Hi,
    You can delete the BIPublisher deployment in the "Deployments"(in the weblogic admin console) and then you can create the new "BIPublisher" (not BIPublisher11.1.1) using the bipublisher .ear/.war files available in the ORACLE HOME directories.
    i believe this will work and you are not disturbing any setup here .its just like you are creating a new deployment
    let me know if this works
    Thanks
    Naga

  • Help needed to create fsdb mode CM Repository

    dear KMC friends,
    I am trying to create CM Repository of fsdb persistent mode.
    with the help of http://help.sap.com/saphelp_nw04/helpdata/en/62/468698a8e611d5993600508b6b8b11/frameset.htm
    Please find below parameters used to create the same.
    Name: kmpublications
    Description: KM Publications
    prefix: /kmpublications
    Repository ID in Database: kmpublications
    Root Directory: E:\KMPublications
    Root Directory for Versions: E:\KMPublications1
    Windows Landscape System:
    Active: true
    Auto Versioning:
    Hide in Root Folder:
    Internal Links Default to Dynamic:
    Preserve Version Histories:
    Send Events:
    Persistence Mode: fsdb
    Property Search Manager: com.sapportals.wcm.repository.manager.cm.CmPropertySearchManager
    Compress content greater than: -1 bytes
    Repository Services:
         <...many...>
    ACL Manager Cache: ca_rsrc_acl
    Cache: ca_cm
    Cache for small content (<32KB): Not Set
    Connection Pool : dbcon_wcmdb_cm
    Security Manager: W2kSecurityManager
    Problem is in Component Monitor this CM Repository status is RED, so it is clear that it is not created properly.
    But What is wrong in my parameters?
    Root directory folders are exists in the file system.
    is Windows Landscape System is compulsory?
    Please anybody help on this at the earliest.
    Thanx in advance
    Kantha

    Hi Kantha,
    I would suggest not to use E:\KMPublications and E:\KMPublications1 for Root/Versions Folder Parameter Entry in the Repository Manager but
    20.0.0.189\kmpublications and
    20.0.0.189\kmpublicationsversions
    <b>And try to access this share from the portal server using "net use t:
    20.0.0.189\kmpublshare\documents /persistent:no".
    If you get the error:
    Startup Error: folder '
    20.0.0.189\kmpublshare\Root' does not exist
    try again : "net use t:
    20.0.0.189\kmpublshare\Root' /persistent:no"</b>
    Hope this helps,
    Robert
    PS: Don't forget to restart the J2EE Engine after this changes to the CM Repository.
    Message was edited by: Robert Briese
    Message was edited by: Robert Briese

  • Have been lost, all the properties files in the CM repository (FSDB mode)

    Hi,
    I encountered the following problem: lost all descriptions to folders and files in the CM repository, which is connected to the FSDB mode. This happened as follows. At desired time connection to the server where the repository was broken, after some time the link was restored, but the repository was not available. After this portal has been restarted, and the repository to work, but lost all completed file properties, including the description.
    How do I return all the description files?

    Hi Stanislav,
    Has this issue been resolved?
    If not then the only way to restore this lost metadata would be a be restore, see sap notes 900571 and 737877 for more details.
    Regards,
    Lorcan.

  • Startup Error in CM repository in fsdb mode

    Hi all,
    I have configured CM repository in fsdb mode.I am getting the following error in the Component Monitor
    " Startup Error:  folder '
    <server name>\<shared folder>\Root' has no canonical file "
    Can anybody tell me what does this error mean?
    Thanks
    Pramod.

    Hi Pramod,
    did you solve this? I'm just struggling with the same problem, but there is no info to be found on SDN or anywhere else...
    Did you configure a netork path? Before I have done that, I got some message that the folder wouldn't exist.
    Best regards
    Detlev
    PS: Solved - some minutes later it just worked :-|

  • Problem in copyResource()-Repository Manager,ClassCastException

    Hi,
    I have written a read-write custom repository manager from the sample downloaded from sdn(A kind of extension of SimpleRepositoryManager).
    I tried to implement the ImutableNamespace opertion copyResource(IResourceHandle handle, ICopyDescriptor copy) with supported option COPY_DEEP and COPY.
    It really does a copy to the destination directory but after that it throws a ClassCastException
    for com.sap.netweaver.bc.rf.common.Rid;some how my feeling is its failing either in findResource or lookup after copy.
    For detail exception pls see below(from EP KM Iview-call stack)
    System Error
    An exception occurred during the program execution. Below you will find technical information pertaining to this exception that you might want to forward to your system administrator.
    Exception Class 
    Exception Message 
    Call Stack java.lang.ClassCastException: com.sap.netweaver.bc.rf.common.Rid
            at com.sapportals.wcm.repository.GeneralImpl2.internalCopyManager(GeneralImpl2.java:705)
            at com.sapportals.wcm.repository.ResourceImpl2.internalCopyManager(ResourceImpl2.java:246)
            at com.sapportals.wcm.repository.ResourceImpl.internalCopy(ResourceImpl.java:2130)
            at com.sapportals.wcm.repository.ResourceImpl.copy(ResourceImpl.java:1393)
            at com.sapportals.wcm.repository.ResourceImpl.copy(ResourceImpl.java:1376)
            at com.sapportals.wcm.rfadapter.CopyUtility.copy(CopyUtility.java:112)
            at com.sapportals.wcm.rendering.uicommand.cm.CopyUtil.massCopy(CopyUtil.java:65)
            at com.sapportals.wcm.rendering.uicommand.cm.CopyUtil.copy(CopyUtil.java:51)
            at com.sapportals.wcm.rendering.uicommand.cm.UIMassCopyCommand.execute(UIMassCopyCommand.java:105)
            at com.sapportals.wcm.rendering.uicommand.cm.UIMassEmbeddedSelectCommand.execute(UIMassEmbeddedSelectCommand.java:85)
            at com.sapportals.wcm.rendering.uicommand.cm.UIMassEmbeddedSelectCommand.execute(UIMassEmbeddedSelectCommand.java:64)
            at com.sapportals.wcm.rendering.control.cm.CommandDispatcher.onMassExecute(CommandDispatcher.java:45)
            at com.sapportals.wcm.rendering.control.cm.WdfProxy.onMassExecute(WdfProxy.java:2002)
            at java.lang.reflect.Method.invoke(Native Method)
            at com.sapportals.wdf.stack.Control.dispatchHtmlbEvent(Control.java:389)
            at com.sapportals.wdf.WdfEventDispatcher.dispatch(WdfEventDispatcher.java:175)
            at com.sapportals.wdf.WdfCompositeController.onWdfEvent(WdfCompositeController.java:549)
            at java.lang.reflect.Method.invoke(Native Method)
            at com.sapportals.htmlb.page.DynPage.doProcessCompositeEvent(DynPage.java:204)
            at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:142)
            at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:101)
            at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
            at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:23)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:81)
            at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:313)
            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:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:191)
            at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:217)
            at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:580)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:191)
            at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:670)
            at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:229)
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
            at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:832)
            at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:666)
            at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:313)
            at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
            at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
            at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
            at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
            at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
             Report Error
    I am using my own xercesImpl.jar ,xalan.jar api's.which exactly didn't cause me any problem for the delete,rename opertaions.
    Is it any thing to do with configuration ,which i am missing.Pls help
    rgds
    Shovan

    You might have a look at
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/92322ab24e11d5993800508b6b8b11/frameset.htm">this documentation</a>.
    The CM repository in mode FSDB keeps the namespace structure of the repository in the database just as it does in the other modes. Any change is done parallel in the file system and in the internal database.
    Since we have mode FSDB and the file system might change at any time by external processes, there is a component called synchronizer that checks with every lookup if the file system and the internal structure are still in sync. To determine this it looks at the modification date for folders and at modification date and size for plain files.
    If any of these do not match then the synchronizer overwrites and modifies the internal data to reflect again the status of the external file system.
    Now in your portal the synchronizer itself is working OK. That's because your repositories run fine locally.
    With your remote file systems I can think of some possible explanations.
    The caches might deliver responses after immediate file system changes. We ruled out this one already.
    The synchronizer might not recognize the changes in the file system's meta data. This is why I'd like you to try and compare the behaviour of the file system repository, see above.
    The synchonizer might run into some error when it tries to access the remote file system. This should be visible in the logs.
    Michael

  • DB type repository manager for information broadcasting?

    I read some article which says only FSDB type of repository manager can be used for BI informaiton broadcasting. I want to broadcast to MOSS server, which uses IIS, but stores everything in database. Is there anyway to use DB or WSDL type repository manager for broadcasting?
    Thanks
    Jane Zhou

    Where did you get this information from? Is there any document that states that? Below is the information I got, it says FSDB has to be used:
    Can I use information broadcasting to distribute precalculated queries, Web applications, and workbooks to a third-party file server, Web server or document management systems?
    Yes. With information broadcasting, you can precalculate queries, Web applications, and workbooks and publish them into the Knowledge Management of the SAP NetWeaver Portal.
    In KM, you can easily create a Repository Manager (CM repository with persistence mode FSDB) that is attached to a file system directory (for example, the directory of an Internet Information Server (IIS)). You have to create a link in the KM folder of documents to the folder of the CM Repository attached to the file system or you can define your CM Repository as an entry point in KM. For more information, see SAP Note 827994 (SMP login required).
    Information broadcasting can automatically put a new report on the third-party file server (for example, using the data change event in the process chain). KM offers repository managers for many different file servers, Web servers, and document management systems (such as IIS and Documentum):
    1.                            Create CM Repository attached to file system.
    2.                            Use iView KM Content to create subfolder in file system (optional).
    3.                            Set permission to Administrator (optional).
    4.                            Create link in /documents to folder of CM Repository attached to file system or define CM Repository as entry point. (See SAP Note 827994.)
    5.                            Schedule Broadcasting Settings that export to a linked folder of CM Repository.
    Because documents created via Information Broadcasting have additional attributes attached to them which mark them as broadcasted documents, it is not possible to store these kind of documents in a "pure" file system repository because such a repository usually only stores properties like "last changed", "creator", etc. Fortunately, KM provides a mechanism to nevertheless use a file system repository to store the documents. The additional properties will be stored in the database. Details are given here and here.
    The "persistence mode" of the repository must be "FSDB" to allow this kind of behavior. Please note that because of the distributed storage of file and additional properties, the property assignment will be lost when moving around the document in the file system using some non-KM tool like windows explorer.

Maybe you are looking for