Anonymous_User Absent Member.
Absent Member.
3568 views

Failed communication with NSM engine

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.
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Failed communication with NSM engine

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.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Failed communication with NSM engine

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.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Failed communication with NSM engine

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.

>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Failed communication with NSM engine

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.

>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Failed communication with NSM engine

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.

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Failed communication with NSM engine

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.

>>

>



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.