Skip to Content
author's profile photo Stephen Spalding
0
Stephen Spalding

CM Repository problem

Posted on Oct 23, 2006 at 02:31 PM 10 Views

Hello all,

I have a CM repository set up with FSDB persistence mode. The files sit on a Windows server other than the portal server. The server that these files sit on had been shutdown over the weekend for some reason. When I came in this morning, the CM repository, of course, could not see the files. We have since brought up the server where the files sit, but KM still cannot see the files. In the KM monitoring log, I see the error:

Startup Error: folder '
10.0.32.191\PRDRepositoryEP6\san\Files' does not exist

What can I do to get the portal to see this again?

Thanks!

-Stephen Spalding

Web Developer

Graybar

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 23, 2006 at 02:50 PM
    1

    Hi Stephen,

    Did you restart the portal? If not, give it a try.

    When the repository is running again, please take quick check if the meta data (resource properties) is still there. The automatic synchronization mechanism should have been aware that the whole file system was absent and remain inactive, but better make sure.

    Best regards,

    Michael

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Boris Magocsi
    Boris Magocsi
    Posted on Oct 23, 2006 at 03:11 PM
    1

    Hi Stephen,

    it would be important to know what version of the portal you are working with.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Stephen Spalding
    Stephen Spalding
    Posted on Oct 23, 2006 at 03:07 PM
    0

    Hi Michael,

    Sorry, I should have mentioned this, but we're trying to avoid having to restart the portal servers themselves. We have over 4000 users logged in and don't want to disturb them right now.

    I'm wondering if anyone has any tricks to get this repository back with out restarting the portal.

    Thanks!

    -StephenS

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Stephen Spalding
    Stephen Spalding
    Posted on Oct 23, 2006 at 03:33 PM
    0

    My portal version info is:

    J2EE Engine 6.40 PatchLevel 100627.313

    Portal 6.0.15.0.0

    KnowledgeManagementCollaboration 6.0.15.0.0 (NW04 SPS15)

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Stephen Spalding
    Stephen Spalding
    Posted on Oct 23, 2006 at 06:40 PM
    0

    I solved the problem on my own...I was able to get the repository to come back without restarting the portals.

    What I did was create a new network path that had all of the same attributes as the network path used for the repository in question. I didn't have to tell the repository to use the new network path, the repository just started working after I created it. It's almost like the portal had to be reminded of where the repository's files were located.

    The reason why I remembered to try this is because I had encountered the same problem in our dev env last week and in the process of trying to create a new repository, I noticed that the old one started working after I created a new network path.

    Thanks to those who responded,

    respectfully,

    Stephen Spalding

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.