Error in CM Repository with FSDB mode

[Former Member]

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.

[Former Member]

Hi,

Sometimes this error appear when you have not defined the network path.

Have you defined network path ?

System Administration->System Configuration->km->cm->Global Services.

Patricio.

[Former Member]

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

[Former Member]

Hi Vivek,

can you please verify the following:

With some tool change some test file in a test directory in your network file system (rename or content change). Now check (not via KM, but directly accessing the FS) that the modification date of the directory in fact did change!

This feature of the file system is essential for CM synchronization to work properly.

Best regards,

Michael

[Former Member]

Hi Micheal,

I tried changing the contents of the file directly from the file system. After doing that, the modification date in the file system has changed but not in KM.

The same thing would work had I pointed the CM repository to a directory on teh portal server.

Please help, I am really stuck with it.

Thanks you very much,

Vivek

[Former Member]

Hi Vivek,

please set your log level to debug on location com.sapportals.wcm.repository.manager.cm.persistence.fsdb.DBFSSynchronizer and check if there's anything suspicious in the log.

Maybe the status was cached in the CM store and it did not actually access the file system? Please clear the CM caches and access the resources again via KM (System Administration -> Monitoring -> Knowledge Management -> Cache Monitor)

regards,

Michael

[Former Member]

Hi Micheal,

I'll check this ane get back to you.

But the same reposiory manager works file when the file system is the Portal server and gives problems when the file system is on the network .

Any hints ?

Thanks,

Vivek

[Former Member]

Hi Deepa, I have a question. What's the environment for your portal and for the file server? Are they both Win2K? I have a similar problem but my Portal runs on UNIX and the file system on Windows2K.

Thanks.

[Former Member]

Hi Deepa,

The reasons are :

1.The error is that the portal server is able to access but not able to get in due to incorrect password or so while configuring the network path.

2. Check the path, folder name and name of shared folder

Regards,

venkat.