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 :-|

Similar Messages

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

Extremely slow startup/"Error loading kernel" when single user mode is run

My daughter's iMac has become very poorly responsive with a very slow startup time. It takes about 1 minute for the progress wheel to begin when I startup her machine. And then it takes another 2 1/2 to 3 minutes before the login screen appears. The computer runs very slowly with the spinning activity wheel occurring frequently. When I start it up in single user mode I get the following message on screen:
efiboot loaded from device: Acp:(PNP0A03,0)/PC: (1F12)/SATA(0,0)/HD(Part 2, Sig56BF F8F1-9ADB-4101-BD3C-BFBC38AEED26)
boot file path: \System\Library\CoreServices\boot.efi
.Loading Kernal cache file 'System\Library\Caches
com.apple.kext.caches\Startup\kernel cache_i386.AE149BE8'
Read error 0x7
Loading 'Mach Kernel'...
Could not open file 'Mach kernel'
Error loading kernel 'Mach_kernel' (0x9)
Could some one tell me what this means? And better still, what do I need to do to fix it?
Thanks.
JOhn

I can't picture what is doing this other than something missing or muxed, but perhaps it's time for a relatively painless Archive & Install, which gives you a new/old OS, but can preserve all your files, pics, music, settings, etc., as long as you have plenty of free disk space and no Disk corruption, and is relatively quick & painless...
http://docs.info.apple.com/article.html?artnum=107120
Just be sure to select Preserve Users & Settings.

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 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

Repository FSDB Startup Error - RID is too long

Hi all,
I've a problem with a FSDB repository.
We are going live in the next week. We mapped a repository of type FSDB. Everything was working fine, but we move from SP15 to SP16.
Now, the repository shows this error:
Startup Error: the RID /MyRepository is too long to be mapped to a file
Any help will be great!
Thanks,
Rami

Hi Robert
Thanks again for your promt reply, look I found this error in the log viewer...
startup failed : class=com.sapportals.wcm.repository.manager.cm.CmRepositoryManager, uri=crt://runtime/repository_managers/ZCMHOLE_SPEED, exception: com.sapportals.wcm.crt.component.StartupException: the RID /Speed is too long to be mapped to a file
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.initDB(CmRepositoryManager.java:929)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.makeNewRepository(CmRepositoryManager.java:853)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.startUpImpl(CmRepositoryManager.java:648)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.addComponent(CrtComponentManager.java:608)
     at com.sapportals.wcm.crt.CrtComponentManager.createComponents(CrtComponentManager.java:358)
     at com.sapportals.wcm.crt.CrtConfigurationEventListener.notifyComponentConfigAdded(CrtConfigurationEventListener.java:56)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.sendChangeEventOrRestart(CmConfigurationProvider.java:1201)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.configEvent(CmConfigurationProvider.java:277)
     at com.sapportals.config.event.ConfigEventService.dispatchEvent(ConfigEventService.java:227)
     at com.sapportals.config.event.ConfigEventService.configEvent(ConfigEventService.java:112)
     at com.sapportals.config.event.ConfigEventDispatcher.callConfigListeners(ConfigEventDispatcher.java:308)
     at com.sapportals.config.event.ConfigEventDispatcher.flushEvents(ConfigEventDispatcher.java:251)
     at com.sapportals.config.event.ConfigEventDispatcher.run(ConfigEventDispatcher.java:110)
com.sapportals.wcm.repository.UnassignableNameException: the RID /Speed is too long to be mapped to a file
     at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:399)
     at java.lang.Throwable.<init>(Throwable.java:195)
     at java.lang.Exception.<init>(Exception.java:41)
     at com.sapportals.wcm.WcmException.<init>(WcmException.java:59)
     at com.sapportals.wcm.util.content.ContentException.<init>(ContentException.java:38)
     at com.sapportals.wcm.repository.ResourceException.<init>(ResourceException.java:238)
     at com.sapportals.wcm.repository.UnassignableNameException.<init>(UnassignableNameException.java:34)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DefaultFileSystemWrapper.getChildren(DefaultFileSystemWrapper.java:493)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer.synchronize(DBFSSynchronizer.java:437)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer.synchronize(DBFSSynchronizer.java:84)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer.synchronize(DBFSSynchronizer.java:79)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.PersistenceFSDB.synchronize(PersistenceFSDB.java:136)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.initDB(CmRepositoryManager.java:920)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.makeNewRepository(CmRepositoryManager.java:853)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.startUpImpl(CmRepositoryManager.java:648)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.addComponent(CrtComponentManager.java:608)
     at com.sapportals.wcm.crt.CrtComponentManager.createComponents(CrtComponentManager.java:358)
     at com.sapportals.wcm.crt.CrtConfigurationEventListener.notifyComponentConfigAdded(CrtConfigurationEventListener.java:56)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.sendChangeEventOrRestart(CmConfigurationProvider.java:1201)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.configEvent(CmConfigurationProvider.java:277)
     at com.sapportals.config.event.ConfigEventService.dispatchEvent(ConfigEventService.java:227)
     at com.sapportals.config.event.ConfigEventService.configEvent(ConfigEventService.java:112)
     at com.sapportals.config.event.ConfigEventDispatcher.callConfigListeners(ConfigEventDispatcher.java:308)
     at com.sapportals.config.event.ConfigEventDispatcher.flushEvents(ConfigEventDispatcher.java:251)
     at com.sapportals.config.event.ConfigEventDispatcher.run(ConfigEventDispatcher.java:110)
startthe RID /Speed is too long to be mapped to a file - com.sapportals.wcm.repository.UnassignableNameException: the RID /Speed is too long to be mapped to a file
     at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:399)
     at java.lang.Throwable.<init>(Throwable.java:195)
     at java.lang.Exception.<init>(Exception.java:41)
     at com.sapportals.wcm.WcmException.<init>(WcmException.java:59)
     at com.sapportals.wcm.util.content.ContentException.<init>(ContentException.java:38)
     at com.sapportals.wcm.repository.ResourceException.<init>(ResourceException.java:238)
     at com.sapportals.wcm.repository.UnassignableNameException.<init>(UnassignableNameException.java:34)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DefaultFileSystemWrapper.getChildren(DefaultFileSystemWrapper.java:493)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer.synchronize(DBFSSynchronizer.java:437)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer.synchronize(DBFSSynchronizer.java:84)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer.synchronize(DBFSSynchronizer.java:79)
     at com.sapportals.wcm.repository.manager.cm.persistence.fsdb.PersistenceFSDB.synchronize(PersistenceFSDB.java:136)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.initDB(CmRepositoryManager.java:920)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.makeNewRepository(CmRepositoryManager.java:853)
     at com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.startUpImpl(CmRepositoryManager.java:648)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.addComponent(CrtComponentManager.java:608)
     at com.sapportals.wcm.crt.CrtComponentManager.createComponents(CrtComponentManager.java:358)
     at com.sapportals.wcm.crt.CrtConfigurationEventListener.notifyComponentConfigAdded(CrtConfigurationEventListener.java:56)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.sendChangeEventOrRestart(CmConfigurationProvider.java:1201)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.configEvent(CmConfigurationProvider.java:277)
     at com.sapportals.config.event.ConfigEventService.dispatchEvent(ConfigEventService.java:227)
     at com.sapportals.config.event.ConfigEventService.configEvent(ConfigEventService.java:112)
     at com.sapportals.config.event.ConfigEventDispatcher.callConfigListeners(ConfigEventDispatcher.java:308)
     at com.sapportals.config.event.ConfigEventDispatcher.flushEvents(ConfigEventDispatcher.java:251)
     at com.sapportals.config.event.ConfigEventDispatcher.run(ConfigEventDispatcher.java:110)
Any idea?
Thanks in advance...
Ra.-

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

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

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

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

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.

Document repository in fsdb/dbfs mode

Hi,
Has anyone implemented the document repository in fsdb / dbfs mode? I am looking at possiility of storing documents in different server from where KM is installed. TREX needs to be able to search the documents as well.
Please advise how the configuration would differ in this scenario.
Points definitely will be awarded to answers that guide me in the right direction.
Thanks and regards,
Arun

Hi Arun,
Here is the weblog we followed for implementing FSDB in our system (EP6.0 SP2):
Creating a CM Repository Manager - FSDB
We were also able to migrate existing documents from DB persistence mode to FSDB. The trick is to first download all the files via WebDAV to your storage folder, then point your FSDB repository to this folder. This way your existing properties won't get deleted during the transition. I still advise to do a full KM backup before this operation, unless you're starting from scratch.
Hope this helps,
Olivier

Config Error in CM Repository 'dbfs'

Dear All,
I am creating CM Repository in dbfs Mode....we are on EP 7.0 Unix OS and Repository is on Content Server 6.40 Win32 OS.
The Configuration for CM Repository is as mentioned Below:-
Description:KM Repository to Content Server FileSystem
Prefix (must start with /): /RepositoryCont
Active: Checked
Hide in Root Folder: Unchecked
Persistence Mode: dbfs
Repository ID in Database: RepositoryCont
Auto Check-In/Check-Out: Unchecked
Preserve Version Histories: Unchecked
Root Directory:
10.2.16.107\ZPORTAL_KM_FS\kmroot
Root Directory for Versions:
Repository Services:
accessstatistic
comment
discussion
feedback
layout
personalnote
properties
rating
statemngt
subscription
svc_acl
tbp
Property Search Manager:
com.sapportals.wcm.repository.manager.cm.CmPropertySearchManager
Security Manager: AclSecurityManager
ACL Manager Cache: ca_rsrc_acl
Windows Landscape System: ContentSrvrPath (NetWork Path)
Send Events: Checked
Memory Cache: ca_cm
Memory Cache for small content (<32KB):
Compress content greater than: -1
Internal Links Default To Dynamic: Checked
Filesystem Content Cache Directory:
Max Size of Filesystem Cache: 100 Megabytes
Maximum Number of Cache Files: -1
Disable Automatic FSDB Synchronization:
Enable FSDB Content Tracking: checked
Read-only Content Expiry Delay: 0 Seconds
Configuration of Network Path is Defined Below:-
Name "ContentSrvrPath"
jCIFS Protocol: Checked
Description:Remote Path to KM Content Server Repository
Network Path:
10.2.16.107\ZPORTAL_KM_FS
Password: Windows Content Server Password to access Directory
User: administrator
We are receiving error in Component Monitoring: Start Up Error
Configuration Error: creating content handler: Content
folder '
10.2.16.107\ZPORTAL_KM_FS\kmroot' does not exist.
We have already shared the defined repository on content server and
assigned full access to administrator.
Now, Our content Server is on Windows OS and Portal is on UNIX so, so,
may be portal server is unable to identify windows directory path...
so, kindly let me know the workaround ...is it required to mount
WIndows Content Server Repository on to Portal Server????
Reg,
Tushar Dave

Hi Dave,
There is a restriction here with dbfs mode which is not that clearly documented, see section 'E) Network Paths and the CM Repository' of note 900571, essentially the way DBFS repository is designed the Network path is not been taken into account.
Regards, Lorcan.

It make sense changing from DB persistence mode to DBFS (or FSDB)mode?

hi,
we are running on NW04 SPS17
KM 6.0.17.0.0
we have a portal with 30.000 (stimated) users access. CM is configured in cluster mode, with a unique DB.
In the KM area, we use a CM repository in DB mode, wich contains all the documents of the portal(2500-3500 documents,but will increase).Documents have small size (from 100k to 4 MB max) We have a lot of READ access on documents (99% of the users have "read only" permission).
With this scenario (as described in SAP how-to-guide), may be necessary to set the persistence mode on DBFS (or FSDB).
So, I would like to know:
1) it make sense, for INCREASE THE PERFORMANCE, to change the persistence mode from DB to DBFS (of FSDB) of the actual CM repository?
2)if affermative, what are the correct steps for making this change?
(in other therms:what happens to the documents properies -ACL, metadata, etc.- during the conversion? Data loss will occour?)
Thanks and regards,
Paolo

No, it doesn't make sense to make that change at all.
If there's a performance issue, the other persistence modes will make things worse, not better.
Instead, have a look at the various caches you can configure.

DMSRMRepositoryManager startup error

Greetings,
If you can please advise. I receive the following startup error with a DMSRMRepositoryManager.
"Startup Error: Failed to init sub-manager: Exception loading and instantiating sub-manager: com.sapportals.wcm.repository.manager.generic.security.AclSecurityManager (java.lang.NoSuchMethodException: com.sapportals.wcm.repository.manager.generic.security.AclSecurityManager.<init>(com.sap.netweaver.bc.rf.mi.IManager))"
Regards,
Keith

Dear
Please refer following threads
https://forums.sdn.sap.com/thread.jspa?messageID=8033144#8033144
and also look at
http://help.sap.com/saphelp_erp60_sp/helpdata/EN/42/d259f55d745043e10000000a1553f6/frameset.htm
Regards
Tushar Dave

Startup Error in CM repository in fsdb mode

Similar Messages

Maybe you are looking for