user2101801
user2101801

Reputation: 731

R6030 CRT Not initialized

We are facing an issue at the customer site; the Customer has built his application using VS2010 Runtime dated 19th Feb 2011 and version 10.0.40219.1 The customer’s app uses our dll, which is also built using the VS2010 Runtime but slightly older version.

We have an option in out installer where you can skip the installation of VC Runtime re-distributable, here the customer would have skipped as he already has the runtime installed.

The problem here is if the customer’s app starts first and then loads our DLL, then there is no issue. but in another scenario if the customer’s App loads only msvcr100.dll and does not load msvcp100.dll And then later when our dll is loaded , then we get an error “R6030 CRT Not initialized”

Is this because of runtime incompatibility issue, should the runtime and the application be compiled with exact same version ?

Upvotes: 3

Views: 9859

Answers (2)

june
june

Reputation: 1

I don't know the cause exactly, but I found that the R6030 runtime error can be resolved by changing Microsoft IME 2010 to Microsoft standard IME in some computer. It may be related to Microsoft office 2010. Also, please uncheck "image protect service" at windows - start - msconfig - service tab.

Refer the following screenshots. Sorry for that the language in the screenshots is Korean.

Microsoft IME change

Image Protect Service

Upvotes: 0

xMRi
xMRi

Reputation: 15355

Yes! I would recommend that you program is always delivered with the CRT you build with.

But I wonder about this. Internally the newer DLLs are binary compatible with the previous build. So because you build with the older version, the newer version "shouldn't" break you application.

I always avoid this problem in using a local installation for the VC Runtimes.

Upvotes: -1

Related Questions