Failed communication with NSM engine

[Anonymous_User]

I've downloaded NSM 2.0 and have received a 30-day trial license and
installed it on a test Active Directory server. When I login to NSAdmin, I
get..."Attempt to communicate with the NSM engine failed." When I
manually try to start the service, it reports back that it started and
stopped and that this may occur if the service has nothing to do.

[Anonymous_User]

Brett,

Is the NSMEngine service not starting up or the NSMSentinel service?

NSM Development

<brett.king@austinisd.org> wrote in message
news:gTZlg.5752$tN4.1665@prv-forum2.provo.novell.com...
> I've downloaded NSM 2.0 and have received a 30-day trial license and
> installed it on a test Active Directory server. When I login to NSAdmin,
> I
> get..."Attempt to communicate with the NSM engine failed." When I
> manually try to start the service, it reports back that it started and
> stopped and that this may occur if the service has nothing to do.

[Anonymous_User]

I am having the same problem on a NW 6.5 sp5a server, did you have any luck
resolving the provlem on your end?

> I've downloaded NSM 2.0 and have received a 30-day trial license and
> installed it on a test Active Directory server. When I login to NSAdmin, I
> get..."Attempt to communicate with the NSM engine failed." When I
> manually try to start the service, it reports back that it started and
> stopped and that this may occur if the service has nothing to do.

[Anonymous_User]

Brett,

When you requested your LICENSE.DAT did you put in the Forest Root Domain
name? There is a tool on the license request page that will help you find
out what your Forest Root Domain name is...if you need it.

Hope this helps,

NSM Development



"fsfdev" <fsfdev@novell.com> wrote in message
news:Pnimg.6666$tN4.5123@prv-forum2.provo.novell.com...
> Brett,
>
> Is the NSMEngine service not starting up or the NSMSentinel service?
>
> NSM Development
>
> <brett.king@austinisd.org> wrote in message
> news:gTZlg.5752$tN4.1665@prv-forum2.provo.novell.com...
>> I've downloaded NSM 2.0 and have received a 30-day trial license and
>> installed it on a test Active Directory server. When I login to NSAdmin,
>> I
>> get..."Attempt to communicate with the NSM engine failed." When I
>> manually try to start the service, it reports back that it started and
>> stopped and that this may occur if the service has nothing to do.
>
>

[Anonymous_User]

Jmccrea,

What error message are you receiving when you start the FSFEngin.nlm?

thanks,

NSM Development

<jmccrea@capitol-college.edu> wrote in message
news:L2zmg.7294$tN4.5946@prv-forum2.provo.novell.com...
>I am having the same problem on a NW 6.5 sp5a server, did you have any luck
> resolving the provlem on your end?
>
>> I've downloaded NSM 2.0 and have received a 30-day trial license and
>> installed it on a test Active Directory server. When I login to NSAdmin,
>> I
>> get..."Attempt to communicate with the NSM engine failed." When I
>> manually try to start the service, it reports back that it started and
>> stopped and that this may occur if the service has nothing to do.
>

[Anonymous_User]

Yes. When I applied for the trial license, I put "server1.test.org" in
the field for test root domain when I should have only put "test.org". It
only needed my root domain.

Hope that helps you.
Brett

> I am having the same problem on a NW 6.5 sp5a server, did you have any
luck
> resolving the provlem on your end?
>
> > I've downloaded NSM 2.0 and have received a 30-day trial license and
> > installed it on a test Active Directory server. When I login to
NSAdmin, I
> > get..."Attempt to communicate with the NSM engine failed." When I
> > manually try to start the service, it reports back that it started and
> > stopped and that this may occur if the service has nothing to do.
>

[Anonymous_User]

Brett,

Thanks for the update...

NSM Development
<brett.king@austinisd.org> wrote in message
news:gAdog.10473$tN4.8361@prv-forum2.provo.novell.com...
> Yes. When I applied for the trial license, I put "server1.test.org" in
> the field for test root domain when I should have only put "test.org". It
> only needed my root domain.
>
> Hope that helps you.
> Brett
>
>> I am having the same problem on a NW 6.5 sp5a server, did you have any
> luck
>> resolving the provlem on your end?
>>
>> > I've downloaded NSM 2.0 and have received a 30-day trial license and
>> > installed it on a test Active Directory server. When I login to
> NSAdmin, I
>> > get..."Attempt to communicate with the NSM engine failed." When I
>> > manually try to start the service, it reports back that it started and
>> > stopped and that this may occur if the service has nothing to do.
>>
>