Beta Not Working Now

[lennycutler]

I downloaded the update..installed...tried to follow the Mig-21 procedure....removed module...exit....restart....but I got this message.

 

"can't find MSVCP110.dll"

 

I did a repair...no help.

 

I uninstalled the beta....re-installed the beta...no help.

 

I copied a backup version of the beta...updated it..ran it...same error message.

 

My regular install of DCS works fine.

 

I suspect this message is related to Starforce implementation of the Mig-21.

 

In anycase...any ideas on what I need to do to get the Beta working?

[USSR_Rik]

PLease:

 

1. Attach logs:

Saved Games\DCS.openbeta\Logs\me.log

Saved Games\DCS.openbeta\Logs\dcs.log

<DCS World Open Beta>\autoupdate_log.txt

<DCS World Open Beta>\autoupdate_log_old.txt

 

2. After that update your runtime: http://www.microsoft.com/en-US/download/details.aspx?id=30679

Edited February 25, 2015 by USSR_Rik

[lennycutler]

Beta Won't Work

 

see attached

dcs.txt

me.txt

[USSR_Rik]

Thanks

 

and these:

 

<DCS World Open Beta>\autoupdate_log.txt

<DCS World Open Beta>\autoupdate_log_old.txt

[lennycutler]

I downloaded and installed the runtime packages from Microsoft for both 64 and 32 bit.

I only got it back working after the re-install of the 32 bit runtime version.

 

I ran the Beta..but Mig -21 was not working right...no cockpit etc.

Did a repair...now it seems to be working.

 

No clue why this happened...but I now realize that instead of deactivating the mig-21...I had hit the remove module button....don't know why that should have messed up the Beta.

 

Any thanks for the help...and if others run into this....a re-install of the Microsoft Runtimes can be the fix.

[Flagrum]

I downloaded and installed the runtime packages from Microsoft for both 64 and 32 bit.

I only got it back working after the re-install of the 32 bit runtime version.

 

I ran the Beta..but Mig -21 was not working right...no cockpit etc.

Did a repair...now it seems to be working.

 

No clue why this happened...but I now realize that instead of deactivating the mig-21...I had hit the remove module button....don't know why that should have messed up the Beta.

 

Any thanks for the help...and if others run into this....a re-install of the Microsoft Runtimes can be the fix.

I had troubles with the beta update as well - maybe it is related (see http://forums.eagle.ru/showpost.php?p=2328270&postcount=2)

 

The difference: when trying to start DCS, i got an error "Can not create process"

 

A DCS Repair did not help - although it stated that the runtimes would have been updated, the problem remains.

 

But something else is odd: I ran the update with a clean (freshly repaired - just in case!) installation. After encountering the issue above, I ran a DCS Repair. Although it did not fix that issue, it DID still re-installed the whole MiG-21bis package (460ish MB).

 

So, to be clear: the update seemed to require an immediate repair. Why? Seems that there is probably something more serious broken with the autoupdater?

[msalama]

the update seemed to require an immediate repair

 

Mine worked OK on the first try. Didn't have to reinstall or repair anything.

[Flagrum]

Mine worked OK on the first try. Didn't have to reinstall or repair anything.

If you have not tried it, then you would not know ... :o)

 

I have no idea if really something was wrong with the MiG-21 module after the update. But the autoupdater thought it were necessary to install it once more from scratch. Why did the autoupdater think that? Because either it was somehow ... "confused" (why? bug?) or the 1.2.15 update did indeed break something in the mig-21 module (then again: bug!?)

[wolle]

I downloaded the update..installed...tried to follow the Mig-21 procedure....removed module...exit....restart....but I got this message.

 

"can't find MSVCP110.dll"

 

I did a repair...no help.

 

I uninstalled the beta....re-installed the beta...no help.

 

I copied a backup version of the beta...updated it..ran it...same error message.

 

My regular install of DCS works fine.

 

I suspect this message is related to Starforce implementation of the Mig-21.

 

In anycase...any ideas on what I need to do to get the Beta working?

 

I have exactly the same problem! Anyone else have this?

[jcbak]

I'm getting the MSVCP110.dll missing error message as well. Did a repair to no avail.

[kazereal]

I'm getting the MSVCP110.dll missing error message as well. Did a repair to no avail.

 

As mentioned already, check runtime installations for both 32-bit and 64-bit versions.

[jcbak]

As mentioned already, check runtime installations for both 32-bit and 64-bit versions.

And that is done how? 1.2.14 is working fine. I ran a repair with MS Visual C++ but still no joy.

Edited February 25, 2015 by jcbak

[msalama]

If you have not tried it, then you would not know ... :o)

 

I SAID THE UPDATER UPDATED MY OB INSTALL CORRECTLY ON THE 1ST TRY, SO YES, I DEFINITELY DID TRY THE UPDATER

 

Clear now?

[wolle]

I SAID THE UPDATER UPDATED MY OB INSTALL CORRECTLY ON THE 1ST TRY, SO YES, I DEFINITELY DID TRY THE UPDATER

 

Clear now?

 

In my experience it is not the updater alone that does it. Mine updated fine, but once I went into the module magner and installed the Mig-15 module, then this error started to pop up. And if I understand the OP correctly, he could also update fine, it was only after he went into the module manager to reactivate the Mig-21 module that things went wrong.

[msalama]

Ah, right :D Well FWIW, my modules all work correctly as well.

[SkateZilla]

Regarding MSVCR110.dll

 

MSVCR110.dll is the Microsoft Visual C++ Redistributable dll that is needed for projects built with Visual Studio 2011. The dll letters spell this out.

MS = Microsoft, V = Visual, C = C++, R = Redistributable

For Winroy to get started, this file is probably needed.

This error appears when you wish to run a software which require the Microsoft Visual C++ Redistributable 2012. The redistributable can easily be downloaded on the Microsoft website as x86 or x64 edition. Depending on the software you wish to install you need to install either the 32 bit or the 64 bit version. Refer the following link:

http://www.microsoft.com/en-us/download/details.aspx?id=30679#

[lennycutler]

In my case the reinstalled ms 32 bit package solved it along with a repair of the beta...to..get mig 21 working

[jcbak]

Regarding MSVCR110.dll

I ran the MS Visual repair to no avail. Doesn't DCS 1.2.14 require that Dll? My 1.2.14 works fine.

[lennycutler]

It is puzzling,...since I also had no problem running the prior version 1.2.14..(the non beta version).

 

Perhaps someone from

ED will explain if this file from Microsoft is newly required?

[SkateZilla]

There was a runtime library update put out by MS within the last few weeks, Will check my update logs when I get home.

[Flagrum]

I SAID THE UPDATER UPDATED MY OB INSTALL CORRECTLY ON THE 1ST TRY, SO YES, I DEFINITELY DID TRY THE UPDATER

 

Clear now?

I meant the repair function. When everything seemed ok for you and you have therefore not tried to run a DCS Repair, then you can't know if the repair function would do something weired or not.

[Flagrum]

There was a runtime library update put out by MS within the last few weeks, Will check my update logs when I get home.

The question then would be, why doesn't the autoupdater update the runtimes then? Afaik that is always the last step when it is run.

[SkateZilla]

Everyone with the issue should be attaching logs (autoupdater.log) etc.

[HiJack]

I have the same problem on Windows Server 2012 R2 Standard edition! Missing msvcp110.dll but the file is where it should be.

 

No problems on my Windows 7 workstation.

[Kwiatek]

The same problem. I found that start launcher from BIN folder open the game.

autoupdate.cfg

autoupdate_log.txt