nLite error on startup

[OpeeTaylor]

I'm having troubles starting nLite. I downloaded the latest non-beta version and the latest beta version. Prior to installing, I had .Net 1.1, 2.0, and 3.0 installed. The install completed without error. I get an error every time I attempt to start it. It starts with: #Error: System.Reflection.TargetInvocationException...

I'm attaching the error...

I uninstalled, reinstalled 2 different versions of nLite. I uninstalled .Net 3.0, .Net2.0, reinstalled .Net 2.0, and reinstalled nLite. I still get the exact same error. Thank you in advance to anyone that may assist.

PS I see that someone had a very similar error. However, reinstalling the .Net Framework did not resolve my problem. I also tried installing the nLite runtime framework with no success...

OpeeTaylor

Edited July 5, 2007 by OpeeTaylor

[OpeeTaylor]

Searching posts and found solution... The local security policy, Security Option: 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing' was Enabled. I disabled it and nLite launches. I don't believe I will leave this setting off in the long term, but I can launch the software. Could this possibly be added to the list of improvements? I'm using the 1.4 beta version.

Thank you,

OpeeTaylor

[nuhi]

Never heard of this issue so why are you using this option and what can I do to help?

[OpeeTaylor]

See this article for the effects of enabling this feature in either a Local Security Policy or Group Policy: http://support.microsoft.com/kb/811833.

Another article on the topic: http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true

At the second article, here is a quote from that site: 'FIPS 140-1 validated software is required by the U.S. Government and requested by other prominent institutions.'

The feature basically enforces FIPS 140-1 compliance for hashing algorithms among other things. FIPS 140-1 Compliant, Transport Layer Security (TLS) 1.0 protocol, is stronger than Secure Socket Layer for encrypting communications. SSL3 uses the MD5 hashing algorithm (an algorithm that is not FIPS compliant), users whose local security policy forces the use of only FIPS compliant algorithms would experience the error.

Information about the FIPS 140-1 validation program can be obtained from the National Institute of Standards and Technology, Computer Systems Laboratory, Gaithersburg, MD 20899.

I've never encountered an error with any other program I've used since enabling the feature. The standard has been around for over a decade. Being as this is freeware, it may be a bit much to expect FIPS compliancy.

Thank you for your consideration.