Contracts fail when going to VAB

[GraczNet]

KSP Version: 1.5.1

What Happens: When I accept contract for testing Flea or Hammer and I go to VAB the contract sometimes disappear and is marked as failed.

Mods / Add-Ons: All Stock, clean install

Steps to Replicate:

1) Accept contract for testing  Flea or Hammer

2) Go to VAB

Other Notes/Pictures/Log Files:

- Output.log: https://www.dropbox.com/s/56r2ghee4q76817/output_log.txt?dl=0

- Screenshot: https://imgur.com/a/YI66Oi0

Edited December 2, 2018 by GraczNet

[Gargamel]

I see no reason given for the contract failure, aside from what is listed in the screenshot.  I also see other contract failures listed before you enter the VAB, or re-enter as it seems it happened a few times. 

If this is a steam install, I'd try verifying your files, there might be something wonky there. 

To clean up the log, start up the game, accept the contract, and go to the VAB.  If it doesn't fail, try again.  If it does fail, upload that log without doing anything else in the game.   That will minimize the amount of stuff we have to sort through. 

 

[GraczNet]

 It always says that 2 files need to be reacquired, I don't know if this is normal. 

Log: https://www.dropbox.com/s/56r2ghee4q76817/output_log.txt?dl=0

Sorry but I needed to decline some contracts to get the right one but I hope it won't be hard for you to find something in that log.

Also, my game is crashing sometimes. Can someone tell me why?

Ksp.log: https://www.dropbox.com/s/wr6pkbh8vmfm0ze/KSP.log?dl=0

Crash log: https://www.dropbox.com/s/owhrujpnytb78d9/error.log?dl=0

Read from location 0000fffc caused an access violation. - What is this?!

Thank you for all your help.

[GraczNet]

Cleanest log I could get: https://www.dropbox.com/s/56r2ghee4q76817/output_log.txt?dl=0

[Vardyn]

Has anyone found a solution to this problem?  I've just run into it also with a new game started in 1.6.1.

[FlyingSpaceRhino]

I've found a solution to this problem, if you're on Steam.
1. Go the folder Kerbal Space Program folder in Steam/steamapps/common (this is the folder path in Windows, dunno about other OS's)
2. Delete every folder inside that folder, but not the folder itself.
3. Uninstall and reinstall the game (this is the way I did it, but verifying integrity of game files instead should also work).

[GraczNet]

Didn't solve it for me. It seems like developers messed up something when updating textures of these parts. KSP has a lot of bugs so I am not suprised. Just look at the bug tracker.

Edited April 1, 2019 by GraczNet

[Neilski]

[Responding to a fairly old thread again but it feels like the least bad thing to do in this case, because the problem is identical and clearly uncured.]

I've had this too.

The first occurrence (Flea) was a few weeks ago, and just after a complete reinstall when totally stock (thus v1.8). I didn't understand it and just ignored it.
Today another contract failed (Twitch) and I looked a bit harder. I now have KAC installed, but nothing else by way of mods.
My suspicion based on the sfs file contents is that the failures occurred because both contracts specified the original version of the parts, without the v2 suffix.
I don't really know why going to the VAB should trigger the failure of the contract, but perhaps it's because the old version is gone/deprecated...
Given that I had installed a completely fresh copy, this feels like it's a bug that can/will bite anyone, regardless of mods or the age of the installation.

Edit: I just got offered another Flea contract, which puts the problem beyond doubt for me. This one has the part "solidBooster.sm.v2", while the first one (which instafailed) had the part "solidBooster.sm". It appears that the part files (or the game logic?) don't switch off tests for hidden parts, so when those tests are then offered, they instafail for reasons I don't fully understand instead of merely being uncompletable.

Edited January 19, 2020 by Neilski
adding new info