Error creating .NET application build with Vault source control

I set up BuildMaster on my windows 10 box, everything work beautifully. I'm now trying to set BuildMaster on my windows server 2008 produciton box and i cannot get it to work.

When i create an application, i am able to successfully navigate my Vault repository and choose my .NET sln file, but when i hit NEXT i get:
Cannot connect to the service: Error in deserializing body of reply message for operation 'SendMessageWithResponse'. The maximum array length quota (16384) has been exceeded while reading XML data. This quota may be increased by changing the MaxArrayLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader.

If i choose a different (smaller) SLN file it works, only the large SLN file breaks but this large SLN works fine on my windows 10 machine (connected to the same production Vault).

Alot of googling says to edit the binding in web.config (related to wcf in general, not specifically buildmaster). but the web.config does not have any bindings defined, so i'm guessing they are build in code.

Product: BuildMaster
Version: 4.8.5

I was able to somewhat reproduce the issue with a test WCF message but I had to send 100K worth of data to put the service messenger in fault state. Note we do not use XML for the communication channel between the service and web app, so the message itself must be coming from Vault.

For now, you can enter the path directly into the "source path" text box without browsing it in the UI if there's too much data returned, that should at least get you going. We'll have to investigate a way to allow that max array quota value to increase. It's possible the WCF config settings will take effect if added to the web.config but I am not able to confirm that at this point.

the error was not occuring when trying to select project. Browsing worked perfectly, i was able to browse and choose my SLN file. the error occurred upon clicking "next".

All that aside, installing .NET 4.5 seems to have resolved the issue. 4.5 is not a requirement for vault or for BuildMaster, but seems to have changed something. I found an unrelated artical on google saying that they were getting a MaxArrayLength error, and that the error went away after installing .NET 4.5, so i figured it was worth a shot, and sure enough issue resolved!