kautium Absent Member.
Absent Member.
5389 views

Latest Windows updates broke our Storage manager 3!

After the latest Windows updates, our Storage manager 3 stopped working. Server was rebooted after updates were installed and since then NSM engine has been unable not start anymore.

Everytime we try to start engine, it stops right away and in Windows event logs it says "NSMEngine ServiceBody ServiceStart() - CRC32GenerateToken() returned 185".

NSM is the latest version and it is running on Windows 2008 R2. Engine has been updated from 2.5 to 3.0.0.0 and then on last week to 3.0.0.1.

I found one thread about the same kind of error message and it suggested to input clear <CRC32></CRC32> to NSMENGIN.CFG right before <HTTPSPORT> -line. I did that and then did "nsmengine.exe -forceproxyreset" from console, but that does not work here.

Engine inputs new CRC32-code to NSMENGIN.CFG and then stops and returns this error message:
- - - - - -
C:\Novell\Storage Manager\Engine>nsmengine.exe -forceproxyreset
Setting up NSM for AD: Windows Engine.
12/16 13:27:27 4: M101 Logging Subsystem active. Base debugging level=7.
12/16 13:27:27 0: SRSVerifyLicense: Unable to read license file (C:\Novell\Storage Manager\Engine\fr.lic).
01 2010-12-16 13:27:27 7200 2 8001 2832 2728 Failed to open the log file "C:\Novell\Storage Manager\Engine\LOGS\nsmengine-20100921-143221.log", RC = 54.
- - - - - -

Updates were installed last night and after that there has been several hundred delete operations performed in AD, so I'm hoping that at least the event monitor service has been awake so that events will eventually start to process when and if the engine is able to start again. Event monitor service is running, but i don't know if it is really working.

Any advice what to do?
0 Likes
9 Replies
kautium Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

Uninstalled all recently installed Windows updates --> didn't work.
Reinstalled the engine (repair) --> didn't work.

Btw. I Noticed that there are 2 Storage Manager Engine Services in Windows Service list. One is called "Novell Storage Manager Engine" and the other is "Novell Storage Manager 3 Engine". Both are set to start automatically, but only the one called "Novell Storage Manager Engine" is able to start. Is this right?
0 Likes
kautium Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

kautium;2057219 wrote:
I Noticed that there are 2 Storage Manager Engine Services in Windows Service list. One is called "Novell Storage Manager Engine" and the other is "Novell Storage Manager 3 Engine". Both are set to start automatically, but only the one called "Novell Storage Manager Engine" is able to start. Is this right?

Looks like both of these services are starting from different locations:
Novell Storage Manager Engine --> C:\Novell\Storage Manager\Engine\NSMEngine.exe
Novell Storage Manager 3 Engine --> C:\Program Files\Novell\Storage Manager\Engine\NSMEngine-AD.exe

NSM 3.0.0.1 was working just fine after it was updated (last week), so that is why I think that it was one of the recent Windows Updates that broke it, but at the moment I'm not so sure anymore.

More errors from application even log:
The description for Event ID 1 from source NSMEngine-AD cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

01 2010-12-16 14:12:42 7200 1 0001 2024 976 ML: Failed to initialize 1 or more components and/or subsystems. Engine is switching to stop-pending state.


Windows updates that was installed last night:
- Update for Windows Server 2008 R2 x64 Edition (KB2443685)
- Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (KB2416400)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2436673)
- Update for Internet Explorer 8 Compatibility View List for Windows Server 2008 R2 x64 Edition (KB2447568)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2296199)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2423089)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2305420)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2442962)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2385678)
- Windows Malicious Software Removal Tool x64 - December 2010 (KB890830)
- Update for Internet Explorer for Windows Server 2008 R2 x64 Edition (KB2467659)
0 Likes
kautium Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

I can't wait for help that may never even come, so I decided to remove all components, services and registy settings and then install them everything from scratch (and to lose about 1000 directory events at the same time). I was sure that this method eventually gets the job done and that after installation all services start ok --> but no, the NSM engine service just simply won't start.

At the moment I'm installing a whole new Win2008R2 server to see if I get that one to work any better. I'm going to install NSM v3.0.0.1 to it, so there won't be any previous versions to mix things up.

Something got pretty badly screwed up in the previous installation and it happened exactly at the same time as the server got rebooted after the automatic installation of recent Windows updates. I sure would like to know what happened and how it could have been prevented or at least fixed, even though it won't help us on this time.

I'm not a very happy camper with the Windows version of NSM at the moment... 😞
0 Likes
kautium Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

kautium;2057307 wrote:
At the moment I'm installing a whole new Win2008R2 server to see if I get that one to work any better. I'm going to install NSM v3.0.0.1 to it, so there won't be any previous versions to mix things up.

After clean install, everything is working again. I lost all events since last night, but I hope GSR will telee me what is missing.

There is only one engine service running now, so updating from earlier 2.5.x version left the one extra engine-service and it is possible that it was the main cause of all this. It is weird though that why didn't this happen before? This was not the first time server was rebooted after NSM updates.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

kautium,
Thanks for your posts.... I am force updating my lab machine with all
windows updates to try and figure out your issue. Please send an email
to storagemanager-at-novell.com so we can help you get running again.

thanks,
NSM Development

On 12/16/2010 8:36 AM, kautium wrote:
>
> kautium;2057219 Wrote:
>> I Noticed that there are 2 Storage Manager Engine Services in Windows
>> Service list. One is called "Novell Storage Manager Engine" and the
>> other is "Novell Storage Manager 3 Engine". Both are set to start
>> automatically, but only the one called "Novell Storage Manager Engine"
>> is able to start. Is this right?

> Looks like both of these services are starting from different
> locations:
> Novell Storage Manager Engine --> C:\Novell\Storage
> Manager\Engine\NSMEngine.exe
> Novell Storage Manager 3 Engine --> C:\Program Files\Novell\Storage
> Manager\Engine\NSMEngine-AD.exe
>
> NSM 3.0.0.1 was working just fine after it was updated (last week), so
> that is why I think that it was one of the recent Windows Updates that
> broke it, but at the moment I'm not so sure anymore.
>
> More errors from application even log:
>> The description for Event ID 1 from source NSMEngine-AD cannot be found.
>> Either the component that raises this event is not installed on your
>> local computer or the installation is corrupted. You can install or
>> repair the component on the local computer.
>>
>> If the event originated on another computer, the display information
>> had to be saved with the event.
>>
>> The following information was included with the event:
>>
>> *01 2010-12-16 14:12:42 7200 1 0001 2024 976 ML: Failed to initialize
>> 1 or more components and/or subsystems. Engine is switching to
>> stop-pending state.*

>
> Windows updates that was installed last night:
>> - Update for Windows Server 2008 R2 x64 Edition (KB2443685)
>> - Cumulative Security Update for Internet Explorer 8 for Windows Server
>> 2008 R2 x64 Edition (KB2416400)
>> - Security Update for Windows Server 2008 R2 x64 Edition (KB2436673)
>> - Update for Internet Explorer 8 Compatibility View List for Windows
>> Server 2008 R2 x64 Edition (KB2447568)
>> - Security Update for Windows Server 2008 R2 x64 Edition (KB2296199)
>> - Security Update for Windows Server 2008 R2 x64 Edition (KB2423089)
>> - Security Update for Windows Server 2008 R2 x64 Edition (KB2305420)
>> - Security Update for Windows Server 2008 R2 x64 Edition (KB2442962)
>> - Security Update for Windows Server 2008 R2 x64 Edition (KB2385678)
>> - Windows Malicious Software Removal Tool x64 - December 2010
>> (KB890830)
>> - Update for Internet Explorer for Windows Server 2008 R2 x64 Edition
>> (KB2467659)

>
>

0 Likes
Highlighted
kautium Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

Novell File Management Suite Team;2057469 wrote:
kautium,
Thanks for your posts.... I am force updating my lab machine with all
windows updates to try and figure out your issue. Please send an email
to storagemanager-at-novell.com so we can help you get running again.

As I said, I rebuilt a whole new server from scratch and everything is running again. I'm not sure anymore that Windows updates had anything to do with this situation, other than it was the cause of rebooting the server and after that, NSM services got somehow mixed and corrupted the system.

I bet the real reason is that the server had been upgraded from v2.5.x to 3.0.0.0 and then to 3.0.0.1. It had been rebooted earlier few times, but for some reason problems never occured until now.

Marko K.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

Marko,
I have not been able to reproduce the scenario. Please keep us posted as
we do want to solve any issues that come up.

thanks,
NSM Development

On 12/17/2010 4:06 AM, kautium wrote:
>
> Novell File Management Suite Team;2057469 Wrote:
>> kautium,
>> Thanks for your posts.... I am force updating my lab machine with all
>> windows updates to try and figure out your issue. Please send an email
>> to storagemanager-at-novell.com so we can help you get running again.

> As I said, I rebuilt a whole new server from scratch and everything is
> running again. I'm not sure anymore that Windows updates had anything to
> do with this situation, other than it was the cause of rebooting the
> server and after that, NSM services got somehow mixed and corrupted the
> system.
>
> I bet the real reason is that the server had been upgraded from v2.5.x
> to 3.0.0.0 and then to 3.0.0.1. It had been rebooted earlier few times,
> but for some reason problems never occured until now.
>
> Marko K.
>
>

0 Likes
kautium Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

Novell File Management Suite Team;2058603 wrote:
Marko,
I have not been able to reproduce the scenario. Please keep us posted as
we do want to solve any issues that come up.

thanks,
NSM Development

Like I said, we were in a hurry, so we had to install NSM server all over again from scratch, so we are not able to troubleshoot the old system anymore. Our new system is working basically like it is supposed to.

I bet there had been some sort of bug in install program or misconfiguration within server when we updated the old Storage Manager from 2.5.x to 3.0.0.0.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Latest Windows updates broke our Storage manager 3!

ok, thanks for the updates...

On 12/23/2010 3:06 AM, kautium wrote:
>
> Novell File Management Suite Team;2058603 Wrote:
>> Marko,
>> I have not been able to reproduce the scenario. Please keep us posted
>> as
>> we do want to solve any issues that come up.
>>
>> thanks,
>> NSM Development

> Like I said, we were in a hurry, so we had to install NSM server all
> over again from scratch, so we are not able to troubleshoot the old
> system anymore. Our new system is working basically like it is supposed
> to.
>
> I bet there had been some sort of bug in install program or
> misconfiguration within server when we updated the old Storage Manager
> from 2.5.x to 3.0.0.0.
>
>

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.