.Net Framework Error during Lenovo Power Manament Tools Deployment [ Edited ]

[Maik1987]

Hi I am deploying a cloned WinXP 32bit image on several client machines using Tivoli Provision Manager for OS Deployment .

Everytime I want to install the Lenovo Power Manager I got a strange .NetFramework application error.
The application (netframework) could not be started because the configuration is wrong (screenshot attached).

The Power Manager Tool is working correctly but I have to click the OK button to get rid of the .NetFramework error.
Strange thing is that the error is about .NetFramework 2.x, but I have already installed 4.x of .NetFramework.

Thanks for your answers:-)

http://img834.imageshack.us/img834/4523/powermanagementerror.jpg

Moderator edit: Converted pic >50k to link per the Community Rules.

[lenardg]

Did you install ONLY the 4.0 .NET Framework or did you install a previous version as well?

Unlike the three previous versions, the 4.0 Framework has a newer run time inside. Your error message refers to ngen, which is a core component. This would have been the same for .NET 2.0, 3.0 and 3.5, but would be different for 4.0.

Although these things should be compatible with each other, that is not always the case. You might want to try and install the latest 3.5 release - .NET Framework 3.5 SP1 - and see if the error goes away.

(Side note: .net runtimes in framework versions:

.net 1.0 / runtime 1.0

.net 1.1 / runtime 1.1

.net 2.0 / runtime 2.0

.net 3.0 / runtime 2.0

.net 3.5 / runtime 2.0

.net 4 / runtime 4

Actually 3.0 and 3.5 only added new class libraries to the .net framework and a new compiler for C# and VB.NET, but the core was the same. In effect, it was enough to install 3.5, and all 2.0, 3.0 and 3.5 applications would work, because they all relied on the same core. This changed when version 4 came out)

[napalm]

So which program is written in .NET? IBM's Tivoli agent or Power Manager?

Nap.

[lenardg]

Don't know about Tivoli, but parts of Power Manager are in .NET. Those parts being mainly the user interface. Other parts are native code, probably written in C++. Those other parts are some of the older dialogs (like battery charge threshold) and the code that interfaces with the hardware. 

BTW, given what I know about IBM, I would bet Tivoli is in Java

[napalm]

---

lenardg wrote:

Don't know about Tivoli, but parts of Power Manager are in .NET. Those parts being mainly the user interface. Other parts are native code, probably written in C++. Those other parts are some of the older dialogs (like battery charge threshold) and the code that interfaces with the hardware. 

BTW, given what I know about IBM, I would bet Tivoli is in Java

---

Interesting, I checked on Lenovo site and it lists .NET as a prerequisite for Power Manager for Windows XP but not for Windows 7.... And on my T510 in the control panel "add/remove program" I don't see any .NET mentioned, however I do have some directories in "Program Files (x86)" containing "Reference Assemblies" for .NET 3.0 and 3.5..... what gives.....

As for IBM - my first guess would be that's it's a Websphere based java application that needs at least half of your hard drive, all your memory and takes 99.99% of your CPU time just to trash a 100 GB pagefile. And oh I forgot to mention that the other half of the hard drive is needed for the DB2 backend. I'm looking forward to the moment when Larry Ellison will start collecting his java license and patent fees from them......

Nap.

[Maik1987]

Hi,

Thanks for your posts and ideas.

I have an update for you.

TPMfOSD is not based on Websphere or Java and it doesn't require JAVA.

It is definetely the Lenovo Power Manager Tool. I deployed the same image on a Fujitsu-Siemens Lifebook (without these ThinkVantage Tools) successfully. There were no errors.

The image contains all versions of .NETFramework from V2 up to 4 with German Language Packs.

So is it possible to have just .NETFramework Version 3.5 and 4 installed to use all the .NETFramework features?

[napalm]

We were just kidding about Websphere/java....

Now to the serious part - the document here (Power manager deployment guide):

http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/tpmmst.pdf

says that it needs .NET 3.0 or later.

There's also this note that I hope you didn't overlook:

Note: Power Manager has two different versions. One is for Windows XP
operating systems and the other is for Windows Vista and Windows 7 operating
systems. When you install Power Manager on your computer, match the Power
Manager version with your operating system. Power Manager designed specifically
for Windows Vista and Windows 7 operating systems might not function correctly
on Windows XP operating systems, and vice versa.

Nap.

[lenardg]

The reason it is not listed is probably because Windows Vista comes with .NET 3.0 and Windows 7 comes with .NET 3.5 SP1 already part of the system. So on those OS versions there is no need to install anything other than the application.

It is also the reason why you already have those files on your computer.

And yes, I have the same impression of IBM software ... I never met a user who was using IBM software and who would have praised them or even liked them. So why they are everywhere? Probably they have a pretty good marketing department :-)   (</joke>)

[lenardg]

Maik19871, If you install v3.5 of the .NET Framework, it will also include an installation of v2.0, v3.0 and v3.5 itself. So yes, it is enough to install the latest 3.5 SP1 version and V4 version, that should have you covered all the way as far as .NET applications go (except for v1.0 and v1.1, but I don't think those are needed nowadays anyway, except maybe in some rare cases).

As for the Power Manager problem, I would suggest the same as napalm said above, double check you downloaded and installed the correct version.

Also note, that NGEN.EXE - which gives the error in the initial message - is used to pregenerate native images on the computer the program is running. This saves start up time from the application, because the .NET Framework does not need to perform this step everytime (compile Intermediate Language code to native code). It is also the reason why your program will still work. 

Have you by any chance disabled the .NET code generation system services? They have names like "Microsoft .NET Framework NGEN ...". There are different services for the different frameworks (2.0 and 4.0) and for x86 and x64 (in case you run in 64 bit OS). In your case I am guessing you have 2 services, one for each of the framework versions.

I am not sure, but NGEN might depend on these services? You might want to play with the disabled/enabled/started/notstarted status of these services, to see if they have an effect on your situation. 

[napalm]

I'm looking foward for the moment when MS will decide to re-write Windows in .NET and NGEN will be implemented by BIOS manufacturers so Windows could start. Way to go, MS!

Nap.