PR-BF2 update 1.1.1.0 critical error

[h58fhze]

reporting critical error

PR-BF2 trying to update from 1.1.0.0 to 1.1.1.0

os: win7 x64

best regards, hope this info helps!

an unhandled exception has occurred. details as follow:
exception has been thrown by the target of an invocation:

PRUpdater.log ...

Code: Select all

Project Reality Log File
PRUpdater.exe started at: 2014-01-04T19:12:57

Critical Error: An unhandled exception has occured. Details are as follows:

Exception has been thrown by the target of an invocation.

Further details can be found in the following file:

[url]C:\Program Files (x86)\EA GAMES\Project Reality - BF2\mods\pr\bin\PRUpdater.log[/url]

Please report this error to the Project Reality Team, and include the log file in your report.

[url=https://www.realitymod.com/forum/f27-pr-bf2-support]Visit Support Forum[/url]

 > System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
   at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
   at System.Security.Cryptography.MD5.Create(String algName)
   at Reality.Utils.Extensions.ToMD5(String s)
   at Reality.BF2.GameSpy.GameSpyConnection..()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

[h58fhze]

was able to resolve the issue! FIPS sounded somewhat familiar
go to to registry:
HKLM/system/currentcontrolset/control/Lsa/FipsAlgorithmPolicy
and change "Enabled" from 1 to 0.
after a restart the update process progressed flawlessly!
never encountered this issue before although FIPS was enabled for my WiFi connection
best regards...

[LITOralis.nMd]

Thanks for the update on resolution.

We'll look into this, but might be some time before we find someone willing to volunteer the expertise to make the PRLauncher encryption up to FIPS compliant.

[AncientMan]

PRLauncher uses MD5 for certain things for BF2 compatibility (algorithm is used for GameSpy and Punkbuster support, as well as CD Key hashing). MD5 is not a FIPS compliant algorithm.

However, I have modified some code in the launcher for the next version to not throw such an exception and allow you to play, but you probably shouldn't be playing PR (or any games for that matter) on a computer where FIPS compliancy is enforced (usually government computers)

[h58fhze]

Thanks for addressing the issue. Being an admin, I have FIPS enabled on all my home computers too, just for security reasons because... 'Windows 7 performs the AES encryption in software, rather than relying on the wireless network adapter'. Just a personal preference. Never encountered any issues with software installations before.