Loading FSFengin

If i unload fsf engin and try and reload it i get module did not release 2
resources. If i wait awhile and try to load it again it sometimes works.
This happens all the time.
If i reboot the server this seems to happen also?
Any ideas???

  • We will look into it - What version of the engine are you running?

    NSM Development

    >>> On 2/22/2007 at 10:01 AM, in message

    <jfiDh.4471$rL6.2515@prv-forum2.provo.novell.com>, <tsefton@btboces.org>
    wrote:
    > If i unload fsf engin and try and reload it i get module did not release
    > 2
    > resources. If i wait awhile and try to load it again it sometimes works.
    > This happens all the time.
    > If i reboot the server this seems to happen also?
    > Any ideas???

  • I have the same error/problem using latest offical version of FSF (Oct.
    2006) I can´t load FSFEngin - not even after server restart and no matter
    how many times I try to load it.

    I also tried a clean install on a new server (NW65 SP5)without any luck.

    When i load the FSFengin.nlm through Remote Manager i get this:

    Novell Storage Manager Engine mainline start.
    FSFEVENT.NLM - Connection Manager is shut down.
    FSFEVENT.NLM - NCP Extension CCC_FSFactorySentinel Deregistered
    FSFEVENT.NLM - Logging Manager is shut down.
    FSFEVENT.NLM - Statistics Manager is shut down.

    I can´t find any information to get further in debugging.
    No problems in loading fsfevent -Sxxxx

    Martin Eilsøe

    "NSMDev" <storagemanager@novell.com> skrev i en meddelelse
    news:45DD7F83.862B.00A0.0@novell.com...
    > We will look into it - What version of the engine are you running?
    >
    > NSM Development
    >
    >>>> On 2/22/2007 at 10:01 AM, in message

    > <jfiDh.4471$rL6.2515@prv-forum2.provo.novell.com>, <tsefton@btboces.org>
    > wrote:
    >> If i unload fsf engin and try and reload it i get module did not release
    >> 2
    >> resources. If i wait awhile and try to load it again it sometimes works.
    >> This happens all the time.
    >> If i reboot the server this seems to happen also?
    >> Any ideas???